Skip to main content

​
Test Cards

Everything you need to know about test cards

​
Cards for testing

Here there are some testing cards.
CardNumberCVCDue Date
Mastercard5031 4332 1546 635112311/25
Visa4235 6471 2692 568212311/25
Amex3753 651551 54995123411/25

​
Documents for Scenarios

The result of the payment of the charge is linked to the document, so it is important that when creating the charge the document is informed according to the expected result.
DocumentStatusReason
34960826312confirmedApproved payment.
45131731265rejectedRenew the card expiration date.
70814577358rejectedReview the data on the card.
38532397400rejectedReview the card security code.
10322493562rejectedCard disabled/ blocked.
58125837746rejectedYou have already made a payment with this amount. If you need to pay again, use another card or other form of payment.
27943315625rejectedInsufficient balance (money) not this transaction.
87782371525rejectedThe card issuing bank declined payment. Please use another card or contact your bank.

​
Retry

In cases of status Rejected it is possible after the generation of the error, try to pay the charge again, but this made in order to approve the payment, re-approve a rejected payment, on mercadopago simply use a Pix card Visa.

​
Example:

CardNumberCVCDue Date
Visa4235 6471 2692 568212311/25

​
Refund

Charges that have been confirmed may be chargeback, the chargeback status is listed in the Reason entered in the chargeback request.
ReasonScenario
APROApproved refund
REJECTrejected refund
CANCELcancelled refund
Any other Reason informed from the mapped scenarios returns default error fallback.

​
Testing Flow

1

Create a charge

Use the Create Charge endpoint with one of the test cards above
2

Use test document

Select a document from the scenarios table to test different payment outcomes
3

Process payment

Complete the checkout process using the test card and document
4

Verify status

Check the payment status based on the document used
5

Test retry (optional)

For rejected payments, retry with the Visa test card to approve
6

Test refund (optional)

For confirmed payments, test the refund flow with different reasons

​
Best Practices

Sandbox Environment: Always use test cards in the sandbox environment. Never use real card numbers for testing.
Document Matching: The payment result is directly linked to the document (CPF/CNPJ) used. Make sure to use the correct document for the scenario you want to test.
Complete Testing: Test all scenarios including approved, rejected, retry, and refund flows to ensure your integration handles all cases properly.

​
Common Test Scenarios

Document: 34960826312Expected Result: Payment confirmed and approvedUse this scenario to test the happy path of your integration.
Document: 45131731265Expected Result: Payment rejected - “Renew the card expiration date”Test how your application handles expired card errors.
Document: 27943315625Expected Result: Payment rejected - “Insufficient balance”Test how your application handles insufficient funds scenarios.
Document: 58125837746Expected Result: Payment rejected - “You have already made a payment with this amount”Test duplicate payment detection.
Document: 87782371525Expected Result: Payment rejected - “The card issuing bank declined payment”Test how your application handles bank-side rejections.

​
Refund Testing

To test refunds, first create a successful payment using document 34960826312, then request a refund with one of the following reasons:

APRO

Approved refundRefund will be processed successfully

REJECT

Rejected refundRefund will be rejected

CANCEL

Cancelled refundRefund will be cancelled

Create Charge

Create a new credit card charge

Rejection Status

Understanding rejection reasons

Transparent Checkout

Learn about transparent checkout

About Credit Card

Learn about credit card charges