Urban vs Intercity Taxi Commission: Geofence Rules That Change the Cut

Flat “one take rate for the city” looks clean on a pitch slide. It breaks the first week a driver runs an airport drop that starts downtown and ends past the ring road — or the reverse — and asks why last night’s cut matched a short urban hop. Passengers do not care about your commission taxonomy. Drivers do. Finance does. Franchise partners who signed for “city work” vs “out-of-town work” definitely do.

On Ptaxi’s taxi dispatch software, taxi orders are classified by whether pickup and dropoff both sit inside the urban geofence. Both inside → urban. Anything else → intercity. Each class can carry its own commission scheme. Fares for taxi trips still come from meter pricing. When the passenger pays cash, the platform cut is taken from the driver wallet, not from money you never held. This article stays on that classification → commission → meter → cash-wallet chain. Broader commission vs monthly-pass tradeoffs live in taxi app commission models; here the geofence is the point.

Why one city rate is a silent fight waiting to happen

Urban density and intercity deadhead are different products wearing the same taxi badge. An urban trip might be short, metered, high frequency, low risk of empty return. An intercity trip often means longer meter time, different negotiation with the passenger, and a real chance the driver returns empty. If you tax both the same way, you either overcharge short hops (drivers mute the app) or undercharge long runs (you subsidize highway work without admitting it).

Ops arguments that start as “the rate feels unfair” usually end as “the software classified the trip wrong.” Classification has to be mechanical and demoable: fence, both ends, label, scheme. Not a supervisor’s gut call after the passenger already paid.

The classification rule, stated without poetry

Documented admin behavior:

1. Configure an urban geofence for the company / city context you are running.
2. On trip completion economics, check pickup and dropoff.
3. If both points sit inside the urban fence → treat as urban order → apply urban commission.
4. Otherwise → treat as intercity order → apply intercity commission.

That “both ends” test matters. A trip that starts inside and ends outside is intercity. A trip that starts outside and ends inside is intercity. Only the fully-inside pair is urban. Train dispatch and driver support on those two sentences before you publish rates. Otherwise every airport-bound meter run becomes a ticket: “I never left the metro area in my head.”

Company creation can sync a default commission; staff then tune urban and intercity schemes separately. Treat defaults as scaffolding, not a forever rate card.

Meter pricing still owns the fare

Taxi orders use meter pricing (on-vehicle meter / meter-driven fare entry in the taxi trip flow). Commission schemes sit on top of that fare reality. Do not demo urban/intercity as if the software invents a new quote engine for out-of-town work. The passenger still rides a metered taxi trip; the platform still needs a truthful fare before it can take a truthful cut.

Driver-side bill confirm for taxi trips includes filling the fare and optional add-ons (highway, bridge/road, parking) as the trip flow requires, then choosing how the passenger pays. Classification for commission should be visible enough in admin that a dispute agent can answer “why this cut?” without opening a spreadsheet of guessed zones.

If your market also runs non-meter “simple” call-desk jobs on a separate switch, keep that product story separate in training. This piece is about metered taxi trips and the urban/intercity cut that follows them.

Cash pay: the cut still has to land somewhere

Cash is not “commission free” just because the platform never saw the banknote. Documented cash settlement for taxi trips: passenger pays offline; the system deducts platform commission from the driver wallet. That is why wallet top-up and balance discipline show up next to cash enablement.

Practical ops rules that belong in launch notes:

• Drivers who run mostly cash need a minimum wallet balance habit so the cut can clear when they mark cash paid.
• Bill detail must show the cut amount on cash trips the same way it shows on passenger online pay — otherwise end-of-day wallet math feels like a penalty.
• Withdrawal review still sits in admin; cash volume does not bypass finance controls.

When urban and intercity rates differ, cash nights amplify confusion. A driver who did three urban cash hops and one intercity cash drop will only trust the wallet if each line shows the matching scheme. Opaque “adjustment” rows recreate the fight you tried to automate.

How to configure without painting yourself into a corner

A workable setup sequence for demos and first cities:

1. Draw the urban fence from how you actually sell the market — not from a tourism map. Include the districts where short metered work is the product. Leave airport approaches, satellite towns, and long corridor exits outside if those trips are commercially “intercity” for your partners.
2. Set urban commission for the dense product. This is usually the rate drivers compare in group chats.
3. Set intercity commission with deadhead and time in mind. Higher or lower is a commercial choice; the software’s job is to apply the choice consistently.
4. Run ten synthetic trips in staging: both-in, start-in/end-out, start-out/end-in, both-out. Screenshot classification and cut. Put those screenshots in the partner playbook.
5. Publish driver-facing language that matches the fence. “Inside the city fence on both ends” beats “local trip” every time.

Tradeoffs to say out loud:

• Fence too tight: almost everything becomes intercity; urban rate is marketing fiction.
• Fence too loose: intercity work gets the cheap urban cut; you underprice the hard trips.
• Fence redraw without grandfathering rules: yesterday’s “urban” trip looks “intercity” tomorrow and trust collapses. Version the fence change with an effective time and a driver notice.

Franchise and multi-company cities

When several companies share a metro area, each may need its own urban fence and rate pair. A downtown cooperative and a suburban franchise rarely agree on where “city” ends. Documented admin support for company-level urban and intercity commission — including the fence used for classification — exists so you are not forced into one political compromise fence for everyone.

Still enforce a shared vocabulary: both ends inside *that company’s* urban fence means urban *for that company’s cut*. Drivers hopping companies must be retrained; the pin that was urban yesterday under company A may be intercity under company B.

Phone-desk bookings still need the same labels

Some fleets still take bookings by phone. In product terms that is ops creating the order in admin from a phone call — not a special commission universe. Once the trip exists with pickup and dropoff, the same geofence test applies when the cut is calculated. Do not invent a third “desk rate” in training unless finance truly wants a third scheme and admin actually has it. Mystery desk exceptions are how franchise audits fail.

Keep overseas messaging free of market-specific hotline brands. The capability that matters is admin-side order creation plus the same urban/intercity classification the app trips use.

What this is not

Stay precise in sales and implementation:

• This is not a promise that intercity always costs drivers more. Rates are yours to set; the product gives you two buckets and a fence.
• This is not dynamic surge by polygon. Urban/intercity commission is classification + scheme, not a demand multiplier essay.
• This is not a substitute for monthly-pass logic when you waive per-trip commission for subscribed drivers. Pass behavior is a parallel commercial tool; see the commission-models article for that axis.
• This is not WeChat, official-account, or national hotline channel design. Those entry points appear in some source docs for specific markets; this blog and overseas product pages keep focus on dispatch, meter, fence, and wallet settlement.

Soft next step

If you are modeling a city launch, draw the urban fence on a blank map first, then assign two draft rates, then walk five real sample itineraries through both-ends-inside vs not. When that spreadsheet matches what admin shows on a demo order, you are ready to talk implementation on the taxi dispatch software page or request a walkthrough of company commission and geofence screens. Bring one cash-heavy driver persona and one card-or-balance-heavy persona; the wallet deduction story only lands when both are in the room.