Carsharing Passenger Wallet: Top-Up, Withdrawal, and Billing Details
A carsharing trip is easy to over-explain in a chat thread. The rider paid a qualification deposit, then a trip fee, then maybe a subsidy appeared, then someone asked for an invoice, then a withdrawal sat in review. If those movements only exist in screenshots, the desk cannot answer a simple question: what is spendable, and what is held. Ptaxi’s carsharing system documents a passenger wallet that keeps those records in one place: account top-up and withdrawal plus those records, billing details for top-up, withdrawal, orders, and subsidies, invoice query and issuance, and a view of the violation prepaid deposit paid after ride qualification.
This is not the qualification gate, and it is not the driver payout card. Carsharing violation prepaid deposit already covered why that hold exists. Driver wallets already covered driver withdrawals and commission. Today’s card is the passenger wallet, and the boundaries that keep it from being mistaken for those neighbors.
What the passenger wallet actually holds
The documented passenger wallet has four parts. Keep them distinct in a launch brief.
Account top-up and withdrawal, with a record of those movements. The rider can move money onto the account and move it back off. The list names both directions. It does not publish a minimum top-up, a withdrawal fee, a same-day limit, or a named payment rail. Describe payment as configured in-app methods and account balance. Do not invent a bank card, a credit card, or a specific processor.
Billing details list top-up and withdrawal records, order lines, and subsidies. That is the ledger the desk and the rider can both point at when a number does not match. The list does not itemize every column. In a demo, open a test account and write down the line types you actually see. Do not brief a packaged “weekly statement PDF” unless the demo shows one.
Invoice query and issuance lives in the same wallet. The rider can look up order invoices and request one. Admin finance includes order invoicing. The carsharing wallet line does not itemize a minimum invoice amount, or a paper-versus-electronic split, the way some other product lists do. Do not import those rules from taxi or ride-hailing. Confirm the invoice flow in a demo, and keep this article from becoming a second invoicing post.
A view of the violation prepaid deposit paid after the passenger completes ride qualification. This is a view, not a rewrite of the booking gate. The deposit is paid because the rider qualified to use the car, and it is intended for issues such as violations or overtime after a trip. The wallet can show it. The list does not say the rider can spend that deposit as ordinary trip credit. In a demo, top up a small amount and pay the deposit on a test account. Write down whether they appear as two balances or one. If they are separate, say so in the brief.
That is the first tradeoff to say out loud. A wallet that shows deposits, trip charges, subsidies, and withdrawals in one billing list helps a support call. It also tempts a sales brief to call everything “balance.” Spendable credit, a withdrawable amount, and a prepaid hold are not automatically the same thing. The list does not publish a formal split of those buckets beyond the labels above. Copy what the demo shows.
What this wallet is not
Ride qualification — personal information plus a driver’s license — is the gate before the deposit. It already sits next to the emergency contacts and identity post on the safety-settings side, and next to the deposit post on the booking side. The wallet is not the qualification form.
Violation query after a trip is a separate passenger tool. A deposit view is not a live ticket search. Use a short pointer if a buyer asks how a later violation is checked.
Coupons are a different personal-center item. Do not treat a subsidy line in billing details as a coupon wallet unless the demo uses the same record for both. The list names subsidies in billing details and coupons in their own menu.
The driver wallet is withdrawals, withdrawal records, and billing details for withdrawals, orders, and subsidies. Drivers on this line are the people who pick up the car and serve the trip. Do not brief passenger withdrawal rules as if they were driver payout rules. Driver withdrawals already have a review step in finance management. The passenger-wallet line names withdrawal and its records. It does not say an admin must approve a passenger withdrawal. Confirm that in a demo before you promise instant payouts, or before you promise a review queue.
Admin passenger list actions on this product are documented as viewing details, account suspension, related orders, bulk coupon distribution, and push messages. There is no documented admin top-up on that list. Taxi and car-rental lists do document a staff top-up on the user list. Do not import the button. If a demo later shows it, write it down as a demo finding, not as a fact from this list.
Neighbors to keep off this card
The violation prepaid deposit walkthrough already explained the hold. One pointer is enough. This article only adds that the wallet can show the amount paid after qualification.
Violations, invoices, and driver payouts after the trip already have a post. Invoice management in finance is “order invoicing.” Use that as a pointer, not a retell.
Unpaid-order auto-cancel and the fee stack (base fee, service fee, insurance, driver fee) already have their own posts. The wallet is how value moves; it is not the price list. A billing-details order line should match a finished or canceled trip. Confirm that in a demo rather than promising a live running total during the trip.
Push notifications and referral or sign-up rewards can create subsidy or reward lines. If a billing-details row looks like a campaign reward, open the campaign screens before you invent a new wallet type.
System settings can include payment-method switches, privacy, share content, download, and safety settings. Those switches are not the wallet. Mention them only if a buyer asks why a top-up method is hidden. Confirm the available methods in the demo tenant. Do not name a vendor.
What not to promise
Do not invent card rails, a credit line, or a particular payment processor.
Do not promise that the violation prepaid deposit can be used to pay a trip, or that it is automatically refunded into spendable balance, unless the demo shows that movement.
Do not promise staff-side top-up from the passenger list.
Do not import another product line’s invoice types, mailing workflow, or minimum amount as if they were documented here.
Do not describe China-only booking channels or a named customer-service vendor. Overseas copy should stay on the passenger wallet in the app, configured in-app payment methods, and account balance.
Do not invent a wallet interest rate, a loyalty point currency, or a multi-currency account.
A short ops checklist before you brief the app
Keep this to one page.
- Create a test passenger, complete ride qualification, and pay the violation prepaid deposit. Open the wallet and write down how that deposit is shown, and whether it is separate from spendable balance.
- Top up a custom amount with a configured in-app method. Confirm the top-up record appears, and that the balance can be used on a test booking.
- Request a withdrawal. Write down every field, the status you see, and whether an admin review appears in finance. If no review appears, do not invent one.
- Open billing details and list the line types: top-up, withdrawal, orders, subsidies, and anything else the demo shows.
- Start an invoice request from the wallet. Follow it only far enough to see whether admin finance has a matching row. Then stop — invoicing is a neighbor, not this card.
- Open the admin passenger list and confirm the documented actions: details, suspension, orders, coupons, and push. Note the absence of top-up if it is not there.
- Open the driver wallet on a test driver only to keep it off this card.
Close
The carsharing passenger wallet is the rider-facing ledger: top-up and withdrawal with records, billing details for those movements plus orders and subsidies, invoice query and issuance, and a view of the violation prepaid deposit paid after qualification. The list does not publish payment rails, a staff top-up button, or a formal rule that the deposit and the spendable balance are the same. Those are demo items, not brochure items.
If you run a car-plus-driver carsharing operation and riders still argue about deposits and trip charges in a chat thread, walk this path in a carsharing system demo. Bring one account with a deposit, one top-up, one trip line, and one withdrawal. Then decide how you will explain the split to support staff. For the deposit as a booking gate, use the violation prepaid deposit post. For driver payouts, use the driver wallet post. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
What can a carsharing passenger do in the wallet?
The passenger wallet supports account top-up and withdrawal, plus records of those movements. Billing details list top-up and withdrawal records, order lines, and subsidies. The same wallet also has invoice query and issuance, and a view of the violation prepaid deposit paid after the passenger completes ride qualification.
Is the wallet the same as the violation prepaid deposit?
No. After ride qualification, the passenger must pay a violation prepaid deposit, used for issues such as violations or overtime after a trip. That booking gate already has its own walkthrough. The wallet can show that deposit. It is not a claim that the deposit and the spendable balance are the same pot of money. Confirm the split in a demo.
Can staff top up a passenger from the admin list?
The carsharing passenger list documents viewing details, account suspension, related orders, bulk coupon distribution, and push messages. It does not document an admin top-up action. Do not import that button from the taxi or car-rental lists. If you need staff-side top-up, confirm it in a demo or leave it out of the brief.
Does this article explain how invoicing works end to end?
No. The wallet includes invoice query and issuance, and the admin finance area includes order invoicing. Types, minimum amounts, and delivery methods are not itemized on the carsharing wallet line the way they are on some other product lists. Treat invoicing as a pointer and confirm the flow in a demo. Do not retell another product line’s paper-versus-electronic rules as if they were this list.