01
Fits the journey
Add payment collection to websites, portals or booking flows without losing control of the experience.
Embedded Checkout
Embedded checkout that keeps conversion and finance connected.
Let customers pay inside your booking journey while keeping the payment status, booking reference, fees and settlement trail usable for finance.
UXbranded payment flow
3DSsecure card authentication
FXcurrency options when needed
Embedded checkout, inside your booking journey.
The felloh SDK drops directly into your booking flow. Customers pay inside the same journey they booked in — your brand, your URL — while the payment, the booking reference, the traveller and the settlement evidence stay connected to the booking for finance to pick up after conversion.
felloh checkoutSandbox session
ReadyTry the form with test card 4242 4242 4242 4242, any future expiry and any 3-digit CVC.
The job is not only taking payment. It is preserving the trail.
Customers can pay in a smoother branded flow while finance still receives the operational detail it needs after conversion.
02
Supports security
Use secure payment handling and authentication without bringing raw card data into your own systems.
03
Keeps finance informed
Capture references, customer details, payment status, fees and settlement context for follow-up.
Checkout that stays connected after payment
Booking root
Customer payment to reporting line
£8,420Booking value
BKBooking
Booking
Travel date, lead passenger and package details
ConnectedPYPayment
Payment
Customer payment matched to booking and channel
ConnectedSTSettlement
Settlement
Acquirer settlement and fees visible
ConnectedPFProtected funds
Protected funds
Protected amount held until travel date
ConnectedATATOL
ATOL
Report line traceable back to booking movements
Connected Explainability
Checkout that stays connected after payment
Website payments, booking references, customer details, authorisation status, settlement and fee evidence stay joined instead of becoming another disconnected payment export.
CASHWhat has been received, settled and made available.
PROTECTEDWhat is held or restricted until travel.
REPORTINGWhat supports ATOL, APC, trust or audit reporting.
Works alongside offline sales.
Embedded checkout does not need to replace every payment workflow. Teams can still use links or other channels where they fit better.
01
Online bookings
Collect payment at the point of booking or enquiry confirmation.
02
Assisted sales
Use payment links where a consultant needs to guide the customer after a conversation.
See how we send payment links03
Reporting continuity
Keep payment data consistent even when customers pay through different channels.
04
Exception handling
Keep failed, abandoned, refunded or partially paid journeys visible enough for the team to follow up.
See how we tighten financial controlBring connected checkout into the booking journey.
Give customers a smoother way to pay while keeping the finance trail attached to every booking.