The Private White-Label Payment Facilitator

Your own branded agent-payment rail — running on infrastructure that already settles real money.

AgentPay / x402-agent-pay.com

Built on Base L2 · Patent-pending A2A Escrow with Message Protocol

Request white-label access → Partner portal

1. What this is (in one line)

We give a company its own private, branded payment facilitator for AI-agent transactions — the same rail that already runs live on x402-agent-pay.com, but wearing your name, on your path, settling to your wallet. You get the infrastructure on day one. We keep it running.

The rail is live on Base L2 today, has settled real USDC with verifiable on-chain proof, and charges a flat, predictable fee. A white-label tenant plugs into all of that without building any of it.


2. The "why" — the problem this solves

AI agents are starting to pay each other for services — data, compute, expertise, API calls. The moment money moves between agents, a company hits three hard walls:

  1. Building a payment rail is a project, not a feature. On-chain settlement, signature verification, nonce/replay protection, escrow, dispute handling, fee accounting, gas management — that's months of specialized crypto engineering before a single dollar moves.
  1. Handing money-movement to a third party means handing over your brand and your customer relationship. Most payment processors put their name on the flow. Your customers see the processor, not you.
  1. Public blockchains are radically transparent. Every payment, counterparty, and amount is visible forever to anyone. For business transactions that's a confidentiality problem, not a feature.

The white-label facilitator answers all three: you get the rail instantly, it carries your brand, and it settles privately.


3. The "how" — how it actually works

The relationship model: API key, not credential handoff

A white-label tenant is provisioned as a partner in the facilitator. They receive:

There is no private-key handoff. The tenant never gives us the keys to their money. Authentication is a rotating API token; settlement authority stays on the tenant's side. This is the single most important design choice — it removes the custody liability that sinks most "white-label crypto" offers.

The payment flow (x402 standard)

Every agent-to-agent payment follows the x402 protocol on Base L2 using USDC:

  1. A buyer agent requests a paid resource → the facilitator returns HTTP 402 Payment Required with the exact terms (amount, asset, receiver, memo, expiry).
  2. The buyer signs an EIP-3009 transferWithAuthorization — a gasless, off-chain USDC authorization.
  3. The facilitator verifies the signature and settles on Base, broadcasting the authorized transfer.
  4. Every settlement is logged with its on-chain tx hash → a clickable BaseScan proof.

The buyer signs; the facilitator broadcasts and pays the tiny gas (~$0.002 per settlement on Base). Atomic, verifiable, final.

The economics


4. Escrow — money held safely until the work is done

For higher-value or trust-sensitive agent transactions, a raw "pay-and-hope" transfer isn't enough. The facilitator includes a full A2A (agent-to-agent) escrow system (this is the patent-pending piece):

This turns "I paid an agent and hope it delivers" into "the money is locked, released only on acceptance." It's what makes larger agent-to-agent deals safe enough to actually happen — and it's a capability most payment rails simply don't have.


5. The Message Protocol — payments that carry meaning

A plain USDC transfer is just a number moving between addresses. It carries no context — no order ID, no purpose, no cryptographic link to what was bought.

The facilitator's Message Protocol attaches a signed, structured message header (X-Agent-Token auth + a memo payload) to every payment. That header binds the payment to:

The receiving agent's instruction is literally: "Send USDC on Base with this memo, then confirm the tx hash." The memo is the cryptographic thread that ties the on-chain money movement to the off-chain business intent. This is what makes agent payments machine-verifiable and disputable rather than anonymous blobs of value.


6. Private Payments — confidentiality on a public chain

Public blockchains expose everything. For business transactions between companies and their agents, that's unacceptable — competitors shouldn't be able to read your entire payment history off a block explorer.

The white-label facilitator provides private / stealth settlement: the sensitive relationship between payer, payee, and purpose is handled through the facilitator's message layer and rotating receive-addresses, so the business meaning of a payment isn't broadcast in the clear. You get the finality and verifiability of on-chain USDC settlement without publishing your commercial relationships to the world.

The result: on-chain trust, off-chain confidentiality.


7. What a white-label tenant gets on day one

CapabilityWhat it means for you
Instant branded railYour name, your path, your payout wallet — no build time
x402 settlement on BaseAtomic, gasless-for-payer USDC payments, ~$0.002 gas each
A2A EscrowLock funds, release on delivery, deny to protect — patent-pending
Message ProtocolSigned memo headers binding payment to purpose
Private settlementOn-chain finality without broadcasting your business relationships
Live trust feedReal, verifiable settlements with BaseScan links
Members dashboardPer-tenant stats: settlements, volume, earnings, gas balance
No key custodyYou hold your keys; we never touch your money
Flat fee$0.02/settlement — you keep ~98%+

8. Hosting: "You Host" (default) vs "Self-Host" (premium)

You Host (default, recommended). We run the facilitator for you — uptime, security patches, gas monitoring, RPC failover, and the settlement infrastructure are our job. You point your agents at your branded endpoint and go. This is the fastest path and removes all operational burden.

Self-Host (premium). For companies that require the rail inside their own infrastructure, we deploy the facilitator into your environment. You own the box; we provide the software, the escrow engine, the message protocol, and setup. Best for regulated or infrastructure-sensitive organizations.

Either way, the architecture is identical — the only difference is whose servers it runs on.


9. The bottom line

Building this from scratch is months of crypto-payment engineering with real custody risk. The white-label facilitator gives a company the finished rail — branded, private, escrow-backed, and already proven on a live network with real settlements — in near-zero setup time, while keeping ~98%+ of transaction value and never surrendering the keys to its own money.

On-chain trust. Off-chain privacy. Your brand. Your wallet. Running today.


AgentPay — x402AgentPay · A2A Escrow with Message Protocol (Patent Pending) · Built on Base + x402

Inquiries: [email protected]


Learn more

Explore the individual pieces of the rail in depth:

Request white-label access →

← Back to home