Suggest edit
Help us improve the documentation
Did you see wrong information and would you like us to explain something else or improve our manuals? Please leave your suggestions on GitHub.

Test your integration

We will explain how to use our test cards and users to check that your payments are correctly created and your messages are effective.

How to test your integration

Test users allow you to test your integration by generating payment flows in an exact copy of your integration.

Types of users Description
Seller It is the test account you use to configure the application and credentials for collection.
Buyer It is the test account you use to test the purchase process.

How to create users


First, you should have, at least, two test users: a buyer and a seller.

Execute the following curl to generate a test user:


curl -X POST \
-H "Content-Type: application/json" \
-H 'Authorization: Bearer PROD_ACCESS_TOKEN' \
"" \
-d '{"site_id":"MLM"}'



    "id": 123456,
    "nickname": "TT123456",
    "password": "qatest123456",
    "site_status": "active",
    "email": ""
  • Both buyer and seller must be test users.
  • You can generate up to 10 simultaneous test user accounts. Therefore, we recommend you save each email and password.
  • Test users expire after 60 days without activity in Mercado Pago.
  • To make test payments we recommend using low amounts.
  • Amounts should be within the minimum and maximum values for each payment method.

Test the payment flow

      1. Configure the integration with seller user data

Configure your seller user's test public key at your application frontend, and the test private key at the backend.

      2. Make a payment with your buyer user

        Credit card tests

Start your integration with your test seller user credentials:

  1. Fill out test card data.
  2. Enter your test buyer user e-mail.
  3. Confirm purchase. Done!

Test Cards

Card Number CVV Expiration Date
Mastercard 5474 9254 3267 0366 123 11/25
Visa 4075 5957 1648 3764 123 11/25

To test different payment results, complete the information you want in the name of the cardholder:

  • APRO: Payment approved.
  • CONT: Payment pending.
  • OTHE: Rejected by general error.
  • CALL: Rejected with validation to authorize.
  • FUND: Rejected for insufficient amount.
  • SECU: Rejected by invalid security code.
  • EXPI: Rejected due to problem with expiration date.
  • FORM: Rejected by error in the form.

Consider that you can't test the entire flow for cash payment methods.

Start receiving payments

To start charging, you need to meet the production environment requirements, and must activate your credentials.

Before activating them, verify that the credentials in your integration are those of the account that receives the money from the sales.

Next steps

Your search returns no results.

Verifique a ortografia de termos de pesquisa ou teste com outras palavras-chave.