Home · Platform · PSP and agent supervision

The agent laundering money on Tuesday takes scam deposits on Thursday

A platform designed for correspondent banking has never seen either, and cannot treat them as one problem if it sells AML and fraud separately.

What a generic engine misses

Same-agent round trip

SAME_AGENT_ROUND_TRIP

  • Funds leave and return through one agent inside a short window
  • Each leg beneath the reporting threshold
  • Invisible to any rule looking at single transactions

Cross-agent structuring

CROSS_AGENT_GEO_STRUCTURING

  • Structuring spread across agents and locations
  • No single agent trips a threshold
  • Only visible when the network is treated as one

Complaint clustering

AGENT_COMPLAINT_SPIKE

  • Cash-not-credited complaints concentrating on one agent
  • Frequently the first signal an agent has gone bad
  • Lives in the complaints system at most institutions, unread

Wallet behaviour

DORMANT_WALLET_REACTIVATION · NIGHT_TIME_VELOCITY

  • Long-dormant wallets moving quickly on reactivation
  • Activity outside the customer's established pattern
  • Velocity before a behavioural baseline exists

Thresholds that fit the network

Agent volumes differ by an order of magnitude between a city network and a rural cooperative. A micro-structuring rule tuned for one alerts on every ordinary customer of the other, so thresholds are configured per tenant rather than shipped as constants.

An agent suspended for laundering and an agent held for scam exposure are the same agent.

Next

See it with your rules, not our demo data

Tell us where you operate and what you sell, and we will show you the platform configured the way it would actually run for you.

What happens next

One of us reads it, not a queue. We come back inside two working days with a time — or a straight answer about whether we are the right fit.

So we can configure the demonstration before we speak.

We use this to reply to you and nothing else. No newsletter, no list.

FINANCIAL CRIME. UNIFIED.