Taxi Passenger Wallet: Custom Top-Up and Billing Details
A taxi fare can be paid from a prepaid balance, or it can be settled in cash at the curb. Those two paths look simple until a passenger asks where the money went, or a driver takes a cash job and cannot cover the platform commission. Ptaxi’s taxi dispatch software documents a passenger wallet with a custom-amount top-up, billing details for income and expense, and a driver wallet that has to stay funded when the passenger pays cash.
This article stays on top-up and billing details. Invoice request lives in the same passenger wallet, but it is only a short pointer here. This is not a finance-ledger article, and it is not a coupons post.
What the passenger wallet actually holds
The passenger wallet sits in the personal center, under My Wallet. Three items are documented: top-up, invoice, and billing details.
Top-up is a custom amount. After the top-up, the balance can pay the fare. That is the whole prepaid contract in the list. There is no documented auto-reload, no family wallet, and no card pre-authorization. A custom amount is easy to explain at a support desk. It also means the passenger has to come back and top up again when the balance runs out. Do not brief a “keep my wallet full” rule the list does not describe.
For an overseas buyer, keep the payment wording plain: configured in-app payment methods and account balance. Do not name a card rail or a payment provider. Cash settlement is a documented taxi option, and it has a direct effect on the driver wallet, which belongs on the same training card.
Billing details let the passenger view all income and expense records. Train this as a visible list, not as a paper envelope the passenger has to request later. The list does not publish column names, date filters, or an export button. In a demo, open a test wallet after a top-up and after a fare payment, and write down what the rows actually show. Do not invent a spreadsheet download or a monthly statement as a product fact.
Invoice sits in the same wallet, and it should stay in one short paragraph. The passenger can select taxi trip orders to request an invoice and can view invoice history. Invoicing must meet the minimum invoice amount set in the backend. On the admin invoice screen, paper invoices go through customer-service review and mail, and electronic invoices are handled by a third party and sent to the passenger’s email after the passenger selects orders. That is enough to answer “can they invoice from the wallet?” The rest of this article is about top-up and billing details, not about invoice operations.
Admin top-up is a support path, not the main story
On the admin passenger list, staff can view the platform’s passengers and open passenger details, including account information, login and registration logs, related orders, and invoice records. Staff can also top up a passenger, plus suspend or unsuspend the account, issue coupons, and send a push.
Mention admin top-up only as a support path. A passenger who cannot complete a top-up in the app, or a goodwill credit after a disputed fare, can be handled here. Do not turn the walkthrough into a coupons training, and do not treat “issue coupons” or “send a push” as wallet features. They are neighboring actions on the same passenger row.
The list does not say admin top-up posts a different kind of billing row than a passenger self-serve top-up. In a demo, top up from the passenger app and from the admin list, then open billing details and compare the records. Write down what you see. Do not promise a labeled “support credit” line unless the build shows one.
The driver wallet is the cash-job counterpart
The driver wallet, also under My Wallet in the driver personal center, is the documented contrast you should put on the same card.
Top-up is again a custom amount. The reason it matters is cash settlement. When the passenger pays cash, the driver must have enough balance to cover the platform commission deduction. The earlier note on bill confirm, add-ons, and cash settlement still applies: cash is a real taxi option, and the commission still has to come out of the driver wallet. A driver who takes cash with an empty wallet is not just “unpaid by the app.” The list says the balance has to be sufficient for that commission cut.
That is the tradeoff you should say out loud. Prepaid balance is tidy for the passenger and leaves a billing row. Cash at the curb is still allowed, but it moves the funding problem onto the driver. If your operations team prefers cash-heavy shifts, the driver top-up is the account that has to hold the commission.
Withdraw lets the driver request a withdrawal from the driver wallet. Withdrawal records include status, amount, and request time. Admin withdrawal management is the review step: after the driver requests a withdrawal, backend staff must review it. Do not invent a payout calendar, a bank-account form, or a named payout provider. Confirm the review screen in a demo, and keep the documented record fields to status, amount, and request time.
Billing details on the driver side show all of the driver’s income and expense records. Use the same habit as the passenger list: open it after a cash job, after a passenger-paid job, after a top-up, and after a withdrawal request. The list does not name every row type.
A short pointer to admin finance, then stop
Admin finance has screens you should know exist, without turning this article into a ledger post.
Order accounts summarize income by company. Opening the detail lets you see that company’s drivers, their income, and those drivers’ order records and details. The payment ledger records all expense and income data. Invoice management is the admin side of the passenger invoice request already mentioned, including the minimum amount and the paper versus electronic split.
That is enough of a pointer. If a buyer wants a company-level income drill-down, schedule that as a finance walkthrough, not as a wallet demo. The wallet story is the passenger balance, the passenger billing list, and the driver wallet that funds the cash-job commission.
What not to promise on a taxi wallet
Do not promise auto-reload, a family or shared wallet, or card pre-authorization. Do not name a card rail or a payment provider. Use “configured in-app payment methods and account balance,” and keep cash settlement as the documented taxi option that pulls commission from the driver wallet.
Do not make invoicing the center of the talk. One paragraph is enough: request plus history, with a minimum amount, and paper versus electronic on the admin screen. Do not turn admin passenger actions into a coupons article. Do not invent an export, a scheduled statement, or a family billing group. Do not claim the passenger wallet can pay a cash job; cash settlement is offline, and the commission comes from the driver wallet.
A short ops checklist before you brief the app
Keep this to one page.
- In the passenger app, open My Wallet. Top up a custom amount, then pay a fare from the balance. Open billing details and note the income and expense rows.
- Stay on invoice only long enough to show order selection, invoice history, and the minimum amount set in the backend. Do not run a full invoice training here.
- From the admin passenger list, top up the same test passenger as a support path. Compare the billing row with the self-serve top-up. Do not demo coupons or push as part of this card.
- On the driver side, top up a custom amount. Run a cash settlement and confirm the driver balance covers the platform commission deduction. Then run a passenger-paid job and compare the two billing paths.
- Request a driver withdrawal and open withdrawal records. Confirm status, amount, and request time. Show that admin review is required after the request.
- If useful, open order accounts and the payment ledger for a one-minute pointer, then leave finance.
If a script starts promising auto-reload or a named card rail, cut it back to a custom amount, a visible billing list, and a driver wallet that must cover the cash-job commission.
Close
A taxi passenger wallet is a prepaid balance with a custom-amount top-up, plus a billing list of income and expense. The same personal center also holds invoice request and history, but that is a short side path. The driver wallet is the counterpart for cash work: the driver tops up a custom amount so the platform commission can be deducted when the passenger pays at the curb, and the driver can request a withdrawal that staff later review.
That is enough to brief prepaid balance versus cash at the curb. It is not enough to sell auto-reload, a family wallet, or a card pre-authorization the list does not describe. Look at the passenger and driver wallets on the taxi dispatch software product page. If you want a walkthrough, ask for a demo and bring one balance-paid job and one cash job, then watch billing details and the driver balance after the commission cut.
Frequently asked questions
How does a passenger add money to the taxi wallet, and what can that balance pay?
The passenger wallet sits in the personal center, under My Wallet. Top-up is a custom amount. After the top-up, the balance can pay the fare. The list does not document auto-reload, a family wallet, or card pre-authorization. Payment should be briefed as configured in-app payment methods and account balance. Do not name a card rail or a payment provider.
What do billing details show, and is invoicing part of the same wallet?
Billing details let the passenger view all income and expense records. The same wallet also lets the passenger select taxi trip orders to request an invoice and view invoice history, and invoicing must meet the minimum invoice amount set in the backend. Invoicing is a short side path on this topic, not the focus. The list does not publish billing column names or an export button.
Can admin staff top up a passenger wallet?
Yes. On the admin passenger list, staff can top up a passenger, along with suspend or unsuspend, issue coupons, and send a push. Treat admin top-up as a support path, for example when a passenger cannot complete a top-up in the app. Do not turn this into a coupons walkthrough. The list does not say the admin top-up posts a differently labeled billing row; compare both paths in a demo.
Why does the driver wallet matter when the passenger pays cash?
When the passenger pays cash, the driver must have enough wallet balance to cover the platform commission deduction. The driver can also top up a custom amount, request a withdrawal, and view withdrawal records that include status, amount, and request time. Backend staff review the withdrawal after the request. Driver billing details show all of that driver’s income and expense records.