Use case
Sanctions screening for stablecoin payments
Screen sender and recipient wallet addresses against the OFAC SDN list before a stablecoin payment settles, and screen counterparty details like emails and websites during onboarding.
Stablecoin rails move value like payments infrastructure, and the parties on each end matter the way they do in any payment system. Teams building stablecoin checkout, payouts, or remittance products need a screening step before funds move.
CompliAPI provides that step as an API call: check the wallet addresses on both sides of a transfer for direct appearance in OFAC SDN data — USDT and other identifiers published in SDN records are covered — and screen the emails, websites and government IDs of the businesses and users behind them.
Where CompliAPI fits
Merchant and partner onboarding
Screen a counterparty's email, website and government ID when they join your payment network.
OFAC API — screen against the official SDN list →Pre-settlement wallet checks
Screen sender and recipient addresses before initiating or settling a transfer.
Wallet screening API for crypto compliance →Jurisdiction rules on payment initiation
Geolocate the initiating session and apply your policy for sanctioned or restricted jurisdictions.
Crypto geofencing API →Re-screening on list updates
Re-run checks on stored counterparty identifiers on your own schedule — the underlying list refreshes every 15 minutes.
OFAC API — screen against the official SDN list →Scope
CompliAPI performs direct checks against officially listed OFAC identifiers. It is not transaction monitoring, wallet risk scoring, or a full AML program — it is one screening control inside the payment workflow you design. Organizations should determine their obligations with qualified counsel.
Frequently asked questions
Which stablecoin addresses can be screened?
Any address type that appears in OFAC SDN records, including USDT, ETH and BTC identifiers. Coverage follows the official list rather than a fixed set of assets.
Where in the payment flow should the check run?
Most teams screen at onboarding and again immediately before funds move — a single GET request per identifier fits inline in both places. Where your policy requires checks is ultimately your compliance team's call.
Does CompliAPI monitor transactions after settlement?
No. Each request is a point-in-time check of an identifier against current OFAC data. Ongoing monitoring is something you schedule by re-screening, or a capability you source from transaction-monitoring tooling.
Is there an audit record of checks?
Yes. Every request is logged for your organization, so you can show what was screened and when.
The solutions behind this use case
Sanctions screening
Wallet screening API for crypto compliance
Screen crypto wallets against OFAC and global sanctions lists in one GET request.
Sanctions screening
OFAC API — screen against the official SDN list
Screen crypto wallets, emails, IDs and countries against the official US Treasury OFAC SDN list, refreshed every 15 minutes.
Access controls
Crypto geofencing API
Geolocate requests, flag sanctioned countries automatically, and apply jurisdiction rules in your crypto app.
From the blog: Crypto Wallet Screening: What It Is and How It Works →
Add screening to your payment flow
Get a free API key and screen your first transfer in minutes.
14-day free trial. No credit card required.