Introduction
Supporting Stripe as a payment provider for TripBuilder allows users to make payments through credit cards or alternative payment methods, removing payment barriers and enhancing the user experience.
To enable Stripe, customers must select Stripe as a Payment Processor in Settings.
User Flow
Finalise the itinerary definition and component selection in Planner.
Start checkout.
Select Online Payment as the payment option.
Click on Book and Pay Now.
Stripe popup appears.
Fill in with the appropriate credit card data
Click on the "Pay now" button
Receive payment and itinerary booking confirmation in TripBuilder.
For more information, please check the Checkout Process with Online Payment article.
Configuration
Stripe Connect: Simple Configuration from Cockpit
After selecting Stripe as a Payment Processor, a “Connect with Stripe” button will be displayed, where customers will be redirected to the Stripe website. Customers already with a Stripe account can log in and complete the setup. Alternatively, non-Stripe customers can sign up through the link and then do the setup to connect with TripBuilder.
User experience is improved through a transparent configuration process, avoiding the need for our customers to enter complex configuration parameters.
We also support a manual account selection for customers already connected to Stripe. Customers will be able to select a Connected Account ID after a successful “Connect with Stripe” flow within their TripBuilder instance. After selection, the Connect Account ID will be re-validated by TripBuilder, stored and applied to future transactions.
This feature is particularly relevant when multiple Distribution Channels use Stripe, as the same Connected Account ID could be selected, avoiding multiple “Stripe Connect” flows.
Please note that if a manually selected configuration is defined, it will be superseded should the “Connect with Stripe” method be utilised.
Testing
Nezasa's STAGING and DEV environment use the sandbox environment of Stripe. As a customer of Stripe, you can switch to your a sandbox account when logged in.
Please note that only test credit cards can be used in that environment. The list of test credit cards can be found in the Stripe documentation: https://stripe.com/docs/testing?testing-method=card-numbers
Further Remarks
How to enable/disable payment methods?
Everything within the Stripe Payment Page is to be configured in your Stripe account. For further help with your Stripe account, please reach out to Stripe directly.
Payment Data in TripBuilder / PCI
Nezasa is not holding nor processing any of the relevant payment data. The user directly enters the data on the hosted payment page of Stripe.
Do you support a Stripe account per distribution channel?
Yes, TripBuilder supports configuring different credentials for each distribution channel.
How are refunds handled when a booking paid with Stripe is cancelled?
TripBuilder does not move money, in either direction. It does not create refunds in Stripe automatically. If a traveller cancels a trip they paid for (fully or with a deposit) through Stripe, you make the refund yourself in your own Stripe account, for example from the payment in the Stripe Dashboard. The money then goes back to the card or payment method the traveller used.
To keep the itinerary balance correct in TripBuilder:
Open the itinerary in Cockpit and go to the Billing section.
Check the Refund record. When automatic payment and refund records are enabled for your account, TripBuilder creates it after the cancellation. It is calculated as the amount paid minus any non-refundable costs. If the feature is not enabled, add the refund record manually.
When you have made the refund in Stripe, confirm the refund record in TripBuilder as fulfilled.
Please note: refunds you make in Stripe are not synced back to TripBuilder. Always confirm the refund record in Cockpit as well.
Automatic creation of payment and refund records is a Beta feature. Nezasa needs to enable it for you. For details, see Itinerary Billing.