Many rails, one booking
Card, open banking, MOTO and links each settle differently. Joining them back to the booking is finance's problem.
Card, open banking, payment links, embedded checkout and payment plans, all connected to the booking, traveller and protected funds behind every transaction.
Travel businesses take customer payments across many rails, channels, customers, agents and suppliers — and finance is usually left to join the picture back together later, against a clock and a regulator.
Card, open banking, MOTO and links each settle differently. Joining them back to the booking is finance's problem.
ATOL APC, trust account movements and audit trails all depend on the underlying payment evidence staying intact.
Chargebacks, refund queries and trustee reviews all need the booking-level trail to defend or explain.
From the moment the customer pays through to the moment a trustee reads the APC line, felloh keeps the same booking-level trail running.
Card, open-banking A2A, payment links, embedded checkout, payment plans, MOTO and virtual terminal — all running through one platform. The booking reference, traveller and travel date are captured at the moment of payment, and each rail picks up the right authentication and consent flow for the transaction.
Cardholder authentication routes through 3DS by default. Fraud signals — velocity, BIN, AVS, behavioural — feed the decision and stay attached to the booking, so the evidence is already in place if a chargeback ever lands.
Settlement files, open-banking arrivals, fees and chargeback adjustments all match back to the bookings they relate to in one ledger. Multi-acquirer setups reconcile to the same picture, so finance reads one source of truth.
ATOL APC lines, trust-account movements, refund history and supplier-payout evidence all derive from the same connected ledger — so renewal and audit season are about packaging the picture, not rebuilding it.
Each capability sits on the same booking-level ledger, so you can start with one and add the rest as you need them.
Send a secure payment request that arrives with the booking, traveller and reference attached. Use for deposits, balances and ad-hoc collection.
See payment linksDrop the felloh payment journey directly into your booking flow. The customer stays in your brand; the booking-level evidence comes back to you.
See embedded checkoutSchedule deposits, balances and instalments against the travel timeline. Cards, open banking or BACS, all reconciled to the booking.
See payment plansDetect eligible card brands and recover the cost — with the surcharge decision and evidence attached to the booking.
See automatic surchargingATOL APC, trust-account and trustee reporting evidence built from the same booking ledger as the underlying payments.
See protected fundsTravel-aware fraud rules across 3DS, card, customer, device, location and velocity — each decision attached to the booking.
See Fraud ShieldA branded, self-service portal where customers pay balances, approve scheduled payments and see history.
See the customer payment portalRole-gated authorisation that sits between a refund request and the actual refund — with audit trail attached to the booking.
See refund authorisationRouting, chargeback defence and decline recovery, all tied back to the booking record.
See payment optimisationBooking-level payment processing removes work from the finance team's week and adds evidence to the dispute, audit and renewal conversations.
Acquirer, open-banking and bank movements matched to bookings as they arrive — no weekly rebuild.
APC, trustee and audit evidence drawn from the same booking ledger.
Authentication and booking evidence already attached when a chargeback or query arrives.
The booking-level payment picture changes shape with the kind of travel business you run. Start with the cut closest to yours.
Departures, deposits, balances and supplier obligations connected per trip.
For tour operatorsMulti-channel collection and booking-level follow-up across customers and suppliers.
For travel agenciesHigh-volume corporate travel with reconciliation and refund discipline.
For TMCsB2B payments for agencies operating under head-office licences and consortia.
For homeworker networksInbound payments, agent settlements and supplier obligations evidenced per booking.
For DMCsHigh-volume online flows with booking-level reporting.
For OTAsMost UK travel businesses operate under a regulatory protection scheme. felloh carries that protection evidence with every transaction, so APC, trust-account and trustee reporting share the same booking-level trail.
APC, trust-account and franchise-member reporting connected to the booking-level money trail.
For ATOL holdersCAA-approved trust reconciliation matched to booking and travel events.
For trust account holdersMember-level booking evidence ready for head-office reporting cycles.
For franchise membersBring one payment, reporting or cash-position problem. We will show how felloh connects the booking-level money trail behind it.