BLACK_WALL
● OFAC::SCREEN | PRE-SIGNATURE::GATE
OFAC compliance for autonomous payments

Your AI agent just wired money.
Do you know it wasn't to a sanctioned wallet?

OFAC liability is strict — it does not matter that you didn't know. Autonomy didn't remove the obligation. It removed the human who used to catch it.

Screen your agent payments — free Try the live check →
The exposure

Strict liability, priced per transaction.

~$377,700
max civil penalty per violation, or 2× the transaction value — whichever is greater (IEEPA programs, 2026)
Per tx
each violating payment is a separate fine — and agents transact at machine speed and volume
$968M
OFAC civil penalty Binance paid for processing sanctioned transactions — this class of failure, enforced
The gap nobody screened

Payments got solved. Screening them didn't.

x402 and agentic payment rails made it trivial for software to move USDC on its own. The industry celebrated "the agent can pay." Almost no one asked the next question: should it have paid that counterparty? That question is your legal obligation — and right now, nothing is answering it before the signature.

The control

Black_Wall screens before the signature — and proves you did.

01

Screen — before it signs

Every agent payment is checked pre-signature against OFAC/sanctions, counterparty reputation, price anomaly, and velocity. The verdict comes back GO HOLD STOP before any money moves.

02

Prove it — a signed receipt

Each verdict ships with an Ed25519-signed receipt anyone can independently verify. Documented evidence that the payment was screened — the audit trail your compliance file needs.

03

A control OFAC counts in your favor

OFAC's own enforcement guidelines treat a risk-based sanctions compliance program as a mitigating factor. A pre-signature screen plus provable evidence is exactly that kind of documented control.

Straight talk
No vendor can promise immunity, and we don't. What Black_Wall gives you is a documented, pre-signature control and provable evidence you ran it — the difference between "we had no idea" and "here is the signed record showing we screened every payment."
Straight answers

OFAC & agent payments — FAQ

Do AI agent payments need OFAC or sanctions screening?

Yes. OFAC sanctions run on strict liability — a company can be penalized for paying a sanctioned party even without knowing. An agent acting autonomously is not a defense, and penalties are assessed per transaction. Screening the counterparty before the payment signs is a legal obligation, not an optional feature.

What is the penalty for an AI agent paying a sanctioned wallet?

Up to ~$377,700 per violation, or 2× the transaction value, whichever is greater (IEEPA programs, 2026; adjusts for inflation), assessed per transaction. Binance paid OFAC a $968M civil penalty for processing transactions tied to sanctioned jurisdictions.

How do you screen an agent payment before it signs?

Black_Wall checks the payment pre-signature against OFAC/sanctions, counterparty reputation, price anomaly, and velocity, and returns a GO / HOLD / STOP verdict before any money moves. Callable from the browser, via API, or via a remote MCP endpoint for agents like Claude and Cursor.

How do I prove a payment was screened for compliance?

Each verdict ships with an Ed25519-signed receipt anyone can independently verify — documented evidence the payment was screened. OFAC's enforcement guidelines treat a documented, risk-based compliance program as a mitigating factor.

Free, no integration

See what your agents almost paid.

Point us at your agent's payment flow — or send a week of it. We'll screen every payment, hand you the ones that should have been held and why, plus a signed receipt for each. No integration, no commitment.

Get your payments screened →