Solution

Take payments without losing the booking trail.

Card, open banking, payment links, embedded checkout and payment plans, all connected to the booking, traveller and protected funds behind every transaction.

Book a walkthrough See the platform

Railscard, open banking, links, embedded

Bookingattached to every payment

Evidenceready for APC, trust and audit

The challenge.

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.

Many rails, one booking

Card, open banking, MOTO and links each settle differently. Joining them back to the booking is finance's problem.

Compliance rides on the payment

ATOL APC, trust account movements and audit trails all depend on the underlying payment evidence staying intact.

Disputes ask the same question

Chargebacks, refund queries and trustee reviews all need the booking-level trail to defend or explain.

How felloh handles a payment, end to end.

From the moment the customer pays through to the moment a trustee reads the APC line, felloh keeps the same booking-level trail running.

Collection

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.

Rails Card · A2A · MOTO

Authentication 3DS · bank app

Capture Booking-attached

See payment collection

Authorisation

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.

3DS Default

Liability Shifted where eligible

Evidence Per booking

See payment optimisation

Settlement

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.

Match Per booking

Files Per acquirer

Exceptions Surfaced early

See reconciliation

Reporting

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.

APC Drill-down ready

Trustee Connected

Audit Trail preserved

See protected funds

What's inside

Mix and match what you need.

Each capability sits on the same booking-level ledger, so you can start with one and add the rest as you need them.

Payment Links

Send a secure payment request that arrives with the booking, traveller and reference attached. Use for deposits, balances and ad-hoc collection.

See payment links

Embedded Checkout

Drop 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 checkout

Payment Plans

Schedule deposits, balances and instalments against the travel timeline. Cards, open banking or BACS, all reconciled to the booking.

See payment plans

Automatic Surcharging

Detect eligible card brands and recover the cost — with the surcharge decision and evidence attached to the booking.

See automatic surcharging

Financial Protection Data

ATOL APC, trust-account and trustee reporting evidence built from the same booking ledger as the underlying payments.

See protected funds

Fraud Shield

Travel-aware fraud rules across 3DS, card, customer, device, location and velocity — each decision attached to the booking.

See Fraud Shield

Customer Payment Portal

A branded, self-service portal where customers pay balances, approve scheduled payments and see history.

See the customer payment portal

Refund Authorisation

Role-gated authorisation that sits between a refund request and the actual refund — with audit trail attached to the booking.

See refund authorisation

Payment Optimisation

Routing, chargeback defence and decline recovery, all tied back to the booking record.

See payment optimisation

How felloh helps.

Booking-level payment processing removes work from the finance team's week and adds evidence to the dispute, audit and renewal conversations.

Faster reconciliation

Acquirer, open-banking and bank movements matched to bookings as they arrive — no weekly rebuild.

Defensible reporting

APC, trustee and audit evidence drawn from the same booking ledger.

Stronger dispute defence

Authentication and booking evidence already attached when a chargeback or query arrives.

By business model

Built around the way your travel businesses works.

The booking-level payment picture changes shape with the kind of travel business you run. Start with the cut closest to yours.

Tour operators

Departures, deposits, balances and supplier obligations connected per trip.

For tour operators

Travel agencies

Multi-channel collection and booking-level follow-up across customers and suppliers.

For travel agencies

TMCs and corporate travel

Lodge cards, virtual cards, central billing and per-client reconciliation for corporate travel programmes.

See corporate travel payments

Airline ticket sellers

BSP reconciliation, ADM/ACM handling and refund chains for agencies selling airline tickets.

See airline payment solutions

Homeworker networks

B2B payments for agencies operating under head-office licences and consortia.

For homeworker networks

DMCs and wholesalers

Inbound payments, agent settlements and supplier obligations evidenced per booking.

For DMCs

OTAs

High-volume online flows with booking-level reporting.

For OTAs

Built for ATOL, ABTA and trust-protected businesses.

Most 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. For the full picture of how payments, protected funds and reporting connect, see our travel payment solutions overview.

ATOL holders

APC, trust-account and franchise-member reporting connected to the booking-level money trail.

For ATOL holders

Trust account holders

CAA-approved trust reconciliation matched to booking and travel events.

For trust account holders

ATOL franchise members

Member-level booking evidence ready for head-office reporting cycles.

For franchise members

Common questions

Travel payment solutions, answered.

What buyers usually ask before booking a walkthrough.

What is felloh?

felloh is a travel-specific payment platform that connects card, open banking, payment links, embedded checkout, payment plans, MOTO and virtual terminal — keeping each payment attached to the booking it belongs to, along with ATOL, trust and audit evidence.

What payment methods does felloh support for travel businesses?

felloh supports card payments (Visa, Mastercard, Amex), open-banking account-to-account payments, payment links, embedded checkout, scheduled payment plans, MOTO and virtual terminal — across multiple acquirers and currencies, with the booking reference attached to every transaction.

Does felloh integrate with travel booking systems?

Yes. felloh integrates with major travel booking systems including Traveltek, Moonstride, Spark Travel and Travelgenix, plus custom systems via its API. Payment status, refunds and reconciliation flow back into the booking record.

Can felloh route payments across multiple acquirers?

Yes. felloh supports multi-acquirer setups, so card payments can be processed across providers such as Trust Payments, Total Processing and Nuvei. Settlement, fees and refunds reconcile to the same booking-level ledger regardless of which acquirer processed the transaction.

How does felloh handle ATOL APC and trust-account reporting?

felloh keeps the booking-level money trail — payments received, supplier payments out, protected funds held and refunds processed — connected to each booking. APC contributions, trust-account reconciliation and trustee evidence are drawn from the same source of truth as the underlying transactions.

Is felloh PCI DSS compliant?

Yes. felloh is a PCI DSS Level 1 compliant payment platform — the same compliance level as the largest acquirers — so card data is handled to the highest security standard.

How long does it take to migrate to felloh from another payment provider?

Migration timelines vary by provider, booking-system integration and the scope of the workflows being moved. Typical migrations from providers such as Adyen, Stripe or Worldpay take 4–8 weeks, including integration, testing and parallel run.

See how this works around your bookings.

Bring one payment, reporting or cash-position problem. We will show how felloh connects the booking-level money trail behind it.