Overview
TripBuilder is integrated with external payment providers, thus being able to trigger a payment flow close to the end consumer/traveller for payment via credit card.
When the itinerary cost is not settled, the Customer Care user can use the Rest payment feature, which generates a payment URL. When opened by the traveller, it redirects to the payment step in checkout, where a credit card payment can settle the difference.
Rest Payment
The Rest payment functionality can be enabled for all customers using the LiveBookingOnlinePayment checkout flow.
If a booking is performed more than 30 days before departure, the user will be asked to make a down payment. However, the remaining booking payment still needs to be collected before departure. Two functionalities have been introduced with the Rest payment support workflow to facilitate this process.
|
Please note: On the successful completion of a rest payment, TripBuider will capture a pre-authorization on a credit card, following the same process as when a down payment is required and paid. |
Auto Reminder Emails
When enabled, a maximum of 3 reminder emails will be sent to the traveller requesting them to settle the payment online with TripBuilder. The emails are scheduled for 45, 35, and 30 days before the departure.
|
Important: This feature needs to be enabled by Nezasa. Please contact our support team or your customer success manager to enable the feature flag available at the Distribution Channel > Checkout > Contact & PAX Details > Payment > Automatic Rest Payment Reminders. |
Manual Rest Payment Reminder
The link to the Rest payment page is available within the billing information of the itinerary.
1. Go to Customer Care
2. Under Bookings, click on the Itinerary ID that you want to view in detail
3. Click on the Billing tab on the left-hand side
4. Scroll down until the Rest Payment Link section
5. The link can be copied and sent manually by the Tour Operator to the customer. The link will direct the user to the payment step of the checkout flow, where the Rest payment can be fulfilled.
Alternative to Rest Payments
Instead of using the online payment integration in TripBuilder, payments can also be conducted externally to TripBuilder with a different platform and workflow. In this use case, TripBuilder enables the creation of transaction records, representative for the payment and refund transactions. This way, all information is centralised: itinerary and components, commercial transactions and their status.
|
Know more: Please check the article Offline Payment and Refund Transactions for a complete explanation of this feature. |
Comments
0 comments
Article is closed for comments.