Agentic payments protocols cover different layers

Updated · by the Xenarch team

Agentic payments are payments or purchases that an AI agent starts on someone’s behalf. x402 and MPP cover paid HTTP requests, ACP and UCP cover merchant checkout, and AP2 covers authorization within commerce protocols.

Agentic payments split into payment, checkout and trust layers

Agentic commerce includes the purchase an agent starts and the payment that follows. A paid API request, a merchant checkout and an escrowed job have different requirements, so their protocols cover different parts of the transaction.

x402, the Machine Payments Protocol (MPP) and L402 define machine-to-machine payments over HTTP. The Agentic Commerce Protocol (ACP) and Universal Commerce Protocol (UCP) define interactions between an agent and a merchant, including checkout.

The Agent Payments Protocol (AP2) supplies authorization evidence. Visa Trusted Agent Protocol, Mastercard Agent Pay and Verifiable Intent address agent recognition, payment credentials or proof of user permission.

ERC-8004 covers agent identity, reputation and validation. ERC-8183 covers job escrow with an evaluator. Agent2Agent (A2A) carries agent messages, including payment extensions.

A protocol’s specification can cover more networks, assets or payment rails than a particular facilitator or payment provider supports. The x402 exact scheme includes EVM, Solana and Bitcoin Lightning specifications, while its documentation defines facilitator support by network.

ProtocolPublisherLayerRailsStatus, Nov 2026
x402Created by Coinbase, x402 Foundation (Linux Foundation)Pay per HTTP requestStablecoins on many networksProtocol v2, live
MPPStripe and TempoPay per HTTP request, sessionsStablecoins, cards, LightningLive on Tempo mainnet, IETF individual draft
L402Lightning LabsPay and authenticate API callsBitcoin LightningbLIP-0026
ACPOpenAI and Stripe, Meta on the TSCAgent checkout with a merchantCards through Shared Payment TokensBeta, spec 2026-04-17
UCPGoogle with Shopify and retailersFull commerce lifecyclePayment handlers (Google Pay, Shop Pay)Live in AI Mode and Gemini (US)
AP2Google, donated to the FIDO AllianceAuthorization: mandates and receiptsCards, crypto through x402v0.2
Visa Intelligent CommerceVisaTokenized cards for agentsVisa cardsGated by Visa
Visa Trusted Agent ProtocolVisa, with CloudflareAgent identity for merchantsNone of its ownSpec on GitHub
Mastercard Agent PayMastercardAgentic card tokensCards, plus accounts and stablecoins for machinesLive transactions
ERC-8004Ethereum ERC authorsOn-chain agent identity and reputationNone, payments out of scopeDraft ERC, registries on mainnets
ERC-8183Ethereum ERC authors, VirtualsJob escrow between agentsERC-20 tokensDraft ERC
A2ALinux Foundation project, started by GoogleAgent-to-agent messagingThrough AP2 and x402 extensionsv1.0

From each protocol's spec and its publisher's posts, read November 17, 2026.

x402 prices requests and carries signed payments

x402 is an open payment standard created by Coinbase. Its whitepaper is dated May 6, 2025. The current specification is version 2, dated December 9, 2025.

Over HTTP, the server returns status 402 with a base64-encoded JSON PAYMENT-REQUIRED header. The client signs a payment and retries with PAYMENT-SIGNATURE. The server returns settlement information in PAYMENT-RESPONSE.

An optional facilitator exposes /verify and /settle endpoints. It verifies and settles the signed payment without holding funds. A resource server can also perform those steps itself.

The specification supports HTTP, MCP and A2A transports. Its exact scheme covers a specified payment amount, while upto authorizes a maximum and settles actual consumption. Other schemes cover authorization and capture or batch settlement.

x402 supports stablecoins and other tokens across EVM, Solana and additional networks. EVM token payments use EIP-3009 or Permit2. The standard also includes fiat asset identifiers and a Bitcoin Lightning scheme, so its scope extends beyond USDC.

The Linux Foundation announced the x402 Foundation on April 2, 2026, with operational launch on July 14, 2026. Coinbase, Cloudflare and Stripe hold Technical Steering Committee seats.

x402.org advertises zero protocol fees. Provider charges remain separate. Coinbase’s CDP facilitator includes the first 1,000 onchain transactions each month, then charges $0.001 per additional transaction.

MPP uses HTTP payment authentication across multiple rails

The Machine Payments Protocol is an open standard co-authored by Tempo and Stripe. Stripe announced MPP on March 18, 2026, and says Stripe users can accept it through the PaymentIntents API.

