Understand cash orders and payment events
Order details can present one payment method, several payment-method labels, a Change of cash value, and a Payments event list. These are returned/read- only display states. They do not instruct a Driver to collect money and do not prove payment authorization, capture, receipt, balance, payout, or settlement.
:::warning Never infer a collection amount from the payment-event list
Cash, wallet, gateway, order total, event amount, and Change of values have different meanings and can be formatted by different UI branches. Do not add, subtract, collect, refund, exchange, or mark payment based only on these rows.
:::
Availability
Payment information appears within an authorized order detail when the current order read returns payment-method or payment-event data. Driver App has no dedicated Earnings or payout route in the accepted navigation; an order summary is not a payout surface.
The header can display Payment method or Payment methods. The order bill can also display Payments when the returned event array is nonempty. These sections do not use exactly the same event filter or wallet fields, so they can show different-looking labels or counts for the same returned order.
State and result matrix
| Visible state | Safe interpretation |
|---|---|
| One header method | The header derived one returned payment label |
| Several header methods | More than one returned event classified as a payment for the header |
| Missing or empty event array | Header falls back to the order-level payment method when available |
| Non-payment events only | Header can show zero classified payment methods while Payments still renders returned rows |
| Cash | A returned gateway/order method is labeled cash |
| Change of amount | The order's returned cash field is formatted as change information; it is not an amount-to-collect receipt |
| Cash Wallet or Pay with Cash Wallet | A returned wallet field mapped to the cash-wallet label |
| Credit-points wallet label | A returned wallet field mapped to the points label |
| Gateway label | A returned event or order payment method supplied a gateway/name |
| Blank or unfamiliar row | The returned event shape did not map to the expected display branch |
| Negative-looking event amount | The UI prefixes a non-cash event amount with a minus sign; it is not proof of debit, refund, or settlement direction |
Header and Payments are different projections
The header counts only returned events classified as payments, then builds its labels from wallet-currency data, event gateway/name, or the order- level fallback.
The Payments section appears when the event array is nonempty and iterates every returned event. It derives wallet labels from a different wallet-event field. A non-payment event can therefore appear in this section even when it was not counted by the header.
Do not use header singular/plural wording, row count, or label agreement as an audit of the underlying payment timeline.
Cash and amount boundaries
For a cash gateway, Driver App can replace the event amount with the order's cash field and show that value positively. In the header, the same field can be formatted as Change of. For other rows, the UI generally formats the event amount with a leading minus sign.
Keep these values separate:
- Order total.
- Order-level payment method.
- Cash/change field.
- Individual payment-event amount.
- Wallet label or wallet event.
- Gateway label.
- Driver tip, fees, taxes, discounts, or other bill rows.
The displayed values are not a reconciliation equation. Driver App source does not establish that the event list totals the order, that cash is still due, or that a wallet/gateway settled.
Effects and boundaries
This reference is view-only. Opening an order detail can start authenticated order/message reads, location work, socket subscriptions, and remote image loads, but the inspected payment display itself has no collect, payout, settle, refund, or payment-event mutation control.
Financial truth belongs to the current order/payment system and the operator's approved reconciliation process. A formatted amount, gateway name, wallet label, completed order, printed-looking layout, or absent error is not a provider or settlement receipt.
Troubleshooting
Header and Payments show different labels or counts
They use different filters and wallet/event fields. Do not choose one as the authoritative settlement record. Record the visible non-sensitive state and ask the operator/payment owner to reconcile the order.
Cash shows Change of an amount
Treat Change of as the returned cash-display field only. Do not interpret it as cash tendered, amount due, amount collected, or payout. Follow the business's approved cash-handling policy outside this article.
A payment row is blank or unfamiliar
The returned event may not include a recognized wallet/gateway shape. Do not guess the method or edit the order. Ask the operator/payment owner to inspect the current payment record.
Event amounts do not match the order total
Do not sum or net the displayed rows as a settlement calculation. Taxes, fees, tips, discounts, wallet events, cash display and event semantics remain separate. Use the approved payment reconciliation source.
The order is completed but payment still looks unresolved
Order status and payment settlement are different lifecycles. Do not contact a customer for payment, issue a refund, or repeat an order action from this view. Escalate to the operator/payment owner.
Related guides: Understand an active delivery · Complete a delivery · Review delivery history · Navigate Driver App