StrimzStrimz
Concepts

Compliance

What stops a blocklisted wallet from paying through Strimz today, and what Strimz does not screen yet.

Stablecoin payments are still payments. They're subject to OFAC's sanctions list and the country-level sanctions regimes that follow. This page says exactly what protects a Strimz payment today and what doesn't, so you can decide what to layer on top.

What runs today

Strimz does not run third-party wallet screening. No payer or merchant wallet is sent to a screening provider, and no risk score is computed.

What does stop a sanctioned wallet is the chain itself. Arc enforces Circle's USDC blocklist in the protocol:

  • A transaction from a blocklisted sender is rejected before it reaches the mempool.
  • A USDC transfer or transferFrom where the sender or the recipient is blocklisted reverts.

See Arc's blocklist compliance guide.

Strimz simulates every relayed payment before it submits it. When the payer is on Circle's blocklist, the simulation fails, the relay answers 400 with code: 'relay_simulation_failed', and nothing is broadcast, so no gas is spent.

This covers wallets on Circle's blocklist. It does not cover wallets that are high risk but not blocklisted; those pay normally.

What isn't live yet

The API contains adapters for TRM Labs and Elliptic, switched off. When a provider is turned on, a provider error counts as a block: Strimz would rather refuse a payment than settle one it could not screen. Screening at checkout is not wired in yet, and we'll update this page and the changelog before it is.

A few published names exist for that future and are not sent today:

  • The webhook events compliance.wallet_flagged and compliance.wallet_blocked.
  • The SDK error code compliance_blocked.

Don't build a flow that waits for them yet. The read-only GET /v1/compliance/logs endpoint returns an empty list while screening is off.

What it doesn't cover

Even once screening is on, a few things are out of scope:

  • It doesn't do KYC on the payer. Strimz doesn't know who's behind a wallet; we know the wallet address.
  • It doesn't do AML investigation. If a wallet is moving suspicious amounts to and from your business, we don't surface that.
  • It doesn't do travel-rule data exchange.
  • It doesn't do tax reporting.

If you have a regulated use case that needs more than this, such as a money services business or anything that does customer due diligence, layer your own KYC on top of Strimz. We give you the wallet address; you can hook a Persona, Sumsub or similar flow at signup.

Questions about a specific sector or jurisdiction go to support@strimz.finance.

On this page