Prepare a controlled purchase scenario
Use a staging or other agreed test environment with products, accounts and delivery options that your team can reset. Follow the payment provider's sandbox instructions. Stripe, for example, provides test credentials and payment values for simulated successes, declines and authentication. Keep test activity out of live payment processing, and do not enter customer payment details into a shared test session.
Check the work before payment
Add and remove items, edit quantities and inspect the displayed totals. Enter a long name and address, correct a postcode error and change a delivery choice. Check that the keyboard does not cover the active field or hide the next action. Compare guest and signed-in paths if both are supported. Record the cart and account state so another tester can recreate the journey.
Follow redirects and the return journey
Some integrations use a hosted payment page, while others embed a form. Stripe documents both approaches. Include leaving the original page, completing the supported authentication step and returning to the merchant experience. Check the customer-visible status as well as the outcome in your product's test backend. A visible success screen alone does not explain every part of a payment integration.
Give recovery the same attention as success
Use the provider's documented test scenarios for declines or authentication failures. Review the message, available retry action and preserved cart. Try browser back and an interrupted journey in the agreed environment. If the result is uncertain, the interface should explain how the user can verify it. Capture timing, steps and the resulting order state when reporting a failure.
Your testing checklist
- Use approved test accounts and provider sandbox data
- Check cart edits, delivery options and displayed totals
- Complete address fields with the mobile keyboard
- Review supported payment redirects and return states
- Test a documented failure and the available retry path
- Compare customer confirmation with the test order result
A practical workflow
Define the test purchase
Prepare known products, customer state and the expected order outcome.
Choose mobile browser coverage
Request the devices and browser versions your checkout is intended to support.
Run success and recovery paths
Repeat the same purchase, capture failures and retest without live payment data.
Common questions
Use your payment provider's documented testing environment and test values. Stripe explicitly separates sandbox testing from live payments. Check the instructions for your own integration.
Also check the return to your product, the customer-visible confirmation and the expected result in your test order system. Record the scope of the outcome you verified.
Include the URL access restrictions and payment-provider requirements in your request. The team will confirm whether a suitable testing setup is available before activation.
Technical references
Official documentation for the underlying testing concepts. Available capabilities vary by provider and setup.
Chrome Developers: mobile device mode limitationsStripe Documentation: payment testingStripe Documentation: Checkout quickstarts