AI agent payments are transactions that a software agent starts and completes on a person's or company's behalf, within limits that person has set. In 2026 they run on two kinds of rails: card networks that issue agent-specific tokens (Visa Intelligent Commerce, Mastercard Agent Pay) and internet-native protocols such as x402, where an API answers "402 Payment Required" and the agent pays in stablecoins. Google's AP2 sits above both, recording what the user actually approved.
Agents can now book travel, buy data and call paid APIs without a human typing a card number. That breaks three assumptions behind today's payments: that a person is present to authenticate, that every payment is big enough to absorb a fixed card fee, and that the merchant can tell a real customer from a bot.
This guide explains the AI agent payment protocols in plain terms, using each standard's own documentation, then walks through a worked build: a paywalled API that agents pay per call, with the fee maths, and the risk controls that stop an agent from spending money it should not.
Key Takeaways
- There is no single standard. AP2 handles authorisation, x402 and MPP handle settlement over HTTP, and Visa and Mastercard provide tokenized card credentials and agent verification.
- x402 is now neutral infrastructure. Coinbase contributed it to the x402 Foundation at the Linux Foundation, which became operational in July 2026 with members including Visa, Mastercard, Google, Stripe and AWS.
- Fees shape the design. Coinbase's x402 facilitator is free for 1,000 on-chain transactions a month, then $0.001 each, which is 20% of a half-cent API call unless you batch.
- Card networks are adapting fast. Visa added an agent directory and agent scoring in June 2026, and Mastercard launched Agent Pay for Machines for high-frequency, low-value payments.
- Controls matter more than rails. Spending caps, destination allow lists and address checks prevent the most common agent payment failures, including address poisoning.
- Rules differ by market. The GENIUS Act governs US payment stablecoins, the UAE limits which tokens can pay for goods onshore, and the UK stablecoin regime starts in October 2027.
What Are AI Agent Payments?
An AI agent payment is any payment where software, not a person, decides the moment of purchase and executes it. The person or company still owns the money and sets the rules. The agent acts within them.
Two broad patterns exist:
- Agentic commerce. An agent shops for a person: it compares flights, fills a basket and checks out with the person's card. The amounts are normal retail sizes, and the main problems are trust and liability.
- Machine payments. An agent pays another service for something it consumes: an API call, a dataset, a page of content, a minute of compute. The amounts can be fractions of a cent, and the main problem is cost per transaction.
Card networks lead the first pattern. Stablecoin protocols lead the second. Most real products will use both.
Why Agents Need New Payment Rails
Today's payment systems assume a human. Three gaps follow.
| Problem | Why it breaks for agents | What the new standards add |
|---|---|---|
| Authentication | 3-D Secure and passkeys expect a person at the screen | Agent-specific tokens and signed user mandates |
| Bot detection | Merchants block automated traffic by default | Verified agent identities (Visa Trusted Agent Protocol, Mastercard agent registration) |
| Micropayment cost | Card pricing usually includes a fixed per-transaction fee | Stablecoin settlement with sub-cent network fees and batching |
| Accounts and API keys | Every paid API needs signup, a key and billing | Pay per request with no account (x402, MPP) |
| Proof of intent | Disputes ask "did the customer authorise this?" | Cryptographic records of what the user approved (AP2 mandates) |
The AI Agent Payment Protocol Stack
The AI agent payment protocol landscape looks crowded until you sort it by layer.
| Layer | Standard | Led by | What it does |
|---|---|---|---|
| Authorisation | AP2 (Agent Payments Protocol) | Google, now at FIDO Alliance | Signed mandates that record what the user approved |
| Settlement over HTTP | x402 | x402 Foundation (Linux Foundation) | Server returns 402; agent pays, usually in stablecoins, and retries |
| Settlement over HTTP | Machine Payments Protocol (MPP) | Stripe and Tempo | 402 challenge with one-off charges and streaming sessions; stablecoins, cards and Lightning |
| Card credentials | Visa Intelligent Commerce | Visa | Tokenized credentials, controls and authentication for agent purchases |
| Agent identity | Visa Trusted Agent Protocol | Visa, with Cloudflare | Lets merchants verify a legitimate agent |
| Card credentials | Mastercard Agent Pay | Mastercard | Agentic tokens and a trust framework for agent purchases |
| Machine settlement | Mastercard Agent Pay for Machines | Mastercard | Multi-rail settlement for high-frequency, low-value payments |
The rest of this guide takes each in turn, starting with the one developers ask about most.
x402 Explained: Paying for a Web Request
x402 turns HTTP's long-unused "402 Payment Required" status code into a working payment step. The x402 site describes it as an open, neutral standard for internet-native payments, blockchain-agnostic across EVM chains and Solana, with no protocol fee for buyers or sellers.
How the x402 flow works
- The agent calls an endpoint, for example
GET /weather. - The server's payment middleware replies 402 Payment Required, listing the price, the accepted networks and the payment scheme.
- The agent's wallet signs a payment authorisation for that amount.
- The agent retries the request with the signed payment attached.
- A facilitator verifies the signature and settles the payment on-chain.
- The server returns the data.
No signup, no API key and no invoice. The agent needs only a funded wallet.
What the facilitator costs
Coinbase runs the most widely used facilitator. Its facilitator documentation lists, as of October 2026:
- Networks: Base, Polygon, Arbitrum, Monad, World and Solana, plus test networks
- Tokens: any ERC-20 via EIP-3009 or Permit2 on EVM chains, and SPL tokens on Solana
- Schemes:
exact(one payment, one settlement),upto(pay up to a ceiling) andbatch-settlement(many signed vouchers claimed in one transaction, EVM only) - Pricing: free for the first 1,000 on-chain transactions a month, then $0.001 per on-chain transaction; verification is always free
- Compliance: OFAC and Know Your Transaction checks that decline payments involving sanctioned or high-risk addresses
Coinbase says its facilitator has processed more than 100 million x402 transactions and about $28 million in payment volume on Base and Solana. The x402 site showed 75.41 million transactions and $24.24 million of volume in 30 days (page updated 25 August 2026). That is about $0.32 per payment, so today's usage is overwhelmingly micropayments.
Who governs x402 now
The Linux Foundation announced the operational launch of the x402 Foundation on 14 July 2026, after Coinbase completed its contribution of the protocol. Forty organisations had joined by then, with premier members including Visa, Mastercard, American Express, Google, Stripe, AWS, Circle, Cloudflare, Shopify and Coinbase. That broad membership is why x402 is becoming a safe default for machine payments.
Visa Intelligent Commerce and the Trusted Agent Protocol
Visa Intelligent Commerce is Visa's platform for agent-initiated card payments. Visa's Intelligent Commerce page describes it as embedding payment credentials, controls, authentication and protections into automated buying, with examples of controls such as spending limits, approval workflows and authentication requirements. It also offers an MCP server so agents and language models can call its APIs.
Three pieces matter to builders:
- Trusted Agent Protocol. Introduced in October 2025 with Cloudflare, it helps merchants tell legitimate agents from malicious bots. Visa said it is working with Coinbase on interoperability with x402.
- Intelligent Commerce Connect. Announced in April 2026 as a network and protocol agnostic on-ramp that accepts payments started through several agent protocols.
- June 2026 additions. At its Payments Forum on 10 June 2026, Visa added Agent Score, an Agentic Directory of verified agents and merchants, and richer token data. It also said its stablecoin settlement had reached an annualized run rate of about $7 billion as of March 2026.
Mastercard Agent Pay and Agent Pay for Machines
Mastercard Agent Pay issues agentic tokens, built on Mastercard's existing tokenization, so an agent can pay with a credential that is tied to that agent and that purchase. In September 2025 Mastercard said all US cardholders would be enabled for Agent Pay by the holiday season, with Citi and U.S. Bank cardholders first and a global rollout to follow.
On 10 June 2026 Mastercard launched Agent Pay for Machines, aimed at high-frequency, low-value payments between agents and automated systems. It offers settlement across cards, accounts and stablecoins, with more than 30 early adopters including Adyen, Coinbase, Cloudflare, Stripe and Tempo. This is the card networks' direct answer to x402: they want micropayments to run through their networks too.
Google AP2: Proving What the User Approved
AP2, the Agent Payments Protocol, is the authorisation layer. The AP2 site describes it as an open protocol that extends the Agent2Agent (A2A) protocol and MCP. It does not move money. Instead, it creates signed mandates:
- A Checkout Mandate records the items and purchase details agreed with the merchant.
- A Payment Mandate authorises payment against an instrument, first as an open budget and then for a specific final amount.
These mandates are verifiable digital credentials chained together into an audit trail. If a dispute arises, the merchant and the card issuer can see exactly what the user allowed. AP2's samples cover both human-present card payments and human-not-present flows, including x402. Standardisation has moved to FIDO Alliance working groups.
Machine Payments Protocol: Stripe's Route
Stripe and Tempo co-authored the Machine Payments Protocol. It also uses a 402 challenge, but adds sessions: the agent deposits funds into on-chain escrow once and then exchanges signed vouchers. Tempo's sessions announcement says a session costs exactly two on-chain transactions, open and close, whether 10 or 10,000 vouchers pass in between. For a Stripe merchant, MPP payments land in the normal Stripe balance.
Stablecoin Payments for AI Agents
Stablecoins are the default money for machine payments because they settle in seconds, work at any hour, and cost a fraction of a cent to move on networks like Base or Solana. The basics are covered in the guide to what stablecoins are. What matters here is the rulebook in each target market.
| Market | Rule that affects agent payments |
|---|---|
| United States | The GENIUS Act sets reserve, redemption and licensing rules for payment stablecoins; issuers cannot pay interest to holders |
| Singapore | MAS's stablecoin framework covers single-currency stablecoins issued in Singapore |
| UAE | The Central Bank's payment token rules allow only licensed dirham tokens for paying for goods and services onshore; foreign stablecoins are limited to virtual asset purchases |
| United Kingdom | The FCA published final stablecoin issuance rules in June 2026; the new crypto regime starts on 25 October 2027 |
The UAE row is the one most guides miss. An agent paying a UAE mainland merchant in USDC for a physical good may fall outside what the payment token rules permit. For UAE products, design for a licensed dirham token or settle the merchant leg in AED. Businesses that need their own token can see the stablecoin development company service.
Worked Build Example: A Paywalled API That Agents Pay Per Call
Here is a realistic design: a market data API that charges agents $0.005 per call, with no accounts and no API keys.
Architecture
- API server with x402 middleware on paid routes, priced at 0.005 USDC per call on Base.
- Facilitator (Coinbase's, or self-hosted) to verify and settle payments.
- Merchant wallet that receives USDC, ideally an MPC or multi-signature wallet.
- Treasury job that sweeps USDC to a custodian or off-ramp on a schedule.
- Usage ledger that records each paid request, the payer address and the transaction hash, so finance can reconcile revenue.
- Agent client for your own testing: a wallet with a spending cap and the x402 client library.
Fee maths for 400,000 calls a month
- Revenue: 400,000 x $0.005 = $2,000 a month
Option A: exact scheme, one on-chain settlement per call
- Billable transactions: 400,000 – 1,000 free = 399,000
- Facilitator fee: 399,000 x $0.001 = $399 a month
- Fee as share of revenue: $399 / $2,000 = about 20%
Option B: batch-settlement, claiming 1,000 vouchers per transaction
- On-chain transactions: 400,000 / 1,000 = 400
- Facilitator fee: 400 is inside the free tier = $0 a month
- Fee as share of revenue: 0%, plus some delay before funds land
Option C: a card checkout with an illustrative fixed fee of $0.30 per transaction
- Fixed fees alone: 400,000 x $0.30 = $120,000 a month, 60 times the revenue
The lesson is simple: at sub-cent prices, the settlement scheme decides whether the business works. Use batching or sessions for high-volume calls, and keep exact for higher-value requests. Card rails only fit if you sell prepaid credit bundles, so the fixed fee is paid once per top-up.
Build effort
Pixel Web Solutions has no published price for AI agent builds, so here is an industry estimate with the maths shown. A production version of this API (x402 middleware, wallet setup, usage ledger, reconciliation, dashboard and testing) is roughly 250 to 400 engineering hours. At Pixel's custom rate from $40 an hour, that is $10,000 to $16,000. The merchant acceptance and settlement side maps to a crypto payment gateway, which Pixel prices from $6,000.
Risk Controls: Stopping an Agent From Overspending
An agent with a funded wallet is a spending risk until you constrain it. Developers on the r/ethdev forum have already described an agent that was address-poisoned after a long run of small payments. Address poisoning, where attackers send dust from lookalike addresses so a victim copies the wrong one from transaction history, is well documented: a 2025 academic study found it overwhelmingly targets USDC and USDT holders. Agents that read destinations from history are an easy target.
| Control | What it prevents | How to implement |
|---|---|---|
| Per-transaction cap | One large mistaken payment | Hard limit in the wallet policy, not just the prompt |
| Daily and monthly budget | Runaway loops | Rolling spend counter checked before signing |
| Destination allow list | Address poisoning and fake merchants | Only pay addresses from a signed, pre-approved registry; never from transaction history or page text |
| Full-address verification | Lookalike addresses | Compare the entire address, not the first and last characters |
| Merchant identity check | Paying impostor services | Accept only verified agents and merchants (Visa directory, facilitator metadata) |
| Human approval threshold | High-value surprises | Route payments above a set amount to a person, ideally with an AP2 mandate |
| Session keys with expiry | Stolen or leaked keys | Short-lived keys limited to one budget and one merchant set |
| Kill switch and logs | Ongoing damage | One action freezes the wallet; every payment logged with request and hash |
The rule to remember: the language model can suggest a payment, but code enforces the limits. Prompts are not security controls. The AI agent security guide covers the wider control stack, including prompt injection.
Decision Framework: Which Rail Should Your Product Use?
- Is the buyer a person shopping? Use card rails with Visa Intelligent Commerce or Mastercard Agent Pay, and record intent with AP2.
- Is the buyer an agent paying for API calls or data? Use x402 or MPP with stablecoins.
- Are prices under one cent? Use batch settlement or sessions, never one settlement per call.
- Do you already run on Stripe? MPP lands funds in your existing Stripe balance.
- Do you sell to UAE mainland merchants? Plan for a licensed dirham token or AED settlement.
- Can you show what the user approved? If not, add mandates or signed approvals before scaling.
How Pixel Web Solutions Can Help
Pixel Web Solutions builds agent systems and the payment rails behind them, from offices in Ras Al Khaimah, UAE and Madurai, India. The team implements x402 and stablecoin acceptance, agent wallets with spending policies and allow lists, usage ledgers and reconciliation, and merchant settlement. Teams can explore the AI agent development services for the agent side, the crypto payment gateway development service for acceptance and settlement, or book a consultation. For the wider picture of where agents and blockchains meet, see the guide to AI in blockchain.
Frequently Asked Questions
What is the x402 protocol?
x402 is an open standard that uses the HTTP 402 "Payment Required" status code to let a client, often an AI agent, pay for a web resource in the same request. The server asks for payment, the agent signs it, a facilitator settles it on-chain, and the server returns the content. It is now governed by the x402 Foundation at the Linux Foundation.
How do AI agents pay for things?
Agents pay in two main ways: with tokenized card credentials issued for agent use, through programmes such as Visa Intelligent Commerce and Mastercard Agent Pay, or with stablecoins from a wallet using protocols such as x402 and MPP. In both cases the owner sets limits the agent cannot exceed.
Do Visa and Mastercard support AI agent payments?
Yes. Visa runs Intelligent Commerce and the Trusted Agent Protocol, and added an Agentic Directory and Agent Score in June 2026. Mastercard runs Agent Pay with agentic tokens and launched Agent Pay for Machines for low-value machine payments in June 2026. Both are also premier members of the x402 Foundation.
What is the difference between AP2 and x402?
AP2 records and proves what a user authorised, using signed mandates; it does not move money. x402 moves money, settling a payment inside an HTTP request. They work together: an AP2 mandate can authorise a payment that settles through x402.
Why do AI agents use stablecoins?
Stablecoins settle in seconds at any hour, cost a fraction of a cent to move on low-fee networks, and need no merchant account. That makes them practical for payments worth less than a cent, which card fees make uneconomic.
Is it safe to give an AI agent a wallet?
Only with hard limits enforced in code: per-payment and daily caps, a pre-approved destination list, full-address checks, human approval above a threshold and a kill switch. Never let an agent take a destination address from transaction history or untrusted text.
AI agent payments are moving from demos to infrastructure, with card networks and open protocols converging on the same agent economy. Build on the open standards, pick a settlement scheme that suits your price per call, and enforce spending controls in code from the first release.
