Carsharing Passenger Coupons: Issue, View, and Pay the Fee Stack

A coupon campaign fails in public when marketing has already promised a discount and the passenger cannot find the offer—or worse, finds it and nobody can say which fee it touches. In a car-plus-driver hall, that argument happens next to a real stack: base fee, service fee, insurance fee, and driver fee. Ptaxi’s carsharing system documents three coupon surfaces that belong together: passengers view coupons and usage in the passenger center; admins can bulk-issue coupons from the passenger list; the marketing center can add, edit, and delete coupons and view their details.

This line is car-plus-driver hire, not hardware peer-to-peer car sharing. A driver still picks up the vehicle, serves the trip, and returns it. Coupons do not turn that hall into a keyless P2P protocol list. They also do not come with a published stacking formula. This piece stays on issue, view, and the nearby pay path—without inventing arithmetic the docs do not give.

Why coupons need a home the passenger can actually open

Launch teams love to announce “we have coupons” and then forget where the rider looks. The documented passenger center includes personal profile, trips, wallet (top-up, withdrawal, bills, invoices, and the violation prepayment collected after qualification), coupons, violation lookup, safety settings, and customer service. Coupons sit there as their own item: view coupons and usage.

Typical pains this surface is meant to blunt:

1. Marketing issues an offer, then tells riders to “check the app,” and nobody knows which menu to open.
2. A passenger insists they still have an unused coupon, and support has no usage view to talk through.
3. Ops bulk-messages riders about a campaign but never bulk-issues the actual coupon.
4. Sales explains coupons by inventing “it knocks 20% off insurance, then stacks with a second code,” which the carsharing list does not say.

The passenger-center view answers a simple question: what offers does this rider currently have, and what is their usage status? It does not replace qualification. Before a rider can use the hall they still complete vehicle-use qualification with personal information and a driving license, and they may need to pay the documented violation prepayment. A coupon in the center does not skip that door.

It also does not replace search. Riders still find vehicles by place and time, then filter by site, vehicle type, brand, seats, pickup address, rental window, distance, rental count, and price. A coupon that cannot be found is useless. A found coupon that nobody issued is a support ticket.

How admins issue and maintain coupons

Two admin surfaces do the work behind that passenger view.

On the passenger list, staff can look up riders (phone, name, gender, status, city, and related details), view related orders, suspend an account, bulk-issue coupons, and send push messages. Treat bulk issue and push as a pair you can use together, not as the same button. A push without an issued coupon is an advertisement. An issued coupon without a notice may sit unseen. The list lets you do both. It does not force you to do them well.

In the marketing center, staff can add, edit, and delete coupons and view coupon details. That is the catalog of offers: create one, change one, remove one, inspect what you created. The carsharing marketing list does not add extra coupon-type labels here. Other product lines document discount versus reduction coupons in their own lists. Do not import those labels into a carsharing demo unless you are looking at that other line. On this line, say what the docs say: add, edit, delete, and view details.

Neighboring marketing tools on the same center include referral rewards and sign-up rewards—campaigns you can add, edit, or delete for referring new users or drivers, and for new user or driver registration. Keep them on their own cards. A sign-up reward is not automatically a coupon unless your own campaign is set up that way, and the list does not spell out that wiring. Do not promise that every new registration drops a coupon into the passenger center.

Driver management, vehicle import, and realtime location remain fleet tools, not coupon tools. Point vehicle load-in at vehicle import. A generous coupon on an empty vehicle list just moves disappointment around.

The pay path next to the coupon, without invented math

When the passenger confirms and pays, the documented order information includes base fee, service fee, insurance fee, and driver fee. Payment follows that confirmation. An unpaid order is kept for about half an hour, then auto-cancels. That cancel window already has its own write-up at half-hour unpaid cancel. The fee stack and weekday, weekend, and holiday pricing live at fee stack and realtime vehicle location and weekday, weekend, and holiday pricing.

Why mention pay on a coupon page? Because riders judge an offer against the number they are about to pay. If you cannot name the four fee lines, you cannot have an honest coupon conversation. If you then invent how a coupon splits across those lines—or whether two coupons stack—you are writing fiction. The confirmed carsharing lists do not publish that arithmetic. Demo the passenger-center coupon view, demo bulk issue and marketing add/edit/delete, then open confirm-and-pay and name the four fees. Stop before the whiteboard formula.

Admin pricing plans set rates by vehicle type across weekday, weekend, and holiday cycles, plus service, insurance, and driver fee fields. Platform commission then splits paid orders by the configured company share. Those are pricing and finance controls. They are not a hidden coupon engine you should invent during the same slide.

After pay, the trip still needs a driver in the order hall: the driver picks up the car, goes to the passenger, runs the hire, and returns the vehicle for inspection. A coupon does not skip driver qualification review or return inspection. If the buyer’s question has moved to the trip itself, step off the coupon card.

Ops tradeoffs to say out loud

• Issue coupons before vehicles, prices, and drivers are ready: the passenger center looks busy; the hall cannot fulfill the booking.
• Build the hall and never give coupons a view or an issue path: campaigns live in posters, not in the app.
• Invent stacking rules in sales because “everyone stacks”: finance and support will spend the first month unwinding promises the product list never made.
• Bulk-issue without a written campaign owner: nobody knows who may delete a coupon or why usage looks off.

Practical notes that match the surfaces:

• Create the coupon in the marketing center first, then bulk-issue from the passenger list to the riders who should receive it.
• Show riders the passenger-center coupons item during onboarding screenshots, next to wallet and trips.
• When a rider asks why an order still shows four fee lines, name base, service, insurance, and driver fees. Do not invent which line the coupon supposedly erased.
• If the order sits unpaid, the half-hour cancel still runs. A coupon does not pause that clock unless your own undocumented customization says so—and this article will not claim that.

Customer service on this line includes in-app online service on the App. Keep that as support, not as a second place to invent coupon codes by hand.

What this is not

• Not hardware peer-to-peer car sharing, keyless lock protocols, or store-rental smart unlock. Store locks live on the separate car-rental line.
• Not a published stacking formula, discount-versus-reduction taxonomy copied from another product, or a claim about which fee line a coupon hits.
• Not qualification, violation prepayment, or return inspection—those remain their own gates.
• Not named map vendors, bank cards, credit cards, or card processors.
• Not WeChat mini-program packaging for overseas App buyers, and not a local emergency short-code pitch. Passenger emergency tools on this line stay on their own safety card.
• Not vehicle import, realtime location, or driver withdrawal review.

Launch sequence sales can repeat

1. Open the marketing center, add a sample coupon, and show that you can later edit, delete, and view its details.
2. Open the passenger list, bulk-issue that coupon to a test rider, and optionally send a push.
3. Log in as that rider and open the passenger-center coupons item to view the offer and its usage.
4. Start a booking and stop on confirm-and-pay. Name base fee, service fee, insurance fee, and driver fee. Say out loud that the docs do not publish stacking math.
5. Remind the room this is a car-plus-driver hall: a driver still has to accept, pick up the car, and complete return inspection.

If a prospect wants “unlimited stacking until the trip is free,” ask who pays the driver fee when the whiteboard reaches zero. The honest answer is a policy you write, not a formula this product list already printed.

Soft next step

If your car-plus-driver campaigns still live in posters while riders cannot find an offer, put coupons back on their three documented surfaces: passenger-center view and usage, admin bulk issue, and marketing add/edit/delete. Keep the pay screen’s base, service, insurance, and driver fees in the same conversation, without inventing stack math. When a lead can demo that without turning the product into hardware P2P, you are ready to run the carsharing system as a hire hall that can also issue an offer a rider can actually see.