SYS::ONLINE | PRE-SIGNATURE::GATE

BLACK_WALL

A BLUETIER PRODUCT · PAYMENT VERDICT

// WHY THIS MATTERS

Autonomous payments still carry your OFAC liability.

OFAC sanctions are strict liability — you can be penalized for paying a sanctioned party even if you had no idea. An agent acting on its own isn't a defense; it's the problem. Autonomy didn't remove the obligation — it removed the human who used to catch it.

$377,700
max civil penalty per violation, or 2× the transaction — assessed per transaction (IEEPA, 2026)
Strict
liability — intent is irrelevant. "The agent did it" is not a defense.
$968M
civil penalty Binance paid OFAC for processing sanctioned transactions

// HOW IT WORKS

One call before your agent signs.

1

Agent initiates payment

Your agent is about to pay a counterparty in USDC (x402) on Base.

2

Black_Wall screens — pre-signature

Checked against sanctions, counterparty reputation, price anomaly and velocity.

OFAC / SANCTIONSCOUNTERPARTYPRICE ANOMALYVELOCITY
3

Verdict returned

Before any money moves.

GOHOLDSTOP
4

Signed receipt issued

Ed25519-signed proof anyone can verify — your audit evidence.

// TRY IT — FREE & LIVE

// PRE-SIGNATURE :: VERDICT

Check a payment before you sign

> ask before your agent pays a counterparty — get GO / HOLD / STOP and a receipt anyone can verify. verdict, never custody.

[ SANCTIONED ] [ UNKNOWN PAYEE ]
// VERDICT
TRUST_SCORE

    FREE PREVIEW · AMOUNTS < $10 · VERDICT ONLY, NEVER CUSTODY
    SIGNALS :: reputation · price-anomaly · OFAC · recipient-integrity

    // HOW TO USE IT

    Three ways to call the gate.

    A human checking one payment, or an agent screening every payment — same verdict, same signed receipt.

    01 · IN YOUR BROWSER

    Check one payment

    1. Paste the wallet you're about to pay
    2. Enter the amount (USDC) + chain
    3. Hit Check payment → GO / HOLD / STOP + a receipt

    Tip: tap the [ SANCTIONED ] or [ UNKNOWN PAYEE ] preset in the tool above to see a live STOP.

    02 · IN YOUR AGENT · MCPRECOMMENDED

    One tool, zero install

    Point any MCP client (Claude, Cursor, …) at the remote server. Your agent gets a forecast_payment tool it calls before it signs.

    { "mcpServers": {
    "blackwall": {
      "command": "npx",
      "args": ["-y", "mcp-remote",
        "https://mcp.blackwalltier.com"]
    } } }
    03 · DIRECT API · x402

    One HTTP call

    POST the payment, get the verdict + signed receipt back. Free under $10 at risk; pay-per-call over that via x402 (USDC on Base).

    curl -X POST \
 https://agent-egress-proxy.onrender.com/v1/forecast-payment \
 -H 'content-type: application/json' \
 -d '{"counterparty":"0x…","amount":"5",
      "asset":"USDC","chain":"base"}'

    → { verdict, score, reasons, signed_receipt }

    // SIGNALS

    What we screen

    Four signals, every payment, before the signature.

    OFAC / Sanctions

    SDN + EU / UN / UK consolidated lists, including entities 50%+ owned by sanctioned persons. Strict liability.

    Counterparty reputation

    On-chain settlement & dispute history. Is this payee known and clean?

    Price anomaly

    Quoted amount vs the payee's own median. Catches overcharge and drain.

    Velocity / fan-out

    Sudden flow spikes and sybil fan-out patterns across counterparties.

    // THE DIFFERENCE

    With / without

    The same agent payment, two outcomes.

    Without
    • Pays the counterparty blind
    • No sanctions screen on the payee
    • No record that you checked
    • Exposure: $377,700 / violation
    • "We had no idea it was sanctioned"
    With Black_Wall
    • Screens before the signature
    • OFAC + counterparty + price + velocity
    • GO / HOLD / STOP verdict
    • Signed receipt = audit evidence
    • "Here's proof we screened it"

    // RULES OF ENGAGEMENT

    The rules you answer to

    Agents inherit the full compliance obligation of whoever deploys them — and the rules assume a human. These are the ones that bite payment-capable agents.

    Sanctions — OFAC
    Strict liability, per transaction. Screen every payee. Intent is no defense.
    50 USC 1705 · 31 CFR 501
    AML / Bank Secrecy Act
    Suspicious-activity reporting, currency reports over $10K, and a documented audit trail.
    31 USC 5318 · SAR + CTR
    KYC / Customer Due Diligence
    Know your counterparty. Identity is not optional.
    CDD Rule · 31 CFR 1010.230
    GENIUS Act — stablecoins
    Stablecoin issuers now carry a sanctions-compliance program — mandated by law.
    FinCEN / OFAC 2026 · up to $100,000 / day
    Travel Rule
    Counterparty identity must travel with a crypto transfer and be sanctions-screened.
    FinCEN / FATF · EU TFR (no threshold)

    // FREE, NO INTEGRATION

    See what your agents almost paid.

    Point us at your agent's payment flow — we'll screen it and hand you the payments that should have been held, plus a signed receipt for each.

    Get your payments screened →
    OFAC compliance details · Remote MCP · Verify a receipt

    Not legal advice. This page describes general US OFAC/AML exposure for autonomous payments; confirm your specific obligations with qualified compliance counsel. Penalty figures are statutory maximums (IEEPA-based programs, 2026) and adjust for inflation. Sources: OFAC Civil Penalties & Enforcement, OFAC Economic Sanctions Enforcement Guidelines, GENIUS Act AML/sanctions NPRM (FinCEN/OFAC, 2026).
    Black_Wall is a product of BlueTier Operations. Verdict only, never custody.