Setup & sandbox
Provision sandbox credentials, wire SDKs into a non-production environment and validate authentication, webhook signing and a sample booking-payment flow.
Migrating to felloh
A booking-aware home for travel payments.
Provider-specific migration guides for the most common payment stacks travel businesses run today. Each one covers concept mapping, the operational shifts that matter day one, the travel-specific advantages and a four-phase rollout you can run in parallel.
Provider guides
Pick the stack you're moving from.
Each guide is provider-specific — concept mapping, the operational shifts, the code shape and the four-phase rollout — written for the team that will run the cutover.
Adyen Global Enterprise gateway · global card processing Read the migration guide Global Payments Global · US-led Acquirer · US-led, global card processing Read the migration guide Mint Payments Australia, UK & APAC Acquirer · Australia, UK & APAC Read the migration guide Stripe Global Global gateway · general commerce Read the migration guide Trust Payments UK & Europe UK-focused acquirer · travel + retail Read the migration guide Worldline Europe & UK European acquirer · card processing Read the migration guide Worldpay UK & global Global Acquirer · UK & global card processing Read the migration guide
What's the same across every migration
Six shifts that show up no matter which provider you're leaving.
The provider-specific details change. The travel-shaped operational improvements look the same — and they're what teams notice first.
BKG
Booking-aware ledger
Payments, refunds, settlement and supplier disbursements all attach to the booking. Finance, customer support and dispute teams read from the same record — no metadata mapping, no merchantReference plumbing.
Explore REFTwo-stage refund authorisation
One user initiates, another approves. The booking, supplier-payment status and cancellation policy surface inline before money moves, with an audit log of who did what.
Explore RCNAutomatic reconciliation
Acquirer settlement files unpack into per-booking fees, refunds and chargebacks automatically. Bank transfers match against bookings without manual reference chasing.
Explore ATLTrust & ATOL evidence
Protected funds, ATOL Trust positions and trustee reporting attach to bookings as routine — not as a separate compliance project. The trustee picture matches the operating picture.
Explore SCHScheduled payments
Deposit-then-balance flows and multi-instalment plans run from the booking record with network-tokenised cards that stay current through reissue. Capture rates on long-lead bookings stay high without engineering work.
Explore DSBSupplier disbursements
Pay suppliers, agents and DMCs directly against the bookings they relate to, with full audit trail. The same ledger that holds customer money holds the supplier obligations against it.
Explore How a migration runs
Four phases, both stacks running in parallel.
Every migration is reversible at every step. Move data and flows brand by brand, confirm acceptance and settlement timing against your existing baseline, then decommission the legacy integration on a schedule that suits the dispute window.
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.
Don't see your current provider?
Talk to the team Same story applies. Bring us your stack.
The shape of the migration is the same — concept mapping, two-stage refund authorisation, automatic reconciliation, booking-aware ledger, trust evidence. If you're running a stack we haven't published a guide for, tell us which one and we'll walk through it on the call.