Scenario: Agent Pays an Embargoed Jurisdiction
The jurisdiction scenario: why a clean wallet can still be a prohibited payment.
The setup
Your agent pays a supplier whose wallet is clean — not on the SDN list. But the counterparty operates from a comprehensively embargoed jurisdiction (Iran, North Korea, Cuba, Syria, Crimea).
The gap
Wallet-only screening passes the payment: the address is clean. Jurisdiction screening catches the geographic exposure — OFAC comprehensively sanctions 16 jurisdictions.
The resolution
- The jurisdiction check flags the counterparty location
- The workflow pauses for review
- The counterparty confirms the embargoed jurisdiction
- The payment is blocked and logged
The takeaway
Screening wallets and names leaves the geography surface open. The full screen is wallets + names + jurisdictions — that is the 947 / 19,218 / 16 dataset.