Payment Links

Payment links that carry the booking context with them.

Send secure payment requests for deposits, balances, amendments and retries while keeping the customer, booking and finance trail connected.

Fastsend in seconds
PCIreduce card handling
Trackbooking-level status

Payment requests with booking-level context

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

Payment requests with booking-level context

Each link can carry the booking reference, customer, balance, payment status, surcharge decision and reconciliation trail that finance teams need later.

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

The job is quick collection without messy follow-up.

Payment links are often the fastest way to collect money without asking customers to read card details over the phone or leaving finance to match the payment later.

01

Reduce fraud and PCI exposure

Let customers enter card details securely rather than sharing them with the sales team.

02

Collect flexibly

Use links for deposits, balances, amendments, extras, failed-payment retries and offline sales.

03

Track automatically

Keep payment status, booking references and finance evidence together.

Useful on its own, stronger when integrated.

Teams can start with simple links and later connect creation, status and reconciliation into the booking system.

01

Manual links

Create a link quickly when a customer needs to pay now.

02

System-triggered links

Generate requests from booking, itinerary or CRM workflows.

03

Finance visibility

Make it easier to understand which link relates to which customer and settlement.

04

Exception follow-up

Spot unpaid, failed or duplicate requests before they become booking-day confusion.

Send links that finance can still understand later.

Collect deposits, balances and ad hoc payments without losing the booking context.