Software Development
Payment Testing
Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal. Covers Stripe test-mode card numbers and their decline codes, the 3DS/SCA challenge flow and its nested-iframe handling in Playwright, test clocks for subscription/billing-cycle simulation, webhook testing (stripe listen/trigger, signature verification, idempotency), failed/retried payments and refunds, and never using real cards. Use when: "test Stripe checkout," "payment test," "3DS test," "test webhook signature," "test subscription renewal," "test clock," "refund test," "decline card test," "checkout E2E." Not for: General API contract testing of non-payment endpoints — api-testing. PCI-DSS/regulatory compliance audit — compliance-testing. Related: api-testing, playwright-automation, compliance-testing, test-data-management, qa-project-context.
- Publisher / source
- petrkindlmann/qa-skills (found on skills.sh)
- Upstream record
- petrkindlmann/qa-skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-02
- Content fingerprint
ab76ecc58d16d0ad3d59678a49c1f01c1ed0eb54dd1363df2e2884cc5386155c