With Proxyclick Access Control integration we encode secure token numbers into the QR code sent to your visitors. This same secure token number is added to their profile in the access control system (ACS), which our integration also creates automatically.

To gain access, QR code reading hardware must be connected to the ACS. Examples of readers tested by Proxyclick are listed below, but any compatible QR code reader may be used*. Once QR readers are installed, visitors can scan the QR code and the reader then sends the token number back to the ACS. The number is then matched with the token number in their profile and access is granted through the door (or gate, barrier, turnstile, etc.).


Tested QR code readers

Proxyclick has tested QR code readers from two different manufacturers so far and can confirm them as compatible with the QR code format used in our invitation emails.


International Barcode (IBC)

The IBC Qscan range of readers listed below are suitable for use with Proxyclick QR codes. They offer various options to allow you to install the reader in different environments (inside turnstiles, for example) and also read a variety of different cards.


Qscan: http://www.internationalbarcode.com/qscan.htm

Qscan (Indoor Version): http://www.internationalbarcode.com/qscani.htm

Qscan Mini: http://www.internationalbarcode.com/qscanmini.htm

QscanT: http://www.internationalbarcode.com/qscant.htm

Nedap

We have tested and confirmed both the Mace MM and NVITE readers from Nedap. The NVITE is the replacement for the now discontinued Mace reader. The NVITE reader can read Proxyclick QR codes alongside various card types, Bluetooth, and NFC.

Nedap NVITE: https://www.nedapidentification.com/products/nvite/nvite/

Full setup steps and instructions are available when deploying your Proxyclick ACS integration.


*Other QR code readers may be compatible with the QR codes in our invitation email, but these should be tested and confirmed before deployment. Contact us if further advice is required.

Tip 💡 If the QR reader is to also support tokens/cards/Bluetooth this should be discussed with your systems integrator. The requirements for our QR codes will need to be considered alongside other technologies in use.

Did this answer your question?