Payments · London

Payments for taxi fleets in London

Stripe + PayPal native, account-pay built in, settlements that close themselves. Configured for Transport for London (TfL).

Payments in London is the stripe + paypal native, account-pay built in, settlements that close themselves, configured against Transport for London (TfL) and the operating reality of a 105.0k-vehicle market. TaxiCloud Payments is Stripe + PayPal native with account-pay for corporate travellers, driver settlement reports, and end-of-day reconciliation that closes itself. Built for fleets where payment friction directly translates to revenue leak. For London specifically, the feature reads from regulator-aware booking, dispatch, and reporting surfaces — no bolt-on integration, no separate console.

Payments in London — the operating reality

Payments ships against the Greater London operating geography as a structural object. Payments is the single most operationally significant feature most fleets underestimate. Friction at booking-time payment converts directly to abandonment; friction at end-of-day settlement converts to driver dissatisfaction; friction at reconciliation converts to operator finance-team overhead. TaxiCloud Payments addresses each. Customer-side: Stripe with Apple Pay, Google Pay, Link, and cards plus PayPal native. The booking flow runs payment up-front for prepaid rides, eliminating the no-show revenue leak that costs unprotected fleets 4-7% of bookings. In London, the feature posts cleanly against Transport for London (TfL) quarterly returns, vehicle inspection cycles, and the 105,000-vehicle scale that defines the market. LHR + LGW + STN + LCY + LTN airport flows integrate natively where applicable.

How TaxiCloud delivers payments in London

Operators in London typically run payments on TaxiCloud after a 6-10 day migration off iCabbi, Autocab, Cordic, or TaxiCaller. Driver settlement is calibrated for end-of-shift clarity. The driver app shows the running settlement statement throughout the shift — drivers always know what they will be paid. End-of-shift, the statement closes with rides, tips, deductions, and cash-collected reconciliation. Disputed rides flag for operator review without holding up the rest of the settlement. Across pilot fleets, settlement disputes are down 60% vs incumbent platforms because the driver-side transparency forecloses on the most common dispute classes. The dispatcher impact is highest in the London operating tempo because Transport for London (TfL) compliance overlays the standard PHV regulatory posture, and payments surfaces the resulting reports through the same dispatch flow rather than as a separate finance task.

FAQ

Payments in London — questions answered.

How does Payments work in London?: Payments in London reads from the live dispatch board, the customer-facing booking widget, and the Transport for London (TfL) compliance reporting layer in a single tenant. Customer pays at booking: Stripe Apple Pay / Google Pay / Link / cards, or PayPal. The London configuration is preset for the city's 105,000-vehicle market and the Greater London operating geography.
Is Payments compliant with Transport for London (TfL)?: Yes. Payments is calibrated for Transport for London (TfL) reporting, audit, and renewal cycles. Vehicle inspection deadlines, driver-licence audits, and the local quarterly return format ship pre-configured. Format updates land in-sprint when the regulator changes requirements.
What does Payments cost for a London fleet?: Payments ships on every TaxiCloud plan — Starter through Pro Ultra. Transparent £49-£349/month pricing. Most London fleets run Pro (£149/€55/$59/A$89 month) or Pro Max (£349/€395/$449/A$629 month). No setup fee on Starter or Pro; month-to-month contracts; payments configuration in London is included.

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales