Outages, uncertain results & support
Avoid duplicates, retain evidence and recover using the original transaction.
On this page · Jump to a section
Before you begin
A duty manager, contingency log and support contact.
Where to go
POS / Support / Audit
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- If the screen stalls after payment, record time, branch, device, bill and observed result. Check the original bill and received funds before proceeding; do not charge again.
- Use the original retry/recovery action with the same request identity. Do not create a new bill to bypass an error. Escalate unresolved outcomes to the manager.
- Board-game, restaurant and pharmacy bills are not supported by Emergency Offline. Record verified times, items and receipts in the shop contingency log; a manager reconciles after recovery.
- Send support the incident time, branch, device/bill reference, app version, steps and error. Redact customer data; never send PINs, passwords, tokens or pairing QR codes.
- After recovery, reconcile bills, money, stock, outstanding games/documents and audit history. Record the incident and follow-up owner.
How to verify success
No duplicate charges, every contingency record reconciles and a manager signs off before closing the incident.
Limits & things to check
Do not clear device data, reinstall or rotate tokens to fix a pending bill before checking its result. Printer failure is not a reason to sell the same transaction again.
Ready to try it in your shop
Lessons are free to read. Actual operations require sign-in and the appropriate permission. Use test data for training.