Stripe, approved payment
- Input
- 4242 4242 4242 4242 | 12/34 | 123
- Expected output
- Visa aprovado em modo de teste
On Stripe any future expiry and any 3-digit CVC work (4 digits on American Express).
Carregando ferramenta… / Loading tool…
test credit card numbers
Testing a checkout with a real card is risky and, on most gateways, does not even work in a test environment. This page gathers two kinds of number: the sandbox cards each gateway publishes (which trigger approval, decline or 3D Secure on demand) and generated numbers that only pass format validation and the Luhn check digit.
On Stripe any future expiry and any 3-digit CVC work (4 digits on American Express).
Use it to test the decline message and the checkout retry path.
Switching the cardholder to FUND, SECU or OTHE simulates other declines with the same card.
The validator shows the brand, the length and which final digit would make the number pass.
No. They only satisfy the public format and the Luhn checksum, so forms and validators accept them. They are not linked to any bank, have no balance and cannot pay for anything. Never use them to attempt a purchase or any kind of fraud.
No. Luhn-valid numbers are not real accounts: they have no balance, are not tied to any bank and are declined on any real purchase. Sandbox cards only work with test API keys. Trying to use them to pay or to get past a real check can amount to fraud.
Because each gateway only recognizes its own list of test cards. A random number passes form validation but is not on that list, so the gateway treats it as an unknown card and declines it. To exercise the payment flow end to end, use the cards in Sandbox mode.
Everything runs locally in the browser. Analytics receives only the action, mode and options, never the card numbers or the pasted list.