01Implemented, shown in the synthetic demo
Mule networks
Accounts that collect from strangers, keep almost nothing and pass it on.
Solutions
Fraud patterns that live in connections
Ten patterns, one engine. Each carries its maturity in the current release, taken from the engine’s own status documents. Nothing here has been validated on customer data yet.
All use cases
Read
02Implemented, shown in the synthetic demo
Recipient risk
Score the account being paid, not only the account paying.
03Implemented, shown in the synthetic demo
Authorised payment scams
The genuine customer is acting. The payment is still the fraud.
04Partial
Account takeover
Signals that the account is no longer in its owner's hands.
05Implemented, shown in the synthetic demo
Compromised payment integrations
An API credential that stops behaving like itself.
06Implemented, shown in the synthetic demo
Insider and privileged control anomalies
Privileged actions outside their established pattern.
07Implemented, shown in the synthetic demo
Agent fraud
Cash-out points that behave unlike their cohort.
08Planned — not built
Merchant abuse
Merchant-side collusion and abuse.
09Partial
Cross-rail fraud movement
Following value as it changes rail.
10Implemented, shown in the synthetic demo
Rapid dispersal and cash-out
One source, many new recipients, minutes.
One layer
The same intelligence layer sees all of them
- Bankcore ledger
- PSPacquiring · payouts
- Mobile moneywallets · agents
- TelecomSIM · device
- API clientpartner integrations
- Merchantcheckout · refunds
- Insiderprivileged actions
- Confirmed caseslabels · signals
Cenvoriq intelligence layerSentinel Engine · IntegrationGuard · TrustGraph · ControlGraph
- Risk dimensions
- Reason codes
- Graph signals
- Integration status
- Recipient intelligence
- Evidence record
- Recommendation