On Friday 13 November OpenAI introduced ChatGPT Wallet. Anyone with a Pro subscription in the United States can register a Visa, Mastercard or American Express card, ask their agent to buy something and approve the purchase, while the shop receives a substitute credential instead of the real number. In August someone had already found it in the code of the Windows app, inside a window titled "Introducing ChatGPT Wallet", so the surprise was relative.

I care little about when it will reach Europe. I care that the word wallet is appearing everywhere, and that it is being used for very different objects.

The wallet that pays

OpenAI's is a place to keep a card for reuse, with no balance to top up and no crypto. PayPal has announced it will bring its own into ChatGPT, Meta's agent according to PCWorld already uses one provided by Stripe, able to generate a virtual card valid for a single purchase, and the card networks offer tokens with a spending cap.

They are all answers to the same question, which money does the agent pay with. It is a legitimate question, and the answers get better month by month.

Identity in your pocket

In Europe the same word means something else. The EUDI Wallet, which Member States must make available by the end of the year, holds an identity issued by the State and presents it to those entitled to ask for it. There is no money inside it, there is the ability to prove who we are and to sign what we decide.

Confusing the two objects produces concrete misunderstandings. A payment wallet inside an assistant knows that a card was linked to an account, and from then on treats whoever uses that account as the holder. An identity wallet knows who the person is, and can put in writing what that person allowed.

How many will arrive

Every assistant with enough users will have its own, because controlling the moment of payment is worth too much to leave to others. So we will have the ChatGPT wallet, the one from the phone's assistant, the marketplace's, each with its own rules on limits, approvals and refunds.

For those who use them it means repeating the same configuration elsewhere, and discovering that the cap set in one place does not hold in another. For a bank it means receiving requests from different parties that all claim to act for the same customer, each with a proof of consent kept in its own archives.

Two days ago Anne Boden, who founded Starling, presented Lockwood, a current account that is not open yet and is designed for this situation, where the bank keeps the list of agents and their permissions. It is a serious answer and it goes in the opposite direction from the platforms' wallets, because it brings control back to the side that holds the money.

One place for permissions

Between the assistant's wallet and the list kept by the bank there is a third possibility, which in Europe we have almost by accident. If permissions are born in the person's identity wallet, signed by them, any bank can read them and any agent can present them, and the payment wallet goes back to doing its job, which is paying.

That is what Plenipo is trying to demonstrate, for now in a sandbox and with test identities. I do not know which of the three models will prevail and I suspect they will coexist for a long time. I do know that in a few years each of us will have given several pieces of software permission to spend, and that we will want to find them all in one place, the day we decide to remove one.

Sources