Skip to main content
During the transparent checkout (or regular checkout) some transactions might be rejected due to one or another issues regarding or not the credit card itself. Here follows a complete list of status_details that might occur.

Incorrect credit card information:

Incorrect card numberThe card number provided is invalid or incorrect.
Incorrect card due dateThe expiration date provided for the card is incorrect.
Incorrect card security codeThe CVV/security code provided is incorrect.
Any other card-related incorrect informationOther card information provided is incorrect or invalid.

General credit card issues:

Disabled credit cardThe card has been disabled by the issuing bank and cannot be used for transactions.
General credit card errorA general error occurred with the credit card processing.
Credit card with insufficient fundsThe card does not have sufficient available credit to complete the transaction.

Internal issues:

Credit card type not allowedThe type of credit card used is not accepted for this transaction.
Duplicated payment for credit-cardA payment with the same details has already been processed.
Invalid number of installments selectedThe number of installments chosen is not valid or not allowed.

Internal due-diligence issues

Credit card or holder signed as black listThe card or cardholder has been flagged and cannot proceed with transactions.
Credit card signed as high risk user to proceed with the transactionThe transaction has been flagged as high risk and cannot be processed.

Fallback general errors:

Transaction rejected due to other reasonsThe transaction was rejected for reasons not covered by the specific error codes above.
Fallback rejection (timeout, invalid payment information…)The transaction was rejected due to timeout, invalid payment information, or other technical issues.
Bad request during transactionThe request was malformed or contained invalid data.

Best Practices

Handle Errors Gracefully: Always provide clear error messages to your users based on the rejection status received.
Security: Never store or log complete credit card information. Only use tokenized data.
Retry Logic: For certain errors like timeouts or temporary issues, implement a retry mechanism with appropriate delays.

Common Solutions

Rejection StatusRecommended Action
cc_rejected_bad_filled_*Ask user to verify and re-enter card information
cc_rejected_card_disabledSuggest user to contact their bank or use another card
cc_rejected_insufficient_amountSuggest user to use another payment method or card
cc_rejected_duplicated_paymentCheck if payment was already processed successfully
cc_rejected_high_riskContact support for manual review
cc_rejected_fallbackRetry the transaction or contact support