A credit card transaction may be declined due to an issuer response, a payment/account related error, or due to an Assembly fraud decline.
Listed below is some more detailed information on why a decline may have occurred, and steps you can take in an attempt to resolve the issue.
A card transaction is declined by the cardholders issuing bank. When this decline occurs, it is completely outside the control of Assembly. There are over thirty different decline response codes that can be returned by an Issuer, but the most common include:
- Incorrect card number or expiration date entered on the checkout page
- Insufficient funds in the associated bank account
- The credit card being over its limit
- Rejection based on fraud filters at the bank
- High level of recent activity on the card
To resolve this problem, the cardholder will need to contact their bank to determine the cause of the decline, and to take necessary action to rectify the issue.
Payment/Account Related Error
A transaction may be declined when using the `Make Payment`, `Authorise Payment`, `Refund`, and other payment-related API calls due to incorrect data. In these instances please refer to our error codes listed here.
A card may be declined by Assembly. When this decline occurs it is usually due to transaction has been deemed high risk, a data element has been associated with a known fraudulent transaction(s), or user exhibits fraudulent behaviour.
To resolve this problem, review the user's behaviour over the last 24 hours and look for :
- Excessive volume of transactions
- Unusual spending pattern
- Value against the item - does the amount match the item being paid for?
If any of the above occurs, its highly likely that transaction(s) has been declined to prevent fraud. Otherwise, email firstname.lastname@example.org for more information.
When emailing Assembly, please include transaction details such as transaction reference number and/or user's email in order for Assembly to locate transaction.