Skip to main content
Didit Raises $2M and Joins Y Combinator (W26)
Didit
Back to blog
Blog · May 20, 2026

Australia DVS - Australia Driver Licence Verification API

Validate Australia driver's licence against the national driver-licensing authority in real time, billed only on conclusive results. Endpoint, parameters, response schema, pricing, and integration.

By DiditUpdated
australia-driver-licence-database-validation.png

Onboarding users in Australia means confirming they are who they claim to be. Verifies input data against the Document Verification Service (DVS). A document or a typed-in detail only proves the data exists — not that it is genuine or belongs to the person in front of you. Australia DVS - Australia Driver Licence Verification closes that gap by checking the data against the national driver-licensing authority. This guide explains what the check does, the exact technical details, and how to integrate it in minutes.

Key takeaways:

  • What it checks — Australia DVS - Australia Driver Licence Verification validates driver's licence against the national driver-licensing authority.
  • What you get back — a normalized match_type plus field-level results you can route straight into approve / review / reject logic.
  • Why it matters — Licence validation confirms the document is genuine and current — critical for mobility, delivery, and gig platforms.
  • How to use it — one POST to Didit's database-validation endpoint, or a no-code workflow module. $0.45 per conclusive query, results in seconds.

What Australia DVS - Australia Driver Licence Verification validates

Verifies input data against the Document Verification Service (DVS). Didit exposes it through a single endpoint so you can verify the submitted data against the national driver-licensing authority and receive a structured, normalized result — not a raw registry dump you have to parse yourself.

A conclusive response returns the matched source_data and a per-field validation block, so your risk engine gets a clear, machine-readable verdict.

Why it matters

Licence validation confirms the document is genuine and current — critical for mobility, delivery, and gig platforms.

For regulated businesses in Australia — fintechs, crypto platforms, lenders, marketplaces, and gaming operators — checking against an authoritative source produces a defensible, auditable record that identity was confirmed at the source, not merely captured from a form or a photo.

Technical details

Didit exposes this service through the unified database-validation endpoint. It is a single POST — no SDK required.

Endpoint

POST /v3/database-validation/

Request parameters

ParameterTypeRequiredDescription
issuing_statestringYesISO 3166-1 alpha-3 country code. Use AUS.
servicesstringYesService identifier. Use aus_australia_driver_licence.
first_namestringYesFirst name.
last_namestringYesLast name.
date_of_birthstringYesDate of birth.
driver_license_numberstringYesDriver license number.
driver_license_card_numberstringYesDriver license card number.
driver_license_statestringYesDriver license state.
middle_namestringNoMiddle name (optional cross-check).

Example request

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=AUS" \
  -F "services=aus_australia_driver_licence" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "driver_license_number=11111111" \
  -F "driver_license_card_number=1111111111" \
  -F "driver_license_state=Sample State"

Example response (conclusive match)

{
  "request_id": "req_01H...",
  "status": "Approved",
  "issuing_state": "AUS",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "aus_australia_driver_licence",
      "service_name": "DVS - Australia Driver Licence",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": true,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}

Performance and billing

  • Latency: typically a couple of seconds.
  • Cost: $0.45 per conclusive query. You are billed only on conclusive results — no charge for source downtime, missing fields, or pre-source rejections.
  • Reliability: runs on Didit's infrastructure with a 99.9% quarterly uptime target.
  • Consent: this service requires documented end-user consent. Capture and store it before you call the endpoint.

Use cases

  • Fintech & neobanks — confirm a real, verifiable account holder before opening a wallet or extending credit in Australia.
  • Crypto & Web3 — meet VASP onboarding requirements with authoritative-source identity proof.
  • Lending — reduce synthetic-identity and first-party fraud with source-verified data.
  • Marketplaces & gig platforms — verify users against authoritative data, not just a self-reported form.
  • iGaming — satisfy identity and eligibility checks for Australia players with an auditable trail.

How to integrate with Didit

You can run Australia DVS - Australia Driver Licence Verification two ways:

  1. No-code workflow. In the Didit Business Console, open the Workflow Builder, add the Database Validation module, select Australia → Australia DVS - Australia Driver Licence Verification, and activate it. Matching users are routed automatically — no engineering required.
  2. Direct API. Call the /v3/database-validation/ endpoint shown above with services=aus_australia_driver_licence. Read match_type and the per-field validation block to drive your approve / review / reject logic.

Every Didit account includes 500 free verifications per month, so you can test the full flow end-to-end before you pay for a single query.

Frequently asked questions

What does the Australia DVS - Australia Driver Licence Verification check confirm?

It validates the submitted data against the national driver-licensing authority and returns a normalized match result, so you learn whether the driver's licence exists at the authoritative source and which fields matched.

What happens if the source is temporarily unavailable?

You are not charged. Billing applies only to conclusive results — source downtime, missing fields, and pre-source rejections are free.

How fast is the check?

Database validation typically returns in a couple of seconds, so it fits inside a real-time onboarding flow.

Do I need an SDK?

No. The check is a single HTTPS POST to one endpoint. You can also wire it into a no-code workflow in the Business Console.

Ready to get started?

Validate your first Australia driver's licence today.

Infrastructure for identity and fraud.

One API for KYC, KYB, Transaction Monitoring, and Wallet Screening. Integrate in 5 minutes.

Ask an AI to summarise this page
DVS - Australia Driver Licence API | Didit