What it is
Payment processors like Stripe only accept specific, published card numbers in test/sandbox mode — not just any Luhn-valid number — and each one is wired to trigger a particular outcome: a successful charge, a specific decline reason, a 3D Secure challenge, and so on.
When to use it
Reach for this while building or QA-ing a checkout flow, to exercise a specific failure path (insufficient funds, expired card, incorrect CVC) or the 3D Secure/SCA challenge without needing a real card, and to pair with the Stripe Fee Calculator when estimating what a successful test charge would net after fees.
Gotchas & limits
These numbers only work in a processor's test/sandbox mode — they are never real, chargeable cards and will always be rejected in a live/production environment. Stripe periodically adds or retires test numbers, so treat this as a curated snapshot of their published list rather than an exhaustive, always-current mirror.