Saved Payment Methods: The One-Minute Checkout for Returning Shoppers

A returning shopper who has to retype their card every time is a shopper you are training to leave. Saved payment methods are not a convenience feature. They are the difference between a one-minute checkout and a five-minute one, and the five-minute one loses people.

The returning shopper is the cheapest conversion

Acquiring a new shopper costs more than bringing back an old one, and the checkout is where that arithmetic shows up. A new shopper has to type an address, a card number, an expiry date, and a security code. A returning shopper with saved details has to confirm and pay. The difference is four minutes of typing against one tap, and four minutes is where people abandon. Baymard's research puts the average cart abandonment rate at around 70 percent, and a long or complicated checkout is one of the reasons shoppers give most often.

Saved payment methods close that gap. The shopper saves a card once, the merchant stores a token rather than the card number, and the next purchase is a confirmation, not a form. The token is issued by the payment processor, it can only be used by that merchant for that shopper, and it can be revoked. The card number never touches the merchant's servers, which is why a small store can offer saved payments without taking on the full PCI DSS burden.

The address autocomplete post made the same argument for the shipping step: every field you remove from a returning shopper is a field that cannot be mistyped. Saved payment does the same for the payment step, and the two together turn a five-minute checkout into a one-minute one.

Show the card, hide the number

A saved card has to be visible enough to be trusted and hidden enough to be safe. Show the card brand, the last four digits, and the expiry date, and nothing else. The shopper should be able to tell which card it is at a glance, and should be able to remove it or replace it from their account page without emailing support. A card that cannot be removed is a card the shopper will not save next time, and a card that shows too much is a card the shopper will not trust.

The expiry date matters more than most stores think. A card that expires next month will fail at the worst moment, usually on a subscription renewal or a repeat purchase. Surface the expiry date at checkout, and prompt the shopper to update it before the payment fails. A failed payment is a lost sale and a support ticket; a prompt is a ten-second fix.

The payment method post found that shoppers choose the method they already trust, and a saved card is the method they trust most, because it is theirs. The wallet options, Shop Pay and Apple Pay, are faster for shoppers who have them, and they should be offered alongside saved cards, not instead of them.

The measure that matters

The metric to watch is repeat purchase time, not saved-card adoption. A shopper who saves a card and then takes the same five minutes to check out has gained nothing. A shopper who saves a card and completes the next purchase in under a minute has gained the whole point. Measure the time from cart to confirmation for returning shoppers before and after the feature ships, and the difference is the return on the work.

If the difference is small, the problem is usually elsewhere: the address is not saved alongside the card, or the checkout still asks for an account password before it shows the saved card. Saved payment only works as part of saved checkout, and the address and the card have to travel together. Fix the pair, and the returning shopper stops being a form to fill in and starts being a customer.

Frequently asked questions

Is it safe to store a shopper's card on file?

The merchant stores a token issued by the payment processor, not the card number. The token can only be used by that merchant, for that shopper, and it can be revoked. The card number itself never touches the merchant's servers, which is why the merchant does not need to be PCI DSS Level 1 compliant to offer saved payments.

Do saved payment methods work for guest checkout?

Yes, and that is the point of the feature. A returning shopper with a saved card and a saved address can complete a purchase in one or two taps, which is the same experience as Shop Pay or Apple Pay. The difference is that it works for your store's own checkout, not just the wallets.

What should a shopper see for a saved card?

Show the last four digits, the card brand, and the expiry date, and let the shopper remove or replace the card from their account page. Do not show the full number, and do not make the shopper email support to remove a card. A card that cannot be removed is a card the shopper will not save next time.

Should I offer saved cards or Shop Pay and Apple Pay?

Offer both, and let the shopper choose. Shop Pay and Apple Pay are faster for shoppers who already have them, and they cost nothing to enable. Saved cards are faster for shoppers who do not use a wallet, and they keep the shopper in your checkout rather than sending them to a third party.

What happens to a saved card if the shopper's card is stolen?

A token is tied to the merchant and the shopper, and it can be revoked by either side. If a shopper reports their card stolen, the token is invalidated and the saved method stops working. The shopper adds the new card, and the old token is gone. That is the whole point of tokenization.