Designated Driver Wallet Top-Up Bonus Packages: Passenger Credit That Changes Behavior

Nighttime designated-driver demand is spiky. Passengers hesitate at the pay sheet. Drivers refuse to go online with empty wallets. Marketing wants a promotion that is not another vague “20% off someday” coupon nobody trusts.

One documented lever on Ptaxi’s designated driver app line is blunt: passenger wallet top-up packages that can grant bonus credit. Choose a package, get extra balance, spend that balance on trips. Pair that with clear trip pay paths and the driver-side go-online balance reserve, and you have a money story ops can actually run. This piece stays inside the designated-driver feature docs — no invented card rails, tip jars, or Stripe billing portals.

What the passenger wallet package does

Under personal center → my wallet, passengers can top up with a custom amount and then pay fares with balance. The same wallet block states that the backend can configure recharge packages; when a user selects a package, they can receive bonus credit.

That is the whole product sentence. Do not inflate it into a points mall. It is:

• Admin defines packages (amounts + bonus grant).
• Passenger picks a package instead of (or alongside) a naked custom top-up.
• Bonus lands as spendable credit for trip pay.
• Invoice and billing details still sit on the wallet surface as documented (invoice of trips subject to minimum invoice amount; full income/expense detail).

Overseas pages should describe pay as in-app wallet / local wallet options documented for the tenant rather than leading with China-brand wallet names from the source tables. The behavior you sell is balance + package bonus + trip settle — not a brand logo wall.

Why bonus packages change Friday night behavior

Custom top-up alone is honest but cold. Passengers add exactly tonight’s estimate and stop. Packages with bonus credit create a small prepaid habit:

• Rider loads a package once.
• Bonus makes the effective rate feel better than paying trip-by-trip through an external wallet every time.
• Next booking is one tap on balance — fewer abandoned pays at the curb.

Ops still has to price packages like an adult. A huge bonus on a tiny package trains one-and-done abuse. A stingy bonus on a huge package never converts. Start with two or three packages tied to realistic trip counts in your city, then read wallet billing details for a week before inventing a fourth.

Trip pay paths the bonus has to survive

Passenger pay on designated-driver orders documents balance alongside other local digital wallet channels. After the trip, bill confirm can include add-ons (highway / bridge / parking as filled), then:

• Passenger pay — bill pushed to the passenger for online settle.
• Driver advance pay — driver uses balance or local wallet channels to advance.
• Show driver payout QR — passenger pays offline; driver confirms received; order ends.

Bonus credit only helps when the passenger actually uses balance. If your city runs heavy offline QR collection, package marketing still works as prepaid acquisition — but train riders that balance pay is the path that consumes the bonus. Otherwise support hears “I topped up and still paid cash to the driver.”

Business switches can enable or disable passenger pay, driver advance, and cash/offline-style collection. Configure those before you blast package ads. A bonus campaign into a cash-only culture is a finance headache.

Driver side: reserve gates are not the passenger bonus

Do not glue passenger marketing to driver wallet rules in one muddy paragraph. Driver go-online on this line can require:

• Wallet balance at or above a configured reserve — below reserve, the driver cannot go online / accept (per business switch for acceptance limits).
• Optional requirement to upload payout QR codes before go-online.

Driver wallet also supports custom top-up (for advancing fares), withdrawal with records, and billing details. Driver-side packages with bonus credit appear in the same wallet documentation pattern — useful for drivers who advance fares — but the go-online reserve is a gate, not a gift.

Coach drivers separately:

• Keep reserve topped so Friday peak is not a locked screen.
• Upload payout QR if the tenant requires it for offline collection.
• Do not tell passengers “use my QR so your package bonus still somehow applies.” Bonus lives on the passenger balance path.

Invoicing and billing detail keep finance sane

Passenger wallet invoicing: select trip orders, view invoice history, respect minimum invoice amount from the backend. Billing details show income and expense. When packages grant bonus credit, finance will ask whether bonus is liability, promo expense, or both. Answer that in accounting policy; the product gives you the ledger lines and package configuration — it does not invent your chart of accounts.

Corporate-style buyers sometimes ask if designated-driver packages replace formal company accounts. They do not. This line’s package tool is a consumer wallet promotion. If you need company employees and approvals, that is a different product surface (ride-hailing / rental enterprise backends). Keep the pitch honest.

Ops checklist before launching packages

1. Configure two packages with clear bonus math; screenshot them for support.
2. Confirm balance appears as a pay option on bill confirm in the tenant build.
3. Align driver go-online reserve so supply is online when prepaid demand spikes.
4. Decide whether offline QR collection stays on during the campaign; write one support macro for “I had balance but paid offline.”
5. Watch billing details for package top-ups vs trip burns for seven days; adjust package sizes before scaling ads.
6. Keep emergency / police dial and trip share coaching unchanged — promos never replace safety flows.

What not to invent

• No credit-card-only checkout story; docs do not list card/Stripe.
• No tip line item as a platform feature.
• No claim that bonus credit auto-converts to driver tips.
• No WeChat mini-program booking pitch on overseas marketing pages.
• No fake “users load 3x more with packages” metric.

Speak in configuration and screens: package list, bonus grant, balance pay, driver reserve gate.

Support macros worth writing once

When packages go live, support will hear the same three tickets. Pre-write macros:

1. “I bought a package but balance looks wrong.” Walk billing details: top-up line, bonus line if separate, trip burns. Confirm they selected a package, not a custom amount with no bonus.
2. “Driver asked me to pay the QR instead.” Explain offline collection does not spend passenger balance; if they wanted to use bonus credit they need the passenger pay / balance path on bill confirm.
3. “Can I withdraw bonus credit as cash?” Wallet docs center top-up for trip pay and invoice of trips — not a cash-out of promo credit. Say no unless your tenant built something outside this feature list (do not invent it in marketing).

Those macros keep Chat from inventing policy under pressure.

Measuring whether packages work

Useful weekly reads from wallet and order data (however you export them):

• Package top-up count vs custom top-up count.
• Share of completed trips settled on balance during the campaign.
• Driver go-online failures attributed to reserve (if you log that reason).
• Offline QR settles during the same window — if that share stays flat while packages sell, you are acquiring prepaid riders who still pay cash at the curb.

Act on the last metric: either educate riders or temporarily tighten offline collection switches while the campaign runs.

Closing

Prepaid bonus packages are a small feature with large ops consequences. Done well, they move designated-driver passengers onto balance and smooth peak settle. Done poorly, they fight your offline collection habits and confuse drivers who still cannot go online under reserve rules.

Ptaxi documents passenger (and driver) wallet packages with bonus credit on the designated-driver line, alongside balance pay and go-online reserve switches. Demo those screens when a buyer asks how you fund loyalty without inventing a second currency.