payment-testing

Test payment and checkout flows against PSP sandboxes with Playwright.

2|Updated Apr 18, 2021

Search Tags:#playwright #stripe #webhooks #checkout #3ds #payment testing #test clocks

Ready to run

npx skills add https://github.com/rabbicse/go-projects --skill payment-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: payment-testing
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/payment-testing
Command: npx skills add https://github.com/rabbicse/go-projects --skill payment-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams test payment and checkout flows the way they fail in production, without using real cards or live payment keys.

Core Features & Use Cases

Validates success, decline, insufficient-funds, and 3DS challenge paths in PSP sandboxes, with Stripe as the primary flow.
Covers webhook delivery, signature verification, duplicate event handling, and order fulfillment that must wait for verified server-side payment events.
Simulates subscription renewals, failed recurring charges, and refunds with server-side test clocks so billing scenarios can be reproduced on demand.
Extends the same testing pattern to Adyen, PayPal, and Braintree by swapping in each provider's sandbox cards, buyer accounts, and notification model.

Quick Start

Ask the assistant to design or debug a sandbox payment test for your checkout flow, including the correct test card, webhook setup, and Playwright steps needed for your PSP.

Frequently Asked Questions about payment-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I test Stripe checkout flows and 3DS challenges without real cards?▼

To test Stripe checkout flows and 3DS challenges without real cards, you use PSP sandbox mode with test-mode credentials and specific test cards. Playwright automates the nested iframe interactions required for SCA challenges to validate success and decline paths safely.

How do I simulate subscription renewals and failed recurring charges in Stripe?▼

To simulate subscription renewals and failed recurring charges in Stripe, you use server-side test clocks. Test clocks allow you to advance billing time on demand, reproducing recurring billing scenarios and refund flows without waiting for real time to pass.

Can I use the same payment testing pattern for Adyen, PayPal, and Braintree sandboxes?▼

Yes, you can apply the same payment testing pattern to Adyen, PayPal, and Braintree sandboxes. You swap in each provider's specific sandbox cards, buyer accounts, and notification models while maintaining the same end-to-end Playwright automation structure.

Why does my Playwright test fail when handling 3DS iframe challenges in a sandbox?▼

Playwright tests fail handling 3DS iframe challenges in a sandbox due to improper nested iframe handling. The testing process requires specific Playwright configurations to interact with elements inside the nested PSP challenge iframes to complete the SCA flow.

What's the best way to test payment declines and insufficient funds in a checkout flow?▼

The best way to test payment declines and insufficient funds in a checkout flow is by using designated sandbox test cards provided by the PSP. The Skill validates these specific failure paths end-to-end against the sandbox environment without touching live payment keys.