Blog
What actually happens when you tap your phone to pay in a store
How a phone wallet turns a tap into an approved purchase: the device token, the one-time code, the unlock check and why the store never sees your card number.
You hold a phone near a terminal, there is a beep, and a screen says the payment went through. The whole thing takes a second or two, and nothing visible happens in between. Behind the beep, though, there are at least six parties and a short exchange of messages, and most of the security in the transaction is built into the first message: the one your phone sends. This explainer follows a single tap from the moment you add a card to your wallet to the moment the money moves days later. The point is practical. Once you know what your phone sends and what the store receives, the questions people ask about phone payments, such as why the receipt shows different digits or why a lost phone is not a lost card, answer themselves.
The description here is general. Phone makers and wallet providers differ in the details of their hardware and software, and a given wallet may do some steps differently. Where details vary, the article says so.
Step zero: adding the card to the wallet
The security of a tap is decided earlier, when you add a card to a mobile wallet. You enter the card, or scan it, or let the wallet pull it from an account you already have with the phone maker. The wallet sends the card details to the card's issuer, usually through the payment network, and asks for permission to create a digital version of the card on this device.
The issuer decides whether to allow it. This is the moment when you may be asked to verify yourself with a code sent by text or email, a call, or a tap inside the issuer's app. It is a deliberate step, because a thief who has your card number but not your phone, or your phone but not your card, should not be able to complete it. If the issuer is satisfied, the network's token service creates a token, a different number that stands in for the real one. The token is tied to your device and, in most designs, to this wallet and this card. It is stored on the phone, together with cryptographic keys, in a protected area. Depending on the phone, that area is dedicated secure hardware or a software-protected store that the wallet manages. In both cases the design goal is the same: the key that proves a payment is genuine must not be readable by the apps on your phone or by anyone looking at the data on the screen.
That substitution is tokenization. The real card number, the one printed on the plastic, is kept by the issuer and the token service. The phone holds the stand-in.
Step one: you unlock and tap
When you reach the register, you wake the phone, authenticate and hold it near the reader. The authentication step varies by wallet and by settings: a face scan, a fingerprint or a passcode, and sometimes a double press of a side button to confirm intent. This step does real work. The wallet will not release a payment credential until the person holding the phone has passed it, which is something a plastic card cannot do. A found or stolen unlocked phone is a different story, which is why phone wallet setup checklist: default card, locks and what to switch on recommends the locks you should switch on.
The phone then uses a short-range radio link, the same technology as a contactless payment card, with a range of a few centimeters. The terminal produces a field, the phone responds, and the two exchange a short conversation. The terminal says in effect: I want to take this amount in this currency, and I speak these payment applications. The phone chooses the application for the default card and replies.
Step two: what the phone sends
What the phone sends is the core of the transaction. It is not your real card number. It sends:
- The token, which looks like a card number and is accepted wherever a card number would be, but works only in combination with the other items.
- An expiry date and related data for the token.
- A one-time code, often called a cryptogram. The phone's secure store computes it using a secret key and details of this transaction, such as the amount and a counter. The code is valid for this one payment and nothing else.
- Flags saying that the phone's owner was verified on the device.
This is the same idea as the chip on a plastic card, an EMV chip, which also produces a one-time code for each payment. The difference is the number it wraps. A chip card's code protects the real card number, while a wallet's code protects a token. Something that a criminal copies from one of these exchanges is a token plus a code that has already been used, which does not work a second time. how chips and tokens protect your card number in different ways compares the two layers.
What the phone does not send is the three-digit security code from the back of your card. That code is for online purchases and is not part of the tap.
Step three: the store's side of the message
The terminal takes what the phone sent and passes it, with the amount and the merchant's identity, toward the store's bank. The store's bank is called the acquirer, because it acquires the merchant's card transactions, and a processor often sits between them and handles the routing. Neither the store nor the acquirer needs to know your real card number. They carry a token and a cryptogram, and they have no use for anything else.
This is why a breach at a store is less harmful for phone payers. A merchant's database that holds a token and its metadata holds a number that does not work at other merchants, or, if reused, fails without its one-time code. A store that is breached after you pay with a plastic card's number is in a different position, and can someone steal from your card by tapping it through your pocket? covers the physical side of tap fraud.
Step four: the network and the token service
The message travels onto the card network, the company whose logo is on the card, such as Visa or Mastercard. The network recognizes the number as a token, not a real card number. It sends the token to its token service, which looks up the real account that the token stands for, checks that the token is active and checks that it is being used in the way it was created for, for example from a phone wallet and not from a website.
The service replaces the token with the real number for the next leg, and it checks the cryptogram, or hands it to the issuer to check. Many designs verify the code at the network, and others let the issuer do it. Either way, if the code does not match, the request is declined. This swap, token in and real number out, happens inside the network and between the network and the issuer. The store never sees it.
Step five: the issuer decides
The issuer receives the authorization request with the real account number and the verified code. It checks things it checks for every card payment: whether the account is open and in good standing, whether there is enough available credit or balance, and whether the amount, location and pattern look like you. It also sees the flag that the device owner was verified.
Then it answers, approved or declined, and the answer travels back along the same path: issuer, network, acquirer, terminal. That all takes about a second or two. A hold of the approved amount appears on your available credit, shown as a pending transaction, and the phone shows a checkmark. In the illustration below, the figures are invented.
| Step | Who acts | What they hold | Example |
|---|---|---|---|
| 1 | You and the phone | The token, the keys, your face | You unlock for a $4.60 coffee |
| 2 | Terminal | Amount, merchant, the token you sent | Reads the token and code |
| 3 | Acquirer or processor | The token and the merchant's account | Forwards the request |
| 4 | Network and token service | The mapping from token to real number | Swaps the token for the real number |
| 5 | Issuer | Your real account | Checks the code and the credit, approves |
| 6 | Terminal and phone | An approval | Beep, checkmark |
Step six: after the beep
The approval is not the money. Over the next day or so, the merchant's batch of approved sales is sent for clearing, and the issuer posts the final amount to your account, replacing the pending item. Funds move from the issuer to the acquirer and then to the merchant after the network's fees are taken out, and the merchant receives the sale amount minus those fees. what happens in the seconds after you tap: network, issuer and merchant follows that stage in detail, and the swipe-fee questions are in where the swipe fee goes and why prices already include it.
Two small effects of tokenization that surprise people show up here.
- The receipt may show different digits. Because the merchant received a token, a receipt or a store's record often shows the last four digits of the token, not the last four digits of your plastic card. That is normal. Your wallet's card entry usually lists the token's last digits too, under a "device account number" or similar label, so you can match them.
- Returns go back through the token. When a store refunds a purchase, it sends the refund to the token it has on record, and the network maps it to your real account. If the token has been replaced in the meantime, for instance because you got a new card or a new phone, the refund still normally finds you, but it can take extra days. A statement that is slow to show a refund is a reason to ask the issuer, with the receipt in hand.
What happens when something changes
A token is a managed object, and the issuer and the network can change its status without touching the plastic card.
- A new physical card. If your card is replaced because of an expiry or a reissue, the issuer can update the token to the new card, often without you re-adding anything. Sometimes the wallet needs a fresh verification, and sometimes the update does not go through, which is why a card that works as plastic can fail in the phone for a day.
- A new phone. Tokens are device-specific, so a new phone needs a new token, and each card in the wallet is re-added and re-verified. The old device's token can be deactivated.
- A lost or stolen phone. The issuer can suspend the token for that device, which stops tap payments from that phone while the plastic card keeps working. I lost my phone and my cards are in its wallet. What do I do first? gives the order of steps.
- A declined tap. Contactless transactions sometimes fail for reasons at the terminal or in the issuer's checks, and My tap payment failed but the chip worked. Why does that happen? explains why a plastic chip may work when a tap does not.
Edge cases that confuse people
No signal on the phone. A tap can still work when the phone has no mobile or Wi-Fi connection, because the phone only talks to the terminal over the short-range link. The terminal is the part that needs a connection to reach its acquirer. The phone needs its stored keys and a passed unlock check. If the store's terminal is offline, the sale may fail or the terminal may follow its own offline rules, which is a store setting and not something your phone controls.
Two cards in the wallet. The terminal gets whichever card the wallet has set as default, unless you choose another before tapping. Paying with the wrong card is a common source of missed rewards and of balance surprises, and the setup checklist covers how to set the default.
Tapping a phone and a card together. Holding a phone and a physical card against a reader at once can confuse the terminal, which may read the wrong one or neither. Present one at a time.
Online and in-app payments. A wallet used inside an app or on a website works on the same principle: a token and a one-time code, with the unlock check, instead of a typed card number. The merchant receives the token, so a breached online store holds something that does not work elsewhere. The three-digit code is not needed for those payments either.
Transit and tickets. Some transit systems and ticket gates accept a tap from a phone wallet and handle the fare differently from a store, for example by totaling several taps and charging later. The wallet and the transit operator's rules govern those, and a fare that posts a day later is not a sign of fraud.
What this does and does not protect
Knowing the chain makes it easy to say what a phone wallet protects against and what it leaves alone.
It protects against a store or a processor holding your real number, against a captured tap being replayed, against someone paying with a card number they copied from a receipt and against unlocked use by someone who cannot pass the phone's check.
It does not protect against a scammer who persuades you to approve a payment, against a thief who has your unlocked phone, against fraud at the issuer's own systems or against a merchant who simply does not deliver. Those are fraud and dispute questions, and the same federal rules cover them as for a plastic card: federal law caps a cardholder's liability for unauthorized use at $50, and a written billing-error notice must reach the issuer within 60 days of the statement showing the error. If something seems wrong, call the number on the back of the card, and the CFPB takes complaints if the issuer does not resolve it.
A short test of understanding
If you can answer these five questions, you have the model.
- Which number does the store receive when you tap a phone: the real one, or a stand-in? A stand-in.
- What stops a recorded tap from being replayed? The one-time code, valid for one payment only.
- Who swaps the stand-in for the real number? The network's token service, not the store.
- Why can a lost phone's wallet be shut off without replacing the card? The token is tied to the device, and the issuer can suspend it separately.
- Why might the last four digits on a receipt differ from your card? They are the token's, not the plastic's.
Key takeaways
- Adding a card to a wallet is verified by the issuer, and it creates a device-specific token that stands in for your real card number.
- A tap sends the token plus a one-time code made for that single payment, after you unlock the phone. The store never sees the real number.
- The network's token service swaps the token for the real number and the issuer approves or declines. The path takes about a second or two.
- Receipts may show the token's last four digits, and refunds return through the token. A lost phone's token can be suspended without cancelling the card.
- Wallets reduce copying and breach risk but do not stop scams that trick you into approving a payment. The $50 federal cap and the 60-day billing-error window apply as they would to a plastic card.