Split payments are payment flows where the funds from a single customer transaction are split across multiple recipients at settlement — for example, between a marketplace, an underlying supplier and a service fee account. Splits can be defined as percentages or fixed amounts and may include conditional logic. They simplify accounting and reduce the need for separate post-settlement transfers.
Split payments
Splitting a single transaction’s funds across multiple parties at settlement.
Why it matters in travel
Travel marketplaces, OTAs and agency-supplier flows are natural candidates for split payments. Done well, the split reduces operational steps after the customer has paid; done poorly, it complicates dispute handling because the funds have already moved.
For a marketplace handling tour-operator bookings, splitting at settlement saves a manual remittance step the next day. The supplier’s share lands in the supplier’s account, the agency’s commission lands in the agency’s account, and the marketplace fee lands in the marketplace account, all driven by the same customer payment. The visible work is gone but the underlying accounting has to be airtight.
The hard case is when a refund or chargeback arrives weeks later. If the split was clean, every share can be traced and recovered cleanly. If it was not, the marketplace has to chase recoveries across multiple recipients while the original customer waits for a refund. The teams that get split payments right build the recovery flow before they need it.
How felloh helps
felloh keeps split-payment context attached to the booking so the share that went to each party is traceable and reconcilable when refunds or disputes appear later.
Where this shows up in payment collection.
Split payments touches more than one workflow at felloh. Start with the pages most travel teams reach for next.
- Payment Collection
Card, open banking, payment links, deposits and instalments — captured against the booking.
Explore - Payment Links
Shareable, authenticated payment links so customers pay against a specific booking without keying card details.
Explore - Embedded Checkout
Booking-aware checkout that keeps card data out of your systems and the payment trail tied to the booking.
Explore
More on collecting payments in travel.
Real-world context from the felloh team and customers, written for travel finance and operations.
-
UpdatesSetting up payment links manually
See how felloh connects all of your payments, cards, open banking and direct deposits with your bookings
Read article -
UpdatesMaking multi channel payments work across travel systems
Multi-channel friction in travel usually sits between booking, payment and finance systems. Connected payments keep finance teams in control.
Read article
Connect the dots.
See how payments, settlement, refunds and reporting evidence connect around every booking.