Car Rental Passenger Wallet: Custom Top-Up, Balance Pay, and Billing Details
A rental booking often fails at payment, not at the car. The renter wants to keep a balance for the next weekend trip, then see a list of what went in and what went out. If the brief only talks about invoices, the desk still cannot explain a missing top-up or a charge the renter does not recognize. Ptaxi’s car rental software documents a passenger wallet with three documented cards: custom-amount top-up, invoice request, and billing details. After top-up, the balance can be used to pay rental fees.
This is not an invoice article, and it is not the store finance ledger. Car rental invoice requests already covered pending, successful, and failed invoice applications. Today’s card is top-up, balance pay, and the income-and-expense list.
Custom top-up, then pay with balance
The passenger action is straightforward. Top up with a custom amount. After that, the balance can be used to pay rental fees.
“Custom amount” is the documented control. The list does not publish preset packages, a minimum top-up, a maximum, or a bonus on this wallet. Designated-driver bonus packages are a different product line. Do not import them. If a demo tenant shows suggested amounts, write them down as configuration, not as a packaged product fact.
That flexibility is the point, and also the support load. A custom field lets a renter load exactly what they need for a weekend hire. It also means staff cannot point to a standard package when someone tops up the wrong amount. If you want packaged amounts, confirm whether the demo tenant can offer them. Do not brief packages as a default on this line.
Checkout on this line supports account balance plus configured in-app payment methods. For an overseas brief, do not lead with a domestic wallet brand. Say balance and the methods the tenant actually has enabled. The docs do not name bank cards, credit cards, or a card processor. Do not add them.
The list says the balance can pay rental fees. It does not say the same balance can pay the vehicle deposit, the violation deposit, a delivery fee, or a post-return extra fee by itself. Those are easy to assume and expensive if they are wrong. In a demo, try a booking with balance only, then a return that adds an extra fee, and write down whether balance is offered again. Deposit records already have their own post. Keep deposit behavior off this card except as a question for the demo.
Do not brief an automatic top-up, a stored card on file, or a pre-authorization hold. None of those are in this list.
Billing details are a list, not an invoice
Billing details let the passenger view all income and expense records. That is the renter-facing ledger for “what happened to my balance.”
It is not an invoice, and it is not the admin payment ledger. A renter who needs a fileable document should use the invoice request in the same wallet, subject to the minimum amount, as already described in the invoice post. Billing details are the running list.
The list does not name the columns, a filter by booking, or a download button. It does not say a canceled order, a refund, a coupon discount, or a staff top-up appears as its own row type. Open the list after a custom top-up, a paid booking, and — if you can — an admin top-up or a refund, and copy the rows. Do not invent transaction types to make the page look complete.
The tradeoff is operational, not cosmetic. A clear billing list cuts down on “where did my money go” tickets. It also creates an expectation that every fee the store later adds will show up there the same day. The list does not document a delay, a pending row, or a push when a new charge posts. Confirm that in a demo before support scripts promise instant visibility.
What staff can do from the user list
Admin user list shows rental users and a detail view that includes user name, ID number, driver’s license number, phone, real name, nickname, city, registration time, last login, and status. The documented actions include details, top-up, and account suspension.
Staff top-up is the support path when a renter says a self-serve top-up failed, or when the company wants to credit an account. It is not the passenger wallet screen. The list does not document a mandatory remark, an approval step, or a cap. Open the action in a demo and copy the fields. If your finance team needs a reason code on every credit, confirm whether the screen can hold one. Do not invent it.
Account suspension is a neighboring action on the same row. Mention it so staff know the list is also an account-control tool. Do not turn this article into a fraud-operations guide.
Enterprise recharge is a different flow: after a company is reviewed, staff can top up the enterprise account, and an enterprise administrator can invoice recharge orders. That already sits in the invoice and corporate-hire posts. A staff top-up on a personal user is not an enterprise recharge.
Neighbors to keep off this card
Invoice request lives in the same wallet. Select trip orders, meet the minimum, view history. Admin invoice management lists pending, successful, and failed requests. Point at that post, then return to top-up and billing details.
The store wallet on the store app is a different account. It documents top-up that can be used to advance fares, withdrawals, withdrawal records, and billing details. Do not mix those withdrawal fields into the passenger wallet. The passenger card on this list is top-up, invoice, and billing details. It does not document a passenger withdrawal.
Store finance and the payment ledger already have a walkthrough. The payment ledger records income, expense, and top-up rows for users and stores, with amount, type, payment method, and time. That is the back-office ledger. This card is what the renter sees.
Coupons, deposits, and return extra fees have their own posts. A coupon changes what the renter pays; it is not a top-up.
What not to promise on the car rental passenger wallet
Do not invent preset top-up packages or a bonus amount on this wallet.
Do not name bank cards, credit cards, or a card processor.
Do not say balance always covers deposit, violation deposit, or a post-return extra charge. Confirm each in a demo.
Do not retell the invoice pending/success/failed queue here. Link it.
Do not describe a passenger withdrawal, a store-wallet advance, or an enterprise account credit as this screen.
Do not claim a tax-authority feed, a monthly statement download, or an automatic receipt email from billing details. Those are not in the list.
A short ops checklist before you brief the app
Keep this to one page.
- In the passenger app, open My Wallet. Find top-up, invoice, and billing details. Top up a custom amount and confirm the new balance.
- Place a test booking and pay with balance. Write down whether checkout also offers other configured methods, and which part of the fare balance was allowed to cover.
- Open billing details after the top-up and the booking. Copy the rows and any status labels you see.
- From the admin user list, top up the same test renter. Return to the passenger billing list and note whether that credit appears, and how it is labeled.
- Try one path that is easy to assume: a return extra fee, or a deposit payment, and see whether balance is offered. Record a yes or no. Do not generalize from a single tenant.
- Open the invoice card only to confirm it is still a separate request. Do not spend this rehearsal on paper versus electronic delivery; that is not how this rental invoice list is documented.
Close
The car rental passenger wallet is a custom-amount top-up, a balance that can pay rental fees, and a billing-details list of income and expense records. Invoice request sits in the same wallet and already has its own walkthrough. Staff can also top up a renter from the user list. The list does not document card rails, passenger withdrawals, or a guarantee that balance covers every deposit and extra fee.
If you run a rental company and renters keep asking why a completed booking still does not show a clear movement in their balance, walk this path in a car rental software demo. Bring a custom top-up, a balance-paid booking, and one staff credit from the user list. Then decide what the launch brief can say about balance pay. For the invoice request in the same wallet, use the invoice requests post, and come back here for top-up and billing details. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
Can a renter pay a car rental order with wallet balance?
Yes. The passenger wallet allows a custom-amount top-up, and that balance can then be used to pay rental fees. Checkout on this line also supports configured in-app payment methods alongside balance. The list does not say balance can cover deposit, violation deposit, or a later extra fee by itself. Confirm those cases in a demo.
What shows up in billing details?
Billing details let the passenger view all income and expense records. The list does not itemize the columns, the filters, or whether a failed payment appears. Open a test wallet after a top-up and a paid booking, and write down the rows you actually see.
Is this the same as car rental invoice requests?
No. Invoice request also lives in the same wallet: select trip orders, meet the minimum amount, and view invoice history. That path already has its own walkthrough. This article is the top-up and the billing-details list. Keep those rehearsals on separate cards.
Can staff top up a renter from the admin user list?
Yes. The rental user list includes a top-up action, along with details and account suspension. That is a staff-side credit, not the passenger’s own top-up screen. The list does not document a required reason code or a daily cap. Confirm the fields in a demo.