You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have customers that scan Driver License PDF 417s to collect the raw data and send to our authentication service.
We then validate against known formats for the issuing states to ensure it matches.
This is beyond parsing based on AAMVA standard. This is best attempt to combat use of fraudulent IDs.
Our customer uses barcode_scan2 4.2.1.
It appears that barcode_scan2 4.2.1 is 'reacting' to the data and possibly altering the result causing the hash to fail.
Any ideas on how this can be rectified?
The text was updated successfully, but these errors were encountered:
We have customers that scan Driver License PDF 417s to collect the raw data and send to our authentication service.
We then validate against known formats for the issuing states to ensure it matches.
This is beyond parsing based on AAMVA standard. This is best attempt to combat use of fraudulent IDs.
Our customer uses barcode_scan2 4.2.1.
It appears that barcode_scan2 4.2.1 is 'reacting' to the data and possibly altering the result causing the hash to fail.
Any ideas on how this can be rectified?
The text was updated successfully, but these errors were encountered: