Digital wallets for merchants: accept tokenised card payments without asking customers to type the card

Digital wallets let customers use payment credentials stored on a phone, browser or wallet account instead of typing the full card number into every checkout. For merchants, the payment still normally reaches the existing card-processing stack, but wallets can reduce checkout friction and limit direct exposure to reusable card credentials.

Wallets shorten the customer payment journey

Stripe's UK payment-method guidance describes wallets such as Apple Pay and Google Pay as ways for customers to use digitally stored cards and avoid manually entering card and billing details. Online checkout can show a wallet button when the device or browser supports it.

In person, NFC-enabled terminals can accept contactless wallet transactions much like contactless cards. The merchant still needs compatible acquiring and terminal support.

The merchant receives tokenised payment data

Digital wallets commonly use tokenisation so the merchant does not receive the customer's underlying card number in the same form as manual card entry. Device or transaction cryptographic data can also strengthen the authorisation.

This reduces exposure but does not remove the merchant's need for secure checkout, PCI controls and protected processor credentials.

The wallet can authenticate the user on the device

Customers can approve with Face ID, fingerprint, device passcode or another wallet method. That can satisfy or support authentication requirements depending on the transaction and market.

Do not assume every wallet payment has identical liability treatment. The processor and card network determine the authentication data attached to each transaction.

Wallet payments can still use normal card economics

A card stored in a wallet normally remains a card-funded payment to the merchant, so domestic, international, commercial and premium card pricing can still matter.

Compare fees using the actual underlying transaction mix rather than treating wallets as a completely separate cheap payment rail.

Refund the original wallet transaction through the processor

Use the provider's refund flow against the original wallet payment. The customer can receive the credit to the underlying card or wallet-linked credential according to network rules.

Customer service should search the processor transaction ID rather than ask the customer for a full card number that the merchant never needed to collect.

Measure wallet conversion and share by device

Wallets can reduce mobile checkout friction because customers do not need to type long card and address details on a small screen. Track usage, authorisation and conversion by wallet and device.

Do not clutter checkout with every available wallet. Show methods relevant to the customer's device and market and keep a normal card or bank option as fallback.

Worked example: a mobile customer already has Google Pay configured. Instead of typing card number, expiry, CVC and billing address, they select the wallet and authenticate on the device. The merchant receives a tokenised payment through its processor and reconciles it alongside other card transactions.

Test wallet buttons after website changes. Domain configuration, browser rules and checkout scripts can make a wallet disappear even while ordinary card entry keeps working.

Keep wallet terminology out of accounting categories where it hides the underlying economics. Finance can report wallet share commercially while still reconciling the transaction through the same acquiring settlement as other card sales.

Worked example: mobile checkout abandonment is 35 percent when customers must type card and address data. After adding a supported wallet button, some returning customers can complete payment with device authentication in a few taps. The merchant should compare conversion improvement with transaction fees and fraud performance rather than assume the wallet creates value automatically.

Keep wallet availability tied to device capability. Apple Pay, Google Pay and browser wallets can appear differently across operating systems and countries. Checkout should fail gracefully to card or bank payment instead of showing a broken wallet button.

For refunds, teach staff that the last four digits shown for a wallet token can differ from the physical card. Customer service should search by processor transaction or wallet payment reference rather than tell the customer the refund was sent to the wrong card solely because the digits differ.

Review domain and certificate configuration after website migrations. A wallet can stop appearing when the merchant changes checkout domain even while ordinary card payments continue to work.

Review wallet acceptance by legal entity and merchant ID after international expansion. A wallet that works on the UK checkout can require separate domain, acquirer or market setup for a new country even when the website code is shared.

Compare wallet approval rates with manual card entry. Better device authentication can improve some issuer outcomes, but the merchant should measure its own traffic rather than rely on generic conversion claims.

Keep wallet-specific checkout analytics separate from the underlying card-brand report so product teams can measure user preference without making finance reconcile the same transaction twice.