<aside> <img src="/icons/warning_yellow.svg" alt="/icons/warning_yellow.svg" width="40px" /> Only once the ACS integration deployment is completed will tokens be encoded to the QR codes generated by Proxyclick. Until then, please use the test QR below which has a token number encoded in the standard Proxyclick format.
</aside>
Below is an example ACS QR code from a Proxyclick invitation email:
This QR code decodes to:
67065804|M-BFVEJG234,V-JYDHR701,CO-JTR184|67065804
The token number that will be inserted into the access control system is shown in bold at the start and end of the decoded string. The content between the | characters can be variable in length, so be sure to test that your reader is compatible with the above once set up.
In order to be compatible with the QR codes that are issued, your QR code reader will need to be able to read only the first or last 8 digits of the QR code and pass it through to the controller it is connected to. You can enter a test user into the ACS with the above token number to test your reader setup is suitable.
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> The Wiegand format advice above will also apply to readers we have not tested.
</aside>