Mobile wallet (Apple Pay, Google Wallet)
Also known as: digital wallet, Apple Pay, Google Wallet, Google Pay, Samsung Wallet, phone wallet
A mobile wallet, such as Apple Pay, Google Wallet, or Samsung Wallet, stores digital versions of your payment cards on your phone or watch so you can tap to pay in stores or check out online.
While it looks like your card has simply been copied onto your phone, the wallet actually uses a separate device-specific token. That's why a mobile wallet is generally safer than the physical card it replaces.
Mobile wallet (Apple Pay, Google Wallet), explained at three levels
At home
A mobile wallet is like giving your phone a stand-in for each card rather than a photocopy of it. When you add a credit or debit card, your bank creates a separate number that only works from that phone or watch. To pay, you hold the device near the terminal and confirm with your face, fingerprint, or passcode. The store gets the stand-in number, so your real card number never leaves your pocket.
At work
A mobile wallet such as Apple Pay, Google Wallet, or Samsung Wallet stores tokenized versions of customers' cards on their phones and watches. In stores, wallet payments run through the same contactless terminals as tap cards. Online, a wallet button fills in payment and shipping details in one step. For a business, that means faster checkouts, fewer abandoned carts on mobile, and lower fraud, without needing new card agreements.
At home
When you add a card, the wallet sends its details to the card network, which asks your bank to approve a device token, a stand-in card number tied only to that phone or watch. The token and its keys are stored on the device. At checkout, the device sends the token plus a one-time cryptogram, and the network swaps the token back to your real card number before your bank approves it. If your phone is lost, you can remove the token remotely and keep using your physical card.
At work
Wallet payments rely on network tokenization: Visa's and Mastercard's token services map each device token to the real card number, and only the network and issuer can reverse that link. Because the device authenticates the user with biometrics or a passcode, wallet taps can exceed normal contactless limits. Online, wallet buttons pass a token and cryptogram instead of raw card data, which reduces PCI DSS scope and often lifts authorization rates. Receipts show the token's last digits, which won't match the physical card during returns.
At home
Apple Pay stores the token in a secure element, a tamper-resistant chip, while Android wallets largely use host card emulation, where secure software and cloud-provisioned keys do the job. Both generate a cryptogram per transaction. In my view, the biometric step is the underrated part: it gives every tap a strong form of cardholder verification that physical cards never had.
At work
Strategically, wallets sit in a powerful position between banks and customers. Apple charges issuers a fee on transactions, and control of NFC access became an antitrust issue in the EU, where Apple opened iPhone NFC to third parties in 2024. For merchants, wallets are also a data question: the wallet provider sees the transaction context, and the merchant may receive less customer information than with a direct card entry.
Real-world examples
At home
Carlos went for a run and left his wallet at home. At a café on the way back, he paid for a smoothie by double-clicking his watch and holding it to the terminal. The café received a device token rather than his actual card number.
At work
Lena runs e-commerce for a sporting goods retailer. After adding Apple Pay and Google Pay buttons on mobile checkout, she saw fewer abandoned carts from shoppers who didn't want to type card numbers on a small screen.
How it compares
| feature | Mobile wallet (Apple Pay, Google Wallet) | Physical card |
|---|---|---|
| Card number shared with merchant | No, a device token instead | Yes, the actual card number for many transactions |
| Verification | Biometric or device passcode | PIN, or none for small taps |
| If lost | Remove the token remotely; phone is locked | Cancel and replace the card |
| Online checkout | One-tap wallet button | Type card details |
| Works without battery | Generally no (some phones have limited reserve modes) | Yes |
A mobile wallet uses the same networks as your card, with a safer token and stronger verification.
For analysts
If you sell online, wallet buttons are one of the cheapest conversion wins available. I'd test them on mobile checkout first, since that's where typing card details hurts most.
History & origin
Google launched the first major phone wallet, Google Wallet, in 2011, but carrier resistance and limited phone support slowed it down. Apple Pay launched in the United States on October 20, 2014, using tokenization and Touch ID, and it reached Canada in 2015. Google rebuilt its offering several times, merging services into Google Pay in 2018 and reviving the Google Wallet name in 2022. For years Apple kept the iPhone's NFC chip closed to rival wallets, but under pressure from the European Commission it committed in 2024 to open it to third-party apps in the European Economic Area. In my opinion, Apple Pay's success came less from the technology than from persuading banks to accept a new fee in exchange for lower fraud.