How AvaiBook's Payments Gateway Works
When the guest's card is charged according to your payment rules (retainer, remainder, or additional charge), both you and the guest will receive an email confirming the success of the charge with full details.
If an attempt fails, the system will automatically retry it after 3 hours. If it fails again, another attempt will be scheduled within 24 hours of the first failure, notifying you in each case.
🚨 For bookings coming from Booking.com, if the third attempt also fails, we will report the card as invalid and ask the guest for a new one. Once provided, the system will automatically generate a new collection for the outstanding amount, without manual intervention. If you don't update your card, you'll need to manage the payment yourself.
In cases of irrecoverable errors (non-operational or expired card), it will be reported directly as an invalid card for the traveler to provide another.
Recoverable errors
Some errors are identified as recoverable if the card is operational, but has temporary problems.
Valid card, but there is something wrong with the card
At the moment you will not be able to make a charge because the issuing bank is telling us that there is a problem with the card because the cardholder is entering some wrong information, does not have enough balance, or the amount you are trying to charge exceeds the limit of the guest's card.
The error codes you'll see are:
Error 102: Card not active, insufficient balance, or limit exceeded.
Error 111 and Error 115: Incorrect CVV2 / CVC2 code.
Error 114: The card has credit restrictions.
Operational card, but there is a specific communication error with the POS
You will not be able to make a payment at the moment because there has been a specific error in communication with the POS.
The error codes you'll see are:
Error 1099, Error 535, and Error 500: Unexpected error.
Error 1026: Duplicate reference.
Error 1186: Maximum limit per operation not allowed, you cannot make withdrawals of more than €10,000.
If it is Error 1186, use our POS to divide this charge into different partial payments and follow our recommendations to make good use of the POS.
Operational card, but there is an error related to PSD2 or Strong Authentication (SCA)
This regulation requires the cardholder to be identified in a reinforced way when they are making an online payment within the European Economic Environment. You will not be able to make a charge at the moment because the cardholder has not authenticated himself in the transaction and his bank has denied the charge.
The error codes you'll see are:
Error 195 and Error 1322: The operation requires strong authentication.
Error 143 and Error 1327: The cardholder has made a mistake in the authentication or has not completed it.
Error 1326: The issuing bank denies because of its security checks.
Non-recoverable errors
These are situations in which the charge cannot be made with that card, even if it is tried again.
List of codes and causes:
Error 100: Card expired.
Error 137: Invalid card.
Error 101 and Error 119: Blacklisted card, cancelled.
Error 562: The card does not support pre-authorizations, they are usually American Express cards.
Error 1001: User not found.
Error 172 and Error 173: Non-operational card.
Error 174: Operation denied. Do not repeat before 72 hours.
Error 1189: Maximum amount per card / 24 hours.
Error 1191: Limit IP transactions/day.
Error 1202: Too many failed attempts in 30 minutes.
Error 1367: Same card for flight payments.
Error 113: Invalid credit card.
Error 106: Card not registered or not registered by the issuing bank.
Error 109: The data provided by the traveller is incorrect.
Error 1480: Card not supported by the system.
⚠️ How to handle Error 1480: Card not supported by the system.
This error occurs in operations related to failed returns. Specifically, it occurs when attempts are made to refund the passenger on several occasions, but the associated card is no longer operational or does not accept the receipt of the payment.
As a result, it is not possible to complete the return via the original payment method.
In these cases, you should not continue to try to process the refund from the system, as it will continue to generate the same error. It is necessary to contact the traveler directly to manage the refund through an alternative route.
Non-recoverable failover procedure
For Booking.com bookings, the system will automatically mark the card as invalid and the portal will prompt the guest to provide a new one.
For bookings from other channels, AvaiBook will request a new card via the secure Traveller Credit Card link.