Use case
OFAC compliance API for DeFi
Screen connecting wallets against the OFAC SDN list, geofence restricted jurisdictions, and detect VPN usage — from a DeFi frontend, with simple authenticated GET requests.
DeFi protocols are permissionless at the contract layer, but the teams building frontends still face sanctions exposure: a listed wallet connecting to your app, or users in comprehensively sanctioned jurisdictions reaching your interface.
CompliAPI gives a frontend team the screening primitives to address both, without running a sanctions data pipeline: direct SDN checks on wallet addresses (including ENS names), IP geolocation with a sanctioned-country flag, and a VPN signal to weigh the location result.
Where CompliAPI fits
Wallet connect
When a wallet connects, screen the address against OFAC SDN data before it can interact with your app. ENS names are resolved and screened automatically.
Wallet screening API for crypto compliance →Jurisdiction gating
Geolocate the session and branch on the sanctioned-country flag — or on region for rules like New York State handling.
Crypto geofencing API →Location-signal confidence
Check the session for VPN usage to decide how much weight to give the geolocation result.
VPN Detection API for Sanctions Compliance →Recipient checks
Before your UI helps a user send funds, screen the destination address the same way.
Wallet screening API for crypto compliance →Scope
CompliAPI checks for direct appearance of an address on the enabled lists — official sanctions data plus labeled direct-interaction risk lists (Tornado Cash association); it does not cluster addresses or score indirect exposure the way blockchain-analytics platforms do. Which controls a DeFi frontend needs is a policy and legal question — CompliAPI supplies the data and tools, not legal advice.
Frequently asked questions
Can I call CompliAPI from a frontend dapp?
The API is authenticated with organization-scoped bearer tokens, so most teams proxy calls through a lightweight backend or edge function to keep the token out of client code.
Does screening a wallet analyze its transaction history?
No. The check is for direct appearance of the address in OFAC SDN data. Indirect-exposure analysis is the domain of blockchain-analytics tools and is out of scope.
Can I block users from specific US states?
Geolocation responses include city and region alongside country, so your frontend can apply state-level rules such as different handling for New York users.
What happens when the OFAC list changes?
CompliAPI ingests the SDN list automatically every 15 minutes and tracks delistings, so each screening call runs against the current list. Re-screen stored addresses on the schedule your policy requires.
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.
Access controls
Crypto geofencing API
Geolocate requests, flag sanctioned countries automatically, and apply jurisdiction rules in your crypto app.
Access controls
VPN Detection API for Sanctions Compliance
Detect VPNs that defeat geo-blocking.
From the blog: OFAC compliance best practices for DeFi platforms →
Add screening to your DeFi frontend
Get a free API key and screen your first wallet in minutes.
14-day free trial. No credit card required.