CONCEPT 13 / 87

Payment: totals, next steps and status

Show the total before payment and label the button with the next step. Payment choices should be clear, including any departure from the storefront.

01 / THE PROBLEM

Returning from a payment page is not evidence of payment completion.

02 / WHEN THIS FITS

ReAI and the payment provider own payment state. The lab tests UI outcomes without payment or order creation.

Try the pattern

01
In the lab: review the item, fulfillment and total before simulated payment.
02
Choose failed payment: no paid confirmation should appear.
03
Choose pending: the result should clearly state payment is unconfirmed.
04
Simulate pending: confirmation requests status verification and never says paid.
05
Simulate an unpaid B2B invoice: order confirmation is not a payment receipt or a dispatched EHF invoice.

Measure confirmed, deduplicated outcomes per eligible checkout start. Define paid orders and accepted credit orders separately.

Payment errors, duplicate orders, incorrect totals, unclear arrival dates and discount cost. A pay click is only an attempt.

This is a proposed investigation, not a measured result. Choose one hypothesis and define the audience before testing.