Latest / Fintech Conversations with Fexingo: Banking, Payments, and Financial Software Companies / How Fintech Is Using Tokenization to Secure Payments
Transcript
- Luna: Lucas, we talk a lot about new payment rails and digital wallets, but I want to focus on something that makes all of them safer without users even noticing. Lucas: You mean tokenization. It's one of those infrastructure pieces that quietly underpins billions of transactions a day. In simple terms, when you tap your phone at a terminal, your actual card number never leaves the device. Instead, a one-time token — a random string of numbers — gets sent to the merchant. Luna: Right, and it's not just for tap to pay anymore. Tokenization is expanding into card-on-file scenarios, recurring billing, even cross-border payments. It's becoming a standard layer of the payment stack. Lucas: And that's the story I think is underreported. Tokenization isn't a flashy new product — it's a security protocol that's quietly reducing fraud liability and simplifying PCI compliance. For merchants, if they never store a raw card number, they shrink their compliance scope dramatically. Luna: We should mention that this kind of deep-dive conversation is exactly what listener support makes possible. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: Yeah, it's a small thing that adds up. And it's what lets us stay ad-free and dig into topics like tokenization without any sponsor constraints. So, back to it — where did tokenization really start gaining traction? Luna: I'd say the big catalyst was Apple Pay launching in 2014. Apple built tokenization into the core of its payment system. Every transaction uses a device-specific token and a dynamic security code. That set the standard. Lucas: Exactly. And then EMVCo, the body behind chip card standards, formalized tokenization as a specification in 2014 as well. That gave card networks — Visa, Mastercard, American Express — a framework to issue what they call 'payment tokens' that work across digital wallets, in-app purchases, and online checkouts. Luna: So how does it actually work under the hood? I know there's a token vault, a mapping between the token and the real card number. But who controls that vault? Lucas: Great question. Typically the card network or a token service provider operates the vault. When a merchant requests a token, the network generates it and stores the mapping. The merchant only ever sees the token. If that token gets compromised, the network can simply deactivate it and issue a new one without ever touching the underlying card account. Luna: That's a huge improvement over the old model where a merchant stored your full card number in their database. One breach, and millions of numbers are exposed. With tokenization, the blast radius is limited to a single token. Lucas: Right. And there's a useful distinction: there are 'payment tokens' issued by the network, and 'merchant tokens' — sometimes called vault tokens — that a payment gateway or processor stores on behalf of the merchant. The merchant token can be used for recurring payments, but it's still not the real PAN, or primary account number. Luna: So the merchant has two layers of protection: they don't store the PAN, and the payment token can be revoked. What about the consumer side? Do my card details ever get exposed during a transaction? Lucas: In a well-tokenized system, no. When you add a card to Apple Pay, the device generates a token that's stored in the secure element. The actual card number is never transmitted to the merchant's terminal. Even Apple doesn't store the full PAN on its servers. It's a zero-trust approach at the hardware level. Luna: And now we're seeing tokenization expand beyond the phone. Wearables, connected cars, IoT devices — all of them can use tokens to make payments without storing sensitive data. That's opening up new use cases. Lucas: Sure. Imagine your car paying for gas automatically. The car's payment profile is tokenized. If the token is compromised, you just rotate it. You don't have to cancel your credit card. That's a huge convenience gain. Luna: There's also the click to pay initiative from the card networks — essentially a tokenized checkout flow that works across any merchant. You enroll once, and your tokenized credentials are shared via the network. No more typing in card numbers on every site. Lucas: Which also helps with cart abandonment. Visa says click to pay can boost conversion by 10 to 15 percent. Part of that is the speed, but part is also security trust. Consumers are more willing to complete a purchase if they know their data isn't stored everywhere. Luna: So tokenization is a win-win: better security, better user experience, less compliance burden for merchants. Why isn't every merchant using it universally? What's the barrier? Lucas: The main barrier is integration complexity. Not every payment gateway or processor fully supports network tokenization yet. Smaller merchants may rely on older systems that store raw PANs. And there's a cost — token service providers often charge per token or per transaction. But the trend is clearly moving toward tokenization as the default. Luna: I also think there's an education gap. Many merchants don't realize that storing tokens instead of PANs can reduce their PCI compliance scope from Level 1 to Level 3 or 4, saving thousands of dollars in audits annually. Lucas: That's a massive financial incentive. A Level 1 merchant — processing over six million card transactions a year — might pay fifty thousand dollars or more for a PCI audit. With tokenization, they could drop to Level 3 or 4, where audits are much cheaper or even self-assessed. Luna: So the ROI on tokenization isn't just about fraud reduction. It's about compliance cost savings. That's a message that should resonate with any CFO. Lucas: Exactly. And the networks are pushing it. Visa and Mastercard have been mandating tokenization for certain transaction types. For example, Visa's 'Token ID Requirement' for e-commerce transactions encourages merchants to adopt network tokens. Over time, it'll become table stakes. Luna: What about the role of tokenization in open banking? Where third-party providers access account data? Is tokenization used there too? Lucas: Yes, but in a slightly different form. In open banking, access tokens — usually OAuth tokens — are used to grant limited access to account information or payment initiation. They're not the same as payment network tokens, but the concept is similar: a surrogate identifier that can be revoked without exposing the underlying credential. Luna: So tokenization is becoming a universal pattern across financial services. Secure, revocable, scoped tokens replace raw sensitive data everywhere. Lucas: And it's spilling into adjacent areas — digital identity, credential management, even healthcare data sharing. The tokenization market is growing fast. Allied Market Research estimated it at about two billion dollars in 2025, growing at over twenty percent compound annual growth rate. Luna: That's impressive. But let's bring it back to the consumer. The average person tapping their phone at Starbucks has no idea tokenization is happening. Should they care? I think yes, because it's lowering fraud rates without adding friction. Lucas: Absolutely. And as fraudsters become more sophisticated — using AI to generate convincing phishing attacks or to crack weak security — tokenization raises the bar. A stolen token is useless outside its specific context: it only works with that merchant, for that transaction, often with a limited lifetime. Luna: So it's a defense-in-depth strategy. Tokenization, encryption, biometrics — they all layer together. But tokenization may be the most elegant because it fundamentally changes the value of stolen data. Lucas: Exactly. If the data has no value outside a narrow context, the incentive to steal it plummets. That's the endgame. And we're already seeing the results. The major card networks report that tokenized transactions have fraud rates near zero — often less than one basis point. Luna: One basis point — that's 0.01 percent. Compared to standard e-commerce fraud rates which can be ten to twenty basis points, that's an order of magnitude improvement. Lucas: Right. And the user doesn't have to do anything differently. They just tap or click. The security is invisible. That's the holy grail in payments. Luna: So what's next? I hear about 'dynamic tokenization' where the token changes with every transaction. Is that already happening? Lucas: In some implementations, yes. Apple Pay uses a dynamic security code — a cryptogram — that changes per transaction. But the token itself can be static for a given device and merchant pair. The cryptogram proves the transaction is fresh. Some networks are experimenting with fully dynamic tokens that expire after one use, but that adds complexity for recurring payments. Luna: I also wonder about the intersection with quantum computing. If quantum computers can break encryption, could they also break tokenization? Since tokens aren't encrypted — they're just random numbers mapped in a vault — quantum doesn't directly threaten them. The vault itself might use encryption, but that's a different layer. Lucas: Good point. The token itself is a random identifier, not a ciphertext. So even if quantum computing could factor large primes, it doesn't help you guess a random 16-digit token. The security of tokenization relies on the randomness and the vault's access controls, not on the hardness of a math problem. Luna: That makes tokenization relatively future-proof compared to encryption alone. And as we move toward a cashless society, having a robust, quantum-resistant security layer is critical. Lucas: Exactly. And I think that's the key takeaway: tokenization is quietly becoming the backbone of payment security. It's not flashy, but it's effective. And it's enabling the next generation of payment experiences — from wearables to connected cars to seamless online checkout. Luna: Well, Lucas, I think we've demystified tokenization for our listeners. Next time they tap their phone, they'll know what's happening under the hood. Lucas: And hopefully they'll appreciate that a couple of dollars a month helps keep these deep dives coming — buy me a coffee dot com slash fexingo. That's about it for this episode of Fintech Conversations.