Rules anyone can read
Plain-English rules. Test them on last month, then switch them on.
Flag any payout to an account added less than 24 hours ago.
Catch fraud before it happens.
Fraud prevention built for how Africa pays. Sieve checks every sign-up, login and payout, and stops fraud before the money leaves.
- 90%+ accurate
- <50 ms per decision
- KE · NG Kenya and Nigeria
One call. An answer in milliseconds.
Your app asks before money moves. Sieve answers with a decision and the reasons. Tap a step to see how.
{ "type": "payout.requested", "customer_id": "cus_1001", "amount": 48500, "currency": "KES", "method": "mpesa" }
4 earlier events · 2 devices · new payout account
{ "decision": "block", "fraud_probability": 0.94, "reasons": [ { "reason": "Phone and payout account changed 16 minutes after signup" }, { "reason": "Payout account added 5 minutes ago" }, { "reason": "Withdrawing 99% of the balance" } ], "patterns": [{ "name": "New-account cash-out" }], "latency_ms": 16 }
- Case opened
- Alert sent
- STR drafted
- Logged · hash-chained
Built for how Africa pays.
Most fraud tools were made for card payments. Here, money moves through mobile wallets, agents and instant payouts, and fraud can happen in under an hour.
Works with how your customers pay
Also PalmPay, paybills, tills, USSD, POS, agents, bank transfers and cash.
SIM-swap theft
SIM swapped, PIN reset, wallet emptied. All inside an hour.
Money mules
Many small deposits from strangers, then one fast cash-out.
Sleeping accounts
A quiet account wakes up on a new device and starts paying out.
Structuring
Deposits kept just under the reporting limit.
Crypto cash-outs
Cash in, USDT out to a brand-new wallet, within minutes.
Not your good customers
Festive sends, night shifts and travel stay approved.
Local in all ten countries.
Pick a country. Currency, phone format, payout rail and local time all follow it.
Kenyapayout.requested16 msHeldKES 48,500
- Customer
- +254 712 ••• 412
- Payout to
- M-Pesa •••• 8777
- Local time
- 09:21 in Nairobi
- Why
- SIM swapped 31 minutes ago. Payout account added 5 minutes ago.
- Next
- STR drafted for the FRC, due within 2 days
Watch a fraud get stopped
09:00:04
A new account opens.
One device, basic ID checks. Nothing looks wrong yet. Most fraud starts like this.
09:09:31
Nine minutes in, the phone changes.
From a new device. Sieve notes it: details changed right after signup.
09:16:02
The new number becomes the payout.
It is added as the M-Pesa payout account. A second warning sign.
09:21:40
Then it asks for 99% of the balance.
Sieve sees the whole story and holds the payout. The money never leaves.
09:21:40.016
Blocked in 16 ms. The money stays put.
Your app gets block and three plain reasons. Your team gets a written-up case.
cus_8841 · live · 09:00:04score 1 / 100
- 09:00:04customer.createdBasic KYC · device Aallow · 6
- 09:09:31customer.updated · phoneDetails changed 9 min after signupreview · 24
- 09:16:02customer.updated · payoutPayout account added from a new devicereview · 47
- 09:21:40payout.requestedReading the whole journey…evaluating
● BLOCKED16 ms · before settlement
Pattern: new-account cash-out
- Phone number and payout account changed within 16 minutes of signup
- Payout account added 5 minutes before the withdrawal
- Withdrawing 99% of the available balance
Stop fraud in the moment, not after.
Sieve decides before the money moves. Six tools, one view of each customer. See the platform →
No fresh start for fraudsters
Once fraud is confirmed, Sieve remembers its phones, devices and accounts.
Always-current screening
Sanctions and PEP checks that re-run whenever lists change.
CustomerAbdirahman J. Kassim
ListedCabdiraxmaan Juma Kassim
transliteration · word order · DOB year0%
Cases arrive written up
The AI gathers the evidence. Your analyst decides.
Find the gaps first
Scans your code for the payment bugs fraudsters look for.
router.post('/mpesa/callback', async (req, res) => {
const { Body } = req.body
const cb = Body.stkCallback
const amount = cb.CallbackMetadata.Item[0].Value
await wallets.credit(cb.AccountReference, amount)
res.json({ ResultCode: 0 })
})
Critical · the callback credits wallets without checking who sent it
One call before every payout
const d = await sieve.events.create({ type: 'payout.requested', customer_id, amount, }) if (d.decision === 'block') hold()Read the setup guide
Proof for your auditor
Every decision is logged in a chain that shows if anything was changed.
rule.updatedprev 61c8864f
hash 00000000
hash 00000000
case.closedprev 00000000
hash 9e3779b1
hash 9e3779b1
decision.labelledprev 9e3779b1
hash 3c6ef362
hash 3c6ef362
Simple, public pricing.
No surprises. See full pricing.
- SandboxFree
Try everything with test data.
- Growth$0.01 per decision
Plus $0.10 per screened customer a month.
- EnterpriseAnnual licence
Your own cloud or servers, with guaranteed support.
100,000 decisions + 5,000 screened customers = $1,500 a month.
Questions, answered.
Something else? Talk to our team.
How accurate is Sieve?
94.5% on our benchmark of 515 test cases, and above 90% for every business type. On your own traffic, Watch mode shows the results before anything is blocked.
How long does it take to set up?
Most teams send their first live event the same day. It is one API call before each sign-up, login and payout.
Will it block good customers?
Not without you seeing it first. Test any rule on the last 30 days before you switch it on.
Do you support Nigeria and Kenya?
Yes. Amounts, phone formats and regulator reports follow your country.
Can a bank run it on its own servers?
Yes, fully inside your network, with a local AI model and no outside connections.
Does the AI decide on its own?
No. It writes up cases and recommends. A person makes every final call.
Who uses Sieve today?
Lipana, a payments product from our founder, is our first customer.