01
Provider data
Keep payment status, method, fees and settlement references attached to the booking.
Payment provider integrations
Keep payment-provider choice without losing booking context.
Connect card, account-to-account and provider data into the booking-level finance picture, so travel teams can optimise routes without rebuilding operations.
Choicepayment routes stay flexible
Feesprovider costs visible by booking
Trailsettlement evidence retained
Payments and finance visibility connected to Keep payment-provider choice without losing booking context.
Booking root
Customer payment to reporting line
£8,420Booking value
BKBooking
Booking
Travel date, lead passenger and package details
ConnectedPYPayment
Payment
Customer payment matched to booking and channel
ConnectedSTSettlement
Settlement
Acquirer settlement and fees visible
ConnectedPFProtected funds
Protected funds
Protected amount held until travel date
ConnectedATATOL
ATOL
Report line traceable back to booking movements
Connected Explainability
Payments and finance visibility connected to Keep payment-provider choice without losing booking context.
Keep payment status, booking context, reconciliation evidence and reporting trails together around the travel systems your team already uses.
CASHWhat has been received, settled and made available.
PROTECTEDWhat is held or restricted until travel.
REPORTINGWhat supports ATOL, APC, trust or audit reporting.
Payment optionality should not create finance fragmentation.
Travel businesses may need more than one payment route for resilience, cost, customer preference or geographic coverage. felloh keeps provider data connected to the booking so that optionality does not become another reconciliation problem.
02
Route optimisation
Use card, account-to-account or other payment routes where they best fit the booking and operating model.
03
Settlement visibility
Trace provider payouts back to payments, refunds, chargebacks and booking references.
Built for changing payment stacks.
Payment providers change. Commercial terms change. Customer behaviour changes. The booking-level finance layer should remain stable enough for teams to adapt without losing operational control.
01
Resilience
Keep payment operations less dependent on one provider relationship.
02
Margin
Understand payment costs in context, not only from headline rates.
03
Control
Keep provider choices connected to finance, reporting and support evidence.
04
Portability
Make future provider changes easier to reason about before making the switch.
Connect this integration to the booking ledger.
Show every booking, payment, receipt and settlement in one travel finance picture.