An MPP server returns HTTP 402 with a WWW-Authenticate: Payment challenge. The client retries with an Authorization: Payment credential proving payment. This differs from the payment-specific headers used by x402.

The MPP specifications separate core HTTP semantics from intents, methods and extensions. Intents include charge, session and subscription. Methods describe the payment rail, with drafts covering cards, Lightning, stablecoins and other networks.

The Stripe method uses Shared Payment Tokens (SPTs) representing payment authorization. The card method uses encrypted network tokens and references Visa Intelligent Commerce and the Visa Trusted Agent Protocol.

The core Payment HTTP Authentication Scheme is an active individual IETF Internet-Draft, updated September 9, 2026. It has not been adopted by an IETF working group. Tempo Labs and Stripe maintain the specifications.

mpp.dev documents generic EVM payments and x402 exact flows from one SDK, including adding MPP to an existing x402 server. In its March 18, 2026 announcement, Stripe says it supports both MPP and x402.

ACP defines merchant checkout and delegated payment

The Agentic Commerce Protocol is an open standard co-developed by OpenAI and Stripe. Stripe’s September 29, 2025 announcement introduced it with Instant Checkout in ChatGPT. Businesses can adopt ACP with existing payment providers.

The checkout RFC defines checkout-session operations. Merchants expose POST /checkout_sessions for session creation and support update, retrieval, completion and cancellation. Completing a session with a payment method must create an order.

Delegated payment gives the merchant a vault token usable by its existing payment service provider. An Allowance restricts max_amount, currency and expiry. The Delegate Payment RFC currently supports card credentials.

ACP’s payment-handler specification names the Shared Payment Token as its standardized delegation token for handlers requiring delegated payment. Stripe describes SPTs as allowing an agent to initiate payment without exposing the buyer’s credentials.

The MCP binding is a second transport alongside REST. ACP also defines discovery at /.well-known/acp.json and product feeds for publishing catalog data. Its latest stable date-based version is April 17, 2026.

The repository labels ACP beta and names OpenAI, Stripe and Meta as lead maintainers. OpenAI and Stripe are Founding Maintainers that appoint steering committee seats.

Stripe’s September 29, 2025 announcement says ACP powers Instant Checkout in ChatGPT. OpenAI’s commerce documentation describes browser-use or plugin checkout with ChatGPT Wallet and does not mention ACP or Instant Checkout.

UCP defines commerce capabilities and payment handlers

The Universal Commerce Protocol connects agent-facing platforms, businesses, payment service providers and credential providers. Google launched UCP on January 11, 2026, with Shopify, Etsy, Wayfair, Target and Walmart.

UCP’s initial capabilities cover Checkout, Identity Linking, Order and Payment Token Exchange. Identity Linking uses OAuth 2.0, and Order uses webhooks. Checkout sessions support purchases with or without human intervention.

The UCP specification is transport-agnostic. Businesses can expose capabilities through REST, MCP or A2A, and platforms discover their profiles at /.well-known/ucp.

Payment instruments and payment handlers are separate concepts. Handler examples include com.google.pay and dev.shopify.shop_pay. UCP’s AP2 mandate extension binds payment mandates to a checkout hash to prevent token replay.

At launch, Google described checkout for eligible US retailer listings in AI Mode in Search and Gemini, using Google Pay, with PayPal to follow. On May 19, 2026, Google said it planned to expand UCP-powered checkout on Google to Canada and Australia in the coming months and later to the UK.

The latest protocol release is dated August 25, 2026. Stripe joined the Governing Council on April 28, 2026, alongside permanent members Google and Shopify. A Payments Technical Council formed on September 2, 2026, including Adyen, Coinbase, Google, PayPal, Shopify and Stripe.

AP2 proves authorization within a commerce protocol

The Agent Payments Protocol defines signed mandates for agent-led purchases. Google announced AP2 on September 16, 2025. The launch described Cart Mandates for human-present approval and Intent Mandates for delegated tasks.

The current AP2 v0.2 specification separates what is bought into a Checkout Mandate and how it is paid into a linked Payment Mandate. Each has a signed receipt usable as dispute evidence. Catalog and checkout APIs remain outside AP2’s scope.

In Human Present mode, the user sees and approves the closed checkout and payment. In Human Not Present mode, the user approves open mandates containing constraints such as budget or allowed payees. The agent’s public key appears in a cnf claim, and the agent signs the closed mandates.

