Agent makes cross-border payment touching Russia

What happens when an agent's cross-border payment touches a sanctioned Russian entity, the risk, and the control.

TL;DR

TL;DR: A cross-border payment that touches a sanctioned Russian entity or jurisdiction is a strict-liability risk, even for a legitimate transaction. Screen the counterparty and jurisdiction before funds move and BLOCK flagged matches.

What happens

An agent routes a cross-border payment and the path touches a Russian counterparty, bank, or jurisdiction subject to sanctions. Because sanctions block the transaction, the exposure exists even if the agent did not intend to deal with a sanctioned party. The routing decision, not the intent, is what matters, and the operator is accountable for the path the agent chose even when the instruction was generic.

The risk

OFAC enforces under strict liability, so intent is not required, and civil penalties start at $356,000 per violation. The 50 Percent Rule blocks entities 50% or more owned by a blocked person, and screening must cover the 16 jurisdictions where sanctions risk concentrates. A routing decision that skips jurisdiction checks inherits that whole risk. A jurisdiction check is not optional; it is part of the screen itself.

The control

Screen both the counterparty and the jurisdiction before funds move. agentmail's risk_score weighs jurisdiction risk, and sanctions_check screens the name against the SDN List of 19,218 names and the wallet against 947 OFAC-listed crypto wallets in one call under 100 ms. Clean returns ALLOW, flagged returns BLOCK, and the SCREEN, SCORE, STOP, STAMP protocol halts the payment at the STOP gate with a documented decision.