
Your bank issued the card. Apple owns the tap. Visa runs the rails. So who owns the customer?
A few weeks ago, I wrote about watching my son play shopkeeper with his cousin, grabbing my iPhone to tap against her toy card machine rather than reaching for the plastic coins scattered across the floor. To him, Apple Pay wasn't a demonstration of tech-savviness. It was simply how you pay.
That moment made me wonder whether cash would even exist by the time he's old enough to open a bank account. But over Christmas, something else happened that pushed my thinking further.
We were at a real till this time. I had cash in my hand, actual notes, already counted out. Before I could pass them over, my son reached instinctively for my phone to pay.
The same gesture. The same assumption. But this time it struck me differently.
In the living room, he was playing. At the checkout, he was trying to help. And in both cases, his mental model was identical: the phone is where money lives. The bank, the scheme, the processor, the acquirer? Invisible. Irrelevant.
If his generation sees the phone as the wallet, the question for the rest of us is uncomfortable: who actually owns the customer now?
When the Bank Was the Brand
For most of the last century, the money relationship was easy to understand.
You chose a bank. You carried its card. You saw its logo every time you opened your wallet or walked down the high street. If someone asked who you banked with, you had a clear answer and probably a story to go with it.
The bank owned the artefacts (the card, the chequebook, the passbook, the branch), the channels (statements through the letterbox, calls from the branch, and later the online banking portal and app), and the trust. My money is with X Bank; if something goes wrong, I call them.
Visa and Mastercard were there, but they were background brands. Processors and acquirers were invisible. Even merchants were secondary in the customer's mental model of who helps me pay.
If you had asked someone in 1995 who helps them pay, they would have answered with a bank's name, not a device or an app.
That world is disappearing.
The New Stack Between You and Your Money
Today, a single tap of my son's finger potentially involves a device (his phone or watch), a wallet (Apple Pay, Google Pay, PayPal, or another app), a scheme (Visa, Mastercard, Amex), a processor or acquirer quietly routing the transaction, an issuer (the bank that actually holds the account), and a merchant, sometimes sitting inside a marketplace or platform of its own.
To him, that entire chain is compressed into one gesture and one object: the phone.
What used to be a straight line between customer and bank is now a stack of brands, all competing to be the one name the customer remembers, or the one icon they tap without thinking.
So when we talk about owning the customer in this environment, we need to be precise. It is no longer as simple as whose logo is on the card.
What Does Owning the Customer Even Mean Now?
In a wallet-first world, ownership is less about legal relationships and more about practical ones. Four dimensions matter.
Owning the interface. Who controls the screen the customer sees when they pay? Increasingly, it is the wallet or platform. That is where cards are added, selected, and sometimes even ranked or recommended. If your card is buried in a list or not supported at all, you are already losing.
Owning the identity. Who does the customer log in with? Apple ID, Google account, Amazon account, a super-app login: these become the anchors of digital life. The bank login is just one credential among many. If the customer changes banks, their identity in the wallet stays the same.
Owning the trust. When something goes wrong (a double charge, a failed refund, a suspicious transaction) who does the customer blame? Who do they contact first? If the experience is mediated through a wallet, the first instinct may be to contact the wallet provider, not the underlying bank or retailer. That is a subtle but powerful shift.
Owning the data. Who sees the full picture of behaviour across merchants, channels, and contexts? A single bank sees what flows through its accounts. A single retailer sees what happens in its stores. A platform that spans payments, shopping, messaging, and identity can see much more, and act on it.
Owning the customer is not about whose name is embossed on the plastic anymore. It is about who owns the interface, the identity, the trust, and the data.
By that definition, banks are no longer the default owners of the relationship. They are one layer in the stack.
The Bank's Dilemma: Front-End, Back-End, or Both?
So where does that leave banks?
Broadly, I see three strategic paths. Most institutions will blend elements of all three, but the emphasis matters.
Fight for the Front-End. This is the we-still-want-to-be-the-primary-brand strategy.
Banks that choose this path double down on best-in-class mobile apps and digital experiences, integrated wallets, budgeting tools, rewards, and offers, and embedded experiences inside other platforms (banking inside a retailer or super-app, for example, but still clearly branded).
They partner with wallets, but they work hard to keep a strong, differentiated presence. They want customers to think: I pay with Apple Pay, but my real relationship is with my bank.
The challenge is that competing with tech giants on UX, speed of iteration, and engagement is hard and expensive. If your app is the one customers open once a week, and theirs is the one they open 50 times a day, you are fighting uphill.
Embrace Being Invisible Infrastructure. This is the AWS-of-money strategy.
Here, the bank accepts that it may not be the primary brand the customer sees. Instead, it focuses on reliability, uptime, and security; speed of authorisation and settlement; compliance, risk management, and capital efficiency; and modern APIs that make it easy for wallets and platforms to build on top.
The bank becomes the regulated, resilient backbone behind many different front-ends. The customer might never know its name, but if it fails, everything fails.
The risk is commoditisation. If you are just one of many interchangeable providers behind the scenes, margins get squeezed. Differentiation has to come from superior service, capabilities, and partnerships, not from brand alone.
Specialise and Add Value. The third path is to focus on segments and services where banks can still be deeply relevant and visible: SMEs and merchants who need more than just a current account (they need cash-flow tools, lending, and integrated back-office support), wealth and financial planning (where advice and trust still matter), and niche consumer segments with specific needs.
Here, banks can offer value-added services: integrated accounting, payroll, retail tools, analytics, and insights that go beyond simple payments.
In this model, the bank's brand still matters, but often in partnership with other platforms. You might be the bank inside a retail platform, but still recognised as a specialist, not just plumbing.
My son may never care which bank sits behind his wallet, but the bank that powers his world still has choices about how it shows up.
Wallets and Platforms: How Do You Earn Complete Trust?
If wallets and platforms increasingly sit at the front of the relationship, the obvious question is: how do they obtain complete trust?
Not just I will try this once, but the kind of trust where a parent is comfortable letting their child tap a phone to pay, and where a customer routes most of their financial life through a single app.
I think there are five ingredients.
Relentless Reliability. Trust starts with the basics: it works, every time. The tap goes through. The balance updates correctly. Refunds appear when they should. Outages are rare, short, and transparently communicated.
Customers will forgive a clunky interface more easily than they will forgive money disappearing for a few hours. Reliability is the foundation on which everything else sits.
Radical Clarity. Money is emotional. Hidden complexity erodes trust.
Wallets that want complete trust need to be radically clear about which funding source is being used for this transaction, what fees apply (especially across borders or currencies), and how refunds, chargebacks, and disputes actually work.
That does not mean dumping terms and conditions on the screen. It means designing flows where the important information is obvious at the moment of decision, not tucked away in a PDF.
Fairness in the Grey Areas. Trust is really tested in the grey areas: fraud, disputes, and edge cases. A card is stolen and used via the wallet. A child makes in-app purchases that a parent did not understand. A merchant does not deliver, and both sides point fingers.
How the wallet behaves here matters more than any marketing campaign. Do they default to computer says no, or do they lean into investigation, empathy, and resolution? Do they make it easy to talk to a human when the stakes are high?
I experienced this recently with Revolut. A couple of payments went through that really should not have, the kind of situation where you brace yourself for weeks of back-and-forth and uncertain outcomes. Instead, the chargeback process was swift, straightforward, and resolved within 14 days, with the money back in my account. No theatre, no endless forms, no feeling like I was fighting my own bank. That single experience did more for my trust than any feature announcement or marketing campaign ever could.
Over time, stories about how a platform behaves in these moments circulate more rapidly than any feature announcement.
Visible Security, Invisible Friction. Security that is invisible can feel like magic, or like nothing at all. For trust, people need to see that you are taking it seriously. That might mean occasional, well-timed step-ups in authentication, clear explanations when a transaction is blocked, and simple, human language around what is happening and why. The art is adding just enough visible security that customers feel protected, without turning every payment into a chore.
Values and Alignment. Finally, there is a softer but increasingly important dimension: does the wallet feel like it is on the customer's side? Are recommendations clearly labelled when they are sponsored? Does the platform use data in ways that feel respectful rather than exploitative?
Complete trust is not just thinking my money is safe here. It is thinking this company will generally do the right thing, even when I am not looking.
Wallets that get all five of these right (reliability, clarity, fairness, visible security, and aligned values) will be in a strong position to own the customer relationship for a generation.
The Retailer's Role: From Acceptance to Experience
So far, this sounds like a story about banks and wallets. But it all happens in one very specific place: the checkout.
That is where retailers live.
Historically, retailers treated payments as a cost of doing business. You accepted cash, then cards, then contactless. You negotiated fees, installed terminals, and tried not to think about it too much.
In a phone-first world, that is no longer enough. Retailers are being pulled into the question of who owns the customer, whether they like it or not.
Retailers as Curators of Trust. When my son taps a phone in a shop, he is not just trusting the wallet. He is trusting the retailer to have chosen a safe, reliable way to take his money.
Retailers signal trust in subtle ways: the quality and modernity of their payment setup, whether the terminal just works or constantly fails, and whether staff can confidently explain what is happening when something goes wrong.
If a retailer's payment experience feels flaky, that distrust can bleed into how customers feel about the wallet and the bank behind it, and vice versa. Retailers, in other words, are co-owners of the trust moment.
From Taking Money to Designing Journeys. In a situation in which the phone is the wallet, the checkout is no longer merely a location to take money. It is a critical touchpoint in the overall customer journey.
Retailers now have to think about channel consistency (does the payment experience feel coherent across in-store, online, and mobile?), speed versus reassurance (how fast can we make this without making it feel risky or confusing?), and integration (can we tie payments to loyalty, receipts, returns, and customer service in a way that feels effortless?).
A clunky, fragmented payment experience can undo a lot of good work done earlier in the journey. A smooth, reassuring one can be the last push that turns a casual browser into a loyal customer.
Data, Insight, and the Battle for the Relationship. Retailers sit on a rich seam of data: what people actually buy, how often, in what combinations, and at what times. The question is: who gets to connect that data to identity and payments in a way that creates value?
If the wallet owns the identity and the payment, but the retailer owns the product and visit data, collaboration becomes powerful. If each side hoards data, the experience fragments, and the customer loses.
Retailers that lean into open, privacy-respecting data partnerships with wallets and banks can offer more relevant rewards and experiences, understand lifetime value across channels, and reduce fraud and friction at the same time. Those that stay at arm's length risk becoming interchangeable inventory and fulfilment while someone else owns the relationship.
As digital payments become the default, there is also a strategic dimension to strength: retailers who treat payment continuity as a customer experience issue, not just an IT problem, will be better positioned when things inevitably go wrong.
My Son's Future Bank (If He Has One)
When I picture my son at 25, I do not see him walking into a branch to open an account.
I see him inside a super-app or wallet, tapping a few buttons to enable a new account or balance. He might never visit a bank's website directly. He might never know, or care, which regulated entity actually holds his deposits.
For his generation, banking may not feel like a standalone activity at all. It will just be a feature inside the apps where life already happens: shopping, messaging, mobility, and gaming.
That raises big questions. How do we guarantee customers understand who is really holding their money and bearing the risk? How do regulators oversee a world where loyalty is to the platform, not the balance sheet? And for banks, wallets, and retailers: what does it mean to build trust when your brand may never be the one on the card, or even on the screen?
Standing at that till with my son, I realised the industry debate about who owns the customer is not abstract. For his generation, the answer is already forming:
Whoever owns the experience, owns the relationship.
For banks, that means deciding whether to fight for the front-end, adopt the infrastructure role, or specialise where they can still add visible value. For wallets and platforms, it means earning the trust that comes with their increasingly central position, not just capturing it. For retailers, it means recognising they are no longer bystanders in this negotiation; they are co-owners of the trust moment, with real influence over how customers experience the entire stack.
Everyone has to decide whether they are comfortable living behind that glass, or whether it is time to rethink what it means to be a bank, a wallet, or a retailer in a phone-first world.
Related reading from Major Matters: