Payment

From quote to settled charge, end to end

The payment lifecycle takes a trip from booking through Quote and Price to a TripCharge and TripPayment — pre-authorising on booking, capturing at completion, and reacting to processor webhooks along the way.

Pre-auth to capture
Funds are held on booking and captured when the trip is archived, with manual pre-auth, capture and refund operations available.
Account or card
Trips charged to a corporate account go on the account invoice instead of the passenger card; card, cash, credit and account methods are all supported.
Processor-driven
Processor webhooks drive state changes through a public, idempotent endpoint — built to take a real gateway (Stripe/Adyen) behind it.

6 features in Payment

Payment Lifecycle

End-to-end pipeline that takes a trip segment from booking → Quote → Price → TripCharge → TripPayment

Payment Preauthorisations

A hold placed against the customer's payment method when the trip is booked, guaranteeing funds are available before the

Payment Processor Webhooks

A public endpoint that receives event callbacks from the payment processor (a mock processor in development; a real gate

Payment System

How payments fit together across the platform — from a booking-time hold, through the charge and its line items, to capt

Payments

A captured payment — the money actually taken from the customer at trip-end

Trip Charges

The aggregate billing record for one segment — net + tax + gross + currency + status