> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Resume a payment or unfinished order

> Continue a submitted, initiated or failed payment from History without creating a second order.

Resume the existing order from History when its payment was submitted, initiated or failed. This avoids charging against a duplicate order.

## Who can do this?

The order and payment endpoints used here authorize **Owners, Managers and Staff** for the shop.

## Where to do it

Open **History**, find the order and select it. Payment is available for **SUBMITTED**, **PAYMENT\_INITIATED**, **PAYMENT\_FAILED** and **PAY\_LATER**.

## Resume payment

1. Confirm the order ID, status, items and total.
2. Select **Take payment**, **Resume payment**, **Retry payment** or **Take pay later payment**, depending on the status.
3. Choose one of the payment methods currently wired in the web flow: QR code, payment link, SMS, cash, Pay later or another device.
4. Complete the method-specific screen and wait for the status update.
5. If the result is Paid, mark the order complete when service is finished.

History and POS share one persisted active-order context. If a different POS order is already mid-payment for the same shop, History does not overwrite it; it shows a message pointing to that order instead.

The status-specific labels are deliberate: Submitted starts payment, Payment initiated resumes it, Payment failed retries it, and Pay later either takes payment or opens editing. Terminal states are excluded so a paid, completed, cancelled or refunded order is not offered for another payment.

## Recovery behavior

If a remote payment is still active, avoid starting another payment without first checking the current status. A failed remote payment can be retried on the same order. Closing an active payment can leave the order as Pay later when that path is chosen.

## Platform notes

The web dialog can hand payment to another registered device. That device acts on the same order; refresh History after it responds. Direct card/Tap to Pay tiles may be visible in designs or other platforms, but this web guide lists only methods wired in the current web implementation.

## Market notes

Payment recovery uses the same statuses in GB and Germany. The selected shop supplies currency, tax labels and country-aware phone defaults for SMS. Germany's fiscal processing remains behind the same order API and does not change the resume buttons.

## Troubleshooting

If History points to another active POS order, finish or close that order before retrying. When a remote payment remains active, refresh the order status before creating another link; for a failed payment, retry against the existing order ID.

## Related guides

* [Complete a Pay later order](/en/history/complete-pay-later-order)
* [Take payment in Point of sale](/en/point-of-sale/take-payment)