Payment portal_

Travel portals matter because the time between deposit and balance is long, customers expect self-service, and the back office cannot scale by handling every balance manually. A clean portal also reduces missed balances and last-minute supplier-payment scrambles.

For a tour operator with six months between booking and departure, the portal is the only touchpoint where the customer actively manages money. If the experience is clean — every booking visible, every balance dated, every payment confirmed — the back office runs lean and the supplier deadlines hit without drama. If the experience is broken, every missed balance becomes a phone call and every phone call becomes a recited card number.

The portals that work are the ones designed against real travel flow: a customer who part-paid by card and wants to top up by open banking, a couple splitting a balance across two cards, an agent paying down a commission, a customer trying to find a payment they made six weeks ago. The portals that fail try to look like a generic e-commerce account screen and treat each payment as if it stood alone.

felloh’s payment portal is a booking-aware self-serve experience that keeps the customer view, the back-office view and the finance view aligned to a single ledger per booking.

The pay-hosted customer portal lets travellers view bookings, see outstanding balances, pay via card or open banking and access receipts — all against the booking ledger felloh keeps for the operator. The dashboard’s Bookings view exposes every portal-side payment in real time, so the back-office never has to ask whether a balance has landed.

For tour operators with the long gap between deposit and balance, the portal turns balance collection from an outbound task into an inbound flow. Customers self-serve, supplier deadlines hit, and finance only deals with the genuine exceptions.