What interviewers expect
Interviewers expect more than testing one successful card payment. They want to hear how you protect money, orders, inventory, customer trust, and recovery from provider or network failures.
QA interview guide
How would you test payment checkout?
Checkout is a high-risk flow because it connects user intent, pricing, payment providers, inventory, order creation, receipts, and recovery from failure. A senior answer balances user experience with backend consistency.
Checklist
What to include in your answer
Functional
- Successful checkout creates an order.
- Inventory is reserved or reduced according to business rules.
- Confirmation page and receipt email are shown or sent.
- Single item, multiple items, and quantity changes work.
Cart, tax, and promo
- Cart review, shipping address, shipping cost, tax, discounts, promo codes, and final total are correct.
- Totals cannot be changed client-side.
- Rounding and currency display are consistent.
Payment failures
- Declined, invalid, expired card, insufficient funds, provider timeout, and provider error are handled safely.
- Retry options are clear.
- No ambiguous order state is left after failure.
Idempotency and backend
- Double click, browser refresh, payment retry, and webhook retry do not create duplicate orders.
- Authorization, capture, order creation, inventory reservation, and status-code behavior are tested.
- Authorized payment but failed order creation is handled.
Security, mobile, and accessibility
- Card data is handled by the provider and is not stored, logged, exposed in analytics, or sent in URLs.
- Mobile layout has no horizontal scroll and the payment form is usable.
- Keyboard navigation, labels, focus states, and screen reader errors work.
“visa card, paypal, buy one product”
What it misses
This mentions payment methods and one purchase, but misses failure recovery, duplicate prevention, tax, promo codes, inventory, order consistency, receipt behavior, security, mobile, and accessibility.
“I would test successful checkout with card and wallet payments, one and multiple products, cart review, shipping address, shipping cost, tax, promo code, final total, order creation, inventory reservation, confirmation page, receipt email, declined/invalid/expired card, insufficient funds, provider timeout, provider error, retry, double click, browser refresh, webhook retry, idempotency keys, no duplicate orders, secure provider-hosted card handling, no card data in logs or URLs, mobile layout, keyboard navigation, labels, focus states, screen reader errors, and consistent payment/order/inventory states.”
Ready to practice?
Write your own answer, get scored, see what you missed, and compare it with junior, middle, and senior QA thinking.