Skip to main content
Return to a Pay later order to edit its items or collect payment, then complete it after payment is recorded.

​
Who can do this?

The API authorizes Owners, Managers and Staff to work with the order for their shop.

​
Where to do it

In History, open an order whose status is PAY_LATER.

​
Edit or pay

  1. Verify the order ID, guest, table context, items and total.
  2. To change the basket, choose Edit. Tapp moves the same order back to Draft, rebuilds the POS cart and opens Point of sale.
  3. Add or remove items in POS, then continue to payment. The original order ID is retained.
  4. To pay without editing, choose Take pay later payment directly in History.
  5. Select the payment method and complete its flow.
  6. When the status is PAID, select Mark complete.
  7. Send or print the receipt if required.
Opening a Pay later order for editing replaces the local POS cart with that order. If a different order is already in a live payment state, Tapp blocks the handoff so it does not overwrite the active payment. The edit flow fetches the canonical order, moves it to Draft through the supported API and rebuilds its lines while keeping the order ID and guest context. Review every reconstructed line: a product removed from the current menu may no longer resolve like an ordinary item.

​
Troubleshooting

If another device has already paid or changed the order, the edit request can fail because the status moved. Refresh History and follow the new status instead of recreating the order. If payment fails, retry the existing order.

​
Platform notes

Pay later is shared across web and management mobile order flows. A terminal or other device can finish payment when dispatched; all platforms must converge on the same backend status.

​
Market notes

The lifecycle is the same in GB and Germany. Currency, VAT/tax labels, receipt format and phone defaults come from the order’s shop context. Completing a German order uses the backend fiscal handling rather than an extra manual POS step.