
Agents are about to start spending real money. Institutions will need to know who authorized it.

x402 is an open standard that lets software request and settle a payment as part of an ordinary web interaction. It was incubated at Coinbase, and on April 2, 2026 the x402 Foundation launched under the Linux Foundation, with Coinbase contributing the protocol. Forty organizations joined at launch, with premier members including AWS, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, the Solana Foundation, Stripe, and Visa. That’s a serious list for a protocol this young, and it’s why vendor-neutral governance matters. Nobody wants the payment layer for agents owned by one company.
It’s early. The Foundation’s public dashboard showed about 75 million transactions but only about $24 million in volume over the prior 30 days, which tells you most of this is small, machine-to-machine payments. That’s the point. It’s the plumbing before the volume.
An agent that pays for an API call or a dataset is a software feature. An agent that pays on behalf of a bank is a control problem.
We’ve spent years building the infrastructure institutions use to prove what happened: who acted, under which policy, with whose keys. Staking, custody, MPC wallets. The same questions come up the moment an agent holds a wallet. Who authorized this agent to spend? What’s its limit? Which policy applied? Where’s the audit trail when compliance asks in six months?
Right now the standard solves how an agent pays. For regulated institutions, the harder part is how an agent is allowed to pay. That’s the trust layer, and it’s where we can help.
Work with large banks on the trust layer. The institutions that will let agents move money are the ones that have to answer to regulators. We’ll work with large banks to define what that layer needs: who can authorize an agent, what limits apply, how approvals work, and what the audit record looks like.
Take part in the working groups. The standard is being shaped now, in the open. We’ll bring what we’ve learned about key custody, policy enforcement, and compliance to the groups where those decisions get made.
Build reference implementations with our customers. A standard becomes real when someone ships it. We’ll build a few reference implementations with institutions from our customer base and share what we learn, so the next team doesn’t start from zero.
If you’re building agents that need to pay, or you’re an institution working out how to let them, get in touch. Select “Agentic Payments” in the form so it reaches the right team. We’d like to hear from you.
Tell us about your market access and infrastructure requirements. Our team will be in touch to help you implement the right solutions for your institution.