Free reference · Mercado Pago
Mercado Pago rejection codes
(status_detail) explained
When a payment is rejected, the status_detail field says why. This is the list from Mercado Pago's official documentation for Argentina and Brazil, with what each code means and what to do about it, whether you are the buyer, the seller or the developer.
Rejected payments
status is rejected. The payment was not accepted.
| status_detail | What it means |
|---|---|
| bank_error | The payment was made by bank transfer and was rejected because of an error at the bank. |
| cc_rejected_3ds_mandatory | The payment was rejected because it did not go through the 3DS challenge, which was mandatory. |
| cc_rejected_bad_filled_card_number | The card number looks wrong. Mercado Pago asks the buyer to check it. |
| cc_rejected_bad_filled_date | The expiration date looks wrong. Mercado Pago asks the buyer to check it. |
| cc_rejected_bad_filled_other | The documentation only says to check the data, without saying which one is wrong. |
| cc_rejected_bad_filled_security_code | The card's security code looks wrong. Mercado Pago asks the buyer to check it. |
| cc_rejected_blacklist | Mercado Pago could not process the payment. The documentation gives no reason, so don't tell the buyer one. |
| cc_rejected_call_for_authorize | The buyer has to authorize this payment of this amount with the payment method provider before it can be accepted. |
| cc_rejected_card_disabled | The card is not active. The buyer has to call the card provider to activate it or use another payment method. |
| cc_rejected_card_error | Mercado Pago could not process the payment. The documentation gives no reason, and it uses the same text as cc_rejected_blacklist. |
| cc_rejected_duplicated_payment | The buyer already made a payment for that same amount. |
| cc_rejected_high_risk | The payment was rejected. The documentation gives no reason; it recommends choosing another payment method, preferably a cash one. |
| cc_rejected_insufficient_amount | The payment method does not have enough funds for this payment. |
| cc_rejected_invalid_installments | The payment method does not process payments in the number of installments that was requested. |
| cc_rejected_max_attempts | The buyer reached the limit of allowed attempts. The documentation says to select a different card or payment method. |
| cc_rejected_other_reason | The payment method did not process the payment. The documentation does not give a more specific reason. |
| cc_amount_rate_limit_exceeded | The payment was rejected because it exceeded the payment method's limit, called CAP (Capacidad Máxima Permitida, the maximum allowed capacity). |
| rejected_insufficient_data | The payment was rejected because some of the mandatory information was missing from the request. The code does not say which field is missing. |
| rejected_by_bank | The bank rejected the operation. The documentation gives no reason. |
| rejected_by_regulations | The payment was rejected because of regulations. The documentation does not say which regulation applies. |
| insufficient_amount | The payment was rejected for insufficient amounts. The documentation does not explain further; for a card with too little balance it lists a different code, cc_rejected_insufficient_amount. |
| cc_rejected_card_type_not_allowed | The payment was rejected because the user does not have the credit function enabled on their multiple (debit and credit) card. This code is listed in Mercado Pago's Brazil documentation and not on the Argentina pages. |
Pending payments
status is pending. The payment is waiting for the buyer to do something.
| status_detail | What it means |
|---|---|
| pending_waiting_transfer | Bank transfer payment: it stays pending while the buyer completes the payment process at their bank. |
| pending_waiting_payment | Offline payment: it stays pending until the buyer makes the payment. |
| pending_challenge | Credit card payment: a confirmation is pending because of a challenge. |
Payments in process
status is in_process. Mercado Pago is still processing the payment.
| status_detail | What it means |
|---|---|
| offline_process | Because online processing was not available, the payment is being processed offline. |
| pending_contingency | Mercado Pago is processing the payment. According to the documentation, the buyer is told by email within 2 business days whether it was credited. |
| pending_review_manual | Mercado Pago is processing the payment. According to the documentation, the buyer is told by email within 2 business days whether it was credited or whether more information is needed. |
What this list covers
It lists all the status_detail values for the rejected, pending and in_process statuses that appear on Mercado Pago's official "payment creation results" pages for Argentina and Brazil as of 2026-11-04; other countries' pages may differ. cc_rejected_card_type_not_allowed appears only in Brazil's documentation. Approved and authorized payments are left out. The Orders API documents its own, different set of status_detail values on a separate page, and those are not covered here.
Source: Mercado Pago developer documentation, verified on 2026-11-04. Payment creation results (Mercado Pago)
Questions about Mercado Pago rejection codes
What is status_detail in Mercado Pago?+
It is the field of a payment that gives the reason behind its status. A rejected payment, for example, comes with a status_detail such as cc_rejected_other_reason or cc_rejected_high_risk that says why it was rejected.
Does a pending or in_process status_detail mean the payment failed?+
No. Codes such as pending_waiting_payment or pending_review_manual describe a payment that has not been resolved yet. Keep the order pending and wait for the final status instead of creating a second payment.
Are these all the codes Mercado Pago can return?+
They are all the rejected, pending and in_process codes listed on Mercado Pago's official "payment creation results" pages for Argentina and Brazil as of 2026-11-04; other countries' pages may differ. Mercado Pago can also change its documentation, so check the source link on each page.
| Price | Founder $99 or Lifetime $199, one-time payment (no subscription) |
|---|---|
| License | Full source, commercial use, unlimited projects. Founder is a frozen snapshot; Lifetime includes every future release. |
| Stack | Next.js frontend, Express API, Bun runtime, Prisma, BetterAuth |
| Auth | BetterAuth: sessions, 2FA, magic links, password reset |
| Multi-tenancy and RBAC | Organizations with members, invitations, roles and permissions |
| Payments | Polar: full billing (checkout, customer portal, webhooks, plan sync). MercadoPago: Checkout Pro one-time payments with signed webhooks; subscriptions are not supported yet. Stripe: adapter scaffold, not charging yet. |
| Guardrails for AI agents | ESLint-enforced architecture layers, Claude Code hooks and an AGENTS.md |
| Refund | 14 days |
| Try it: free account | Sign up free and explore the dashboard: organizations, roles, billing, audit log. You buy the license from inside. https://usedeploy.dev/register |
| Docs | Documentation in English, with Spanish and Portuguese translations of the main guides |