Terminals have a diagnostic self-test mode for checking connected components.
The self-test can be executed using:
a special diagnostic QR code at the BATM, or
triggered remotely
...
The QR code is one you create yourself, using a “Diagnostic Key” that you arbitrarily decide upon.
...
via the “Terminal Self Test” action.
...
Introduced in Terminal firmware version 20220106.
...
...
Remote
Navigate to the Terminal of interest and click on ACTIONS: Terminal Self Test
...
Onsite
Set a Diagnostics Key on the Terminal Details page for the BATM being tested.
| Tip |
|---|
The |
...
Diagnostics Key is disabled (empty) by default.
|
...
|
Create a “Diagnostic Key” of any arbitrary string of characters (maximum 255).
Use the same new “key” to generate the QR code, see: https://generalbytes.atlassian.net/l/cp/CKX0V3QX.
Enter the key in the relevant Terminal’s Details to enable the onsite self-test function.
Save the Terminal settings.
The BATM will now download the key, and it should be effective within minutes.
...
...
When onsite, trigger the test by attempting:
a transaction using a QR code created from the Key
...
Remotely:
...
Onsite (at the BATM).
Present the special diagnostic QR whenever a QR is scanned.
...
, or
entering an administration mode (pressing the “!” icon) and presenting the diagnostics QR.