Scenario: Agent Pays a Sanctioned Name
The sanctioned-name scenario: why wallet screening alone is not enough.
The setup
Your agent handles invoice payments to companies. One supplier shares a name and jurisdiction profile with an SDN-designated entity — but its wallet is not on the wallet list.
The gap
Wallet-only screening passes this payment: the address is clean. Name screening catches the entity match (19,218 names screened).
The resolution
- The name screen flags the match (fuzzy, high confidence)
- The workflow pauses for review
- Identifier comparison confirms the SDN entity
- The payment is blocked and logged
The takeaway
Screening wallets alone leaves the name surface open. The full screen is wallets + names + jurisdictions.