Everyone chose wallet anyway
The industry has already run this argument: Apple called it Passbook, then renamed it Wallet in 2015; Google went from Google Wallet to Android Pay to Google Pay and back to Google Wallet; and Samsung folded Samsung Pay and Samsung Pass into Samsung Wallet in 2022. Pay was too narrow once tickets arrived and pass was too narrow once payments did.
There’s other stories too: India has DigiLocker; Vault, locker, store and profile come up in every one of these discussions. Although Tim Berners-Lee's Solid project calls the personal data store a Pod, his company Inrupt, went with data wallet.
Wallet is a bridge word. When Steve Jobs introduced the iPhone he described three things the audience already owned: an iPod, a phone, and an internet communications device. That got everyone across the gap. Nobody describes an iPhone that way now. Bridge words do their job and then get left behind.
The word does not have to win
Does anyone say "let me go into my wallet"? The fact that you pay is the important thing, the container itself does nothing anybody would pay for.
In the meeting we mentioned the use case where somebody moving house is given a smart data wallet for the property. Useful it may be, but it’s about as interesting as a manilla folder. Necessary, passive, and nothing a customer will ever thank you for. But an AI agent that exists to assist your house search, purchase and moving will need somewhere to store everything securely and to be able to share things as it goes through the process. That somewhere is the wallet, but is it yours or does it belong to the agent that manages your house move?
Which is why the naming argument is smaller than it looks. The wallet does not have to win the customer conversation, because that conversation is going to belong to the agent. Here’s a little more on the agent wallet.
The Trusted Agent Triangle sets out what an agent acting for a customer needs. The wallet is where all three come from.
Identity. Financial services already run Know Your Customer. Agents create the same obligation one step out, Know Your Agent. Which agent is this, who does it represent, and which accountable entity is answerable if it gets something wrong?
Preferences. An agent doing real work needs real information. A shopping agent needs clothing sizes and a ship-to address. A travel agent needs an accessibility requirement and a passport expiry date. Strip that context out and the agent produces plausible rubbish at speed.
Delegation. Somebody needs traceability. Who delegated, were they themselves authorised to delegate, and is there a record of the intents, both the task intent and the intent to purchase and pay?
None of this appears in the retail store. I bought a jacket, paid by card, and whether that card lives in leather or an old sock is of no concern to the retailer. The wallet’s the same. It supplies the proof, the context and the audit trail, then stays out of sight.
Two judgement calls
The first is naming the plumbing on the front of the shop. Call it a passenger wallet and you inherit every association Apple and Google have already built, and your customer starts wondering which wallet you mean and whether they need another app.
The second is harder. Selective disclosure is a real privacy gain, but only for a customer who understands what they have just disclosed. Think about the person with no smartphone, the couple sharing one handset, the man who borrows his daughter's phone, or the customer whose entire experience of consent is clicking accept on a cookie banner. If your credential journey has no route for them, you have built a service that excludes the people who already find you hardest to deal with.
Four things for the agentic roadmap
- Work out which roles you occupy. Issuer, verifier, relying party. Most organisations are two of the three, and each carries different obligations.
- Keep the word out of customer-facing copy and name the outcome instead. Use wallet internally, because that is what the engineers, the standards and the auditors call it.
- For each step in a journey, write down the minimum proof you need rather than the data you would like to hold. That list is the start of your credential specification.
- Decide where the delegation record lives when an agent acts for your customer, and who can read it when there is a dispute.
Two questions for your leadership team. If our customer never sees the word wallet, what is the name of the thing they do see, and who owns it? And when an agent buys from us for a customer we have never met, what do we need to see before we accept the order?
Nobody files anything
Nobody is going to maintain a digital wallet, bank accounts and taxes are enough for most of us. But an agent working through a house purchase, an insurance claim or a trip will ask for a document, use it and keep it, because keeping it is how it does the next task. The contents get curated as a by-product of the work, which is the only way a wallet stays current.
So in my mind, the wallet is the enabler but the agent is the product. An agent without a wallet is a plausible stranger. An agent with a wallet can prove who it acts for, stay inside the limits somebody set, and leave a record behind. Your customer will never mention the digital wallet, in the same way they never mention the leather one. So the word to spend a meeting on is not wallet, it’s whatever your customer will call the agent.