01
One booking, many rails
A single booking can carry a card deposit, an open-banking balance and a supplier-side BACS payment, each with its own consent, settlement and reconciliation pattern.
Knowledge Base
Payments for travel agencies.
A practical guide for securing, automating and scaling payments inside a travel agency — covering embedded payments, real-time payments, BACS, SEPA, payment scheduling and the operational workflows behind them.
Embeddedpayments secured per booking
Real-timecollection across rails
Scheduledbalances collected on time
Why payment workflows matter for travel agencies.
Travel agencies live between many payment rails - card, open banking, BACS direct debit, Faster Payments, SEPA, embedded checkout and payment links - and the finance picture has to stay honest across all of them. The guide below covers the verbs travel finance teams actually use: securing, automating, scaling and streamlining payments across the rails the agency runs on.
02
Different rails, different risks
Securing card payments is a 3DS conversation. Securing BACS is a mandate conversation. Securing real-time payments is a fraud-control conversation. Securing embedded payments is all of those at once.
03
Finance reads one picture
The finance team should not see card, BACS, Faster Payments and SEPA as four different reconciliation problems. They should see one booking-level ledger.
How to secure payments in travel agencies.
Securing payments in a travel agency means securing the consent, the rail and the evidence behind every charge - so customer disputes, supplier-side reversals and regulator queries can all be answered from the booking record without rebuilding it under pressure.
01
Capture consent at the right moment
For cards, that means 3DS-protected authentication on the deposit and a tokenised mandate for the balance. For BACS, a Direct Debit Instruction with the right wording. For Faster Payments, a Variable Recurring Payment or single-immediate authorisation. Each rail has its own consent rules and the booking record has to hold the right one.
Cards 3DS-protected
BACS DDI
Faster Payments VRP or single
02
Attach the consent evidence to the booking
Every authentication outcome, mandate reference and authorisation code should sit against the booking, not in a payment-provider portal that finance has to chase. When a dispute lands months later, the evidence is already attached to the booking record rather than spread across acquirer portals and email threads.
3DS outcome Recorded
Mandate ref Linked
Auth code Attached
03
Use the right liability shift
A 3DS-protected transaction shifts chargeback liability to the issuer. An open-banking Push Payment carries different fraud protections. Knowing which shift applies to which booking is what makes representment defensible when a chargeback arrives weeks or months after travel.
3DS Issuer liability
Open banking Push protection
Evidence Booking-linked
Section 02
How to automate embedded payments in travel agencies.
Embedded payments live inside the agency's own booking flow rather than redirecting the customer to a generic checkout. Automating them well means the payment, the booking and the customer journey share one record.
01
Bring the checkout to the booking
Embedded checkout drops the felloh payment journey directly into the booking flow, so the customer never leaves the agency brand and the booking reference is captured against the payment automatically.
02
Automate balance collection
Stored card tokens, open-banking Variable Recurring Payments or BACS mandates let scheduled balance payments run automatically on the due date - without an agent or customer having to action each one.
03
Automate soft-decline recovery
When an issuer soft-declines a balance, the schedule should retry against the booking automatically with the right reason-code logic - not surface in a finance inbox three days later.
How to handle real-time payments (Faster Payments) in travel agencies.
Real-time payments - mostly Faster Payments in the UK and SEPA Instant in Europe - settle to the supplier or to the agency within seconds. That changes how reconciliation, refunds and dispute handling work.
01
Use real-time rails where speed matters
Late-booking balances, last-minute itinerary changes and supplier deposits often need to clear today, not in two days. Faster Payments and SEPA Instant move money in seconds and remove the bank-business-day gap - which matters most when a departure is days away.
Settlement Seconds
Use case Late balance
Cost Lower than card
02
Keep the booking reference attached
Real-time payments arrive faster than the data behind them. Open-banking payment initiation captures the booking reference at consent time, so the arrival can be matched to the right booking automatically rather than landing as a bank-statement line finance has to chase.
Booking ref Pre-attached
Match Automatic
Manual chase Eliminated
03
Plan for irrevocability
Real-time payments are usually final - there is no chargeback equivalent. Refund and dispute paths have to live separately and the booking record has to capture both. Push-payment fraud protections under APP reimbursement rules are different again and need their own evidence trail.
Reversal Manual
APP rules Apply
Evidence Booking-linked
Section 04
How to secure BACS payments in travel agencies.
BACS direct debit is still the workhorse for instalment plans, group bookings and school travel - especially where parents pay over months. Securing BACS in a travel agency context means getting the mandate, the timing and the failure handling right.
01
Get the mandate wording right
BACS DDI text has to match the bookings the mandate covers. A vague mandate covering "future travel" is easier to dispute than a specific mandate against a named booking.
02
Handle indemnity claims with evidence
BACS indemnity claims allow customers to reverse a payment up to 13 months later. The booking record - confirmation, supplier obligations, traveller details - is the evidence that proves the payment was authorised.
03
Match BACS arrivals to bookings automatically
BACS arrivals come as bank-statement lines with limited reference data. felloh matches each arrival back to the booking and instalment schedule it relates to, so finance does not key in a reference for every line.
Section 05
How to handle SEPA payments in travel agencies.
SEPA covers euro-denominated bank transfers and direct debits across the European single payments area. For UK travel agencies selling European itineraries or paying European suppliers, SEPA is part of the picture.
01
Use the right SEPA scheme
SEPA Credit Transfer for ad-hoc payouts, SEPA Direct Debit Core for consumer collection, SEPA Direct Debit B2B for supplier mandates, SEPA Instant for real-time settlement. Each has its own consent and reversal rules.
02
Capture IBAN and BIC against the supplier
Supplier records should hold IBAN and BIC with the same discipline as a UK sort code and account number. felloh attaches them to the supplier and booking so payouts run without re-keying.
03
Reconcile in euros, report in sterling
SEPA arrives in euros. felloh keeps the booking record in the booking currency and the bank arrival in the rail currency, so reconciliation does not lose the FX context.
How to use payment scheduling in travel agencies.
Payment scheduling - staged deposits, balance schedules, instalment plans, supplier release dates - is at the heart of how a travel agency manages cash between deposit and travel. Done well, it moves work from the inbox to the ledger.
01
Schedule against the booking, not the customer
Each scheduled payment should be attached to the booking and traveller it relates to, so a customer with two bookings has two distinct schedules - not one merged one. The travel date drives the schedule, not the day the customer signed up.
Schedule owner Booking
Trigger Travel date
Per-customer Separated
02
Capture consent at setup, not at run time
A stored card token, an open-banking VRP or a BACS DDI carries the consent so scheduled payments run without re-engaging the customer. The consent evidence lives against the booking and is ready when an issuer asks for it.
Card Tokenised
Open banking VRP
BACS DDI
03
Handle the exceptions automatically
Soft declines, expired cards, cancelled mandates and travel-date changes should rewrite the schedule automatically and surface as exceptions only when manual intervention is genuinely needed. Most retries should never reach the finance inbox.
Soft decline Retry
Expired card Token refresh
Inbox Exceptions only
Section 07
How to scale payment workflows in travel agencies.
Scaling a travel-agency payment workflow means it keeps working as booking volume grows, the number of suppliers grows, and the team behind it changes. The pattern that works at 100 bookings a month rarely survives 10,000.
01
Move knowledge out of one person's head
Documented workflows turn the process that lives in an experienced finance person's inbox into a repeatable picture the rest of the team can follow.
02
Standardise the booking-level data
Every payment, refund and supplier obligation attached to the same booking-level record means scaling is a head-count question, not a system-architecture question.
03
Automate the boring 80%
Identification, matching, scheduling and routine refund handling should run without a human in the loop. Exceptions get the attention; the rest stays out of finance's inbox.
How to streamline payment reconciliation in travel agencies.
Reconciliation is where every payment rail eventually has to defend itself. Streamlining means the bank arrival, the booking, the supplier obligation and the reporting line share one trail.
01
Match as payments arrive
Reconciliation is faster when each payment is matched to a booking on arrival rather than once a week. Surface only the exceptions. The week-end reconciliation rebuild becomes a check rather than a forensic exercise.
Match cadence On arrival
Exceptions Surfaced early
Week-end Check only
02
Keep one ledger across rails
Card, BACS, Faster Payments, SEPA and open-banking arrivals all land in the same booking-level ledger, so finance reads one picture rather than four. The reconciliation conversation stops being rail-specific and becomes booking-specific.
Rails Unified
View One ledger
Reports One source
03
Make the evidence trail audit-ready
Every match, every exception and every override is recorded against the booking it relates to, so auditors get a single source of truth instead of a chain of exports. The audit conversation moves from sprint to routine.
Audit trail Preserved
Override Recorded
Exports Eliminated
What this guide connects to.
This is the practical guide for a travel agency payment workflow. Each section maps to a felloh product or solution page if you want to drill into how the engine room works.
01
Travel payment solutions
The pillar page on how a travel payment system differs from a generic payment processor.
Travel payment solutions02
Payment Collection
Embedded checkout, payment links, payment plans and open-banking flows that keep the booking attached to every payment.
See payment collection03
Automate reconciliation
How felloh matches card, bank and settlement data back to bookings without spreadsheet rebuilds.
See reconciliation04
Financial Visibility
See cash received, protected, committed and available against every booking.
See cash visibility05
For travel agencies
How felloh shapes around travel-agency operating models, including multi-channel collection.
For travel agencies06
Payment scheduling
Plain-English glossary entry on payment scheduling in a travel context.
Read the termSee this guide running on your booking data.
Bring the workflow or rail you want to improve and we will show how felloh keeps the booking-level evidence connected end to end.