Taxi Driver Monthly Card vs Per-Trip Commission: What Ops Actually Configures

Fleet managers argue about commission the way dispatchers argue about empty miles. Someone wants a clean percentage on every metered trip. Someone else wants drivers to pay a flat monthly card and stop thinking about the cut on each fare. Both instincts are reasonable. Neither works if your software only stores one vague “take rate” field and hopes finance will invent the rest in a spreadsheet.

On Ptaxi’s taxi dispatch software, those two ideas live as documented configuration: platform commission split by urban versus intercity rules, and monthly card packages that can waive per-trip commission while still charging other fees. This piece stays inside the taxi feature docs — not a generic mobility white paper — so you can walk the same screens in a demo without inventing Stripe subscriptions or unnamed “VIP driver plans.”

Why fleets keep both models in play

Per-trip commission scales with volume. A slow week costs the driver less in platform take; a busy week costs more. That feels fair when demand is lumpy. It also trains drivers to watch every short hop and every cash settle, because the cut still hits the driver wallet when the passenger pays cash.

A monthly card flips the psychology. The driver pays up front for a package tied to their company, then runs trips without the per-trip commission line. Ops gets predictable card revenue and fewer “why did my cut move?” tickets. Drivers who clear enough trips treat the card as cheaper than drip commission; drivers who barely work may feel punished — which is exactly why card pricing and mandatory-card switches matter.

Neither model fixes empty sectors by itself. Commission and cards are settlement tools. Supply still needs go-online behavior, push spread and an order pool when nobody accepts — topics covered elsewhere on this blog. Settlement just decides who owes whom when a trip does complete.

What the monthly card actually waives

Marketing Center → monthly card management is blunt in the taxi docs: ops can create monthly card packages by company. A driver on the card can run without per-trip commission. The same sentence lists what still deducts: information fee, tax and withdrawal handling fee.

That residual list is the part sales decks skip. If a city partner hears “zero commission,” they will hear zero platform economics. Train them on the real sentence: commission off; other configured fees still on. Withdrawal review and wallet history still exist. Cash settlement still needs a wallet that can absorb whatever non-commission fees you kept.

Practical checks before you sell cards as a growth lever:

• Price the package against realistic weekly trip counts for that company, not against a fantasy full-time average.
• Decide whether card buyers still see commission lines at zero on the bill confirm screen, or whether the UI simply omits the line — drivers notice both.
• Keep finance able to report card revenue separately from trip commission so you do not mix subscription-style cash with fare take-rate in one muddy KPI.

Urban vs intercity commission when there is no card

Without a card, taxi commission is not one global percentage. Documented ops setup creates default commission when a city or county-level company is created; staff can adjust. Urban and intercity plans sit side by side. Urban commission can be set per company together with an urban fence: if both origin and destination sit inside the fence, the trip is urban; otherwise it is intercity.

That fence rule is why two trips with similar meter totals can settle differently. A hop that clips outside the urban polygon flips the intercity rate even if the driver never felt “long distance.” Ops that ignore fence hygiene will spend Fridays explaining “wrong cut” tickets that are really polygon tickets.

Taxi trips also use in-vehicle meter pricing for the fare itself. Commission sits on top of that settlement story. Cash pay still deducts the platform cut from the driver wallet — so a driver with a thin wallet and a cash-heavy zone will start declining work that looks like commission risk, not navigation risk. Pair commission design with wallet coaching; see taxi app commission models for the broader cut-and-cash picture.

When the card becomes mandatory

System configuration includes monthly card settings that can require drivers to buy a card. The docs add a sharper rule: when the simplified order flow is enabled, purchasing a monthly card is required. Simplified flow is the lighter on-trip path used for certain phone-dispatch style jobs (no full navigation theater, offline-friendly settle). Bundling that path with a mandatory card is a policy choice encoded in product switches — not something to enable casually on a mixed fleet that still runs full metered taxi jobs.

Use the mandatory switch when:

• The company already sells cards as the commercial contract with drivers.
• Simplified-flow volume would otherwise leak commission-free trips without card revenue.
• Ops can explain the rule in onboarding without sounding like a surprise fee.

Avoid the mandatory switch when half the fleet still thinks commission-only is the deal, or when card packages are priced for full-timers while your actual roster is part-time. Forced cards without clear package economics create silent offline behavior that looks like a dispatch bug.

How this shows up for drivers day to day

Drivers do not open “monthly card management.” They open go-online, heatmaps, order broadcast and bill confirm. What they feel is:

• Whether tonight’s trips still show a commission line.
• Whether cash still punches the wallet for remaining fees.
• Whether withdrawal still needs review and still carries a handling fee.

Taxi driver app features still apply under either settlement mode: authentication before service, listening checks, order pool after the first acceptance window, and clear bill confirm with online or cash paths. The card does not replace those flows. It only changes which money lines move after the trip.

If drivers must buy a card before they can work simplified-flow jobs, put that in onboarding copy and in the first go-online empty state — not in a PDF nobody opens.

Admin work that keeps both models honest

Useful admin muscles for this topic:

1. Company-scoped card packages — wrong company assignment means the wrong commercial deal.
2. Urban fence maintenance — commission class follows fence geometry.
3. Separate urban and intercity rates — so intercity trips are not “accidentally cheap.”
4. Wallet and withdrawal review — card or not, residual fees and cash cuts still hit wallets.
5. Performance stats on accepts and rejects — to see whether card drivers behave differently on short hops (they often do once commission anxiety drops).

Do not invent bank-card billing, Stripe subscriptions or automatic tax filing because the word “monthly card” sounded SaaS-like. Documented payments on the taxi passenger side remain the configured online methods plus cash; the card is a driver-side package product in marketing tools.

A short decision drill

Before you pick a default for a new company:

• Count expected trips per active driver in a normal week.
• Price a card that beats drip commission at that volume, and loses if volume collapses — then decide if that risk sits with the driver or with ops.
• Draw the urban fence on a real map printout with dispatchers, not only in admin.
• Write one sentence drivers will see: “Card waives per-trip commission; information fee, tax and withdrawal fee still apply.”
• If you enable simplified flow, decide explicitly whether the mandatory-card switch turns on the same day.

If that drill produces hand-waving, you are not ready to promise “zero commission” on a sales call.

Close

Monthly cards and per-trip commission are two settlement rails on the same taxi product. Cards waive the trip cut and still leave other fees; commission without a card follows urban and intercity plans tied to company fences; cash still settles through the driver wallet. Configure the package, the fence and the mandatory-card switch on purpose — then train drivers on the sentence they will actually feel at bill confirm.

If you want to map card-versus-commission for a multi-company city, bring your expected trip volumes and fence sketch to a walkthrough of taxi dispatch software. Contact us.