Skip to content

Payment Choices and Failures

Offer payment methods supported for the shopper's destination and make the payment step clear and recoverable. When a payment fails, distinguish a rejected payment from a temporary technical error.

About this path

Level
Intermediate
Reading time
About 4 minutes
Sections
3
Account needed
No

Written for store owners, builders, and designers refining high-performance ecommerce stores.

Foundation · 2 min

What you need to know

Which methods should show?

Offer only methods actually enabled for the customer’s country, currency and order. On a phone, check that card fields and supported wallets are readable and usable.

What if checkout redirects elsewhere?

Tell the shopper that they are moving to a payment provider and how they will return. Verify that the order status is updated securely after the provider responds, even if the browser is closed.

Why do shoppers abandon here?

A method may be unavailable, a field may be confusing or a cost may change between steps. Check payment errors and the full mobile experience, rather than assuming every customer rejected the price.

A quick store check

Test an approved payment, a recoverable failure and a return from any external payment page. Verify both the customer message and order status after each scenario.

Foundation · 2 min

Frequently asked questions

How many payment methods are too many?

Show meaningful supported choices without clutter. The best mix depends on customer location and actual provider support.

Where do I configure payment choices?

Use current payment documentation and run controlled success and failure tests before enabling a method for customers.

Ready for the next stage?

Continue through the Academy sequence to apply advanced optimization and scaling techniques.

Start Advanced techniques