Google released v0.2 and donated AP2 to the FIDO Alliance on April 28, 2026. The specification positions AP2 as a security feature within a commerce protocol and explicitly supports UCP compatibility.

AP2’s implementation documentation says the initial version supports pull methods such as credit and debit cards. E-wallets, push bank transfers and digital currencies appear on its roadmap, despite broader payment coverage described at launch.

For crypto, AP2’s FAQ points to the A2A x402 implementation. The AP2 repository also includes a Human Not Present x402 sample. The A2A x402 extension brings on-chain crypto payments to A2A.

Card programs add credentials, recognition and authorization proof

Visa Intelligent Commerce supplies APIs and a commercial partner program for agent-initiated card purchases. Visa announced it on April 30, 2025. It replaces card details with tokenized digital credentials and lets consumers set spending limits and conditions.

Visa’s developer documentation lists tokenization, Visa Payment Passkey authentication, purchase instructions and signals. Access progresses through sandbox, certification and production with Visa approval. Production integrators must onboard to the Trusted Agent Protocol.

The Visa Trusted Agent Protocol, introduced October 14, 2025, lets merchants recognize signed agent interactions. Each signature includes timestamps, session and key identifiers, and an algorithm identifier. Signatures bind to the merchant domain and the browsing or payment operation.

TAP builds on HTTP Message Signatures and aligns with Web Bot Auth. Using the TAP code means accepting the Visa Developer Center Terms of Use and the TAP Product Terms. GitHub reports the license as NOASSERTION. The repository’s last push was October 28, 2025.

Mastercard Agent Pay, launched April 29, 2025, introduces Mastercard Agentic Tokens. Mastercard’s merchant guide describes certified agents in a trusted registry and signed requests using Web Bot Auth. It says agents must use Agentic Tokens rather than consumers’ existing merchant cards on file.

Verifiable Intent supplies cryptographic proof of user authorization alongside checkout protocols such as ACP or UCP. Its draft credential chain runs from credential provider to user to agent, with selective disclosure and bound purchase constraints. The repo contrasts ACP’s SPTs, which authorize payment execution and are enforced by the PSP, with VI credentials, which prove the user’s authorization and can be verified by any party.

Verifiable Intent v0.1.0 is dated February 19, 2026. Mastercard contributed the framework to FIDO’s standards work on April 28, 2026, alongside Google’s AP2 contribution.

On-chain standards cover agent trust and job escrow

ERC-8004, titled Trustless Agents, defines registries for identity, reputation and validation. The draft ERC was created August 13, 2025. Its specification explicitly leaves payments outside its scope.

The Identity Registry resolves an agent registration file. The Reputation Registry records feedback signals, while the Validation Registry concerns independent checks. Agents can advertise A2A or MCP endpoints and a receiving wallet, and x402 payment proofs can enrich feedback.

The ERC-8004 contracts repository lists Identity and Reputation registry deployments on 25 mainnets, including Ethereum and Base. It says the Validation Registry remains under active update and discussion with the TEE community.

ERC-8183, titled Agentic Commerce, defines funded jobs with an evaluator. The draft, created February 25, 2026, escrows a client’s budget while a provider submits work. The evaluator alone marks completion or rejection, with completion releasing funds and rejection or expiry permitting refunds.

Virtuals calls its own Agent Commerce Protocol ACP. Its April 2026 changelog describes ACP v2.0 as an ERC-8183 reference implementation using USDC escrow on Base. This ACP has a different publisher and purpose from OpenAI and Stripe’s Agentic Commerce Protocol.

A2A supplies the messaging layer for agent collaboration. Google announced it on April 9, 2025, and contributed it to the Linux Foundation. Extensions declared in an AgentCard let payment protocols add transaction messages.

L402 combines HTTP authentication with Lightning payments

L402 is Lightning Labs’ protocol for paid API access over the Lightning Network. Its documented HTTP flow combines a macaroon bearer credential with a Lightning invoice.

The server answers HTTP 402 with a macaroon and BOLT11 invoice in the WWW-Authenticate header using the L402 scheme. After paying, the client retries with Authorization: L402 macaroon:preimage. The payment preimage supplies proof, and verification needs no database lookup.

L402 was previously named LSAT. The specification covers HTTP and gRPC, directs servers to send both scheme names and requires accepting both.

Lightning Labs’ March 11, 2026 update says L402 is formalized as bLIP-0026. Macaroons remain recommended, while other tokens can qualify if they commit to the invoice’s payment hash. Aperture implements L402 as an HTTP and gRPC reverse proxy.

