Stripe Test Card Numbers for Payment Sandbox & QA Testing

Last Updated: August 13, 2026

Access the complete list of Stripe test card numbers for sandbox testing. Verify Luhn algorithm checks, CVV responses, and payment gateway QA flows.

Testing ecommerce payment gateways is a critical step in software release checklists. However, you should never use real credit card numbers in a staging environment. Sandbox environments, like Stripe Test mode, allow developers to use simulated card numbers to verify checkout flows safely.

How Payment Gateways Verify Card Numbers

Before processing transactions, payment gateways run local checks:

• Luhn Algorithm (MOD 10): A simple checksum formula used to validate card number patterns.
• CVV & Expiration: Checks ensuring the card possesses a valid expiration date and 3-digit security code.

You can generate Luhn-valid card numbers for software QA testing using our Card Generator.

Stripe Test Cards Quick Reference

Stripe uses default codes to test different payment states:

• 4242 4242 4242 4242: Default Visa test card that always succeeds.
• 4000 0000 0000 3020: Triggers a declined card error for validation flow checks.

Frequently Asked Questions

Are generated test card numbers legal?

Yes. Test card numbers generated via Luhn algorithms are not real credit cards, do not have credit accounts attached, and cannot be used to purchase goods. They are strictly for software validation.

Do test cards work in live mode?

No. Payment gateways immediately block test cards if the transaction request is sent to a live production endpoint.

---