Chapter 7 — Where Web3 Enters the Story

Card networks solved coordination through institutions — shared rules, shared brands, shared governance. Internet platforms solved onboarding through software. But in 2008, a pseudonymous author published a nine-page paper that proposed something radically different: what if you could build a payment network with no institutions at all?

Bitcoin's whitepaper described a "purely peer-to-peer electronic cash" system. No issuers. No acquirers. No card networks. No chargebacks. Value would move directly from one party to another, validated by the network's participants using cryptographic proofs instead of institutional trust. The double-spend problem — the fundamental challenge of digital money — would be solved by a decentralized ledger rather than a central authority.

In 2015, Ethereum generalized the idea further. Where Bitcoin was primarily about transferring value, Ethereum introduced smart contracts — programmable logic that executes automatically when conditions are met. This meant settlement itself could be programmable. An escrow that releases funds when a shipment is confirmed? A royalty that splits automatically every time an asset changes hands? These weren't features you bolted onto the edges of a payment network — they were built into the settlement layer itself.

Here's where it gets interesting for our story. Decentralized protocols actually rhyme with card networks in some important ways. They both offer open membership (anyone can create a wallet, just as any bank can join a card network). They both operate under shared rules (the protocol, like network bylaws). And they both aspire to global reach.

But, they fundamentally diverge on three dimensions that define everyday payments:

1. Trust model: Card networks rely on institutions — banks, regulators, scheme rules — to resolve disputes and enforce behavior. Protocols rely on cryptographic proofs and consensus mechanisms. If something goes wrong in the card network world, there's a chargeback process, a regulatory body, and ultimately a court system. If something goes wrong on-chain, the protocol doesn't care. The transaction is final.
2. Reversibility: Chargebacks and dispute procedures are a feature of the card system, not a bug. They're what give consumers the confidence to hand over their card number to a website they've never visited. On-chain transactions are protocol-final. If you send funds to the wrong address or get scammed, there's no issuer to call. Consumer protection, if it exists at all, has to be built as an overlay — through custody providers, escrow contracts, or legal agreements.
3. Programmability: In card networks, programmability lives at the edges — issuer fraud rules, acquirer risk engines, merchant checkout flows. In protocols, programmability lives in the settlement layer itself. Smart contracts can encode complex payment logic (splits, conditions, schedules) directly into the transaction. This is architecturally different, and it opens use cases that card networks weren't designed for.

The following table sums this up:

The Evolutionary Arc — Networks → Platforms → Protocols. Each generation solved new problems while inheriting or recreating old ones. The question isn't which model "wins" — it's which problems each is best suited to solve.

We'll return to these protocols in Part VII, where we'll ask the hard questions: What do stablecoins actually solve? Where does Web3 work today, and where does it break?

Before we move on, though, it's worth stepping back and naming the forces that keep pushing new rails into existence — because every player you've just met, from Visa to Bitcoin, is really an answer to one of five unsolved problems.

The Unfinished Business: Why New Rails Keep Emerging

Before we move on, it's worth stepping back and naming the structural tensions that drive continued innovation in payments. Every new player — from card networks to fintech platforms to crypto protocols — is ultimately trying to solve one or more of these problems. And none of them has fully succeeded.

1. Acceptance costs remain contested: Interchange — the fee that flows from acquirer to issuer — is a regulatory target worldwide. The European Union capped interchange at 0.2% for debit and 0.3% for credit. Australia reformed its interchange system to realign incentives between banks and merchants. In the U.S., the Durbin Amendment capped debit interchange. These interventions reflect a fundamental tension: merchants view interchange as a tax on their revenue, while issuers view it as the engine that funds card rewards, fraud prevention, and financial inclusion. We'll see this tension resurface repeatedly in later chapters.
2. Cross-border payments are still expensive: The global average cost of sending a $200 remittance was 6.49% in Q1 2025 — more than double the G20 and UN Sustainable Development Goal target of 3% by 2030. Card networks have cross-border capabilities, but corridor-specific fees and currency conversion margins add up. This is one of the strongest arguments for alternative rails, including stablecoins — a topic we'll explore in Part VII.
3. Fraud and disputes create real costs: The chargeback system that protects consumers is essential, but it's also expensive and strategically complex for merchants. As we'll see in Part III, disputes involve a web of deadlines, evidence requirements, and financial risk that catches many merchants off guard.
4. Privacy and data governance are fragmenting: Even more so in today’s world, where de-globalization is happening, every payment network operates under an increasingly complex patchwork of data protection, localization, and privacy requirements. India requires certain payment data to be stored domestically. Europe's GDPR constrains how transaction data can be used. China's payment ecosystem operates under its own regulatory framework entirely. This fragmentation means no single network architecture works identically everywhere — a topic we'll tackle head-on in the next chapter.
5. Financial inclusion and compliance are in tension: Permissionless access — the ability for anyone to participate without gatekeeping — is one of the most compelling promises of both mobile money and crypto. But it conflicts directly with anti-money laundering (AML) and counter-terrorism financing (CFT) obligations. The FATF Travel Rule, which requires virtual asset service providers to share originator and beneficiary information on transfers above certain thresholds, is a concrete example of where these forces collide. We'll explore this tension further in Part VII.

Every chapter that follows is, in some sense, about one of these tensions. The cast of characters you've just met — networks, platforms, protocols — are all trying to solve them. They just disagree on how.

Timeline: From Diners Club to DeFi

The evolution from physical charge cards to decentralized protocols took 70 years. Here are the milestones that shaped the payments landscape you see today.

Diagram 2: Seventy years of payments evolution, from the first charge card to decentralized settlement protocols. Each era built on — and reacted to — the one before it.

With the cast introduced and the tensions named, one question remains before we zoom into the machinery: why do payments look so different depending on where in the world you're standing? That's Chapter 8.