Customer Payment Portal

Let customers pay balances and approve schedules on their own time.

A branded, booking-aware self-service portal where customers look up their booking, pay outstanding balances, approve scheduled payments and see history — without calling the back office.

Self-servebalances and scheduled approval
Brandedhosted under your name
Bookingevidence kept against the trip

Customer self-service against the same booking record

Booking root
Customer payment to reporting line
BK-24018 · Departure 14 Sep · ATOL protected
£8,420Booking value
BKBooking

Booking

Travel date, lead passenger and package details

Connected
PYPayment

Payment

Customer payment matched to booking and channel

Connected
STSettlement

Settlement

Acquirer settlement and fees visible

Connected
PFProtected funds

Protected funds

Protected amount held until travel date

Connected
ATATOL

ATOL

Report line traceable back to booking movements

Connected
Explainability

Customer self-service against the same booking record

Balances, history and scheduled-payment approval all run against the same booking-level ledger the back office reads, so the customer view stays in sync.

CASHWhat has been received, settled and made available.
PROTECTEDWhat is held or restricted until travel.
REPORTINGWhat supports ATOL, APC, trust or audit reporting.

The challenge.

Balance chasing, scheduled-payment approvals and transaction queries all land back in the inbox and on the phone. The customer wants a single place to manage their booking payments; the back office wants the time back.

01

Balance chasing eats inbound time

Customers ringing to ask what's outstanding, or to pay a balance over the phone, is one of the biggest finance time-sinks in travel.

02

Scheduled-payment approvals add friction

Customers receiving emails for every scheduled instalment is friction — and a missed approval cascades into manual chase work.

03

Generic payment links lose context

A bare payment link asks the customer for money without showing the booking, the breakdown or what they have already paid.

How the portal works.

The portal carries the same booking-level picture finance reads — outstanding balance, transactions, scheduled payments — into a self-serve customer view.

01

Log in

Customers log in with their booking reference and the email used at booking. Or — for emails the operator sends — a magic-link URL with a one-time auth token drops the customer straight into their booking, no typing required.

Standard Ref + email
Magic link Auto-login
Session One-booking-scoped
See payment links
02

See the booking

The customer sees what they have paid, what remains, what is scheduled, and the supplier and traveller context — same data the back office sees, presented for the customer. Multi-currency displays render in the booking's currency.

Balance Live
History Per booking
Schedule Visible
See booking visibility
03

Pay or approve

The customer can pay the balance through embedded checkout — card or open banking — and approve scheduled payments one at a time or all at once. Each approved payment runs against the existing schedule without re-engaging the customer for future instalments.

Pay Card · A2A
Approve Single or all
Authentication 3DS · bank app
See payment plans
04

Evidence kept

Every payment and approval through the portal updates the booking record, sends the customer a receipt and writes the evidence trail back to the same ledger finance reconciles against. No double-entry, no separate portal data store.

Receipt Sent
Booking Updated
Trail Connected
See reconciliation

What customers see.

The portal is the customer's view of their own booking. Everything they need to manage payments themselves — and nothing they do not need to see.

01

Outstanding balance

What is left to pay, calculated against scheduled payments and completed transactions.

02

Transaction history

Every payment made against the booking, with date, amount and status.

03

Scheduled payments

Future-dated instalments awaiting approval, with one-click approve.

04

Multi-currency

Display in the booking currency — pence-accurate values, locale formatting.

How felloh helps.

The customer payment portal lifts collection efficiency, reduces back-office inbound time and keeps the customer journey branded and on-platform.

01

Fewer inbound calls

Customers self-serve balance payments and approvals instead of calling.

02

Higher collection rate

A clear self-serve path lifts on-time balance and instalment collection.

03

Branded under your name

Hosted under the operator's brand — not a third-party processor surface.

Give customers somewhere to manage their booking payments.

See how the customer payment portal fits alongside payment links, embedded checkout and payment plans in your collection mix.