Express Checkout: When Customers Just Want to Buy Fast

There are two kinds of "fast checkout," and conflating them is why a lot of PrestaShop merchants spend money in the wrong place. One kind is structural — fewer pages, fewer fields, everything on one screen. The other is express: a returning customer who taps Apple Pay, authorises with a fingerprint, and is done before a normal checkout has even rendered its address form. This post is about the second kind — wallet and express payments, saved-detail speed, and skipping the cart entirely. If your interest is collapsing the four-step native flow onto a single page, that's a different (complementary) job, and it lives in one-page checkout for PrestaShop.

The distinction matters because express checkout can win you an order that a one-page checkout would still lose. A one-page checkout asks for the address, the carrier, the card — just all at once. An express wallet payment asks for none of it: the customer's name, shipping address, and card are already inside Apple Pay or Google Pay, and PrestaShop receives them back in one signed payload. For a phone buyer who has typed their card into a checkout form one too many times, that's the difference between "later" and "bought."

What "express checkout" actually means on PrestaShop

Express checkout isn't a single feature you toggle on. It's a cluster of mechanisms that all shorten the path between "I want this" and "I paid," and on PrestaShop they come from three different places:

• Digital wallets — Apple Pay, Google Pay, and PayPal's express button. The customer never fills in a PrestaShop address or payment form; the wallet hands over a pre-verified address and a tokenised card. These are delivered by your payment module (Stripe, PayPal, Mollie, Adyen), not by PrestaShop core.
• Express buttons on the cart and product page — a wallet button that appears before the customer reaches the checkout controller at all, so they can pay from the cart summary or even the product page.
• Returning-customer speed — saved addresses, a saved/tokenised card, and a checkout layout that recognises a logged-in customer and asks them for as close to nothing as possible.

Notice none of these is "the order controller, but shorter." That's the one-page checkout job. Express checkout is about removing the form entirely for the customers who shouldn't have to see it.

Why wallets convert the people one-page checkout can't

The friction that kills mobile orders isn't usually the number of pages — it's the typing. Entering a 16-digit card number, expiry, CVV, and a billing address on a phone keyboard, often while standing in a queue, is the single most fragile moment in the whole funnel. Cart-abandonment studies commonly cite a long or complicated checkout and forced account creation among the top reasons people bail; both are really complaints about effort, and a wallet removes the effort instead of merely reorganising it. (We catalogue the full set of leave-reasons in 12 reasons people leave before paying and the abandonment mechanics in why shoppers abandon carts.)

The "So what?" for a store owner: a wallet payment is the only checkout path where a brand-new customer can buy without you ever asking them to register, type a card, or confirm a shipping address — because Apple or Google already verified all three. That's why express buttons disproportionately recover the impulse and mobile buyers a normal checkout sheds. Treat any conversion-uplift figures you read as directional, not a promise; the honest move is to measure it on your own store (covered at the end).

Wallet payments in PrestaShop: where they actually come from

This is the part most "express checkout" advice skips, and it's the part that decides whether you can have it at all. PrestaShop core does not implement Apple Pay or Google Pay. They arrive through your payment gateway module, and each has its own back-office switch and its own domain-verification requirement:

Two practical consequences. First, Apple Pay will not show up on http or on a misconfigured TLS domain — it's a hard requirement of the wallet, not a PrestaShop limitation, and it's the most common reason a merchant "turned on Apple Pay" and saw nothing. Second, the wallet button placement (cart, product page, checkout) is controlled inside the payment module's configuration in Modules → Module Manager, hooked into display points like displayExpressCheckout / displayProductActions — so where the button appears is a setting you choose, not a fixed behaviour.

Skipping the cart: "Buy Now" and pre-checkout express buttons

The fastest possible purchase doesn't pass through the cart page at all. There are two distinct moves here, and PrestaShop treats them differently:

