Skip to main content

Documentation Portal

Pre-Checkout Express

What is Pre-Checkout Express?

Pre-Checkout Express enables shoppers to complete their purchase directly from the Product Page (PDP), Mini-Cart, or Cart before checkout. This can be done using supported wallet methods such as Apple Pay, Google Pay, and PayPal. In other words, it lets shoppers pay without going through the full checkout flow.

This feature reduces friction by allowing eligible shoppers to pay instantly once cart and configuration conditions are met. It mirrors the standard Express experience available at checkout, while applying specific eligibility rules, validations, and business logic tailored to pre-checkout surfaces.

This document explains how Pre-Checkout Express works from a business and functional perspective, including eligibility rules, shopper flows, validations, fallback behavior, configuration requirements, and reporting.

Business Benefits

Pre-Checkout Express provides business value by simplifying the purchase journey and aligning with modern checkout expectations:

  • Reduce friction – Eliminate unnecessary checkout steps and enable faster purchase completion.

  • Increase conversion and OSR (Order Success Rate) – Capture intent earlier in the journey, particularly from the cart.

  • Meet shopper expectations – Deliver a wallet experience consistent with leading e-commerce sites.

  • Ensure compliance – Adhere to wallet brand requirements and merchant eligibility rules.

Prerequisites

Before enabling Pre-Checkout Express, the following conditions must be met:

  • Express must already be enabled at checkout

    Pre-Checkout Express does not introduce new payment methods. It only displays wallet methods (such as Apple Pay, Google Pay, PayPal) that are already configured and active in your standard checkout.

  • Country eligibility must be a subset of checkout configuration

    Countries where Pre-Checkout Express is displayed must be a subset of the countries where the same payment method is enabled at checkout.

  • Example: If Google Pay is enabled at checkout for Germany and Italy, Pre-Checkout Express may be enabled for Germany only (but not for a country where it is not available at checkout).

  • You cannot offer Express from Cart or PDP in countries where that method is not configured at checkout.

Where Express Appears and What Happens

Pre-Checkout Express can appear on multiple shopping surfaces. The behavior and scope of payment depend on where the shopper initiates the Express flow.

Surface

When button shows

What is paid

Business Recommendations

Product Page (PDP)

After all required attributes are selected (e.g. color, size, quantity)

Only the selected product. Other items in the cart are not included in the PDP Express payment.

Recommended if most of the merchant orders have one item only

Mini-Cart

After mini-cart eligibility checks pass

All items in the cart

Recommended

Cart Page

After cart eligibility checks pass

All items in the cart

Recommended

Full Shopper Flow

The following outlines the end-to-end shopper journey when using Pre-Checkout Express, from initial eligibility checks through payment completion or fallback.

Phase 1: Eligibility and Button Display
  1. The shopper lands on the Cart, Mini-Cart, or PDP.

  2. The system evaluates eligibility (see verification details below):

    • Device/browser: The shopper’s device and browser must support the selected Express method (such as Apple Pay or Google Pay).

    • Country: The shopper’s country must be included in the configured pre-checkout eligibility list for that payment method.

    • PDP only: All required product attributes (such as color, size, and quantity) must be selected before the Express button is displayed. Alternatively, merchants may choose to display the Express button before these attributes are selected. In such cases, validation errors will be shown until all required selections are completed.

    • If eligible, Express button(s) are displayed.

    • If not eligible, Express is not shown and the shopper proceeds through the standard checkout flow.

Phase 2: Shopper Clicks Express

Once the Express button is displayed and selected, the system initiates the Express payment process and performs initial technical handling before validation.

  1. The shopper clicks an Express button (Apple Pay, Google Pay, or PayPal).

  2. The system sends the relevant cart data to Global-e.

  3. If the cart details cannot be sent, a technical fallback occurs: the shopper remains on the Cart, Mini-Cart, or PDP and sees a technical error message.

  4. If the cart data is successfully transmitted, the backend proceeds with post-click validations.

Phase 3: Post-Click Validations (Backend)

After the cart data is successfully transmitted, the backend performs a series of validations. If all checks pass, the shopper proceeds to the Express wallet flow. If any validation fails, the shopper is redirected to standard checkout.

Validation

What is checked

If validation fails

Technical

The backend can process the request

Redirect to standard checkout with error

Cart total vs. threshold

Cart amount is within configured country limits

Redirect to standard checkout

Cart amount

Cart total is greater than zero

Redirect to standard checkout

Cart restrictions

