Skip to content

Sanctions screening

Sotirea checks every address your organisation pays, and every address that pays you, against OFAC’s sanctions list and Sotirea’s own blocked list. The lists are refreshed daily. Screening runs for every organisation, in Test and Live, and no payment rule or setting switches it off.

A payment to a listed address is refused before any of your own payment rules run. Nothing is sent and nothing is set aside. It is answered 403 with fields.rule:

fields.rule Why
sanctioned_address A sanctions list names the address. “Sotirea cannot send to this address: it is on a sanctions list. Nothing was sent.”
blocked_destination Sotirea’s own blocked list names it.

The address is checked again when a payment is approved and just before it is signed. If a list names it while a payment waits, for approval for example, that payment is failed, with a payment.failed webhook, and its money is released.

A quote to a listed address answers outcome refused with the same rule, and adding one to your approved addresses is refused 400 with the same fields.rule.

GET /v1/addresses/{address} answers listed true for an address a list names, so your product can tell a customer before they try to pay it. Which list entry named it is never shown.

Money that has arrived cannot be refused: the network has already moved it. So a deposit from a listed address is credited and held for a compliance review:

  • It is checked when it becomes final. Until then, deposit.arriving looks like any other.
  • The balance’s held says how much is held. It is counted in available and never in spendable.
  • Its deposit.received webhook has held true.
  • Only that deposit is held, never the rest of the vault. Paying out of held money is refused 400 with fields.rule insufficient_balance, and the message says how much is held.

Deposits between your organisation’s own vaults and gas pools are not screened.

Only addresses on EVM networks are screened today, which is every network Sotirea supports.