Digital wallet
Also known as: Mobile wallet
A stored-card app like Apple Pay or Google Pay that speeds up secure checkout.
A digital wallet stores a customer's cards on their device and pays with a tokenised, biometric-approved tap or click, for example Apple Pay, Google Pay, or PayPal. Wallets cut checkout friction and reduce fraud because the real card number is never shared.
How it works
Wallets do not have a price of their own. The channel does. A tap in your shop is card-present and costs what any chip sale costs; the same wallet on your website is card-not-present and takes card-not-present interchange. Apple Pay and Google Pay levy no merchant fee of their own, though a wallet that is also its own payment brand, such as PayPal, prices separately. On a phone the wallet button also removes the card entry form, which is where mobile checkouts most often stall.
Adding a card to a wallet provisions a device account number: a token only the card network can map back to the real card. At payment the device signs a one-time cryptogram with that token, and the fingerprint, face or passcode check stands in as cardholder verification. In person the token reaches you over NFC. Online it arrives through a browser or app interface your gateway exposes. Either way, the card number never passes through your systems.
Two things surprise merchants. Your records show the last four digits of the device token rather than the customer's own card, so a shopper reading their statement to your support team will quote a number that does not match yours; refunds still route correctly. The other is a setup step. Accepting Apple Pay on the web needs domain verification in your gateway, which is the usual reason a wallet button works in testing and never appears on the live site.
Worked example
A customer pays $95 on your website with a wallet. That is card-not-present, so on a flat rate of 2.9% + $0.30 you pay $3.06, exactly what a typed card number would have cost. Move the same purchase into your shop, where the wallet is tapped rather than clicked, and it prices as card-present: 2.6% + $0.10, so $2.57. The wallet changed the security, not the price.
Frequently asked questions
- Does accepting Apple Pay or Google Pay cost extra?
- US merchants pay no separate Apple Pay or Google Pay fee, because those wallets earn from the card side rather than from you. You pay your normal rate for the channel: card-present when the customer taps in store, card-not-present when they pay online. On your statement, wallet volume should sit in the same categories as ordinary card volume.
- Do I need a separate merchant account to accept digital wallets?
- A wallet payment is a card payment underneath, so it settles through the merchant account you already have. Turning it on is normally a switch in your gateway, plus a domain verification step for the web. If a provider quotes a separate contract or an extra monthly fee for wallets, ask exactly what it covers before you sign.
- Why does a wallet payment show a different card number from the customer's statement?
- The wallet pays with a device token rather than the card itself, so your records end in the last four digits of that token while their statement shows the funding card. Refunds still reach the right card, because the network maps the token back. Brief your support team, or they will spend time chasing a mismatch that is not an error.