Payment gateway_

Travel gateways have to handle the specific shapes of travel commerce — high-value bookings, deposits and balances, agent screens, payment links, refunds against cancellation terms, multi-currency and cross-border flows. A gateway that does not understand booking context forces finance to rebuild it in spreadsheets.

A travel business that runs on a generic gateway usually does not realise the cost until the operation starts to scale. Every booking-shaped event the gateway does not understand — deposit, balance, ATOL evidence, supplier payment timing — becomes a manual workaround in finance. The cost of that workaround compounds as volume grows.

The teams that get gateway choice right evaluate against travel-specific scenarios: what happens on a balance against a tokenised card six months later, what happens on a refund against a partly-used itinerary, what happens to chargeback evidence on a long-lead booking. The teams that evaluate only on headline rate and integration speed regret the decision around year two.

felloh acts as a booking-aware payment gateway, keeping every payment, refund and settlement attached to the underlying booking ledger so the operational story does not break when the channel changes.

The pay checkout handles cards, open banking, wallets and bank transfers behind one customer-facing experience, with provider-side detail abstracted into the same booking-level record. The dashboard’s Transactions and Settlement views surface every captured payment, refund and chargeback against the booking, with channel and method captured throughout.

For travel businesses replacing a generic gateway with a travel-aware one, the operational picture stops being something finance has to assemble. The booking is the unit of finance, the channel is metadata, and reconciliation runs at booking level rather than at transaction level.