These decline reasons occur due to errors during checkout. This can happen for various reasons, such as misunderstanding of the payment screen, buyer experience issues, lack of field validation, or errors that the buyer may make when entering their data, especially card information.

In these cases, the status_detail field will return:

• cc_rejected_bad_filled_card_number
• cc_rejected_bad_filled_date
• cc_rejected_bad_filled_other
• cc_rejected_bad_filled_security_code

When making a credit or debit card payment, for example, the issuing bank may decline the charge for different reasons, such as expired expiration date, insufficient balance or credit limit, disabled card, or card blocked for online purchases.

In these cases, the status_detail field may return:

• cc_rejected_call_for_authorize
• cc_rejected_card_disabled
• cc_rejected_duplicated_payment
• cc_rejected_insufficient_amount
• cc_rejected_invalid_installments
• cc_rejected_max_attempts

We monitor transactions in real-time looking to recognize suspicious patterns and resources that indicate a fraud attempt. This is done by both Mercado Pago's algorithms and banks, all to minimize chargebacks as much as possible.

When our fraud prevention system detects a suspicious payment, the status_detail field may return:

• cc_rejected_blacklist
• cc_rejected_high_risk
• cc_rejected_other_reason

The response cc_rejected_other_reason is a status given by the bank that doesn’t mention the reason of the rejection, but indicates a fraude risk estimation. However, there may be other reasons why this status is returned. In case of doubt, it is recommended to choose other payment method to fulfill the transaction or to get in touch with the issuer bank institution.

json
Copiar
{
    "status": "rejected",
    "status_detail": "cc_rejected_high_risk",
    "id": 47198050,
    "payment_method_id": "master",
    "payment_type_id": "credit_card",
    ...
}