Booking Engine: SwiftBook
Feature: Various payment options at package level
Payment Gateway: Pay later flag ON
Prepay Only |
Deposit |
Credit Card |
No |
100% (Default) |
Yes (Default) |
Max
extranet:
Max V2 extranet:
Note:
We identified a flaw in the setup logic in the current Max extranet. To avoid
confusion, we will not change the logic. Despite showing a 100% deposit
requirement, we will still treat it as ‘Hotel Collect’ unless ‘Prepay Only’ is
enabled. This setup will offer guests the choice to ‘Pay Now’ or ‘Pay Later’.
On booking engine:
• Customer will see both PAY NOW and PAY LATER option.
• Pay now > Divert to PG for payment collection.
• Pay later > Credit card details will be collected.
Prepay Only |
Deposit |
Credit Card |
No |
1 Night |
Yes |
No |
Fixed $ Value |
Yes |
No |
< 100% |
Yes |
Max
extranet:
Max V2 extranet:
Prepay Only |
Deposit |
Credit Card |
Yes |
100% |
Yes |
Yes |
< 100% |
Yes |
Yes |
Fixed $ Value |
Yes |
Yes |
1 Night |
Yes |
Prepay Only |
Deposit |
Credit Card |
Yes |
100% |
No |
Yes |
< 100% |
No |
Yes |
Fixed $ Value |
No |
Yes |
1 Night |
No |
No |
100% |
No |
No |
< 100% |
No |
No |
Fixed $ Value |
No |
No |
1 Night |
No |
Regardless of the deposit setup, if the credit card flag is turned off, it will be considered a direct confirmation booking. This means no payment or credit card details will be collected at time of booking.
Max
V2 extranet:
On booking engine:
• Direct confirmation. Customer will not be diverted to PG, neither will credit card details be collected.