# A/B Test: Payment Screen With Named Load Steps

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/ab-test-payment-screen-with-named-load-steps

## Hypothesis

If the spinner is replaced with the real steps shown in order, such as verifying the card, waiting for bank approval and creating the order, shoppers may see why they are waiting. Even with processing time unchanged, that could lower the payment-step abandonment rate.

## When to run this test

Analytics showing visitors leaving before the transaction finishes, session recordings of shoppers refreshing the loading screen, or support contacts asking whether a payment went through are signs that shoppers find the wait during payment unclear. If the step display works, fewer shoppers leave while waiting, with actual processing time unchanged. If shoppers leave because of slow infrastructure or frequent failed transactions, look at those first, and make sure the loading screen does not bypass or hide security checks.

## Primary metric

**Payment-step abandonment rate**: Among visitors who see the step-based progress screen during payment, compare those who leave before the process finishes.

## Other metrics

- **Perceived wait time (survey)**: If surveyed, measure perceived wait time; abandonment alone does not measure trust.
- **Actual processing time**: Make sure the step screen does not increase actual processing time.
- **Support after an error**: Track support requests after failed transactions.
- **Payment success rate**: Make sure overall payment completion does not fall.

## What to check before and during the test

- **Progress display**: Show steps tied to real transaction events instead of a spinning icon.
- **Timing**: Keep processing, verification and error handling intact; do not add artificial waiting.
- **Perceived wait**: Measure perceived waiting separately from actual processing time.
- **Errors**: Show existing error states promptly when a transaction fails.
- **Connection**: Review mobile and slower connections without changing the progress display during the test.

## What to watch when reading the result

- The payment-step abandonment rate is the primary measure, but lower abandonment does not justify shipping if the payment success rate or actual processing time gets worse. Lower abandonment alone does not show more trust; rely on the survey and direct feedback before saying anything about trust or perceived wait time.
- This test changes only how the loading screen looks. Hold the number of payment steps fixed in both versions, or the screen cannot be credited with the difference. Look at mobile and slower connections on their own, check that support contacts after a failed transaction do not rise, and validate the result again before reusing it on other waiting screens.
- Abandonment is counted only while payment is processing, so it may be rare; the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) shows how much traffic each version needs before a small change in such a rare event becomes visible. Confirm too that the number of visitors who saw the loading screen in each version matches the planned split (sample ratio mismatch); a mismatch can mean the screen-view event is under-recorded in one version. Should the gap remain unclear after these checks, do not conclude that the step display leaves abandonment unchanged.

## Frequently Asked Questions

### Does showing payment stages make processing faster?

It does not inherently speed up the payment infrastructure. It explains the wait. Measure any processing or performance cost introduced by the interface. Perceived waiting time and actual processing time are different outcomes.

### Which stages can be displayed?

Only show stages tied to real processing events. Do not invent progress or delay the process to display it. Preserve security checks such as 3D Secure and one-time passwords.

### Does lower abandonment prove increased trust?

No. Measure trust through comparable direct feedback rather than inferring it from departure alone. Perceived waiting time is another distinct concept. Track actual processing time and payment success separately.

### What should happen if processing fails?

Display the actual error promptly instead of leaving the user on a progress screen. Monitor support contacts and slower connections. Use abandonment during payment processing as the primary outcome.