The customer should contact their bank to resolve this. The card has been blocked and listed as lost or stolen. Instruct the customer to contact their bank and ask why the card is restricted. The customer must contact their bank to get a more specific reason and ask their bank to help them resolve the issue. Paylike is not able to provide a more specific reason. However, it's most likely the issuing bank or card network responding with a generic error instead of a more specific one, e.g. The card may be rejected for a myriad of reasons, ranging from something simple as the card not being enabled for online use, the transaction being caught in the issuing bank's fraud filter. Instruct the customer to contact their bank and ask why the card was rejected. The card has been rejected by the customer's bank. If the problem persists, have the customer contact their bank. Such limit can often be changed in the customer's eBanking solution.
If the customer has enough funds on the account, the error is most likely due to a card threshold or limit, e.g. Have the customer try another card or add funds to their account. There are not enough funds available to cover the purchase. Have the customer try again or try another card. The card has expired or the customer added an invalid expiry date. Have the customer check the expiry month and year is correct and not overdue. Have the customer check the CVC (security code), typically found on the back of the card. Have the customer check all card details. Errors from issuing banks Error 2: Invalid card This can mean a myriad of things and in general the only way to investigate such an error is to have the cardholder ask their issuing bank for the specific reason as they've send this generic one as a response.
Many errors (30-40 %) are therefore mapped to error 8, which is a generic “card was rejected”. Therefore, the quality of the errors we see from the issuing banks and the card network is, unfortunately, quite poor. The payment system (Visa/Mastercard) is an old system with thousands of issuing banks and in-between processors.
If you are not able to resolve the error yourself, get in touch. 3-D Secure required, transaction size limit or similar). It can be due to a programming error, missing HTTPS, your account not being approved or a rule enforced by Paylike (e.g. In general, you can not resolve errors from the issuing bank, but must instruct the customer to solve it themselves or have them contact their issuing bank.Įrrors originating from Paylike is generally caused by you, the merchant. by entering the wrong card number or due to the issuing bank rejecting the transaction because e.g.
CREDIT CARD TERMINAL ERROR MESSAGES HOW TO
If you're a developer, see our Github repository on how to handle transaction errors.Įrrors are either originating from the issuing bank (the bank that issued the card) or from Paylike.Īn error originating from an issuing bank is returned when either the customer makes a mistake e.g.
0 kommentar(er)
