Search for AI agent payment rails and you get the same duel on every page: cards versus stablecoins. It is a well documented argument. It is also written for a payer incorporated in the United States, and it quietly drops the rail a UK or EU business is most likely to end up using.
There are three rails, not two. The third one changed twice in the last eighteen months while the duel was going on, once by scheme launch in London and once by regulation in Brussels.
A rail is not a protocol
Most of what ranks for this phrase is protocol writing in rail vocabulary, which is why the field looks more crowded than it is.
The useful split is four layers: identity (is this agent who it says it is), authorization (did a human approve this, and within what limits), checkout (how the agent completes a purchase with a specific merchant) and settlement (how the money actually moves). x402, AP2, ACP and MPP are mostly layers rather than rivals, and a single agent transaction can touch three or four of them at once. AP2 is authorization. ACP is checkout. x402 and MPP are settlement mechanics.
None of those is a rail. A rail is the thing underneath that moves value between two balances. Google's protocol is explicit about the separation: AP2 issues signed Mandates as verifiable credentials and is deliberately payment agnostic, covering cards, stablecoins and real time bank transfers alike. It is designed not to care which rail you pick.
So pick the rail on its own terms.
Rail one: cards, with an agent shaped token on top
The card rail extends the existing four party model by issuing the agent a scoped token instead of a card number. Reach is the argument for it, and it is a strong one. Cards account for 84 percent of UK retail spending by turnover, costing businesses 1.5bn GBP a year in fees, and US card networks process 95 percent of UK card transactions. Whatever your agent wants to buy, a card almost certainly reaches the seller, and the dispute machinery behind it is decades old.
The limit is arithmetic, not engineering. Card pricing carries a fixed component per transaction that does not shrink as the ticket does. Below some value the fee exceeds the thing being bought, which is why nobody has built a working card based micropayment product in forty years of trying. Agents generate exactly that traffic: a model call, a lookup, a scraped page.
Cards are the right rail for an agent buying a 300 GBP flight. They are structurally the wrong rail for an agent buying 300 API calls.
Rail two: bank transfer, the rail the US pages leave out
Account to account payments skip the card networks entirely. In the UK that means Faster Payments, in the euro area SEPA. This is the rail the cards versus stablecoins framing has no column for, and it is the one that moved.
What changed in the UK on 2 June 2026
The commercial Variable Recurring Payments scheme went live on 2 June 2026 under the UK Payments Initiative, the first new major UK payment scheme since Faster Payments in 2008, giving a single rulebook and a shared commercial model rather than bilateral deals bank by bank. The customer authorises a long lived mandate bound by parameters, a maximum amount, a frequency and an expiry, and payments are then initiated account to account over Faster Payments.
Read that description again with an agent in mind. A parameter bound, revocable, bank enforced spending envelope is the primitive every agentic payment protocol has been trying to reconstruct in software. Here it is enforced by the account holding bank instead.
The regulator's framing is deliberately open ended: the FCA expects the UKPI scheme to act as a catalyst for other commercial open banking schemes and will consult on a long term regulatory framework by the end of 2026. The ecosystem underneath it is not small. Open banking passed 16 million active users with 53 percent year on year growth in payments, VRPs already account for 16 percent of open banking payments, and industry judged that roughly 75 percent current account coverage was needed for a scheme to be worth building on.
Now the honest limit, because the vendor posts skip it. Wave 1 covers regulated and trusted sectors, utilities, government, charities and financial services. General e-commerce is Wave 2. Today this is a rail for paying billers, not for an agent paying an arbitrary merchant, and anyone telling you cVRP is an agent payment rail right now is describing the second half of 2026 at the earliest.
What changed in the euro area
The euro side moved by law rather than by scheme. Under Regulation (EU) 2024/886, if the payer's provider has not received confirmation that funds reached the payee within 10 seconds, it must immediately restore the payer's account, and providers must let a payment service user set a maximum amount per day or per transaction for instant credit transfers. Ten seconds is a legal ceiling, and a user settable per transaction cap is a spending control that lives at the account, not in a prompt.
Check the deadline that applies to your provider before you assume it is available. Euro area providers had to receive instant euro payments by 9 January 2025 and send by 9 October 2025, but payment institutions and electronic money institutions in the euro area have until 9 April 2027, and non euro area providers later still. Plenty of fintech providers are inside that window right now.
Rail three: stablecoins, where the machine traffic actually is
For sub dollar, high frequency, machine to machine traffic, this rail exists because the others cannot price the transaction.
The mechanism is HTTP 402. The agent calls an endpoint, gets a 402 quoting a price, pays, retries with proof, and the server serves. x402 has processed over 140 million cumulative transactions with more than 600 million dollars in payment volume, while MPP launched on 18 March 2026 with over 100 integrated service providers, adding a session layer and settling on Tempo, a chain with roughly 0.5 second deterministic finality and no native gas token. Settlement in seconds, fees measured in fractions of a cent, no account opening on either side.
Two cautions worth more than the headline numbers.
First, the public counts diverge. A separate research write up puts approximately 69,000 active agents and 165 million x402 transactions at 50 million dollars in volume as of April 2026, alongside the Keyrock finding that 98.6 percent of AI agent transactions settled in USDC. A transaction count and a volume figure that differ by an order of magnitude between two sources are a sign that much of the traffic is infrastructure testing rather than commerce. Treat any single figure as a dated snapshot, not a run rate.
Second, settlement is final. That is the property that makes it fast and cheap, and it is also the property that means a misfiring agent has no dispute form to fill in. Your recovery has to be designed in beforehand, in the mandate and the contract.
The bridge that looks like a fourth rail
You will see virtual cards that spend a stablecoin balance at any card accepting merchant. It is a genuinely useful product, and it is not a fourth rail. It is rail three funding rail one, with the conversion happening at the point of purchase. Price it and govern it as a card payment, because that is what the merchant receives.
How to choose: three questions, in this order
What is the ticket size? Under a pound or so, a fixed fee floor eats the transaction and only stablecoins survive. Between a pound and a few hundred, everything works and the choice is made on the next two questions. Above that, cards and bank transfer are both fine and the fee delta starts to matter in the other direction.
Does this payment need to be reversible? Cards are the only rail with recourse built in after the fact. Bank transfer and stablecoin settlement are both effectively final, and their protection is preventative: the mandate parameters, the funding limit, the counterparty allowlist. Decide which kind of protection you want before you choose, because you cannot add the first kind later.
Where is the counterparty? Reach is not uniform. Cards reach nearly everyone. Faster Payments and SEPA reach anyone with an account in the right currency zone. Stablecoin rails reach the counterparties who opted in, which today is mostly other software.
Most teams that ship this end up routing rather than choosing: stablecoins under a threshold they set, cards or bank transfer above it. If you are picking a protocol layer, note that it composes, so the three layer view of agent payment infrastructure and how AP2 structures a mandate are the pieces to read before you commit to one stack.
Whichever rail you pick, something has to fund it
Here is the question none of the ranking pages asks. Every one of these rails starts at a balance. Which regulated entity is holding it, and under what permission?
That answer determines what happens to your money if the provider fails, and it does not change when you switch rails. If you have not compared the options, start with what an authorised payment institution is allowed to do and the narrower question of whether agent payments are safe yet.
Ours, stated the way we would want a vendor to state theirs. EXFI is a trading name of EX Financial Solutions Ltd, company number 17105188, which is not itself authorised or regulated by the FCA and acts as a distributor of payment services provided by Gemba Finance Ltd, authorised and regulated by the FCA as a payment institution under FRN 804853. EXFI accounts are payment accounts, not bank accounts. They are not covered by the FSCS. Funds are safeguarded in segregated accounts under the Payment Services Regulations 2017. UK customers, business entities only.
On product scope, the same discipline. EX FI provides multi currency payment accounts with dedicated IBANs and access to SWIFT, SEPA, FPS, BACS and CHAPS today, for business customers. MCP native agent banking primitives and stablecoin settlement are announced roadmap items. They are not live, and we will not describe them as though they were. If you are running several entities and want the funding side settled first, that is the ordinary case for a multi currency business account.
This article is general information about how agent payment rails work and are regulated. It is not legal or financial advice.
What a UK or EU business can do this quarter
Fund agents from a separate balance rather than the main operating account, so the worst case is bounded by design. Keep spending limits at the infrastructure layer, because a limit inside the model is a suggestion. Do not marry a rail: the protocol layer above it is about eighteen months old and built to compose. Then watch two dates, Wave 2 of the cVRP scheme, and 9 April 2027 for euro area payment institutions on instant euro.
FAQ
What is an AI agent payment rail? The system that actually moves the value between two balances: cards, bank transfer or stablecoins. It is distinct from the protocols layered on top, which handle identity, authorisation, checkout and settlement mechanics. AP2 and x402 are not rails, and a single transaction can use several protocols over one rail.
Can an AI agent pay by bank transfer in the UK? The primitive now exists. The commercial VRP scheme gives a long lived, parameter bound mandate that settles over Faster Payments, which is close to exactly what an agent needs. But the first wave covers regulated and trusted sectors such as utilities, government and financial services, not open merchant payments, so an agent buying from an arbitrary shop is waiting on the e-commerce wave.
Why can't AI agents use credit cards for tiny payments? Because card pricing includes a fixed per transaction component that does not shrink with the ticket. Below a certain value the fee costs more than the thing being bought. That is an economic limit rather than a technical one, and it applies whether or not the payer is software.
Are stablecoin agent payments reversible? No. On chain settlement is final once confirmed, which is the same property that makes it fast and cheap. There is no chargeback mechanism, so any recovery has to be built in advance through funding limits, mandate parameters and contract terms rather than claimed afterwards.
Does the EU Instant Payments Regulation mean my provider already sends instant euro payments? Not necessarily, and this catches people out. Euro area banks had to receive from January 2025 and send from October 2025, but payment institutions and electronic money institutions in the euro area have until April 2027, with non euro area providers later. Ask your provider which category it falls into rather than assuming.