Settlement matches bookings automatically
Worldpay settlement reports land in formats finance has to unpack into brand and booking-level reconciliation. felloh does the unpacking automatically and ties every line back to the underlying booking.
Migrate from Worldpay
Worldpay to felloh: travel payments without the legacy integration tax.
Worldpay is a capable acquirer but the integration model and reconciliation surface still bear the marks of the pre-API era. felloh replaces multi-format settlement files, manual refund flows and brand-by-brand finance assembly with a booking-aware ledger that finance, operations and customer support all read from at once.
Why teams move
Why travel finance teams leave Worldpay.
The Worldpay 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.
Refund handling adds accountability
Worldpay refunds depend on the operator’s own controls. felloh enforces a two-stage authorisation with full booking, supplier and policy context surfaced inline — and an audit log of who initiated and who approved.
Multi-brand operations roll up cleanly
Where Worldpay separates each MID and brand, felloh holds one booking-level ledger across the group. Risk Analysis, Decline Analysis and Settlement all read at brand, region and group level from the same record.
Trust and ATOL evidence stop being a separate project
Protected funds, ATOL Trust positions and trustee reporting attach to the booking automatically. Audits and trustee questions get answered from the same record finance reads.
Concept mapping
Worldpay → felloh, side by side.
Most Worldpay concepts map directly. A few — bookings, refund authorisation, scheduled payments — are felloh-specific because travel demands them.
Worldpay felloh Note
MID / merchant account Brand within unified ledger Multiple MIDs roll up to one booking-level picture.
Worldpay token Automatic tokenisation Existing Worldpay tokens can be imported where scheme portability is supported. After migration, network tokens keep cards current through reissue.
Authorise + capture Automatic capture by default Booking captures unless deferred capture is explicitly requested.
Settlement file Per-booking settlement view Files unpack to per-booking fees, refunds and chargebacks.
Refund call Two-stage refund flow Submit + authorise with full booking context.
XML/SOAP webhooks JSON webhooks with HMAC-SHA256 One event per HTTP request, standard signing.
What changes
Three shifts that matter day one.
You can map most of Worldpay onto felloh directly. These are the differences travel teams actually feel during cutover — and after.
RCN
Reconciliation lives in the dashboard
Settlement, fees, refunds and chargebacks unpack per booking automatically. Finance opens the morning to a clean picture rather than rebuilding it from acquirer exports.
REF
Refunds gain a separation of duties
Two-stage refund authorisation replaces single-call refund. Approval happens against the booking, supplier-payment status and cancellation policy in one view.
API
XML/SOAP replaced by REST + webhooks
Modern JSON APIs and SDKs replace older XML/SOAP plumbing. Webhook signing uses standard HMAC-SHA256 rather than legacy schemes.
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 Worldpay migration guide What you gain
What felloh adds that Worldpay 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 Worldpay to a booking-aware travel platform.
Bring us one Worldpay workflow you want to fix and we'll show how felloh wires payments, settlement, refunds and trust evidence around the booking.