Coinbase Demonstrates Agentic AI Payments at Sibos as AWS Expands x402 Support
Oct. 13, 2026 • Article • AI in Fintech
Coinbase demonstrated machine-to-machine AI payment workflows at Sibos 2026 in Miami Beach, highlighting the Model Context Protocol, Agent-to-Agent protocol and its x402 payment standard. The demonstration followed the August general availability of Amazon Bedrock AgentCore Payments, which incorporates Coinbase Developer Platform wallet infrastructure and x402 settlement. The AWS service supports Coinbase Developer Platform and Stripe Privy wallets for autonomous USDC microtransactions, while keeping developer credentials separate from AI agents and applying deterministic spending limits.
The work connects a conference demonstration to infrastructure already available to developers. Coinbase and AWS had also enabled publishers and API endpoints using AWS CloudFront and AWS WAF to monetize autonomous agent traffic through x402. Coinbase Institute research argues that AI agents need sub-cent stablecoin payments, although that argument is not evidence of transaction volumes. The developments show how payment authorization, wallet access and settlement are being assembled for agent-initiated transactions, without establishing how widely the technology is used.
Coinbase demonstrated machine-to-machine AI payment workflows at Sibos 2026, highlighting protocols intended to let software agents interact and pay for services. The demonstration in Miami Beach put x402, Coinbase’s internet-native payment standard, alongside the Model Context Protocol (MCP) and Agent-to-Agent (A2A) protocol. It also brought attention to Coinbase’s work with Amazon Web Services (AWS), which has integrated wallet infrastructure and x402 settlement into Amazon Bedrock AgentCore Payments.
The distinction matters for developers assessing agent-initiated transactions: a demonstration can show how protocols fit together, while an available platform gives developers tools to build payment workflows. AWS made AgentCore Payments generally available on August 18, 2026, before Sibos took place from September 28 to October 1. The event was organized by SWIFT under the theme “Digital finance for AI-driven economies.”
How the payment protocols fit together
The Sibos demonstration highlighted MCP, A2A and x402 as components of machine-to-machine workflows. The first two relate to how AI systems access context and interact with other agents; x402 addresses the payment step. Their inclusion in the same workflow reflects a practical requirement for autonomous transactions: an agent needs a way to reach a service and a way to pay when that service requires payment.
Coinbase created x402 as an open standard using the HTTP 402 “Payment Required” status code. Its purpose is to support internet-native micropayments without requiring a subscription for each service an agent uses. In that model, a service can request payment as part of an online interaction rather than relying solely on a standing billing arrangement. The Sibos demonstration showed the protocols in a machine-to-machine setting; it did not, on its own, establish how many transactions they process in production.
Coinbase Developer Platform Head of Engineering Yuga Cohler discussed the AWS partnership and the agentic payment protocols demonstrated at Sibos in a FinextraTV interview broadcast on October 12. The interview followed both the conference and AWS’s earlier product launch.
What AWS has made available
Amazon Bedrock AgentCore Payments embeds Coinbase Developer Platform wallet infrastructure and x402 settlement in its platform runtime. It supports both Coinbase Developer Platform wallets and Stripe Privy wallets for autonomous microtransactions using USDC. That gives developers wallet options within the payment service rather than tying every transaction to one wallet provider.
Agent authorization is a separate issue from choosing a wallet. According to the verified product details, AgentCore Payments isolates developer credentials in AgentCore Identity Secrets Manager and signs transactions with short-lived tokens. The design enforces deterministic spending limits without sharing raw private keys with AI agents. Those controls address a central concern in autonomous payments: software can initiate a transaction while access to the underlying credentials remains restricted.
AWS has also expanded AgentCore Payments’ standards support beyond x402 to the Machine Payment Protocol (MPP), co-authored by Stripe and Tempo. That expansion concerns the payment methods the platform can support; the verified information does not establish that the two standards are interchangeable or that one has become the default for agent transactions.
Earlier rollout and the wider push
The AWS integration builds on work announced in June 2026. Coinbase and AWS enabled publishers and API endpoints routed through AWS CloudFront and AWS WAF to monetize autonomous agent traffic using x402 and the Coinbase x402 Facilitator. That work addresses the receiving side of a transaction: services accessed by agents need a way to request and collect payment, not just a way for agents to hold funds.
Research published by the Coinbase Institute on October 7 argued that AI agents require sub-cent stablecoin micropayments and cited x402 on Base as a primary reference implementation. That is the institute’s assessment of the market need, not a reported measure of agent payment activity. It helps explain why Coinbase is emphasizing per-use payments, particularly for interactions too small to fit comfortably into subscription-based access.
Other payments companies are also developing autonomous transaction systems. Visa has announced work on secure agent transactions, with an aim to move trials from pilot phases toward millions of production agent transactions by late 2026. That remains a stated goal, not a reported production result.
Taken together, the Sibos demonstration, AWS product availability and earlier work for publishers show activity on both sides of an agent payment: initiating a transaction and accepting one. The open question is adoption. The verified developments describe protocols, controls and available infrastructure, but provide no transaction volumes for the Coinbase and AWS workflows.
The Linux Foundation appointed payments veteran Michael Hursta executive director of the x402 Foundation on October 1, 2026, as payment systems designed for autonomous AI agents gained attention. Foundation members reported more than 75 million agentic payment transactions in a 30-day period in September, and Coinbase and Amazon Web Services showcased production payment rails at Sibos 2026. Reported transaction counts, however, do not establish the value or commercial character of that activity. The emerging protocols address different obstacles. Coinbase’s x402 enables per-request USDC payments through HTTP, while Google’s Agent Payments Protocol uses signed mandates to connect an agent’s purchases to a user’s authorization. Stripe and Tempo have also proposed session-based billing through the Machine Payments Protocol. These approaches respond to card fees and interactive checkout checks that can impede small, automated transactions. Card networks are developing delegated-identity tools, leaving multiple potential paths for agent payments rather than a single replacement for existing rails.
Mastercard opened developer early access for Agent Pay for Machines (AP4M) on October 20, 2026, releasing buyer- and seller-side APIs, a sandbox and developer toolkits. In a Cloudflare Connect demonstration, marketing agency Hype tested an autonomous agent making nine payments to two merchants within a single budget, without manual billing or account setup. AP4M uses HTTP 402 payment challenges, but differs from crypto-native implementations of the x402 protocol. Its agents issue digitally signed vouchers off-chain; merchants can batch and redeem them later instead of settling every request on-chain. The pilot combined agent wallet infrastructure from Coinbase Developer Platform and BVNK, settlement on Base, and Mastercard’s multi-currency fiat and stablecoin settlement platform. Circle separately expanded its managed payments service to target AI-agent traffic using USDC. Together, the developments show competing approaches to machine-to-machine payments, with different choices about settlement, funding and who manages digital assets.
Visa launched a live pilot with BILL and Billtrust at Money20/20 USA in late October 2026 to test end-to-end B2B invoice payments executed by software agents. The agents act on invoices enterprise buyers have already approved; they do not decide which supplier payments to authorize. Visa’s Trusted Agent Protocol and Agentic Directory are designed to authenticate those agents when they access supplier and merchant portals without shared credentials or manual human login. Separately, Visa has put Commercial Payment Controls into production for eligible issuers in supported regions, allowing businesses to set limits and restrictions on corporate spending. The company plans general availability of Commercial Virtual Authentication and Commercial Supplier Validation in 2027 after pilot completion. Its SESA 2.0 analytics platform has identified more than $600 billion in potentially cardable supplier spend. The pilot tests whether approved invoice payments can be executed through automated workflows while preserving buyer-defined controls.
Mastercard and Visa are advancing different approaches to AI-initiated business payments. At Cloudflare Connect, Mastercard demonstrated an agent making nine payments across multiple service providers under one authorized budget. It also opened early developer access to Agent Pay APIs, a sandbox and toolkits. Visa expanded its commercial agentic suite around a BILL and Billtrust pilot, alongside spend analytics and fraud tools. The distinction is how each approach constrains the agent. Visa’s pilot lets an agent pay invoices that buyers have already approved, using its Trusted Agent Protocol to navigate supplier-portal security without sharing underlying login credentials. Mastercard is testing controls for machine-to-machine transactions, including signed vouchers, agent verification and a score intended to estimate whether an incoming transaction was AI-initiated. Both efforts leave a consequential question for business payments: how responsibility should be assigned when an authorized agent follows its technical instructions but breaches a procurement condition.
Mastercard opened developer APIs, SDKs and a sandbox for Agent Pay for Machines (AP4M) on October 21, 2026. The tools enable autonomous AI agents on Amazon Bedrock to make multi-merchant micropayments over x402 using off-chain signed vouchers. The launch follows Coinbase Developer Platform’s report that cumulative x402 payments across Base and Solana had exceeded 100 million by October. The x402 protocol uses an HTTP 402 response to tell an agent what a service costs and how to pay. Its growing infrastructure includes a Linux Foundation-governed foundation, while alternative approaches use Lightning payments or existing processor rails. Transaction counts, however, do not establish how much genuine agent-led commerce is taking place. TRM Labs found a much smaller pool of plausible commercial trade after screening out other activity. Security questions also remain, including whether a service can receive payment without delivering its output. Developers therefore face choices about settlement, spending controls and proof of service.
CapitalOS completed a $21.9 million Series A financing round on October 21, 2026, led by LGVP. The company plans to expand its engineering team and scale the infrastructure behind its AI-driven money orchestration platform. WEX Venture Capital, Group 11, Great North Ventures, Night Capital and existing early investors also participated. Founded in 2022, CapitalOS helps vertical SaaS and AI platforms offer embedded charge cards, digital wallets and automated bill payments without maintaining in-house licensing or risk operations. Its architecture uses five specialized AI agents across underwriting, capital, compliance, risk and fraud, and support. Property management platform Guesty is an active customer, and CapitalOS reports managing transactions for more than 25,000 active cardholders across dozens of integrated platforms. CapitalOS relies on infrastructure provider Increase and its chartered partner banks rather than replacing depository institutions. The announcement did not disclose a valuation, credit warehouse partner or the identities of its current primary sponsor banks.