Skip to content
Book a demo
Use cases · USDC & USDT payment rails

Check the wallet before the dollars move.

A stablecoin payout can’t be pulled back. Sieve checks the wallet, corridor and Travel Rule record before you send. Limits apply in one currency, whatever the coin.

Book a demoCrypto & cross-border

For b2B payment companies, treasury and payout platforms settling in USDC or USDT.

How it hits

Four ways the money goes missing.

Each looks like ordinary activity. Sieve scores every event in context, before the money moves.

  1. 01

    Sanctioned wallets

    A “supplier” wallet that turns out to be on the OFAC list.

    Caught by Sanctioned crypto wallet, blocked on any transfer

  2. 02

    Embargoed corridors

    USDT sent on Tron to a counterparty in Iran.

    Caught by Country under comprehensive sanctions, high-risk country

  3. 03

    Travel Rule gaps

    A USD 40,000 payout with no originator or beneficiary details.

    Caught by Travel Rule information missing

  4. 04

    Cross-border layering

    A new business receives USD 30,000 and spreads it across three countries in two hours.

    Caught by Cross-border layering, cash in crypto straight out, money spread across many countries

A catch, step by step

Minutes of activity. One decision.

A story from the Stablecoin cross-border payments demo, run through the same engine as your events. Each reason is written for the analyst who acts on it.

A supplier payment to a sanctioned walletreplayed through the engine
  1. Day −3USD 25,000 received from the business’s bank account
  2. Day −2USDC 24,500 payout to “Global Logistics FZE”, Travel Rule completeWallet checked against the lists
  3. DecisionBlocked
    • Wallet is listed on OFAC SDN (LAZARUS GROUP, DPRK3)
    • Payout wallet is brand new

Blocked, however complete the paperwork: the wallet is on the OFAC list. The case records the list entry and the sanctions programme.

What Sieve does

Choose “Stablecoin cross-border payments” 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.

Rules
  • Sanctioned crypto wallet
  • Country under comprehensive sanctions
  • High-risk country
  • Travel Rule information missing
  • Wallet address doesn’t fit the network
  • Cash in, crypto straight out
  • Large first transfer to a new country
Patterns
  • Crypto cash-out
  • Cross-border layering
Integrate

Send these events. One endpoint.

  • transactionEach payment in, with amount, currency and the counterparty’s country.
  • payout.requestedOn-chain payouts: a crypto_wallet destination with network and country, the asset, and travel_rule.
POST /v1/events
await sieve.events.create({
  type: 'payout.requested',
  customer_id: 'biz_7004',
  amount: 9800, currency: 'USD',
  method: 'crypto',
  asset: { code: 'USDC', amount: 9800, network: 'polygon' },
  destination: { type: 'crypto_wallet', account: '0x52908400098527886E0F7030069857D2E4169EE7',
                 network: 'polygon', country: 'AE' },
  travel_rule: { originator: { name: 'Kamau Traders Ltd', account: 'biz_7004' },
                 beneficiary: { name: 'Supplier Co', address: '0x5290…9EE7' },
                 beneficiary_vasp: 'Partner Exchange' },
})
Compliance

What your regulator will ask, answered.

Sieve supports your obligations. It doesn’t replace your compliance team.

FATF Recommendation 16
Originator, beneficiary and counterparty VASP checked above USD 1,000 equivalent.
OFAC country and address sanctions
Embargoed corridors and listed wallets are blocked for review.
Kenya VASP Act 2025 and SEC Nigeria
Monitoring, screening and Travel Rule records kept together, ready to export.
Other use cases
Book a demo

See it on a workspace built for you.

A private Stablecoin cross-border payments workspace for Kenya or Nigeria, with a month of traffic and the fraud above. We walk your team through a live catch.

Book a demoTalk to our team