How would you test a checkout and payment flow end to end?

Cover the happy path, then the money specific risks: declined and partially authorized cards, timeouts where the charge succeeds but the response is lost, duplicate submissions, refunds and partial refunds, currency and rounding, tax and discount interaction, and inventory changing mid checkout. Use the provider's sandbox test cards, and verify what the backend recorded rather than trusting the confirmation screen.

The happy path takes ten minutes; everything valuable is in the failure modes, because this is the flow where a bug costs money directly. The case I always test first is the interrupted transaction: the provider authorizes the charge, then the response never comes back, times out, or the user closes the tab. Does the order exist? Is the customer charged with nothing to show for it? That is the worst outcome in the whole system and it needs reconciliation logic, not hope. Alongside that, double clicking submit, and going back then resubmitting, which should be idempotent rather than charging twice. Then the provider's specific responses through their sandbox test cards: declines, insufficient funds, expired card, and a card that triggers additional authentication, because that path has its own redirect and its own ways to break. Then the money arithmetic: currencies with different decimal places, rounding on a percentage discount, tax applied before or after the discount, and a coupon exceeding the order total. Also inventory hitting zero while the customer sits on the payment screen. And I verify against the database and the provider dashboard, never the confirmation page.