Perform a test purchase with cards
To test your integration with credit and/or debit cards you should perform a test purchase with these payment methods, simulating the actions of a buyer user.
The Checkout SDK does not have a sandbox mode flag: the test environment is activated by the credential. Initialize the SDK with a test Public Key — the entire flow runs without moving real money.
- Access Your integrations > Application details > Credentials in the Developer Panel.
- Copy the test Public Key of your application.
- Initialize the SDK with this credential, as shown in the example below.
- Open the checkout flow in the application and use the test cards in the form — they do not generate any real charge.
- The payment result is controlled by the cardholder name entered in the form.
kotlinMercadoPagoSDK.initialize( context = this, publicKey = "{{YOUR_PUBLIC_KEY}}", countryCode = CountryCode.BRA )
Mercado Pago provides test cards that will allow you to test payments without using a real card.
Their data, such as number, security code, and expiration date, can be combined with the data relating to the cardholder, which will allow you to test different payment scenarios. That is, you can use the information of any test card and test different payment results based on the cardholder's data.
Below, you can see the data of the test debit and credit cards. Select the one you want to use to test your integration.
| Card type | Flag | Number | Security code | Expiration date |
| Credit card | Mastercard | 5480 8328 0103 3311 | 123 | 11/30 |
| Credit card | Visa | 4235 6477 2802 5682 | 123 | 11/30 |
| Credit card | American Express | 3753 651535 56885 | 1234 | 11/30 |
| Debit card | Elo | 5067 7667 8388 8311 | 123 | 11/30 |
Next, choose which payment scenario to test and fill in the cardholder's information (First name and last name, Document type and number) as indicated in the table below.
| Payment Status | Cardholder’s first and last name | Identity document |
| Approved payment | APRO | (CPF) 12345678909 |
| Declined for general error | OTHE | (CPF) 12345678909 |
| Pending payment | CONT | - |
| Declined with validation to authorize | CALL | - |
| Declined for insufficient amount | FUND | - |
| Declined for invalid security code | SECU | - |
| Declined due to due date issue | EXPI | - |
| Declined due to form error | FORM | - |
| Rejected for missing card_number | CARD | - |
| Rejected for invalid installments | INST | - |
| Rejected for duplicate payment | DUPL | - |
| Rejected for disabled card | LOCK | - |
| Rejected for non-permitted card type | CTNA | - |
| Rejected due to exceeded PIN attempts | ATTE | - |
| Rejected for being on the blacklist | BLAC | - |
| Not supported | UNSU | - |
| Used to apply amount rules | TEST | - |
To verify whether the test purchase was completed correctly, send a request to the /v1/orders/{id}GET endpoint, replacing id with the order identification.
For end-to-end flows, create test users in Your integrations > Tests > Test accounts in the Developer Panel.
To make a successful test purchase, fill in the required data at checkout following the information indicated below.
Buyer email
In the email field, enter the email address test@testuser.com, which is the only one allowed for testing. This way, your system will understand that it is a purchase made with a test buyer user.
Card details
Mercado Pago provides test cards that will allow you to test payments without using a real card.
Their data, such as number, security code, and expiration date, can be combined with the data relating to the cardholder, which will allow you to test different payment scenarios. That is, you can use the information of any test card and test different payment results based on the cardholder's data.
Below, you can see the data of the test debit and credit cards. Select the one you want to use to test your integration.
| Card type | Flag | Number | Security code | Expiration date |
| Credit card | Mastercard | 5480 8328 0103 3311 | 123 | 11/30 |
| Credit card | Visa | 4235 6477 2802 5682 | 123 | 11/30 |
| Credit card | American Express | 3753 651535 56885 | 1234 | 11/30 |
| Debit card | Elo | 5067 7667 8388 8311 | 123 | 11/30 |
Next, choose which payment scenario to test and fill in the cardholder's information (First name and last name, Document type and number) as indicated in the table below.
| Payment Status | Cardholder’s first and last name | Identity document |
| Approved payment | APRO | (CPF) 12345678909 |
| Declined for general error | OTHE | (CPF) 12345678909 |
| Pending payment | CONT | - |
| Declined with validation to authorize | CALL | - |
| Declined for insufficient amount | FUND | - |
| Declined for invalid security code | SECU | - |
| Declined due to due date issue | EXPI | - |
| Declined due to form error | FORM | - |
| Rejected for missing card_number | CARD | - |
| Rejected for invalid installments | INST | - |
| Rejected for duplicate payment | DUPL | - |
| Rejected for disabled card | LOCK | - |
| Rejected for non-permitted card type | CTNA | - |
| Rejected due to exceeded PIN attempts | ATTE | - |
| Rejected for being on the blacklist | BLAC | - |
| Not supported | UNSU | - |
| Used to apply amount rules | TEST | - |
Once you have completed all the fields correctly, click the button to process the payment and wait for the result.
To verify that the test purchase was carried out according to the expected results based on the data entered, send a request to the /v1/orders/{id}GET endpoint, replacing id with the order identification, received in the response to its creation.
APP_USR.Ready! Once these steps are completed, the integration of cards as a payment method is complete, and you can either continue testing other integrated payment methods, or go to production.