The booking finally has a record
Worldline-integrated systems hold the booking-to-payment relationship in operator-side code. felloh makes the booking a first-class record so payments, refunds and settlements attach to it directly.
Migrate from Worldline
Worldline to felloh: travel-shaped operations on a booking-aware ledger.
Worldline covers acquiring well but does not understand the booking. felloh replaces fragmented settlement and manual booking-matching with a single ledger that finance, operations, dispute and trustee reporting all read from — and gives travel teams native trust-account, ATOL and supplier-disbursement handling out of the box.
Why teams move
Why travel finance teams leave Worldline.
The Worldline stack does its job, but the operational picture it produces is rarely shaped for travel. felloh keeps payments, refunds, settlement, trust evidence and supplier disbursements connected to the same booking record from day one.
Refunds gain real controls
A two-stage authorisation, audited end to end, replaces single-call refunds. Approval sees the booking, supplier and policy context before money moves.
Reconciliation runs without spreadsheets
Settlement files unpack into per-booking fees, refunds and chargebacks. Bank transfers match against bookings even when references are missing or wrong.
Travel-specific features are part of the platform
ATOL trust positions, protected funds, supplier disbursements and scheduled instalments are native — not bolt-on integrations the operator has to wire together.
Concept mapping
Worldline → felloh, side by side.
Most Worldline concepts map directly. A few — bookings, refund authorisation, scheduled payments — are felloh-specific because travel demands them.
Worldline felloh Note
Merchant ID Brand within unified ledger Multiple MIDs roll up to one booking-level picture.
Hosted Page Lite Payment Links + hosted checkout Booking-aware payment links replace standalone hosted-page flows.
Tokenisation Automatic tokenisation Network tokens keep cards current through reissue.
Reverse / refund Two-stage refund flow Initiate + authorise with full booking context.
Settlement files Per-booking settlement view Files unpack to per-booking fees, refunds and chargebacks automatically.
Notification handler Per-event webhooks (HMAC-SHA256) One signed HTTP request per state change.
What changes
Three shifts that matter day one.
You can map most of Worldline onto felloh directly. These are the differences travel teams actually feel during cutover — and after.
BKG
Booking becomes the operating record
No more bridging code between booking system and acquirer. The booking is where payments, refunds, settlement and supplier disbursements all attach.
RCN
Reconciliation runs from settlement files automatically
Worldline settlement files no longer need manual unpacking — felloh ties each line back to the underlying booking and surfaces the genuine exceptions.
REF
Refunds enforce two-stage authorisation
The refund queue carries booking and supplier context. The approver sees the cancellation policy, supplier-payment status and refund history before approving.
The new shape
A booking, a payment, a refund.
The felloh API is built around the booking. The same record carries the customer, the supplier obligation, the payment trail and the trust position — so finance, customer support and dispute teams all read from one place.
See the full Worldline migration guide What you gain
What felloh adds that Worldline doesn't.
The travel-specific layer comes built in. ATOL Trust, supplier disbursements, scheduled instalments, two-stage refund authorisation and automatic reconciliation — all live against the same booking record.
Booking-aware ledger
Every payment, refund and settlement lives against the booking it relates to. Finance, customer support and dispute teams all read from the same record.
ExploreTwo-stage refund authorisation
Refunds are initiated by one user and approved by another, with the underlying booking, supplier-payment and policy context surfaced inline.
ExploreTrust & ATOL evidence
Protected funds, ATOL Trust positions and trustee reporting are part of the same operating record — not a separate compliance project.
ExploreAutomatic reconciliation
Settlement files unpack to per-booking fees, refunds and chargebacks; bank transfers match against bookings without manual reference chasing.
ExploreSupplier disbursements
Pay suppliers and beneficiaries directly against the bookings they relate to, with the full audit trail attached.
ExploreScheduled payments
Deposit-then-balance flows, instalments and balance reminders run from the booking record with network-tokenised cards that stay current.
Explore Migration plan
A four-phase rollout — run both stacks in parallel.
Cutover is reversible at every step. Move data and flows brand by brand, with parallel processing while you confirm acceptance and settlement timing match your existing baseline.
Setup & sandbox
Provision sandbox credentials, wire SDKs into a non-production environment and validate authentication, webhook signing and a sample booking-payment flow.
Data migration
Move customer, booking, beneficiary and card-token records across. felloh imports existing card tokens directly from your current acquirer where scheme token-portability is supported, so customers do not need to re-enter card details for live bookings.
Flow migration
Move payment collection, refund, settlement and reporting flows brand by brand. Run both stacks in parallel so cutover is reversible at every step.
Cutover & decommission
Switch live volume across, monitor acceptance and settlement timing against your existing baseline, then decommission the legacy integration on a schedule that suits the dispute window.
Move from Worldline to a booking-aware travel platform.
Bring us one Worldline workflow you want to fix and we'll show how felloh wires payments, settlement, refunds and trust evidence around the booking.