{"slug": "agentic-payments-how-agents-move-money", "title": "Agentic Payments: How Agents Move Money", "summary": "AI agents now initiate money movement across commerce, machine payments, and treasury, with protocols such as MCP, ACP, and UCP competing to define how agents find merchants, authorize purchases, and settle payments. OpenAI and Google lead the commerce race, while Bain projects $300–500 billion for the commerce slice alone. Most shipped examples remain human-assisted, with full execution emerging unevenly across the three flows.", "body_md": "# Agentic Payments: How Agents Move Money\n\nAI agents now initiate money movement. Sometimes they shop for a consumer. Sometimes they pay for an API call. Sometimes they operate a business account under a finance team’s rules.\n\nThose are different jobs. They use different protocols, controls, and settlement paths, even when the same companies appear in more than one.\n\nThe revolution is delegation. A person or business hands part of a decision and its execution to software. Existing checkout, fraud, card-network, and banking systems assumed a human acted in the moment. Agentic payments must establish who the agent represents, what it may do, and how the payment is controlled.\n\nSome of that infrastructure is live. Some is limited to pilots, betas, or proposals. Most of it is driven by the potential to reshape business as we know it and by the fear of becoming irrelevant.\n\nThis is a map of the market as of July 2026.\n\n## Three ways of agentic payments\n\nAgentic payments covers three distinct flows: commerce, machine payments, and treasury.\n\nEach flow has the same cast. The *principal* is the person or business whose money and authority are at stake. The *agent surface* acts for it. The *counterparty* is the merchant, service, bank, or other party on the receiving side.\n\n| Flow | Principal | Agent surface | Counterparty |\n|---|---|---|---|\n| Commerce | Consumer / cardholder | ChatGPT, Gemini, or another shopping agent | Merchant / retailer |\n| Machine payments | Agent owner or business | Agent with a wallet | API, tool, or data-service provider |\n| Treasury | Business / finance team | Treasury agent | Bank, vendor, employee, or supplier |\n\nCommerce gets most of the attention and most of the protocols, led by OpenAI and Google. Bain’s $300–500 billion projection applies to the commerce slice; it says little about the eventual size of machine payments or treasury.\n\nAI-*assisted* still has a human clicking somewhere: the agent finds options, drafts a comparison, and a person confirms.\n\nAI-*executed* is the agent completing the action within rules set in advance: a budget, a policy band, or a standing instruction. Most shipped examples remain assisted; execution is emerging unevenly across the three flows.\n\n## Agentic Commerce\n\nCommerce lets an agent take a buyer from product discovery to a merchant checkout. It has the most visible protocol competition.\n\nEvery agent purchase has to answer four questions:\n\n- Can the agent find and talk to the store?\n- Is this a real, recognised agent?\n- May it make this specific purchase?\n- How does the merchant get paid?\n\n### Commerce at a glance\n\n| Step | The agent needs | The protocols answer |\n|---|---|---|\n| Find | A way to search a merchant’s catalog and call its systems | MCP; UCP catalog |\n| Authorize and check out | Proof it may buy, plus a checkout interface | ACP + SPT; UCP + AP2 |\n| Pay | A credential the merchant can accept and a rail to settle on | Cards and processors; emerging USDC paths |\n| Establish trust | Proof of agent identity and risk controls | Web Bot Auth; Visa; Mastercard; issuers and PSPs |\n\n### Finding a merchant\n\nThe Model Context Protocol (MCP), from Anthropic and now under the Agentic AI Foundation, defines how an agent finds and calls tools on a merchant’s system. It is not commerce-specific. A merchant’s server might expose a catalog search, twenty-five payments tools, or both.\n\nThe Universal Commerce Protocol (UCP) catalog spec standardizes names such as `search_catalog`\n\nand `get_product`\n\n, reducing the need for bespoke merchant integrations. Shopify’s Storefront MCP server has conformed to it since April 2026. UCP spans catalog and checkout; the Agentic Commerce Protocol (ACP) focuses on checkout.\n\n### Two checkout paths: ACP and UCP\n\nACP (OpenAI, Stripe) and UCP (Google, Shopify, and a broader retail and card-network coalition) define competing checkout mechanisms. A merchant that implements only one is not automatically available to agents using the other.\n\nACP is a narrow HTTP/JSON checkout API. It hands off payment through Stripe’s Shared Payment Token (SPT) without exposing a raw card number. It powered ChatGPT’s Instant Checkout.\n\nIn March 2026, OpenAI said the initial version lacked the flexibility it wanted. It began letting merchants use their own checkout experiences while focusing on product discovery.\n\nReading between the lines of official press, merchants refused to become the ghost kitchen for OpenAI’s ChatGPT and pushed back against the Instant Checkout.\n\nUCP spans discovery through checkout. It has native bindings into MCP and agent-to-agent (A2A) systems, with the Agent Payments Protocol (AP2) underneath for authorization.\n\nUCP is now live for Ulta Beauty shopping in Google’s AI Mode and Gemini. Google and Ulta announced the rollout in April 2026. Visa, Mastercard, Amex, Stripe, Shopify, and more than 20 retailers have endorsed it.\n\n### Proving the buyer’s authority\n\nAP2 provides UCP’s authorization layer. Its signed Checkout and Payment Mandates record what a user authorized. They create a tamper-evident record, not a one-time yes. AP2’s Payment Mandate proves authority; it does not replace the payment credential.\n\nACP does it differently. Its checkout API uses merchant-defined bearer authentication and passes a scoped payment token to the merchant.\n\nIn April 2026, Google donated AP2 to the FIDO Alliance. Visa and Mastercard now co-chair the working group that steers it. Mastercard also contributed Verifiable Intent, a complementary proof of user authorization.\n\n### Payment identity: Visa and Mastercard\n\nVisa and Mastercard run separate payment-identity programmes that register agents and apply payment controls.\n\nVisa’s answer is the Trusted Agent Protocol (TAP), an identity and request-integrity component of the broader Visa Intelligent Commerce program. TAP proves who the agent is and detects invalid, expired, or replayed signed requests; it does not itself move money. Visa Intelligent Commerce adds payment and control capabilities.\n\nMastercard’s Agent Pay combines registered-agent identity, Agentic Tokens, and transaction controls. Mastercard describes the tokens as dynamic, cryptographically secure credentials carrying purchase-intent data such as transaction limits and validity windows.\n\nVisa and Mastercard use different systems. There is not yet one standard way for merchants to accept agent payments.\n\n### Request signatures: Web Bot Auth\n\nWeb Bot Authentication (Web Bot Auth) is an emerging approach to authenticating automated HTTP clients with HTTP Message Signatures under RFC 9421. It lets a site verify a signed request without making it a commerce or card-network protocol.\n\nAn IETF working group is taking the work forward. Cloudflare, Amazon, Akamai, and OpenAI have announced support or implementations.\n\nMastercard incorporates Web Bot Auth into Agent Pay, and American Express has announced planned compatibility.\n\nVisa’s TAP also uses RFC 9421-style signed requests.\n\nBoth share the same basic approach—signed requests—but merchants still face different protocols and verification rules.\n\n### Risk and fraud\n\nA merchant facing an incoming agent request has to check two things: is the *agent* legitimate, and *who is it acting for*?\n\nSardine and Forter add different pieces of the risk stack: identity verification, device and behavioral signals, transaction-risk assessment, fraud controls, and monitoring.\n\nCard-not-present fraud rules assumed a human confirmed the purchase in the moment. Agentic commerce makes both agent identity and the human’s authorization part of the dispute trail.\n\nAkamai reports that commerce accounted for 47.9% of all AI-bot traffic across its global network from July through December 2025.\n\n### How the merchant gets paid\n\nAuthorization is not settlement. It tells the merchant that the agent may buy; the merchant still needs a payment credential it can charge.\n\nACP passes an SPT to the merchant. The merchant’s payment service provider (PSP) then processes it through the familiar card path: acquirer, card network, issuer, and settlement. UCP can use a merchant’s existing checkout and payment stack; AP2 records the buyer’s authority, not the payment itself.\n\nStripe says an SPT can be backed by Visa Intelligent Commerce or Mastercard Agent Pay payment methods. These programmes add agent-specific credentials and controls; they do not replace card settlement.\n\nPSPs are trying to keep merchants from implementing every protocol themselves. Stripe, PayPal, Adyen, and J.P. Morgan/Mirakl represent different versions of that merchant-acceptance layer.\n\nSome providers give agents controlled virtual cards instead: Marqeta supplies issuing controls, Alchemy AgentCard connects to Visa Intelligent Commerce, and Agentcard.sh issues single-use virtual Visa cards.\n\nAs an alternate-settlement example, we have built Arc Pay. It supports ACP and UCP over USD Coin (USDC) on Circle’s Arc, demonstrating that alternate rails can work in commerce flows.\n\n## Agentic machine payments\n\nMachine payments let an agent or application pay for an API call, MCP tool, data feed, or other service rather than a shopping checkout. They are often small and frequent, but size is not the defining feature. The main protocols are Coinbase’s x402 and Stripe’s Machine Payments Protocol (MPP).\n\nx402 has live services and a machine-readable directory. When an x402-enabled server receives a request without payment, it returns a 402 Payment Required challenge; the agent pays and retries the request. MPP is live for stablecoin and fiat payments. The open question is whether either can become a broad standard across payment methods and service providers.\n\nx402 began as a stablecoin-only protocol. Its V2 specification opened it to fiat—U.S. ACH bank transfers, European SEPA bank transfers, and cards—through facilitators, though stablecoins remain its primary use case. Coinbase reports 165M+ transactions and roughly $50M in cumulative volume as of April 2026.\n\nCoinbase’s Agentic.Market is a machine-readable directory of x402 services. An agent can use MCP to find and assess a service at runtime; the service returns a 402 challenge, and the agent pays per request. Coinbase donated x402 to the Linux Foundation, whose x402 Foundation became operational in July 2026.\n\nMPP shipped with fiat and stablecoin support. It uses Tempo for crypto and Stripe’s card rails for fiat, via Shared Payment Tokens, and went to mainnet in March 2026.\n\nMPP and ACP share the SPT primitive, but they serve different jobs. ACP uses it for shopping checkout; MPP uses it for machine payments.\n\nCross-company negotiation (something I’ve been chasing since 2016) — an agent agreeing payment terms with a supplier’s agent — remains much less established. It needs shared terms, compatible permissions, and trust between companies.\n\n## Currency: the money moving through those rails isn’t settled either\n\nProtocols move value. They do not agree on what the value *is*.\n\nFiat remains the largest settlement base: real dollars moving over existing Visa and Mastercard rails. TAP signatures and Agentic Tokens are not new money; they identify or control the payment credential.\n\nStablecoins are contested ground. Visa’s stablecoin-settlement activity spans nine blockchains and has reached a $7B annualized run rate; its U.S. settlement pilot uses USDC. Mastercard plans to add settlement in six stablecoins across eight chains, subject to regulatory availability.\n\nIn the machine-native micropayment sample Keyrock tracked from May 2025 to April 2026, 98.6% of 176 million payments settled in USDC. The sample covers on-chain micropayments, not all agent payments.\n\nOn June 30, 2026, Open Standard announced Open USD (OUSD), with more than 140 businesses signed up. The proposed currency would offer free minting and redemption, reserve economics for distribution partners, and an independent partner board.\n\nOpen USD is an attempt to give payment and commerce companies a role in the settlement asset itself, not just the rails that move it. Its founding group includes Visa, Mastercard, Stripe, Amex, Coinbase, BlackRock, Google, Shopify, DoorDash, and hundreds of others. When a new form of money appears, everyone who can wants a seat at the table.\n\n## Agentic Treasury\n\nTreasury lets an agent operate an account under a business’s permissions. It can open accounts, prepare wires, issue cards, and handle vendor-payment workflows.\n\nMeow Technologies launched what it calls an agentic banking platform on April 8, 2026. Its MCP tools can create virtual cards with merchant and spend controls and can draft transfers.\n\nMeow and other providers now expose agent-facing tools. Production access remains bounded by approval rules, permissions, or read-only interfaces. No shared treasury protocol or reliable market-volume measure has emerged.\n\nEvery MCP-initiated transfer is placed in pending approval. A human approves it in the dashboard. OAuth scopes, roles, and any multi-factor authentication (MFA) requirement are checked on each call.\n\nGriffin, a UK banking-as-a-service platform, has a beta MCP server with tools for opening operational accounts and creating and submitting payments. Its safeguards prevent live organisation API keys from being exposed to the server.\n\nAt the enterprise end, J.P. Morgan frames agentic treasury as a control loop: sense, predict, decide, execute, audit. In its illustrative scenario, a hedge within a pre-authorized policy band can move to rapid approval while a recommendation outside the band escalates to the CFO.\n\nTo illustrate the potential: Circle’s treasury team moved more than $68M across eight entities in eleven flows in under 30 minutes in one month, using USDC via Circle Mint. The comparable fiat-wire process took one to three days.\n\nCircle’s transfers were human-operated through established approval practices, not agent-initiated.\n\nThe size of Agentic Treasury is unclear. Broader “agentic AI in banking” forecasts bundle chatbots, fraud detection, and credit decisioning with money movement, so they do not measure this flow cleanly. Published evidence on agent-initiated account activity is still thin.\n\n## Where this leaves you\n\nEach flow is unfinished in a different way.\n\nCommerce has two rivalries: ACP against UCP for checkout, and Visa against Mastercard for agent identity and payment-control frameworks.\n\nConvergence is selective. Web Bot Auth is becoming a common request-authentication approach, and Visa and Mastercard now co-chair FIDO’s AP2 work. Stripe’s SPT can support both Visa Intelligent Commerce and Mastercard Agent Pay. ACP still does not use AP2.\n\nMachine payments are developing around paid, machine-readable services. The Linux Foundation’s x402 Foundation governs x402, not Stripe’s separate MPP protocol.\n\nCurrency is unsettled too: fiat rules commerce, while USDC dominates the observed on-chain machine-payment sample. Almost everybody in the space has backed Open USD, a proposed shared stablecoin that would compete with USDC.\n\nTreasury is newest and least standardized. Banks and banking-as-a-service (BaaS) platforms are cautiously shipping their own MCP servers and permission models.\n\nAgentic payments is three adjacent markets, each still deciding how an agent finds the relevant merchant, service, or account; proves it is authorized; and moves money.\n\n## Timeline\n\nKey launches, rollouts, and governance moves, grouped by market layer and placed in calendar time.\n\n## Who’s building what, with whom\n\nThe protocols, payment programmes, and companies shaping how agents discover, authorize, and pay.\n\n**Sources**\n\nMarket sizing and phase framing:\n\n[Bain & Company — 2030 Forecast: How Agentic AI Will Reshape US Retail](https://www.bain.com/insights/2030-forecast-how-agentic-ai-will-reshape-us-retail-snap-chart/)[J.P. Morgan — 5 payments trends to watch in 2026](https://www.jpmorgan.com/insights/payments/trends-innovation/five-payment-trends-in-2026)\n\nCheckout, identity, and the Visa/Mastercard/Coinbase rivalry:\n\n[Visa Developer — Visa Intelligent Commerce](https://developer.visa.com/capabilities/visa-intelligent-commerce)[Visa Developer — Trusted Agent Protocol](https://developer.visa.com/capabilities/trusted-agent-protocol)[Visa Developer — TAP specifications](https://developer.visa.com/capabilities/trusted-agent-protocol/trusted-agent-protocol-specifications)[Visa — Trusted Agent Protocol and x402 interoperability](https://investor.visa.com/news/news-details/2025/Visa-Introduces-Trusted-Agent-Protocol-An-Ecosystem-Led-Framework-for-AI-Commerce/)[Visa — Agentic Ready in Europe](https://www.visa.co.uk/about-visa/newsroom/press-releases.3457328.html)[Mastercard — Agent Pay framework](https://www.mastercard.com/us/en/news-and-trends/stories/2025/agentic-commerce-framework.html)[FIDO Alliance — FIDO Alliance to Develop Standards for Trusted AI Agent Interactions](https://fidoalliance.org/fido-alliance-to-develop-standards-for-trusted-ai-agent-interactions/)[PayPal — PayPal Launches Agentic Commerce Services to Power AI-Driven Shopping](https://newsroom.paypal-corp.com/2025-10-28-PayPal-Launches-Agentic-Commerce-Services-to-Power-AI-Driven-Shopping)[J.P. Morgan — Mirakl Nexus & J.P. Morgan Payments Enable AI Agent Checkout](https://www.jpmorgan.com/payments/newsroom/mirakl-nexus-agentic-commerce)[Marqeta — JIT Funding](https://www.marqeta.com/platform/jit-funding)[Marqeta — Commando Mode](https://www.marqeta.com/docs/core-api/commando-mode)[Alchemy — AgentCard and Visa Intelligent Commerce](https://www.prnewswire.com/news-releases/alchemy-introduces-agentcard-a-payments-and-identity-platform-for-ai-agents-built-on-visa-intelligent-commerce-302803786.html)[Agentcard — Terms of Use](https://www.agentcard.sh/terms)[Arc Pay — API reference (ACP and UCP payment provider support)](https://arcpay.ai/docs/api)[OpenAI — Powering product discovery in ChatGPT](https://openai.com/index/powering-product-discovery-in-chatgpt/)[Google Developers Blog — Universal Commerce Protocol](https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/)[Ulta Beauty — Gemini-enabled shopping](https://www.ulta.com/investor/news-events/press-releases/detail/226/ulta-beauty-and-google-introduce-gemini-enabled-shopping)[ACP specification](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol)[AP2 specification](https://ap2-protocol.org/ap2/specification/)[Stripe — Supporting additional payment methods for agentic commerce](https://stripe.com/blog/supporting-additional-payment-methods-for-agentic-commerce)\n\nWeb Bot Auth and automated-client verification:\n\n[IETF — Web Bot Authentication working group](https://datatracker.ietf.org/wg/webbotauth/about/)[Cloudflare — Agentic-commerce collaboration](https://www.cloudflare.com/press/press-releases/2025/cloudflare-collaborates-with-leading-payments-companies-to-secure-and-enable-agentic-commerce/)[Akamai — Web Bot Authentication](https://www.akamai.com/blog/security/redefine-trust-web-bot-authentication)[AWS — WAF support for Web Bot Auth](https://aws.amazon.com/about-aws/whats-new/2025/11/aws-waf-web-bot-auth-support/)[AWS — AgentCore Web Bot Auth](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-web-bot-auth.html)[OpenAI Help Center — ChatGPT agent allowlisting](https://help.openai.com/en/articles/11845367-chatgpt-agent-allowlisting)\n\nAgentic machine payments — settlement, direct agent-to-resource payment, and agent-to-agent payments:\n\n[Coinbase — Introducing Agentic.Market](https://www.coinbase.com/developer-platform/discover/launches/agentic-market)[Stripe — Introducing the Machine Payments Protocol](https://stripe.com/blog/machine-payments-protocol)[x402 — Protocol overview](https://x402.org/)[x402 — Introducing x402 V2: Evolving the Standard for Internet-native Payments](https://x402.org/x402-v2-launch/)[Linux Foundation — Launching the x402 Foundation](https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol)[Linux Foundation — Operational Launch of the x402 Foundation](https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications)[Adyen — Adyen Agentic: The Universal Translator for the Next Era of Commerce](https://www.adyen.com/press-and-media/adyen-agentic)[Tempo — Mainnet](https://tempo.xyz/blog/mainnet/)\n\nCurrency:\n\n[Visa — Stablecoin settlement expansion](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.22336.html)[Visa — USDC settlement pilot](https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21951.html)[Mastercard — Mastercard expands settlement capabilities to include stablecoin](https://www.mastercard.com/us/en/news-and-trends/press/2026/june/mastercard-expands-settlement-capabilities-to-include-stablecoin.html)[Open Standard — Introducing Open USD](https://joinopenstandard.com/blog/introducing-open-usd)[Keyrock — Who pays the agent?](https://keyrock.com/who-pays-the-agent/)\n\nAgent-operated accounts and treasury:\n\n[J.P. Morgan — Proof of Movement: AI, Autonomy and the New Architecture of Corporate Cash](https://www.jpmorgan.com/payments/newsroom/agentic-ai-corporate-cash-treasury-management)[Circle — Intercompany Treasury Management with USDC](https://www.circle.com/case-studies/circle-treasury-management)[Meow MCP security](https://developer.meow.com/mcp/security)[Meow MCP tools](https://developer.meow.com/mcp/tools)[Griffin MCP server](https://docs.griffin.com/docs/guides/griffin-mcp-server)\n\nRisk and fraud:\n\nShared infrastructure:", "url": "https://wpnews.pro/news/agentic-payments-how-agents-move-money", "canonical_source": "https://zdne.org/articles/agentic-payments/", "published_at": "2026-08-27 12:26:02+00:00", "updated_at": "2026-08-27 12:49:02.409183+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-agents", "ai-products", "ai-policy"], "entities": ["OpenAI", "Google", "Anthropic", "Agentic AI Foundation", "Shopify", "Stripe", "Bain"], "alternates": {"html": "https://wpnews.pro/news/agentic-payments-how-agents-move-money", "markdown": "https://wpnews.pro/news/agentic-payments-how-agents-move-money.md", "text": "https://wpnews.pro/news/agentic-payments-how-agents-move-money.txt", "jsonld": "https://wpnews.pro/news/agentic-payments-how-agents-move-money.jsonld"}}