Travel finance operations, connected

The Financial Operating System for Travel Businesses

Built for travel businesses that need one booking-level view of payments, protected funds, settlements, supplier commitments and reporting evidence.

Book a walkthrough

450+ travel businesses represented across the felloh network

The problem

Travel businesses struggle to answer one question:

Where is the money?

Bookings, payments and reporting live in different systems. Finance teams spend hours piecing together what cash has been received, protected, committed and available. As the business grows, the answer gets harder to find.

How it works

From payment received to money put to work.

One booking, followed all the way through. felloh captures the payment, matches it to the booking, updates your systems, makes it reportable and gives finance the context to act.

PaymentsSettlementsProtected fundsSupplier obligationsReporting

Everything stays connected in one financial picture, so finance teams can see where money is, what it relates to and what needs to happen next.

Book a walkthrough

CO Collect

Take payment, any way they book.

Card, open banking, payment links, deposits and instalments, all captured against the booking.

See how we improve payment collection Received GBP 8,420

RC Reconcile

Every payment matched to its booking.

Bulk settlements unpacked to fees, refunds and chargebacks. Bank transfers matched with no references to chase; anything that does not fit is surfaced for you.

See how we streamline reconciliation Protected GBP 5,894 · Available GBP 2,526

UP Update

The confirmed truth, pushed back to your systems.

Receipts and entries pushed to your booking system and accounts, with no rekeying.

See how we sync your systems Booking system + accounts updated

RP Evidence

Compliance evidence stays attached.

ATOL, APC, escrow, PTR bond and cash allocation evidence is drawn from the same booking record. Drill from any reporting number back to the payment trail behind it.

See how we simplify compliance reporting ATOL / APC evidence ready

AC Automate

The next workflow starts with confidence.

Trigger the right follow-up once booking context is clear: hold protected funds, release available cash, queue supplier payments or give sales the green light to book the flight.

See how we tighten financial control Hold · release · pay · follow up

What it gives you

Four outcomes from one connected money picture.

felloh makes payments, bookings, settlement, protected funds and supplier obligations usable as one finance record, so each team can move towards the outcome they care about.

Process payments

Take payments across every channel.

Card, open banking, payment links, embedded checkout and payment plans — connected to the booking they belong to.

Explore

What's inside

Card Authentication, capture and settlement attached to the booking.
Open banking Account-to-account payments matched to the booking they cover.
Payment links Deposits, balances and ad-hoc requests with the booking ref attached.
Embedded checkout Inline payment journey that keeps the booking-level trail intact.

Visibility

Know where the money is.

See what cash has been received, protected, committed and available across every booking, without rebuilding the picture from exports.

Explore

What's inside

Received Payments landed against the booking, by method and timing.
Protected Trust, escrow and APC funds tracked by departure.
Committed Supplier obligations attached to each booking.
Available Operating cash separated from what is held for travel.

Compliance & reporting

Keep the evidence with the booking.

ATOL, APC, escrow and reporting trails stay connected to the underlying payment, settlement and protected-funds treatment.

Explore

What's inside

ATOL Trail Booking-level protection evidence ready for audit.
APC Evidence Per-booking protection status and contributions.
Escrow Status Held, released and paid movements per departure.
Settlement Proof Acquirer and bank movements linked to the booking.

Financial control

Act with confidence.

Once supplier obligations, settlement status and protected funds are clear, felloh can trigger the next finance or sales workflow automatically.

Explore

What's inside

Refund Approvals Authorise refunds against the booking and policy.
Supplier Pay-outs Release supplier funds when the booking allows it.
Exception Review Surface unmatched payments before reconciliation.
Auto Workflows Hold, release, pay and follow-up triggered by status.

Developer platform

Built to integrate.

Modern REST APIs, native SDKs and pre-built integrations so both technical and non-technical users can wire booking, payment and finance systems straight into the felloh ledger.

felloh.payments.create 201 · ledger updated

// Take payment, matched to the booking
const payment = await felloh.payments.create({
  amount: 8420,
  currency: "GBP",
  booking_reference: "BK-24018",
  capture: true
});

// → posted, matched, protected vs available split
payment.status     "received"
payment.protected  5894
payment.available  2526

One booking-aware API for payments, settlements and reporting.

Capture payments, post settlements, surface protected funds and pull reconciliation reports against the same booking record. Every state change streams as a webhook, so downstream systems stay aligned without polling for updates.

Authentication is API-key based with granular scopes per environment. Sandbox mirrors production end to end, so engineering teams can validate deposit, balance and refund flows before a single live transaction goes through.

Read the API reference

@felloh/node-sdk installed

$ Install the typed Node SDK
$ npm install @felloh/node-sdk

// Drop-in client — auth, retries, pagination handled
import { Felloh } from "@felloh/node-sdk";
const felloh = new Felloh({ apiKey: process.env.FELLOH_KEY });

const link = await felloh.paymentLinks.create({
  booking_reference: "BK-24018",
  amount:            8420
});

Drop-in SDKs in the languages your team ships in.

Typed clients with auth, retries and pagination handled for you, so engineers focus on workflow rather than transport. The same booking-aware ledger surfaces through every language, with first-class TypeScript types and idiomatic naming per runtime.

Server SDKs cover Node.js, Python, PHP, Ruby and C#. Mobile and browser SDKs round out checkout, card tokenisation and Strong Customer Authentication on the customer-facing side, so the same booking can be progressed from sales floor to settlement without rebuilding payment plumbing in each layer.

SDK getting started

webhook: booking.payment.captured delivered

// Webhook posted when a booking payment captures
POST /your-endpoint
{
  event:             "booking.payment.captured",
  source:            "traveltek",
  booking_reference: "BK-24018",
  amount:            8420,
  currency:          "GBP",
  ledger: {
    received:  8420,
    protected: 5894,
    available: 2526
  }
}

Wire felloh into the systems travel already runs on.

Pre-built connectors plug felloh into the booking, accounting and payment systems travel teams already run, so finance teams stop rebuilding the picture in spreadsheets every month-end. Each connector ships with field mappings, status syncing and webhook routing maintained by felloh.

Booking context travels with the money as it moves. Bank arrivals match references automatically, settlement files unpack to fees, refunds and chargebacks, and accounting entries land against the right cost centre — all without a separate reconciliation step in between.

See all integrations

agent.bookings.flow sandbox

// Agent opens a booking against a customer
POST /agent/bookings
{
  customer_id: "cus_4F9c2a",
  reference:   "BK-24018",
  total:       842000
}

// Then collect the deposit
POST /agent/payment-links
{
  booking_id: "bkg_a4F9c2",
  amount:     100000,
  purpose:    "deposit"
}

// Refunds require two-stage authorisation
refund.state      "pending_authorisation"
refund.requires   "human_approval"

Booking-aware payments built for AI travel agents.

Agent-scoped endpoints, a hosted MCP server and battle-tested prompt playbooks give AI travel agents safe rails to take bookings, deposits and refunds. Drop the MCP server into Claude Desktop, Cursor, Claude Code or VS Code to expose 60+ tools across the booking and payment lifecycle without writing any API client code.

Two-stage refund authorisation, scoped API keys and confirmation flows keep humans in the loop on anything material. The prompt playbooks prevent the off-by-100 currency errors, invented bookings and unsafe refunds that catch out generic LLM agents pointed at a payment API.

Explore the AI-native platform

Bring us one booking, payment workflow or reporting problem. We will show how felloh connects the money trail around it.

Book a walkthrough