Payments overview

Payment workflows that stay attached to the booking.

Collect deposits, balances, extras and refunds across the channels customers want, while finance keeps the booking-level trail it needs.

Linkfast payment requests
Plandeposit and balance schedules
Datafinance-ready payment trail

One payment layer for the travel booking lifecycle

Booking root
Customer payment to reporting line
BK-24018 · Departure 14 Sep · ATOL protected
£8,420Booking value
BKBooking

Booking

Travel date, lead passenger and package details

Connected
PYPayment

Payment

Customer payment matched to booking and channel

Connected
STSettlement

Settlement

Acquirer settlement and fees visible

Connected
PFProtected funds

Protected funds

Protected amount held until travel date

Connected
ATATOL

ATOL

Report line traceable back to booking movements

Connected
Explainability

One payment layer for the travel booking lifecycle

Card, open banking, links, checkout, staged payments, receipts, fees and settlements stay attached to the booking record so teams can drill into the detail when they need it.

CASHWhat has been received, settled and made available.
PROTECTEDWhat is held or restricted until travel.
REPORTINGWhat supports ATOL, APC, trust or audit reporting.

Why travel payments need a connected workflow.

The payment is only one moment in a longer operating job. Travel teams still need to know who paid, which booking it belongs to, whether money has settled, what fees were taken and what action is needed before departure.

01

Take payment without losing context

Use links, checkout, open banking or plans while carrying the booking reference, customer and departure detail forward.

02

Reduce customer-payment chasing

Make deposits, balances and failed-payment follow-up visible enough for sales and finance to act quickly.

03

Keep finance ready for the next step

Preserve receipts, fees, refunds, settlement status and protected-funds evidence around the booking.

Start with one workflow, then connect more.

Teams can begin with the payment problem that creates the most admin, then add deeper integration and reporting as the process matures.

01

Links for ad hoc collection

Send secure requests for deposits, balances, amendments and failed-payment follow-up.

02

Checkout for online journeys

Keep customers in a branded payment experience while recording the data needed after conversion.

03

Plans for staged payments

Manage deposits, scheduled instalments, balances, reminders and status changes in one place.

04

Bank and settlement context

Keep card, open banking, bank transfer and payout evidence visible as the booking moves toward departure.

Map the payment journey around your bookings.

Show us how your bookings, deposits, balances and settlements work today and we will help identify the cleanest starting point.