# Express checkout button order: which payment button should come first? | Checkout Optimize Lab

Source: https://checkoutoptimizelab.com/2026-09-30-express-checkout-button-order/

Put the express button your customers actually use first, which for most Shopify stores is Shop Pay, followed by the wallet matching the shopper's device. Button order matters because the first button gets the misclick-proof tap; everything after it splits the remainder.

## The first button wins by default

Express checkout buttons compete for a single tap, and position is the biggest factor in which one gets it. The first button in the row is the most visible, the most thumb-reachable on mobile, and the one shoppers tap when they have a mild preference rather than a strong one. Order is not a neutral presentation choice. It is a vote.

This means the default order your platform ships is making the decision for you. Most Shopify checkouts show Shop Pay first, which suits most stores, but not all. A store with a heavily iPhone audience and low Shop Pay adoption is leaving taps on the table by burying Apple Pay in third position.

## Know your actual wallet mix

Do not order by gut. Pull your payment method distribution for the last 90 days and order the buttons to match. The wallet with the highest completed-order share goes first. This sounds obvious and is rarely done, because the button order was set once during setup and never revisited.

Segment by device while you are at it. Desktop shoppers and mobile shoppers use different wallets, and Apple Pay does not exist on Android. If your platform supports device-aware ordering, use it. If it does not, order for your dominant device, which for most Shopify stores is mobile.

## Too many buttons is a real problem

Four express buttons plus the regular checkout button is five ways to pay staring at the shopper at once. Choice overload is real at the payment step, and every additional button adds layout weight, script weight, and decision time. The slowest-loading button also delays the whole row if they render as a group.

Consider showing two: your top wallet and the device wallet, with the rest behind a more options disclosure. The data usually supports this. The third and fourth buttons split a small remainder, and the simplification speeds up the render and the decision. Test it rather than assuming, but test it.

## Watch the late-loading button

Express buttons render at different speeds. Apple Pay and Google Pay can appear quickly, PayPal often lags, and Shop Pay depends on the shopper's state. A button that pops in late causes layout shift and misclicks: the shopper taps where Shop Pay was about to be and hits PayPal instead, or taps twice and triggers an error.

Reserve the space. Fixed-height containers for the button row prevent the layout shift, and skeleton placeholders keep the shopper from tapping early. The order question and the loading question interact: a late button in first position is worse than a late button in third, because the shift happens where the eye is.

## Test order, not just presence

Most express-button tests are on or off. The more useful test is order: run your current order against the wallet-mix order for two weeks and compare express attach rate and overall conversion. It is a cheap test with a clear read, and it settles the internal debate with data instead of opinions.

Revisit annually. Wallet adoption shifts, Shop Pay penetration grows, and the order that was right last year drifts. Button order is a setting, not a decision. Treat it like one.

## Frequently asked questions

### What does this guide explain about the first button wins by default?

Express checkout buttons compete for a single tap, and position is the biggest factor in which one gets it. The first button in the row is the most visible, the most thumb-reachable on mobile, and the one shoppers tap when they have a mild preference rather than a strong one. Order is not a neutral presentation choice. It is a vote.

### What does this guide explain about know your actual wallet mix?

Do not order by gut. Pull your payment method distribution for the last 90 days and order the buttons to match. The wallet with the highest completed-order share goes first. This sounds obvious and is rarely done, because the button order was set once during setup and never revisited.

### What does this guide explain about too many buttons is a real problem?

Four express buttons plus the regular checkout button is five ways to pay staring at the shopper at once. Choice overload is real at the payment step, and every additional button adds layout weight, script weight, and decision time. The slowest-loading button also delays the whole row if they render as a group.