An order total or payment result looks wrong

Overview

• MiniTill treats the server Order/Payment state as authoritative, especially after discounts, loyalty redemption, split payments, terminal timeouts, or interrupted network responses.
• A terminal/app timeout does not prove the payment failed; the provider may have approved it while the POS missed the first response.
• Payment recovery/reconciliation exists to determine the result without blindly charging again.
• Order total, Amount due, and recognised Payment total can legitimately differ during partial/split payment or after redemption/refund.

When to use this

• Use this whenever staff see a payment error, uncertain terminal result, amount mismatch, duplicate-looking attempt, or an order that appears paid in one place and unpaid in another.

Step-by-step

1. Stop before initiating another charge.
2. Open the Order/Payment detail and check payment attempt/status.
3. Use Payment recovery/reconciliation for uncertain terminal outcomes.
4. Compare server Amount due with the amount already approved/recorded.
5. For split payments, review each tender separately.
6. Only retry/collect the remaining amount after the existing result is known.

Common mistakes

• Do not press Card/Pay again just because the terminal response was slow.
• Do not manually create a Cash payment to 'fix' an uncertain Card result.
• Do not edit loyalty/discount amounts after payment without following the proper refund/reconciliation workflow.

Troubleshooting

• If the payment is approved but the Order state looks stale, use the reconciliation/repair path rather than charging again.
• If the provider result cannot be resolved, record the Order/Payment/attempt identifiers before contacting support/provider support.