MyProof driver's license verification uses document-derived data on device to support age, residency, document validity, and identity checks. The business receives the verification result without retaining the license payload by default.
Frequently asked questions
What is PDF417 driver's-license scanning?
Many North American driver's licenses and state IDs use a PDF417 barcode containing standardized document fields. MyProof reads supported barcode data on the user's device and evaluates only the facts required by the policy.
What data leaves the phone during a license check?
The partner API result omits the license image, barcode payload, birthdate, address, and document number. It returns the assigned policy result and opaque receipt references.
Which driver's licenses are supported?
MyProof is designed for supported PDF417 driver's licenses and state IDs. Exact coverage should be validated against the document versions and jurisdictions expected in the target workflow.
Can a correctly formatted barcode still be fraudulent?
Yes. Barcode parsing is one document signal, not an absolute proof of physical authenticity. A workflow can combine supported document checks, face matching, and a liveness risk signal.
Which facts can a driver's-license policy evaluate?
Depending on the supported document fields, a policy can evaluate age, document validity, state, ZIP eligibility, and identity match without returning the underlying personal data to the business.