Operator procedures
These are the working procedures for the payment platform. They tell you how to operate the features, install the workstation service, set up a handheld, take a payment, push offline transactions, reconcile at the end of the week. One task per page, written so you can follow it standing at the counter or holding the device.
Where to start
Pick the section that matches what you are working on.
- Workstation: the Windows payment service at the counter. Install and reinstall, daily procedures, terminals and EMV, settings, and the errors you see on screen.
- Handheld: the handheld payment app. Set it up, learn each mode of operation, take payments, and push offline transactions.
- Cloud Portal: the merchant web portal. Reconcile transactions, provision the configs that devices pull down, and run Order & Pay.
New to the platform? Read How it all fits together first, it shows how the three pieces connect, then Getting started for hardware and prerequisites.
Need a fix fast? Managers can jump straight to the common POS errors quick reference: look up what you see, what it means, and the quick fix.
How to read a procedure
Every procedure page is laid out the same way:
- Purpose: what the procedure does, in one line.
- When to use this: the situation that sends you here.
- Steps: numbered, in order, with the on-screen controls in bold so you can match them to the screen.
- Verify: how you know it worked.
- See also: the related pages, so you can follow how the features tie together.
A few conventions:
- On-screen labels are written exactly as they appear, like the Reload Workstation Config button or the SAF Stats button, so you can match them.
- Where a value is specific to your site, you will see a placeholder such as
<your Merchant ID>. Fill in your own. - Where a screenshot still needs to be captured, you will see a bracketed note like [INSERT SCREENSHOT: …]. The step still works without it.
