Core concepts
Payments and the trip ledger
Every dollar as a ledger leg: capture, split, payout, refund — all traceable to the booking.
Double-entry, per trip
When a trip settles, the fare does not become a number in a report — it becomes ledger legs: driver payout, operator commission, tax, gratuity, fees. Debits equal credits on every trip, and every leg carries the booking it came from.
This is the same discipline your accountant already trusts, applied at the trip level, automatically.
Capture and idempotency
Card capture, corporate invoicing, and cash declaration all end in the same ledger. Payment operations carry idempotency keys, so a retried capture can never charge twice; provider webhooks are deduplicated by event ID before they touch money state.
Payouts and statements
Driver payouts aggregate settled legs on your schedule. Each driver statement is a list of trips, not a lump sum — a driver questioning a payout opens the same evidence you see.
- Adjustments and bonuses are ledger entries with reasons, never silent edits.
- Refunds reverse specific legs, keeping the original trip's history intact.
- Exports reconcile to your accounting system by booking reference.
Month-end without archaeology
Because the ledger is written at settlement time, month-end reporting is a read, not a reconstruction. Revenue by zone, commission by channel, tax collected by jurisdiction — each figure expands into the trips behind it.