Skip to content
Try one-tap loginBook a demo

Fraud prevention for payment apps and aggregators

Your rails move money in seconds, and scam money with it. Mule wallets, shell merchants, remittance rings and agent payments each look ordinary one transaction at a time.

Book a demoRequest a retrospective
Journey most at risk
Wallet or merchant onboarding, then the payout
The decisionS-4580

Hold

HOLD · face reused · device shared · settlement mule-linked · payout account shared
Your customer sees
Settlement paused. We’re checking something on your account. You don’t need to do anything now. If we need more from you, we’ll ask in your dashboard.
Your FRM receives
FACE_REUSEDSHARED_DEVICEPAYEE_MULE_LINKEDACCOUNT_SHARED
Stopped or heldIllustrative
The decision on the journey most at risk here, from the merchant laundering use case. Real codes are agreed in the sandbox.

What payment firms face now.

Across the customer journey.

Where each attack appears for payment firms, what DeepID reads at that moment and the action it returns. Each moment is checked against what the one before it bound.

MomentThe attackWhat DeepID doesDecision
Wallet sign-upMule wallets opened in bulkEmulators and device farms, and one face behind many wallets, read at the start.Block
Merchant onboardingShell merchants and laundering ringsBusiness and bank account verification, the director’s face searched across merchants, and shared devices and settlement accounts on the graph.Step up, or hold
Settlement and payoutsScam money moving through collection accountsSettlement held when the settlement account or the payers link to a mule ring.Hold
RemittanceMule senders and receivers on a corridorThe face behind the sender ID and the receiver paid by unrelated senders, decided together before payout.Hold or block
Agent channelsRogue agents and absent customersThe customer confirms a high-risk assisted action on her own bound phone; the agent device is read like any other.Step up

Where to start.

The journey most at risk: wallet or merchant onboarding, then the payout. Start at wallet or merchant onboarding, where the face, the business and the settlement account are verified and the device is bound, so that each payout can be checked against it.

  1. 1Sign-upThe face, the device and the bank account, verified and bound.
  2. 2PaymentOne decision before the money leaves, with its reasons in your FRM.
  3. 3Merchant launderingThe shell merchant ring, and the hold before settlement.
  4. 4Remittance mulesSender and receiver, decided together.
  5. 5Mule account detectionWallets that receive from many unrelated senders.

Your free first analysis.

A free retrospective on 30 to 90 days of wallet openings, merchant applications and payouts.

What it shows. The wallets and merchants linked by a face, a device or a settlement account, and the value that passed through them before each was offboarded. No figure is published for this; you count it on your own data, against what you see today.

How the retrospective works

Use cases for payment firms.

Each shows how the attack unfolds, what your checks saw at each step, what DeepID read and the decision it returned.

All 15 use cases

  • Digital arrest

    Hold the coerced payment before it leaves the account.Hold, then call back

  • Mule accounts

    Catch mule accounts before the money moves.Cool off, then hold

  • Assisted channels

    Prove the customer is there, on her own phone, before an assisted action.Step up, or hold

  • Video KYC deepfakes

    A live person, in front of a real camera, on every video KYC call.Step up, hold or block

  • Account takeover

    Protect the account through recovery and the hours after.Step up, then cool off

  • Merchant laundering

    Hold the payout and find the whole merchant ring.Hold

  • Investment scams

    Slow the scam payment and hold the mule trading account.Warn, then cool off

  • Remittance mules

    Read the sender and the receiver before the transfer leaves.Hold or block

  • AI agents

    Tell the customer’s own assistant from automation that only looks like one.Allow, or step up

  • Vulnerable customers

    Extra time, and a call back, for the customers most at risk.Cool off, then hold

  • Insider fraud

    Hold the takeover that starts with a contact change made from the inside.Step up, then hold

Rules that apply.

India first. Each rule is dated and sourced on its market page, and the rule map covers the six other markets.

India’s rules

The rule map, by market

DeepID supports compliance with these rules. It never claims to guarantee it.

The modules these use cases read with.

Open a module to see what it reads and the reasons it sends with each decision.

How the platform decides

See DeepID on a real phone.

We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.

Book a demoTry one-tap login