What is a test card expiry?

A test card expiry is the expiration date you enter alongside a sandbox card number in a payment gateway's test mode. Test cards are fake credentials published by processors such as Stripe, Adyen, and Braintree so developers can simulate payments without moving real money. The date you type is not tied to any real account.

related article

Do test card expiry dates ever expire?

Generic test cards stay usable indefinitely because the gateway only checks that the date is in the future. Stripe's standard card, 4242 4242 4242 4242, accepts any future month and year. Some processors publish a fixed expiration for scenario cards, and that value is hard-coded in their documentation.

Card Expiry Validation Guide

Because sandbox rules change without notice, the reliable source is always the gateway's own test data page. If a card that worked last quarter now fails with an expired card error, the required date likely changed.

Expiry Date Test Card Guide: Where to Buy CVV

Which expiry date should you use in test mode?

Pick a date at least one year ahead so your test suite does not break as real time passes. December of next year in MM/YY format works for nearly every gateway.

related article

• Stripe: any future date with the published test numbers.
• Adyen: the exact expiry listed next to each test card.
• Braintree: any future date for the standard test values.
• PayPal sandbox: the date set on the fake card in the developer dashboard.

How do you test an expired card decline?

Most processors ship a dedicated number that returns an expired card error instead of a successful charge. Stripe uses 4000 0000 0000 0069 for that decline case. Typing a past date into a generic number usually fails client-side validation before the request reaches the processor, which is a different path than a true issuer decline.

Why does a test card fail with an expiry error?

Three causes cover most failures: the date is in the past, the format does not match the field, or the card number requires one specific fixed expiration. Confirm the expected format first, since some gateways want MM/YY and others want MM/YYYY or separate fields. Scenario cards also change, so a value copied from an old tutorial is a common culprit.

Best practices for sandbox expiry data

• Keep test cards in fixtures or a seed script rather than live configuration.
• Run the same date parsing and validation logic in test and production so behavior matches.
• Refresh processor documentation each quarter, because scenario cards and fixed dates are updated.
• Never enter real card data into a sandbox, and never treat a sandbox number as a usable payment credential.