How to open advanced payment
Open the advanced payment screen for a pending TPV ticket so staff can review the amount due, payable lines, compatible payment methods, amount controls, previous payments and local payment operations before taking payment.
In this article
Advanced payment is the controlled handoff between a live restaurant ticket and collection. It gives floor staff and cashiers one place to confirm the pending balance, selected ticket lines, active payment methods and any local terminal operations before money is taken.
In the GB demo, this guide uses Harbor Soho with Olivia Hart and a pending TPV ticket. The app still shows implemented Spanish UI labels such as `Pago avanzado`, `Métodos de pago`, `Pendiente` and `A cobrar` inside the product screens.
Before you start
- You are signed in with an active organisation and location selected.
- The ticket belongs to the current location, such as Harbor Soho in the GB demo.
- You have the location permission `tpv:use`.
- The route includes a valid `ticketId`.
- When opening from ticket detail or the TPV screen, the ticket still has an amount due and is not void or closed.
- At least one active TPV payment method is compatible with the current user or local terminal.
Instructions
- 1.
Open a pending ticket
From the TPV ticket detail or the selected ticket in the TPV, choose `Pago avanzado`. The source action is intended for tickets with an outstanding balance.
- 2.
Confirm the payment context
Check the ticket header and totals before changing anything. The screen shows status, total, already paid amount, outstanding amount, selected amount to collect, change and tip.
- 3.
Select the lines to charge
Review the pending line list. The screen initially selects all unpaid units for full collection, but staff can clear the selection or choose individual units for a split payment.
- 4.
Choose a payment method
Select one of the visible active methods. The list is filtered to methods allowed for the current user and for the local terminal derived from the signed-in user.
- 5.
Enter the amount
Use the keypad when the collected amount differs from the selected outstanding amount. Cash-like methods show excess as change; non-cash methods show excess as tip.
- 6.
Review payments and operations
Before continuing, check the summary area for existing payments and local payment operations. Operations only appear as actionable when they match the current terminal scope.
Validations and limits
- Without an active organisation or location, the screen asks the operator to select a location.
- Without `tpv:use`, the screen blocks access to ticket collection.
- If `ticketId` is missing or the ticket cannot be loaded, the screen shows a loading or not-found error.
- The source button is disabled when the ticket is void, closed or fully paid.
- A direct deeplink can still reach the screen, so confirm the ticket status after opening; the verified screen block is explicit for void tickets.
- Settled ticket items are disabled and marked as settled.
- Only active compatible payment methods are listed; methods restricted to another user or terminal are hidden.
- If no compatible method exists, the screen shows that no active methods are compatible with the selected terminal.
- The amount accepts comma or decimal point notation, while empty, negative or non-numeric values are treated as no manual amount.
- Do not complete a payment, refund, discount, invoice or local operation when capturing this guide.
Expected result
The operator lands on the advanced payment workspace with the pending ticket context, selected payable lines, compatible methods and operation summary visible, ready for review before collection.