How to use 3DS test cards
- 1. Use test keys. 3DS flows only work in Stripe test mode with pk_test_ / sk_test_.
- 2. Copy a 3DS PAN. 4000002760003184 requires 3D Secure 2 authentication.
- 3. Complete authentication. In Checkout or Elements, finish the test challenge when prompted.
- 4. Verify status. PaymentIntent may show requires_action before succeeded.
About this tool
Strong Customer Authentication shows up when a test PAN is designed to force 3DS. These numbers are for exercising redirect flows, mobile challenges, and webhook timing — not for skipping authentication.
Which Stripe cards force 3DS?
4000002760003184, 4000002500003155, and 4000008400001629 are documented 3D Secure test PANs. Behavior can differ by integration — Payment Element vs legacy Card Element vs Checkout.
3DS is not a decline
requires_action means the customer must authenticate. After a successful test auth, the charge can still succeed. Use decline cards in the Stripe section when you need a hard failure.
Code examples
Stripe Visa (success)
4242424242424242
Expiry: 12/34 CVV: 123 ZIP: 42424Razorpay domestic Visa
4111111111111111
Expiry: any future date CVV: any 3 digitsRazorpay UPI success
success@razorpayStripe PaymentIntent test JSON
{
"number": "4242424242424242",
"exp_month": 12,
"exp_year": 34,
"cvc": "123"
}