Visa has Intelligent Commerce, Mastercard has Agent Pay, Google has published a protocol called AP2, OpenAI and Stripe have another, PayPal is bringing its wallet into ChatGPT and Coinbase proposes that agents pay in stablecoins. In little more than a year everyone who moves money in the world has announced their own way of letting software move it.

Lined up, they give the impression of a building site where everyone is building the same door on different walls.

Payment is the solved part

Giving an agent a means of payment is a problem the card networks have known how to handle for years. Instead of the real number the agent receives a token, tied to it, with a spending cap and sometimes a list of merchant categories, and if something goes wrong that token is switched off without touching the card.

It works, and it is a huge step forward from pasting card details into a chat. The merchant gets paid, the network recognises that a registered agent is on the other side, the customer sees the charge.

Who said yes

When I try to follow one of these transactions to the end I always arrive at the same question, and it is about the person. Who authorised that agent, with which identity, and where is it written what they had granted?

In most cases the answer is an account. The user signed in to a platform, linked a card, ticked a box, and from that moment the proof of their consent lives in that platform's records. Google goes one step further with AP2 and introduces signed mandates that record the user's instructions and approvals, and that is the direction I find most serious.

The crux is where the signature comes from. If the identity of the person delegating is the one a platform collected at sign-up, the bank receiving the request has to trust the platform. If it comes from a document issued by a State and kept on the person's phone, the bank can check it on its own.

Too many protocols for one customer

Then there is a more down-to-earth matter. A merchant today would need to work out which agent is contacting them, with which protocol and on which network, and Visa and Mastercard themselves say they support each other's, because nobody can afford to be left out.

For the buyer, fragmentation has a different cost. The permission I gave my assistant inside one ecosystem is not valid in another, and if I change assistant I start again, with a new account and a new box to tick.

A mandate that travels with the person

In Europe we have a possibility that is missing elsewhere. By the end of the year Member States will have to offer citizens a digital identity wallet, and that wallet can sign, besides "this is me", also "this agent may do this, up to here, until this date".

A mandate like that belongs to whoever issued it. The agent I chose presents it, the bank I already have verifies it, and neither of them needs to be a customer of the same supplier. It is the hypothesis I am working on with Plenipo, and it is worth stating with caution: card tokens will stay the way money moves, what is missing is the sheet of paper that says who allowed it.

A year from now fewer of these protocols will be left, and the merchants and banks that have to integrate them will be the ones to decide. I expect the survivors to be those able to answer a complaint, when a customer says they never authorised that purchase.

Sources