AI resources

Make a test purchase with cards

With the test order created, use Mercado Pago test cards to simulate different payment results. Available scenarios include approved, rejected, and pending payments, allowing you to validate how your integration handles each situation before going to production.

Test a card purchase

To test a purchase with a credit or debit card, follow the steps below.

Go to Mercado Pago Developers and log in with a test buyer account you previously created. Use the username and password assigned to it. You can find these details in Test the integration > Get a test buyer account.

If an email verification code is requested when logging in, enter the 6-digit code associated with your test account. You can find it in Your integrations > Your application > Test accounts.

Go to the store where you integrated Checkout Pro, select a product or service, and start the purchase process at the payment step.
When your integration creates the order and generates the checkout_url, you will be redirected to the Mercado Pago payment form.
Finally, complete a test purchase using the test card data in the next section. The cardholder name defines the simulated payment result.

Test cards

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	5031 7557 3453 0604	123	11/30
Credit card	Visa	4509 9535 6623 3704	123	11/30
Credit card	American Express	3711 803032 57522	1234	11/30
Debit card	Mastercard	5287 3383 1025 3304	123	11/30
Debit card	Visa	4002 7686 9439 5619	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`	(DNI) 12345678
Declined for general error	`OTHE`	(DNI) 12345678
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`	-

Verify the result

To confirm the result of each test purchase, send a GET to the endpoint /v1/orders/{id}API including your test Access TokenTest private key of the application created in Mercado Pago, used in the backend. You can access it through Your integrations > Integration data > Test credentials.:

curl
curl -X GET \
    -H 'Authorization: Bearer ENV_ACCESS_TOKEN' \
    'https://api.mercadopago.com/v1/orders/{id}'

Replace {id} with the id of the order obtained when creating it. The status field in the response will indicate the transaction result for the tested scenario. For all possible statuses, see the Order status documentation.

Introdução

Teste a sua integração antes de entrar em produção.

Subir em produção

Com sua integração configurada e verificada, é hora de sair à produção.