# MD for: https://www.mercadopago.com.co/developers/pt/docs/split-payments-1-n/payment-management/improve-payment-approval/reasons-for-rejection.md

\# Why is a payment rejected? Payment declines are a reality in the world of online sales and can happen for various reasons. \*\*A payment may be declined due to\*\*: \* An error with the payment method; \* Incorrect information entered by the customer; \* Card with insufficient funds; \* Violation of necessary security requirements; \* Suspicious movements indicating fraud risk; \* Communication issues between acquirers and sub-acquirers. You can find \*\*information and check the status of a payment\*\* via API through the endpoint :TagComponent{tag="API" text="Get order by ID" href="/developers/en/reference/orders/online-payments/get-order/get"}. The \`transactions.payments.status\` field indicates whether the payment was approved or not, while the \`transactions.payments.status\_detail\` field provides more details, including reasons for decline. \`\`\`curl ... "transactions": { "payments": \[ { "id": "PAY01J67CQQH5904WDBVZEM4JMEP3", "amount": "24.90", "reference\_id": "01JEVQM899NWSQC4FYWWW7KTF9", "status": "failed", "status\_detail": "insufficient\_amount", ... \`\`\` > SUCCESS\_MESSAGE > > You can also find more information about payments in your \[Mercado Pago account\](https://www.mercadopago.com.co/activities) activity. :::AccordionComponent{title="Declines due to input errors"} These declines 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 \`transactions.payments.status\_detail\` field will return: \* \`bad\_filled\_card\_data\` ::: :::AccordionComponent{title="Declines by the issuing bank"} When making a \*\*credit or debit card payment\*\*, for example, the issuing bank may decline the charge for different reasons, such as passed expiration date, insufficient balance or credit limit, disabled card, or card blocked for online purchases. In these cases, the \`transactions.payments.status\_detail\` field may return: \* \`required\_call\_for\_authorize\` \* \`card\_disabled\` \* \`cc\_rejected\_duplicated\_payment\` \* \`insufficient\_amount\` \* \`invalid\_installments\` \* \`max\_attempts\_exceeded\` ::: :::AccordionComponent{title="Declines due to fraud prevention"} 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 \`transactions.payments.status\_detail\` field may return: \* \`high\_risk\` \* \`rejected\_by\_issuer\` \* \`cc\_rejected\_other\_reason\` > WARNING > > In some cases, the \`high\_risk\` response may occur when two consecutive payments are made with the same items or with very similar parameters (such as identical \`payer\` and \`items\` values in both payments made). This can trigger the anti-fraud engine, which may interpret the attempt as duplicated and reject it as a precaution. As a consequence, subsequent payments may be temporarily blocked. It is recommended to implement controls to prevent immediate new attempts with the same payment data. >   
  
\> The \`cc\_rejected\_other\_reason\` response is a status sent by the issuing bank. Although it does not specify the reason for the rejection, it is an estimate of fraud risk. However, there are other reasons why this status may be returned. If you are unsure, it is recommended to choose another payment method or contact the bank. :::