Can I use these cards in production?

No. They only work in each gateway's sandbox or test environment and don't make real purchases. In production the transaction goes to the card network and the issuer, which don't know these numbers.

Does one gateway's card work at another?

Usually not. Each sandbox recognizes its own list, and several only look at the last digit, the amount or the cardholder name. A Stripe card, for example, comes back with an error in Rede's sandbox, which only accepts the cards on its own list.

What to do when a gateway doesn't publish cards?

Asaas, Efí, Cielo and Stone have no fixed list to approve. Use a number that passes Luhn, like the ones from the credit card generator, and follow the gateway's rule: the last digit at Efí and Cielo, the amount at Stone and any valid number at Asaas.

Why do some numbers fail Luhn?

Two cases show up here, and both are flagged in the table. Stripe's 4242 4242 4242 4241 fails on purpose, to simulate an incorrect number. Cielo's example fails because its sandbox only checks the format and the ending of the number.

Why does the cardholder name change the result?

At Mercado Pago and PayPal, the sandbox reads the cardholder name as a scenario code. With the same card, APRO approves and OTHE declines at Mercado Pago, and a CCREJECT trigger at PayPal makes a success card get declined.

Why does the transaction amount change the result?

Rede, Braintree, Stone and PagBank's 3D Secure cards use the amount as a signal. At Rede, an amount of 111 returns insufficient funds. At Braintree, amounts from 2,000.00 to 2,999.99 are declined by the processor.

Is the data up to date?

Each group shows the date we read the official docs. Gateways change their sandbox without notice, so if a card fails, open the source link and compare.

Has PagBank's 12/2026 expiry passed?

It is the expiry the official docs publish for the test cards. If the date has passed when you test, the sandbox may decline the card. In that case, check PagBank's docs for a new expiry.

Test Cards for Payment Gateway Sandboxes

Cards, amount rules and cardholder names that the official docs of 14 gateways publish for testing payments in the sandbox. Pick a gateway, copy the number and check the source and the date we read it.

These numbers are for testing and only work in each gateway's sandbox. They don't make real purchases and don't belong in production.

Mercado Pago

The cardholder name decides the result: APRO approves, OTHE declines and each code simulates a reason. The same 4 cards work for every scenario.

Test cards

Source:official docsChecked on Oct 6, 2026

The cardholder name decides the result

Type the code from the rules table in the cardholder name field to simulate each scenario.

Any card works for any scenario, and the cardholder name changes the result. On the Web, the buyer email must be test@testuser.com.

Number	Brand	CVV	Expiry
5480 8328 0103 3311	Mastercard Credit	123	11/30
4235 6477 2802 5682	Visa Credit	123	11/30
3753 6515 3556 885	American Express Credit	1234	11/30
5067 7667 8388 8311	Elo Debit	123	11/30

Cardholder name and result

Source:official docsChecked on Oct 6, 2026

The cardholder name decides the result

Type the code from the rules table in the cardholder name field to simulate each scenario.

When	Expected result	Extra data
APRO	Approved	(CPF) 12345678909
OTHE	Declined	(CPF) 12345678909
CONT	Pending
CALL	Declined, validation needed to authorize
FUND	Declined for insufficient funds
SECU	Declined for invalid CVV
EXPI	Declined for expired card
FORM	Declined for form error
CARD	Rejected for missing card number
INST	Rejected for invalid installments
DUPL	Rejected for duplicate payment
LOCK	Rejected for disabled card
CTNA	Rejected for card type not allowed
ATTE	Rejected for exceeded PIN attempts
BLAC	Rejected for being on the blacklist
UNSU	Not supported
TEST	Applies the amount rule

Need a card number that passes Luhn for the sandbox?

Generate card

How to use the Test Cards?

Pick the gateway

Click the gateway you integrate with. The address gets an anchor, like #mercado-pago, that you can share.

See what decides the result

At some gateways it is the card. At others it is the last digit, the amount or the cardholder name, and the rule shows up highlighted.

Send it in the sandbox

Copy the number and use it with the gateway's test credentials, with the CVV and expiry the table shows.

Check the source

Each group shows the link to the official docs and the date we read them. If something fails, start there.

How gateways decide the result

The sandbox doesn't go through the card network or the issuer, so the gateway needs a signal to choose between approving and declining. These are the signals the docs use.

The card number

Each number has a fixed result. Stripe, PagBank, Pagar.me and Getnet work this way.

The last digit

Any valid number works, and the ending picks the status. Efí and Cielo work this way.

The transaction amount

Rede, Braintree and Stone read the amount (or the cents) to return a code. At PagBank, the amount also decides the result of the 3D Secure cards.

The cardholder name

At Mercado Pago, APRO approves and OTHE declines. At PayPal, the CCREJECT-REFUSED trigger declines a card that would otherwise approve.

Sandbox only

The numbers on this page come from the gateways' docs and only have an effect in each one's test environment. You need the sandbox credentials to use them, and the result doesn't depend on balance or limit. Once you switch to the production key, the gateway sends the transaction to the card network and the issuer, which don't know these numbers.

Test Cards FAQ

What usually trips people up when testing payments in the sandbox.