Know the corridor before the money crosses.
Remittance fraud hides in the route money takes. Sieve checks the corridor of every transfer and scores it in your home currency.
For money transfer operators, IMTOs, cross-border payment apps and diaspora remittance services.
Four ways the money goes missing.
Each looks like ordinary activity. Sieve scores every event in context, before the money moves.
- 01
Embargoed countries
A transfer to Iran, North Korea, Cuba or Syria, in any currency.
Caught by Country under comprehensive sanctions
- 02
High-risk corridors
Money to a FATF-listed country, where enhanced due diligence applies.
Caught by High-risk country (FATF lists plus your own)
- 03
Sudden new corridors
A steady sender to Kampala suddenly wires USD 9,500 to a trading company in Dubai.
Caught by Large first transfer to a new country
- 04
Many senders, one receiver
Five senders each wire just under the reporting line to one account.
Caught by Cross-border layering pattern, payout account shared by several customers, structuring
Minutes of activity. One decision.
A story from the Remittance demo, run through the same engine as your events. Each reason is written for the analyst who acts on it.
- Three monthsUSD 150 to 300 a month to family in Uganda
- Day 0, 10:00USD 9,500 to a trading company in the UAENew country, above the limit
- Day 0, 13:00USD 4,000 to a company in Iran
- DecisionBlocked
- Money to Iran, which is under comprehensive sanctions
- FATF call for action
- First transfer to this country
The Iran transfer is blocked. The UAE transfer goes to review. Both are scored in KES at the day’s rate. A Nigerian workspace scores in naira.
Choose “Remittance” and these start enforcing.
Plain-English rules you can adjust, joined into fraud patterns. Everything else runs in Watch, scoring without acting, until you trust it.
- Country under comprehensive sanctions
- High-risk country
- Large first transfer to a new country
- Payout account shared by several customers
- Structuring
- Cross-border layering
- Money mule
- Structuring
Send these events. One endpoint.
transactionEach send in its own currency, with counterparty.country. That’s the corridor.customer.createdSenders with identity details, screened before their first transfer.
await sieve.events.create({ type: 'transaction', customer_id: 'snd_2044', direction: 'out', amount: 800, currency: 'USD', // converted for scoring; original kept method: 'bank', counterparty: { name: 'Grace Nakato', account: 'UG-STANBIC-00419', country: 'UG' }, })
What your regulator will ask, answered.
Sieve supports your obligations. It doesn’t replace your compliance team.
- FATF Recommendation 16 (wire transfers)
- Originator and beneficiary details travel with the event, stored encrypted.
- OFAC and UN sanctions
- Embargoed countries and listed people are blocked for review. Your compliance team decides.
- CBK remittance and CBN IMTO rules
- Corridor and threshold rules are sentences you can edit. Every change is versioned and logged.