# Response handling Payments can fail for a variety of reasons and it’s frustrating when they result in the loss of legitimate business. Many payments fail for good reason and do so to minimize the possibility of a fraudulent payment. There are three possible reasons why a credit card payment might fail: * Payments declined by card issuers * Blocked payments * Invalid API Calls Each type of failure is handled differently. The reason for a payment’s failure is provided within the payment’s details in the Dashboard and through the API response. This parameter includes the type of payment failure, along with additional information about the reason for it. ## Card issuers decline codes There are many reasons why card schemes refuse a transaction. The corresponding authorization responses we receive are not the same for all schemes, and change from time to time. On this page, we describe the most common raw acquirer responses related to refused or cancelled transactions.

DECLINE CODE	DESCRIPTION	NEXT ACTION
`Decline`	The card was declined for an unknown reason.	The customer needs to contact their card issuer for more information. Other codes for similar reasons: `Deny` `declined` `transaction declined for unknown reason`
`Do not honor`	The card was declined for an unknown reason.	The customer needs to contact their card issuer for more information. Other codes for similar reasons: `Unable to authorise` `Do not honour`
`Insufficient funds`	The card has insufficient funds to complete the purchase.	The customer needs to use an alternative payment method or try with another card. Other codes for similar reasons: `Not sufficient funds Insufficient funds/over credit limit`
`Closed account`	The account is closed.	Re-validate the account number for accuracy and do not reattempt with the same PAN or token. Other codes for similar reasons: `Closed account.` `Closed account by issuer. Issuer will not approve same amount in next 30 days`
`CVV2 Failure`	The CVC number is incorrect.	The customer needs to try again using the correct CVC. Other codes for similar reasons: `Invalid CVV2` `Invalid card security code` `Decline for CVV2 failure` `transaction declined (invalid CVV)`
`Invalid Card Number`	Account number was never issued or has been permanently blocked or closed.	The customer needs to try again using the correct card number. Other codes for similar reasons: `Invalid account number (no such number)` `invalid card number`
`Expired card`	The card has expired.	The customer needs to enter the correct card number/expiry date or use another card. Other codes for similar reasons: `Invalid payment details : Expiry date` `transaction declined (wrong expiry date)`
`Exceeds amount limit`	The customer has exceeded the balance or credit limit available on their card.	The customer needs to use an alternative payment method or try with another card. Other codes for similar reasons: `Exceeds withdrawal amount limit`
`Exceeds frequency limit`	The customer has exceeded the balance or credit limit available on their card.	The customer needs to use an alternative payment method. or try with another card. Other codes for similar reasons: `Exceeds withdrawal count limit`
`Suspected Fraud`	Issuer reported the transaction as suspected fraud.	The specific reason for the decline shouldn’t be reported to the customer. Instead, it needs to be presented as a generic decline. Other codes for similar reasons: `Suspected fraud` `suspected counterfeit card`
`Restricted card`	The customer can’t use this card to make this payment (it’s possible it was reported lost or stolen).	The customer needs to contact their card issuer for more information. Other codes for similar reasons: `transaction declined (restricted card)`
`Not permitted on card`	The payment isn’t permitted.	Card issuer does not permit the transaction on this card/account. The customer can use another payment method or contact their bank. Other codes for similar reasons: `Transaction not permitted to acquirer/terminal` `Transaction not permitted to cardholder` `Transaction not permitted to issuer/cardholder` `Authorization not permitted at this time due to policy`
`Security Violation`	The card issuer indicated a security issue with this card.	The customer can use another payment method. Alternatively, the customer can try again after they resolved the issue with their bank. Other codes for similar reasons: `security violations` `Fraud/Security related reasons`
`Policy reasons`	The card was declined for an unknown reason.	The customer needs to contact their card issuer for more information.
`Rejected by Acquirer Risk Management`	The payment was declined by Acquirer for risk reasons	Don’t report more detailed information to your customer. Instead, it needs to be presented as a generic decline.
`3D Authentication Failed`	3D Secure authentication was not executed, or it did not execute successfully.	The customer should try again and authenticate their card when prompted during the transaction. Other codes for similar reasons: `Cardholder 3D Authentication failure!`
`Transaction does not exist`	Transaction does not exist.Most probably the user did not complete 3DS authentication	The customer should try again and authenticate their card when prompted during the transaction.
`Invalid Transaction`	The card issuer does not allow this type of transaction on this card/account. For example, the card is a fleet card for which this type of transaction is not permitted.	The customer needs to contact their card issuer for more information.
`Cardholder 3D Authentication rejected!`	Transaction declined by issuer.	The customer needs to contact their card issuer for more information.
`Pickup Card`	The customer can’t use this card to make this payment (it’s possible it was reported lost or stolen).	They need to contact their card issuer for more information. Other codes for similar reasons: `Pickup card (stolen card)` `Pick-up card` `Lost card, pick-up` `transaction declined (pick up card)`
`Capture card`	Blocked/cancelled cards due to confirmed previous fraudulent situation (other than lost/stolen）	Don’t report more detailed information to your customer. Instead, it needs to be presented as a generic decline.
`Stolen card, pick-up`	The payment was declined because the card is reported stolen.	The specific reason for the decline shouldn’t be reported to the customer. Instead, it needs to be presented as a generic decline.
`Blocked, first used-transaction from new cardholder`	New card that has not been activated -or- card has been temporarilyspecial condition blocked due to a special condition.	The card used for the transaction is blocked, the customer needs to contact their card issuer.
Invalid merchant or service provider	The card is not valid to be used at this Merchant or MCC.	The customer needs to contact their card issuer for more information.

## Blocked payments Moneycollect’s bigdata risk detection toolset, blocks high-risk payments, such as those with mismatched CVC or high risk country or a large number of identity change behaviors are detected.

Using the API, the `riskInfo`of a blocked payment reflects the type of payment failure and the reason for it, along with the risk level that was evaluated.

    "riskInfo": {
      "riskScore": 100,
      "riskMessage": "risk_rejected"
    },
    "status": "failed",
    "displayStatus": "failed",
    "errorCode": "risk_rejected",
    "errorMessage": "risk_rejected",

## Invalid API Calls As you develop your Moneycollect integration, good testing should identify any potential bugs that would lead to invalid API calls. Consequently these failures should be rare in production. Invalid API calls typically don’t result in a payment appearing in your Dashboard. Invalid API Calls have the same error code:'invalid\_parameter',and you can get detail error information from field msg. If you receive this type of error, you should correct the api parameters. ```json { "code": "invalid_parameter", "msg": "PaymentMethod.billingDetails.address: invalid country.", "data": null } ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.moneycollect.com/docs/payment/after-the-payment/response-handling.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.