No restricted items in the cart

Redirect to standard checkout

Pre-order

No pre-order items in the cart

Redirect to standard checkout

Mixed order

Items from different hubs (controlled by Global-e configuration)

If allowed: proceed; if not: redirect to standard checkout

Shipping options

At least one home delivery option is available (not only PUDO/collection)

Redirect to standard checkout

BOPIS

No BOPIS (Buy Online Pickup In-Store) items

Redirect to standard checkout

Gift cards

Gift cards are not supported with Express

Redirect to standard checkout

Optional: If checkout requires a mandatory Terms & Conditions checkbox, a Terms and Conditions pop-up appears before redirect. The shopper must accept to continue; otherwise, they remain on the current page.

Phase 4: After Validations Pass

If all backend validations succeed, the shopper proceeds to complete payment using their selected wallet method.

  1. The shopper is redirected to the intermediary wallet page (Apple Pay, Google Pay, or PayPal).

  2. The shopper completes the payment within the wallet interface.

  3. From this point forward, the flow follows the standard Express checkout process, including wallet validation, success handling, and failure handling.

Important

If your store includes a registration or login step before checkout, the express flow will skip it. Once the express button is clicked, the entire process is handled directly by Global-e.if your store has a registration or login page before the checkout, the express flow will bypass it, once the button is clicked, the flow is managed by Global-e.

Phase 5: Outcomes After Wallet

After the shopper interacts with the wallet, the final outcome depends on whether the payment is completed, canceled, or declined.

Outcome

Result

Successful payment

Order created; shopper sees confirmation page

Shopper cancels in wallet

Redirect to standard checkout; cart kept

Authorization/payment fails (e.g. declined card)

Redirect to standard checkout with warning; shopper can use another payment method

Fallback Flows in Detail

If Pre-Checkout Express cannot proceed at any stage, the system ensures the shopper is safely redirected to standard checkout with their cart preserved. The following scenarios describe how fallback behavior is handled.

Fallback 1: Technical Error Before Redirect
  • When: The cart cannot be sent from the platform to Global-e after the shopper clicks Express.

  • Result: The shopper remains on the same page (Cart, Mini-Cart, or PDP).

  • What they see: A technical error message.

  • Action: The shopper can retry Express or proceed via standard checkout.

Fallback 2: Post-Click Validations Fail
  • When: One or more backend validations (Phase 3) fail.

  • Result: The shopper is redirected to standard checkout.

  • What they can see:

    • A specific error message when possible (such as “Express is not available because your cart contains pre-order items”)

    • A generic restriction message, depending on the validation failure.

    • Action: The shopper can complete the purchase through standard checkout; the cart is preserved.

Fallback 3: Shopper Cancels in Wallet
  • When: The shopper opens Apple Pay, Google Pay, or PayPal and then cancels or closes the wallet.

  • Result: The shopper is redirected to standard checkout.

  • What they see: Standard checkout with the cart intact.

  • Action: The shopper can choose another payment method.

Fallback 4: Payment Failure in Wallet
  • When: The wallet declines the transaction (such as declined card, risk block).

  • Result: The shopper is redirected to standard checkout.

  • What they see: An error message and the option to select another payment method.

  • Action: The shopper can complete the purchase via standard checkout.

Fallback 5: Validation Timeout or Technical Failure
  • When: The backend cannot complete validation due to a technical issue.

  • Result: The shopper is redirected to standard checkout.

  • What they see: A generic error banner.

  • Action: The cart is preserved, and the shopper can complete the purchase through standard checkout.

Not Supported / Blocked

The following scenarios and configurations are not supported for Pre-Checkout Express. In these cases, Express will not be displayed or will be blocked.

  • Gift cards – Not supported with Express.

  • Pre-orders – Express is blocked when pre-order items are present.

Note: Merchants are advised not to enable the express pre-checkout for pre-order items, as express checkout does not currently support pre-orders.M

  • Buy Online Pickup In-Store (BOPIS) – Express is blocked.

  • Shipping limited to PUDO/collection only – Express is blocked; at least one home delivery option is required.

  • Shopify checkout – This feature is excluded.

Analytics

Pre-Checkout Express orders can be identified and reported separately from standard checkout Express orders.

Merchants can identify pre-checkout Express transactions via SOTM (order create) using paymentoptiontypeid = 2.

This allows merchants to distinguish orders completed via Express from Cart, Mini-Cart, or PDP from those completed via Express at the standard checkout stage.