Payments · Perth

Payments for taxi fleets in Perth

Stripe + PayPal native, account-pay built in, settlements that close themselves. Configured for WA Department of Transport — On-demand Transport.

Payments in Perth is the stripe + paypal native, account-pay built in, settlements that close themselves, configured against WA Department of Transport — On-demand Transport and the operating reality of a 2.4k-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 Perth specifically, the feature reads from regulator-aware booking, dispatch, and reporting surfaces — no bolt-on integration, no separate console.

Payments in Perth — the operating reality

Payments ships against the Western Australia 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 Perth, the feature posts cleanly against WA Department of Transport — On-demand Transport quarterly returns, vehicle inspection cycles, and the 2,400-vehicle scale that defines the market. PER airport flows integrate natively where applicable.

How TaxiCloud delivers payments in Perth

Operators in Perth 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 Perth operating tempo because WA Department of Transport — On-demand Transport 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 Perth — questions answered.

How does Payments work in Perth?: Payments in Perth reads from the live dispatch board, the customer-facing booking widget, and the WA Department of Transport — On-demand Transport compliance reporting layer in a single tenant. Customer pays at booking: Stripe Apple Pay / Google Pay / Link / cards, or PayPal. The Perth configuration is preset for the city's 2,400-vehicle market and the Western Australia operating geography.
Is Payments compliant with WA Department of Transport — On-demand Transport?: Yes. Payments is calibrated for WA Department of Transport — On-demand Transport 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 Perth fleet?: Payments ships on every TaxiCloud plan — Starter through Pro Ultra. Transparent A$89-A$629/month pricing. Most Perth 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 Perth 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