Complete a payment operation
Complete an existing TPV payment operation when an external authorisation is ready to become a real ticket payment. If the operation is not already linked to a ticket payment, Antylogic creates the completed payment, applies valid item allocations, refreshes the ticket state and tries to queue a receipt when eligible output devices are configured.
In this article
Use this guide when a non-manual TPV payment operation already exists for a Harbor Soho ticket and the operator needs to finish it from the payment screen or the terminal operations panel.
This is not the manual cash or card flow. Manual methods create the ticket payment directly; this action completes an external operation that Antylogic can convert into a completed ticket payment.
Before you start
- Use an authenticated Harbor Demo Group session with Harbor Soho selected.
- The operator needs location permission `tpv:use` or `tpv:manage`; `tpv:view` can list operations but cannot complete them.
- A `tpv_payment_operation` must already exist in the current location for the ticket and payment method.
- A terminal must be selected, or the operation must already have `terminal_id` or `claimed_by_terminal_id`.
- Receipt output also needs TPV settings and an eligible output device, but the payment can still complete without a receipt device.
Instructions
- 1.
Open the payment operation
Open the ticket payment screen for the active Harbor Soho ticket, or open the terminal payment operations panel from the TPV floor screen. Review the requested amount, terminal and current operation state before completing it.
- 2.
Use Complete on the active operation
Press Complete on an operation that is not already completed or cancelled. The terminal panel is the clearest surface for finishing an external authorisation that is ready to become a ticket payment.
- 3.
Let Antylogic create or finalise the payment
Antylogic updates the operation to `completed`. If it has no linked `ticket_payment_id`, it creates a completed ticket payment using the resolved authorised amount, payment method label, terminal details and external reference.
- 4.
Check the ticket and receipt result
After the update, review the refreshed ticket payment state. The ticket can remain pending, move to partially paid, or become paid depending on effective paid totals. Receipt queueing is best effort and does not block the completed payment.
Validations and limits
- The operation must belong to the selected location and must exist in that location context.
- Operations already completed or cancelled do not expose the UI action.
- The authorised amount, after falling back to the requested amount, must be greater than zero when creating a new ticket payment.
- Explicit allocations must use ticket items from the same ticket, have positive amounts and stay within item and payment balances.
- If the operation already has `ticket_payment_id`, Antylogic does not create a second ticket payment or recalculate allocations.
- Do not promise receipt printing; output jobs depend on active TPV settings and eligible devices.
Expected result
The TPV payment operation is completed. When needed, the external authorisation becomes a completed ticket payment, valid allocations are applied, ticket and item payment states are refreshed, and receipt output is queued only when the configured devices allow it.