All testsAli Demirbaş - Lab

Cart & Checkout

Asking for Payment Before Address in Checkout

Asking for a payment method earlier may help some shoppers continue, but it may be impractical if the total or address-dependent options are not yet known. Compare order completion alongside payment errors.

A/B test scenario. This page is a test plan, not the result of a real experiment.

  • Checkout
  • Order completion rate

Control vs Variant

The sequence is the variable.

Changed
Order
Page
Checkout
Difference
moved

Hypothesis

If shoppers settle how they will pay before they fill in the address form, fewer of them may drop out at the address step over doubts about payment options. Provided the total including shipping is visible from the start, the order completion rate may rise as well.

Test plan

When to run this test

Abandonment concentrated at the address step, shoppers jumping ahead to see payment options and coming back, or support contacts about accepted methods suggest that shoppers give up before they know how they can pay. If the new order clears that doubt, fewer shoppers drop out at the address step and completed orders rise without more payment errors. If the address form's fields or error messages cause the drop-off, fix those first. Before enabling the variant, verify technically that address-dependent methods work in this order; skip this setup if the total cannot be worked out without an address.

How to measure success

Order completion rate

Compare completed orders among visitors who start checkout.

Also track

  • Step abandonment rateReview abandonment by step to see whether it falls or shifts elsewhere.
  • Payment error rateTrack errors caused by payment-method incompatibility.
  • Revenue per visitor (RPV)Make sure revenue per visitor does not fall.
  • Support contactsTrack contacts such as reports that the total amount was not visible.

How to set it up

  • Step orderMove the payment step earlier and compare order completion.
  • Total amountShow the total, including shipping, before requesting payment details. Do not use this setup if the total cannot be calculated without an address.
  • ConfidenceTrack abandonment and errors at the earlier payment step; use direct feedback to understand any hesitation.
  • Method compatibilityCheck whether payment methods that depend on the address still work in this order.
  • DeviceReview whether the step-order change has a different result on mobile.

What to watch when reading the result

  1. 1Do not call the variant a winner on a higher order completion rate without checking the payment error rate; errors from method mismatches should not rise, and revenue per visitor should not fall. Use the step abandonment rate to see whether abandonment actually dropped or just moved to another step.
  2. 2The result covers this checkout flow and the order you tested. The number of steps and the payment security checks must match in both versions; otherwise the difference cannot be traced to the order. Look at the device breakdown too, since the change may play out differently on mobile, and if support contacts about not seeing the total go up, recheck how the total is shown before rolling out.
  3. 3When abandonment shifts between steps, the net difference can stay small. Work out up front how long your current checkout traffic needs: divide the per-variant sample from the sample size calculator by the checkout visitors each arm gets per day. If the result is still unclear, do not conclude that the order makes no difference, and back any claim about hesitation with direct feedback.

Frequently Asked Questions

Can payment-method selection come before the address in every store?

Not always. Selecting a method is different from charging the customer. Address-dependent delivery and payment eligibility must still be calculated correctly. Show the final total before payment confirmation. Use order completion as the primary outcome.

How can I distinguish reduced abandonment from displaced drop-off?

Inspect abandonment by step. Drop-off can move between address and payment without changing overall completion. Review mobile separately and apply the predefined payment-compatibility and revenue guardrails.

What should be checked in support contacts?

Watch for reports that the total was not visible. They may indicate unclear pricing, but do not infer hesitation from abandonment alone. Combine behavioral evidence with direct feedback.