Build a crypto sanctions screening check
Sanctions screening tests whether an address appears on a designated list. The sanctions endpoint returns a boolean match and, when present, the list that flagged it. Record each check so a designation can be evidenced at the moment it was made.
- A live API key with AML scope.
- The address to screen and its chain path segment (eth, btc, tron).
1Call the sanctions endpoint
Issue a GET against the sanctions path for the chain and address. This is a C2 call and is cheaper than a full risk score, so it can run on every counterparty.
curl https://api.1st-node.com/v1/aml/btc/bc1qxy2k.../sanctions \ -H "Authorization: Bearer sk_live_..."
2Interpret the match result
A clean address returns match false. A hit returns match true with the list name so you can cite the specific designation source.
> { "match": true, "list": "OFAC SDN", "entity": "designated-address" }3Block and escalate on a match
Treat any match true as a hard stop: reject the transaction and route it to compliance. Do not net or partially fill against a sanctioned address.
Preguntas frecuentes
How often should addresses be rescreened?
Lists change, so rescreen retained counterparties on a schedule and at each new transaction. A stored clean result is only evidence for the moment it was taken.
Does a clean sanctions result mean the address is low risk?
No. Sanctions checks only test designation lists. Use the risk-score endpoint to measure exposure to mixers, scams, and other categories.
Sigue leyendo
Recarga, obtén tu clave y publica.
Autoservicio. Paga en cripto o con tarjeta. Medido por créditos: las primitivas pesadas cuestan más, las simples son baratas.
Obtener clave API