testland/payment-flow-states-reference

Pure-reference catalog of payment lifecycle state machines across Stripe, Adyen, PayPal, and Braintree: canonical states (created / requires_action / processing / succeeded / requires_capture / canceled / failed), authorisation vs capture, asynchronous webhook states, refund / dispute / chargeback transitions, and the 3-D Secure (EMVCo 3DS 2.x) frictionless / challenge flow paths with per-gateway 3DS test cards (references/3ds-flows.md). Use when designing tests for payment flows, auditing state-handling code, or covering a 3DS round-trip; this is the state model, not a builder - to author suites on it use payment-flow-test-author (refunds, disputes, webhook replay).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Gateway 3DS test cards

Name: testland/payment-flow-states-reference
Rating: 72 (1 reviews)
Author: testland

Per-PAN test cards that drive 3DS challenge, frictionless, and bypass flows in each gateway's test mode. Cross-referenced from 3ds-flows.md. For single-gateway work, prefer the gateway skills (stripe-test-cards-and-webhooks, payment-gateway-sandboxes).

Stripe

Per docs.stripe.com/testing#regulatory-cards:

Card	Behaviour
4000 0027 6000 3184	Authentication required (challenge)
4000 0025 0000 3155	Authentication required (challenge), payment failure after success
4000 0000 0000 3220	Authentication required (challenge), payment success
4000 0000 0000 3055	3DS supported but not required (frictionless)
4242 4242 4242 4242	Standard test card (no 3DS)