Lightning is also a rail in other protocols. x402 defines a Lightning exact scheme, and MPP includes Lightning charge and session methods authored by Lightspark.

Protocol choices depend on the payer, rail and purchase

UCP’s documentation states that UCP is fully compatible with AP2. Its specification carries AP2 mandates through the ap2-mandates payment extension. AP2’s crypto documentation points to A2A with x402, whose extension exchanges payment-required, signed payment-submitted and payment-completed messages.

MPP tooling documents support for x402 exact flows. ACP’s delegated payment and MPP’s Stripe payment method both use Shared Payment Tokens (SPTs). Stripe says its processing may use network tokens from programs such as Visa Intelligent Commerce or Mastercard Agent Pay.

For a person delegating a merchant purchase, assess checkout state, payment-provider support and authorization evidence. ACP and UCP address checkout. AP2 and Verifiable Intent address what the user authorized, while card programs supply credentials and agent-recognition mechanisms.

Agentic payments can use cards or stablecoins, depending on the protocol and provider. ACP’s delegated payment currently supports only card credentials. MPP has methods for cards, Stripe SPTs, Lightning, Tempo stablecoins and other tokens. x402 supports token settlement on EVM, Solana and other networks, defines a Lightning (lnbtc) scheme and allows ISO 4217 fiat currency codes in its asset field. L402 uses Lightning only. A facilitator may support fewer rails than the specification, as noted in the layer overview.

For agent-to-agent payments tied to work, distinguish payment from job evaluation. ERC-8183 provides escrow and evaluator-controlled completion. ERC-8004 provides identity and feedback, and A2A carries messages between agents.

Xenarch is an x402 rail for sellers, publishers and agents

Xenarch issues x402 payment requirements with payTo set to the seller’s own wallet. USDC moves directly from payer to seller without a Xenarch contract between them. Xenarch supports Base mainnet and native USDC.

Xenarch’s HTTP 402 body uses an x402 version 1 envelope with x402Version set to 1 and an accepts array. This differs from the current version 2 HTTP header flow described above.

Sellers can create checkout, subscription, invoice and donation links. Gating integrations include WordPress, Joomla, a Cloudflare Worker and Python FastAPI middleware with a require_payment decorator.

The MCP server is @xenarch/agent-mcp, version 1.3.1. Install it with npx @xenarch/agent-mcp. Its xenarch_pay tool pays only responses carrying a Xenarch gate_id. Agents pay hosted links by link id with xenarch_pay_link, which obtains the x402 envelope from the API.

MCP payments require an agent token in XENARCH_API_TOKEN. A local $1 per-call cap is changeable through XENARCH_MAX_PAYMENT_USD. Hosted-link payments have a separate $1 default maximum, raised with max_price_usd.

The platform enforces per-transaction, daily and monthly caps for agent tokens. Tokened CLI, SDK and MCP payments first call POST /v1/agent/preflight to check pause state, scope and caps. An allowed request receives a 60-second token.

Scope rules use glob allow or deny patterns on host and path. New agents default to allow, and the operator can switch that posture to deny.

Questions

What are agentic payments?

Agentic payments are payments or purchases an AI agent initiates on someone’s behalf. They include paid API requests, merchant purchases and payments for agent work.

What is the difference between ACP and AP2?

ACP defines merchant checkout interactions, while AP2 supplies signed proof of purchase and payment authorization. ACP includes checkout sessions and delegated payment. AP2 leaves catalog and checkout APIs outside its scope.

What is the difference between x402 and MPP?

x402 and MPP use different HTTP payment exchanges. x402 uses PAYMENT-REQUIRED and PAYMENT-SIGNATURE, while MPP uses WWW-Authenticate: Payment and Authorization: Payment. MPP tooling also supports x402 exact flows.

Is UCP the same as ACP?

No. Google announced that UCP would power checkout on eligible Google product listings from eligible US retailers in AI Mode in Search and the Gemini app. ACP is the Agentic Commerce Protocol co-developed by OpenAI and Stripe, with Shared Payment Tokens for delegated card payments.

Which agentic payment protocol should I use?

It depends on who pays and for what. For a machine paying per HTTP request in stablecoins, use x402 or MPP. For an agent checking out at a merchant on a person's behalf, use ACP or UCP, with AP2 mandates for the authorization. L402 fits Lightning payments, and ERC-8183 fits escrowed jobs between agents.

Let your agent pay over x402

Xenarch gives an agent a USDC wallet on Base with per-payment, daily and monthly caps that Xenarch checks before every signature.

npx @xenarch/agent-mcp
AgentsDocs