Feature
How card processing, manual payment methods and policy-based fees actually connect to every trip record.
When a payment happens outside the booking system — a separate card terminal, a text asking for Zelle — matching it back to the right trip becomes a manual, error-prone step.
Cancellation and no-show fees that depend on someone remembering to charge them manually get missed, especially during busy periods.
Card payments process online through your choice of Stripe Connect or Whop; cash, Zelle and bank transfer are recorded manually for reconciliation — every path attaches the payment to the specific trip.
Cancellation and no-show fees are enforced by the policy engine based on your configured rules and grace periods, not by someone remembering to apply them.
A payment method can be declared at booking time and auto-charged when the trip completes, so the driver isn't handling payment collection on the spot.
The specific mechanics behind money moving on a trip.
Processed through Stripe Connect or Whop (your choice), with deposits, gratuities and refunds supported per trip.
Recorded against the trip for reconciliation when a client pays outside the card flow.
A passenger can declare their payment method at booking, and the trip auto-charges the saved card when it completes.
Cancellation fees and no-show fees (with a configurable grace period) apply automatically based on your rules, not manual judgment calls.
Completed trips and corporate invoices sync to your own connected QuickBooks account, validated end-to-end against a real sandbox.
Every charge, refund and fee is logged against the trip in an auditable history.
How a charge connects back to a specific trip.
Card on file, or a manual method the operator accepts (cash, Zelle, transfer).
Charged or recorded at the point they're due, tied to the trip.
A declared card auto-charges; manual methods are marked reconciled by your team.
A cancellation or no-show within your configured window generates its own fee, tied to the same trip record.
Revenue, fees and reconciliation status are all queryable per trip, per driver, per period.
Manual methods still tie back to the trip record instead of living in a separate ledger.
Trips draw against a credit line instead of requiring a card at each booking, still fully reconciled per trip.
Fees apply consistently based on your configured rules, not depending on who's handling the cancellation.
Drivers aren't handling payment collection directly when a card is declared and auto-charged.
Every payment, whatever the method, is already attached to its trip.
Policy enforcement applies cancellation and no-show fees automatically.
QuickBooks sync means revenue doesn't need re-entering by hand.
Declared payment methods with auto-charge remove payment collection from the driver's hands.
Card, Apple Pay and Google Pay process through Stripe Connect or Whop — each operator connects one (or both, and picks which is active).
Yes, cash, Zelle and bank transfer can be recorded manually against the trip for reconciliation, alongside online card payments.
The policy engine applies it automatically once your configured grace period passes without the passenger showing up, tied to the same trip record.
Yes, corporate invoicing and completed trips sync with QuickBooks Online — validated end-to-end against a real QuickBooks sandbox.
Related pages
Set up your payment methods and policy rules in minutes.
Start free trial