Name: Requires given/primary and family names as shown on the licence.
Date of Birth: Always in YYYY-MM-DD format.
ID Type: idType = DRIVERS_LICENCE.
Country: AUS
State: region - one of: VIC/NSW/ACT/WA/SA/NT/QLD/TAS
Licence Number: idNumber = The licence number
Card Number: extraData
- kvpKey: "document_number",
- kvpValue: "nnnnnnn…"

Example JSON

{
  "identityDocs": [
            {
                "idType": "DRIVERS_LICENCE",
                "country": "AUS",
                "region": "NSW",
                "idNumber": "N49187",
                "extraData": [
                    {
                        "kvpKey": "document_number",
                        "kvpValue": "21631234"
                    }
                ]
            }
        ]
}

Formatting

The following images display the patterns for matching licence and card number formats for Australian jurisdictions.

Licence Number Formatting

Jurisdiction	Format	Length
ACT	Numeric	Up to 10
NT	Numeric	Up to 10
QLD	Numeric	Up to 9
NSW	Alphanumeric	6 to 8
SA	Alphanumeric	6
TAS	Alphanumeric	6 to 8
VIC	Numeric	Up to 10
WA	Numeric	7

Card Number Formatting

Jurisdiction	Format	Card Number Length
ACT	Alphanumeric	10
NT	Numeric	6 to 8
QLD	Alphanumeric	10
NSW	Numeric	10
SA	Alphanumeric	9
TAS	Alphanumeric	9
VIC	Alphanumeric	8
WA	Alphanumeric	8 to 10

📘
Victorian Drivers License Verification
As of 1st July 2023 Victorian card number verification is controlled by the DVS.
It's verification will depend on:

if the DL has been included in the list of leaked data (e.g. Optus data breach), then DVS will have the current card number, so it'll pass/fail depending on whether the card number is still valid or not.

If the DL is not part of the list of leaked data, the card number will not be verified, you can put any random number (the suggestion is to just use the same number as the licence), and it will still pass/fail, only by verifying the licence number

While technically it's not a mandatory field in our API, our recommendation is to always capture the data as you don't know if the DL had been previously compromised which is why in our portal it's mandatory.
If you're on direct DVS, If a card number is not verified in DVS, it will be logged in the records Audit Log, the content will be:
_We have a DriverLicense expanded response: Key: expanded_response.1.Issuer.CardNumber Message: Successful Match - Card Number has not been checked.__

DVS Expanded Response

Expanded responses are a DVS initiative to provide more information about an individual’s document verification outcome. An expanded response is a brief explanation provided by the document issuer, on why the individual’s information did not match the document being verified.

To view the expanded response using the Frankie API, you need to use the full check results flag AND you'll find it in the entityResult.nameCheck.checkResult[x].checkProcessResults object.

To view the expanded response from the Portal, go to the Audit Report of the particular entity. Refer to the screenshot below: