Home
Documentation
Resources
Partners
Community

Resources

Check for updates on our solutions and system performance, or request technical support.

Partners

Discover our program for agencies or developers that offer integration services and sellers who want to hire them.

Community

Get the latest news, ask others for help and share your knowledge.

Online payments
In-person payments
Tools and resources
APIs and SDKs
Perform a test purchase with cards - Integration test - Mercado Pago Developers

Perform a test purchase with cards

To test your integration with credit and/or debit cards, after configuring your test environment, you should perform a test purchase with these payment methods, simulating the actions of a buyer user.

To do this, access the store that has your checkout integrated, select a product or service, and start the purchase process.

Complete Payer Data

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 typeFlagNumberSecurity codeExpiration date
Credit cardMastercard5031 4332 1540 635112311/30
Credit cardVisa4235 6477 2802 568212311/30
Credit cardAmerican Express3753 651535 56885123411/30
Debit cardElo5067 7667 8388 831112311/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 | 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.

Verify Test Purchase

To verify that the test purchase was carried out according to the expected results based on the data entered, send a GET request to the /v1/orders/{id}API endpoint, replacing id with the order identification, received in the response to its creation.

The response to this call should bring the detailed information of the test transaction, along with the status chosen for the payment in the previous step within the status field.

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.