Reading BDR Debug information
Located in the "Scan Information" tab and only visible to Scantek staff - These is no filter or nice spacing sorry
‼️ If anything shown here contradicts some other piece of information please ask dev team before responding to client
Example 1: A banned person
Debug] sexSource: How the gender of the scanned person was determined (DB means first name was in DB and we guessed the geneder, ID means gender is written on the ID doc)
[Debug] ocrSource: Options are ARH (Passport) qrScan (Keypass) or Scantek (One of our methods)
[Debug] idserverSource: Where the name and type of ID was determined (idws or ids)
[Debug] dobSource: Where the patrons date of birth was determined (idws or ids)
[Debug] hasIDWS: Did an IDWS response return in time
[Debug] idwsWaitTime: Number of ms it took for IDWS to return (-1 means no response came back in time)
[Debug] uniqueID: B9988-3DQD9POH
[Debug] unitID: B9988
[Debug] sane: Output from the ML debug script
[Debug] checkDetailsVersion: ML script version used to compare details
[Debug] isfake: 1 = fake ID, Missing = Not fake
[Debug] quality: Not used anymore - Blank
[Debug] mlDebug: Debug information for ML team about the check details script
[Debug] Offline: If the unit was not able to get customer information back from the unit backend in time
[Debug] Image_Match: Yes if any ban was shown to operator and match was pressed. No if any ban was shown to operator and No Match was pressed. Missing if no ban was shown.
[Debug] Ban_Type: Not really relevant to BDR
[Debug] Premise_Applicable: Not applicable to BDR - Will always be no - Ignore
[Debug] Name_Match: Yes if an exact name match was shown and operator pressed match. Else no
Example 2: Normal scan
Debug] sexSource: How the gender of the scanned person was determined (DB means name was in DB, ID means gender is written on the ID doc)
[Debug] ocrSource: Options are ARH (Passport) qrScan (Keypass) or Scantek (One of our methods)
[Debug] idserverSource: Where the name and type of ID was determined (idws or ids)
[Debug] dobSource: Where the patrons date of birth was determined (idws or ids)
[Debug] hasIDWS: Did an IDWS response return in time
[Debug] idwsWaitTime: Number of ms it took for IDWS to return (-1 means no response came back in time)
[Debug] uniqueID: B9988-3DQAW0XC
[Debug] unitID: B9988
[Debug] sane: Output from the ML debug script
[Debug] checkDetailsVersion: ML script version used to compare details
[Debug] quality: Not used anymore - Blank
[Debug] mlDebug: Debug information for ML team about the check details script
[Debug] Name_Match: Yes if an exact name match was shown and operator pressed match. Else no
New additions:
[Debug] transactionID: Transaction ID to search in platform portal
[Debug] checkCustomerOnline: Number of milli seconds check ban/tams re entry takes
[Debug] PastTAMS: Past purchases if any (If TAMS off will show enabled:false)
[Debug] ProcessingTime: The amount of elapsed milli seconds for scan processing ready for interface