Linux Foundation Appoints x402 Executive Director as Members Report 75 Million AI Agent Payments in 30 Days
Oct. 28, 2026 • Deep Dive • AI in Fintech
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.
The Linux Foundation appointed payments veteran Michael Hursta executive director of the x402 Foundation on October 1, 2026, putting new leadership behind a payment protocol designed for transactions initiated by autonomous AI agents. The appointment comes as developers and payment companies work through a basic mismatch: agents can request digital services without a person at a screen, but conventional checkout often expects one.
Hursta will steer adoption across more than 50 member institutions. In September, x402 Foundation members reported handling more than 75 million agentic payment transactions during a single 30-day window. At Sibos 2026 in October, Coinbase and Amazon Web Services showcased production agentic payment rails linking cloud compute tasks to small settlements triggered through HTTP 402. Together, the developments show how payment authorization and settlement are being adapted to software that acts on a user’s behalf.
Why Existing Checkout Can Stop an Agent
The economics and design of conventional card payments present separate problems for machine-to-machine transactions. Traditional credit card pricing of around 2.9% plus $0.30 per transaction makes a standalone sub-dollar API call difficult to justify, and fractional-cent calls uneconomic without batching or another settlement method. An API call is a request from one software service to another; an agent may need to make many such requests while completing a task.
Card authorizations can also require interactive checks, including 3-D Secure challenges and CAPTCHAs. Those controls are built around human participation. A headless agent—software operating without an interactive browser session—may be unable to complete the challenge without intervention. Removing a person from the checkout flow therefore creates both a payment-execution problem and a question of how to verify what the person actually authorized.
x402 Handles Payment at the HTTP Request
Coinbase’s x402 uses the HTTP 402 “Payment Required” status code defined in RFC 9110 to let an API and its caller negotiate payment as part of a request. Its design supports per-request settlement in USDC, a stablecoin, with payment information carried in HTTP headers. That makes a small digital-service charge part of the exchange between software systems rather than a separate, human-facing checkout.
Coinbase transferred governance of x402 to the Linux Foundation in April 2026. The resulting independent x402 Foundation is backed by participants including Google, Mastercard, Stripe, Visa, Circle and Amazon Web Services. That governance structure matters because a protocol intended to work across services and payment providers needs adoption beyond its original developer.
Transaction counts indicate activity, but they do not, on their own, establish the scale of commercial spending. Developer and consortium accounts have cited cumulative x402 totals ranging from 50 million to 154 million transactions since launch. Independent onchain analytics, meanwhile, put active daily settlement volume at roughly $28,000 to $800,000, with median payments between $0.20 and $0.32. Those figures leave room for different interpretations of how much activity reflects sustained enterprise use rather than low-value testing.
Authorization and Alternative Payment Paths
Google’s Agent Payments Protocol, or AP2, addresses a different part of the transaction. Its Intent Mandates and Cart Mandates form tamper-evident, cryptographically signed records linking a user’s authorization to what an agent buys. Google contributed AP2 to the FIDO Alliance in April 2026 for vendor-neutral governance and standardized integration of verifiable credentials across banking partners. Google and the alliance later deployed AP2 specification version 0.2, introducing signed “Human-Not-Present” checkout and payment mandates for autonomous operations.
AP2 and x402 are therefore not necessarily substitutes. AP2 is designed to establish authorization and verify intent; x402 can provide an HTTP-based execution and stablecoin settlement path. Other approaches are also being developed. Stripe and Tempo submitted a Machine Payments Protocol draft to the Internet Engineering Task Force on March 30, 2026, targeting session-based billing through off-chain vouchers for agent workflows.
Card networks are working on ways to retain card-based payments in agent-initiated commerce. Mastercard’s Agent Pay uses tokenized card credentials through MDES, while Visa’s Trusted Agent Protocol was developed with Cloudflare. These efforts point to a choice of payment rails rather than a settled winner. The common requirement is to let software complete an authorized purchase without relying on a human to answer every checkout prompt.
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.