Every checkout seems to accumulate wallet buttons: one from the platform, one from a card network, one from a device maker, each with its own brand colors demanding the top of the page. Individually each promises faster checkout. Together they can turn the first screen into a wall of competing doors.
The question is not whether express wallets convert. For shoppers with a saved wallet they plainly do. The question is placement and count: how many doors the first screen can hold before the standard checkout, which most shoppers still use, becomes the one that is hard to find.
The first screen has one main job
A checkout's opening screen should make two things obvious: the express shortcut for those who want it, and the start of the standard form for everyone else. If the wallet stack pushes the first form field off the screen on a phone, the majority path has been demoted to serve the minority path.
A useful test is the squint test on a mid range phone. Can a first time visitor tell, in two seconds, where to begin if they have no wallet? If not, there are too many buttons or they are ordered badly, regardless of what the click data says.
Order wallets by your shoppers, not by deals
Wallet order should follow your own traffic: the wallet your buyers actually hold first, the next one second, and any wallet with negligible use removed rather than kept for completeness. Each additional button costs attention from every shopper to serve a smaller and smaller group.
Placement deals with platforms are a business decision, but they should be made with the conversion cost visible. Track standard form starts, not just wallet clicks, when a new wallet is added, so the trade is measured rather than assumed free.
The divider line does real work
The small or divider between express buttons and the form is not decoration. It tells the shopper the buttons are an alternative, not a requirement, and that the form below is a full checkout rather than a lesser path. Removing it reliably produces hesitation and support questions about whether a wallet account is mandatory.
Label the express section plainly too: Express checkout above the buttons, and a line like or continue below for the form. Plain words remove the ambiguity that brand colored buttons, each with its own verb, create on their own.
Repeat the option at the payment step
Shoppers who skip express at the top often reconsider at payment, after shipping and totals are known, which is when a saved card is most attractive. Offering the wallet again at the payment step catches that second decision point without crowding the first screen.
What should not happen is a wallet button that restarts the flow or discards entered information. The payment step wallet must preserve address and shipping choices, or the shortcut becomes a trap that experienced shoppers learn to avoid.
Related reading
These earlier guides go deeper on connected questions: Post-Purchase Offers: The Upsell That Does Not Tax the Checkout, How Many Fields Is Too Many? The Checkout Field Count Question, Answered With Behavior, and Checkout Page Speed: The Seconds That Cost Completed Orders.
Frequently asked questions
How many wallet buttons should a checkout show?
Usually one or two, ordered by how many of your shoppers actually hold them. More than that tends to push the standard form out of sight and slow everyone down.
Where should express wallet buttons appear?
At the top of checkout for ready buyers, and again at the payment step for late deciders. In both places the standard path must remain obvious.
Why does the or divider matter?
It tells shoppers the wallet is optional and the form below is a complete checkout. Without it, guests often hesitate, unsure whether a wallet account is required.
How should I test adding a new wallet button?
Measure standard form starts and total completion, not just clicks on the new button. A wallet that gains clicks while reducing overall completion is a net loss.