OFAC Contractual Compliance

Sanctions obligations embedded in contracts through warranties, representations, and covenants requiring counterparties to comply with OFAC.

TL;DR

TL;DR: Contractual compliance writes sanctions duties into agreements, so each party warrants, represents, and covenants to comply with OFAC and to screen its own counterparties.

What these clauses do

Sanctions clauses typically appear in three forms. Warranties affirm that a party is not sanctioned and will not use the arrangement to violate sanctions. Representations state facts about the party's status at signing. Covenants create ongoing obligations, such as screening counterparties and not transacting with blocked parties. Together they make compliance a contractual duty, not just a legal backdrop. These clauses also give a counterparty a contractual reason to screen its own downstream partners, pushing the duty through the chain.

Why contracts matter

Contract terms give a party recourse and a paper trail. If a counterparty breaches a sanctions covenant, the contract provides a basis to terminate or seek remedy. More importantly, the clauses force each side to think about screening before the relationship produces transactions.

Contractual compliance for agents

Agent payment arrangements increasingly need these terms, because the counterparty may be another autonomous system. sanctionsai.dev supports the underlying duty with screening: a counterparty checked before payment returns ALLOW or BLOCK. Documenting that check with the dispute_open and kya_verify tools gives a record that the contractual commitment was actually performed. A clause without a working screen behind it is still useful, but the combination of both is what holds up in practice.