Driver's License verification
Quick start

OneView documentation

Driver's License verification

Review released KYC Driver's License verification results safely.

Availability

Driver's License appears under KYC only when the active license includes the Sub-module and the installed OneView version supports it. Running a verification additionally requires an active connection for a released Driver's License service.

Run a verification

  1. Open KYC → Driver's License at /app/kyc/drivers_license.
  2. Select New Verification.
  3. Choose an active connection.
  4. Optionally enter a safe operational purpose.
  5. Complete the service-specific fields displayed by OneView.
  6. Select Run verification and review the normalized result in the same drawer.

Use only provider-approved synthetic data during testing. Follow the fields OneView displays for the selected service; different released providers can require different inputs.

External API integration

This page does not publish a machine-request contract or vendor-service matrix for Driver's License verification. Do not derive an API payload or endpoint by copying the browser address or the fields currently displayed in the form. Use an API Service Account only when the documentation supplied for the selected released service defines its exact request fields and supported response. See Synchronous API for the common authentication, idempotency, outcome, and error behavior.

Review a stored result

verifications:read provides metadata-only history. A reviewer also needs verifications:results:read, shown as View verification results, to reveal result previews and open details.

The result-focused table shows the available normalized name, date of birth, gender, issue date, expiry date, and state of issue. Select a row to open all available safe normalized fields as labelled values. A placeholder means the selected provider service did not return a usable value.

The preview excludes the submitted license number, photos, contact details, street addresses, and raw provider fields. Results remain personal data even when a preview is brief. Do not copy them into logs, tickets, screenshots, or chat.

OneView records authorised preview and detail access per verification and records denied attempts without including the result or identity data in the activity event. See Verification history.