Follow a payment authorization
The storefront gathers the order and presents the checkout. Payment services communicate the authorization request and result. Authorization, capture and settlement are related but distinct stages, so an order page saying “Submitted” should not be treated as evidence that money has successfully moved or that the order is ready to fulfill.
Illustrative test flow: Cart → checkout → payment authorization → declined response → clear retry message. The cart keeps the selected item while the checkout explains that payment was not completed. A made-up order reference, TEST-017, ties the result to the test record. No real card details appear in this specimen, and the scenario is performed only in a permitted provider test environment.
Separate storefront checkout and payment provider
Provider behavior, supported methods, regions and failure states vary. A gateway does not guarantee approval, eliminate payment responsibilities or establish that every error originated with the buyer’s bank. A generic connection error may leave the actual payment state uncertain until the provider record is checked.
Next, map the order and payment states, then test an approved payment, a decline and an interrupted response using the provider’s documented test tools. Confirm which state permits fulfillment and who investigates unresolved results.
Website field guide · Find WooCommerce checkout failures · Webhook
Reference: Stripe: payment gateway overview; Stripe documentation: testing. Checked November 4, 2026.