Use case · Money mule detection · $0.03 per payment assessed
Money mule detection
Money in.Money out.Minutes apart.
Stolen money does not stay where it lands. It moves through mule accounts, in and straight out again, until it cannot be traced. Toden scores every payment as it happens and flags the accounts that receive from many people and pay out at once.
The workflow
Score each payment for the patterns a mule account leaves, and stop the next one before it leaves. This is a starting point: add, remove or reorder any step in the workflow builder.
Step 01
$0.02Transaction assessment
Scores the payment against the account's history
Step 02
$0.01Account activity assessment
Scores the logins and changes around it
Step 03
IncludedDecision rules
Allow, review or block on your rules
Then your rules decide
A starting rule set
- The payment fits the account's usual patternApprove
- Money arrives and leaves within minutesReview
- Many different people pay into one new accountReview
- The recipient is on your blocked listDecline
Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.
Try the workflow builderWhat it costs
Added up from the published rate card as this page loaded. It is what one production run of the workflow above deducts from your credit.
$0.03per payment assessed
- Transaction assessment$0.02
- Account activity assessment$0.01
Connection map
When a face, a phone or an address turns up again, the console draws everyone gathered around it and says in plain words what the connection means and how much weight it deserves.
- Supporting evidence4 people used the same phoneFamilies, agents and business centres share devices. Review the other evidence before deciding.
- Needs review2 of them verified with the same phone numberTwo independent details connect the same people, which deserves a closer look than either alone.
- An illustration with invented people. In the console each card opens the customer's record.
How it works
Send each payment as it happens
One API call per transaction, with the amount, the direction and the counterparty.
Toden scores it against the account's history
It looks for money that arrives and leaves at once, many senders, and a quiet account that wakes up.
Your team gets one alert per pattern
Repeat hits roll into one alert, ready to open as a case.
What powers it
The answer comes back on the same call, in time to hold the payment.
Integrate
Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.
import { TodenVerification } from "@todenhq/sdk-react"; export function Verify({ userId }) { return ( <TodenVerification apiKey="pk_test_..." workflowId="wf_AbC123dEf456" userId={userId} onSubmit={(s) => save(s.verificationId)} /> );}{ "event": "verification.completed", "data": { "verificationId": "ver_8fk2...", "status": "verified", "assuranceLevel": "gov_db", "idType": "bvn", "country": "NG", "dataMatch": true, "facialMatch": true, "facialConfidence": 91 }}Products involved
This solution combines products you can use on their own too.
Related use cases
Coverage
Pick a country to see the IDs you can verify there, which documents carry a chip we read, and whether business checks are available.
Frequently asked
Send the ones you want scored. Most teams send all payments and the logins around them.
Money mule detection,in one workflow.
The sandbox opens when you sign up. Usage-based pricing, no sales call.