Atrium Connect Virtual ID Dynamic Barcode

Atrium Connect Virtual ID Dynamic Barcode

Purpose

The purpose of this document is to provide details regarding the setup and use of the dynamic barcode feature for Atrium Connect’s Virtual ID.

Basics

The barcode value is a randomly generated string that can be user defined.  When a valid transaction is processed using the predetermined ID type, within 5 minutes Atrium will replace the existing barcode with a new randomly generated value.

Setup

  • Go to the Atrium Connect connection page


  • Expand the API Settings to expose the Dynamic Barcode configuration

  • Choose the ID type, Length, and Type to define the custom Dynamic Barcode.

  • Before you switch on Assign ID type to all be sure your configuration is correct as this process will assign the ID type and the initial value to everyone in Atrium.

    • When Assign ID Type to All is toggled on anyone new added to Atrium will also be assigned the ID type and the initial value that is configured.

  • Select Production from the Environment dropdown menu

  • Enter the Production API URL https://apistudentlink.atriumcampus.com/mobile/person/virtual-id

  • Enter the Production API User Name and Password

    • You can get this from the Atrium Connect Dashboard under Security Keys. You need the SLAPI username and password

  • Click Save

  • Go to Cron Jobs under the Configuration menu and make sure the “Process Queued Actions” job is set to ON.



NOTE:  The URL, Username and Password will be provided by Atrium Engineering. This information can be found in Atrium Connect Dashboard under Security Keys.
NOTE: Before you test, please wait at least 5 min for the cron job to run and assign everyone the ID type and initial value.
NOTE:  To test to make sure the dynamic barcode is working correctly, process a charge or refund transaction using the virtual ID and within 5 minutes it should update.
NOTE:  Because the dynamic virtual ID barcode is being used in the Atrium mobile app, the barcode will update there as well.
NOTE: The dynamic barcode will update on wallet passes.  If this does not happen, there is a config file in Core that may need to be updated by engineering.