• A wallet express button on the product page. Stripe's and PayPal's modules can render their Apple Pay / Google Pay / PayPal button in the product-page action area. The customer taps it, the wallet sheet opens, they authorise — and a single-item order is created without the cart or checkout pages ever loading. This is genuinely the shortest path that exists on PrestaShop.
• A "Buy Now" button that fast-tracks to checkout. This adds the product to the cart and jumps straight to the order controller, skipping the intermediate cart summary page. It's not a wallet payment — the customer still pays however your store normally allows — but it removes the "your cart" detour. PrestaShop's default theme doesn't ship this; it comes from a checkout module or a small theme customisation that points the add-to-cart action at the order controller.

Both are worth having for single-item, high-intent purchases (a known SKU, a re-order, a promo landing page). They're less useful for baskets people deliberately assemble — there, the cart review is doing real work.

Returning customers: the express path you already half-have

Express checkout isn't only about new buyers and wallets. Your returning customers are the easiest express win, and PrestaShop hands you most of the parts:

• Saved addresses. A logged-in customer's stored address pre-fills the delivery step — no retyping. The friction is usually that they have to log in first; a checkout that recognises them (or that offers a one-tap login) preserves that speed.
• Tokenised / saved cards. Stripe, Mollie and others can store a card token against the customer so a repeat purchase is "confirm and pay," not "re-enter card." This is a setting in the gateway module, and it's the single biggest speed win for a subscription-like or frequently-reordered catalogue.
• Guest-by-default for everyone else. Forcing registration is one of the most-cited abandonment causes, so the express posture is: never demand an account up front, offer it after the order. The data behind that choice is laid out in guest checkout vs account creation.

Express checkout and the rest of your checkout strategy

Wallets are powerful but partial. A few honest boundaries keep them from being oversold:

• They don't fix a slow or confusing checkout for card payers. The majority of orders in many stores still go through the regular form. Wallets sit alongside a well-structured checkout, they don't replace the work of building one — see why your checkout page is losing you sales.
• They don't help on desktop nearly as much. Apple Pay on desktop needs a paired Apple device nearby; Google Pay needs a saved card in the browser. Wallets are first and foremost a mobile lever, which is why they belong in the same conversation as mobile checkout optimization.
• They don't recover the customer who still leaves. A faster checkout lowers abandonment; it never zeroes it. An abandoned-cart email sequence wins back a share of the rest, and the broader playbook is in reducing cart abandonment in PrestaShop.

Where Checkout Revolution fits

Express wallet buttons come from your payment gateway — but they only pay off if the checkout they drop into is itself fast and single-screen. That's the seam our Checkout Revolution module sits in: it turns PrestaShop's stepped native checkout into one screen where the wallet buttons, the saved address, and the live-updating total all coexist instead of fighting each other across collapsing steps. So what does that mean for you? A customer who declines Apple Pay doesn't fall back into a four-step form — they fall back into a single page that's still fast, and the wallet button stays visible up top for the ones who change their mind. It installs and configures from the back office, and it doesn't fork your theme, so it survives upgrades. The rebuild story is in Checkout Revolution 3.0, and how express speed relates to the single-page question is in one-page checkout for PrestaShop.

How to measure whether express checkout actually helped

Wallets are easy to add and easy to misjudge, because the headline "we enabled Apple Pay" tells you nothing about revenue. Before you turn anything on, record from your analytics: cart-to-order conversion, checkout abandonment rate, and — crucially — your mobile vs desktop conversion split, since that's where wallets move the needle. After enabling express payments, watch two things specifically: the share of orders paid via wallet (your gateway dashboard reports this — Stripe and PayPal both break it out) and whether mobile conversion rises while desktop stays flat. Give it at least 30 days and a few hundred orders before you trust the trend; a wallet that takes 8% of orders without lifting total conversion is just cannibalising card payments, while one that lifts mobile conversion is genuinely recruiting buyers who'd otherwise have left. For the full checkout-tuning workflow this sits inside, see the PrestaShop checkout optimization guide.

The principle underneath all of this is simple: the customer who reached checkout has already decided to buy, and your job is to ask them for as little as you possibly can. For a returning buyer or an impulse mobile order, "as little as possible" is a fingerprint — and on PrestaShop that's a wallet button from your gateway, dropped into a checkout fast enough to deserve it.