1. FAQ's Drivers Licence Card Number

When do I need to be ready? 

At this stage, the card number will be made a mandatory match field from early 2022. However, this is subject to change and we will share more information as it comes to light. 

When will the technical specifications and test data be available?

We are preparing the technical specifications and test data. For an early 2022 launch date, this information will be made available in early Q4 2021. 

Will the driver licence card number be available in all jurisdictions?

By early 2022, the DVS Manager anticipates that the driver licence card will be available for all jurisdictions except:

  • ACT driver licences issued before 1 January 2014
  • NT driver licences issued before 10 December 2019
  • WA driver licences issued before 3 February 2021
  • All Victorian driver licences

Where is the card number located? Is it the same for all jurisdictions?  

The location of the card number field differs between jurisdictions, and for NT driver licences, it can differ depending on the issuing date. For driver licence image samples refer to Attachment B in the DVS match specifications - driver licences.

Is there a user interface best practice we can use to implement the change? ?

Equifax recommends a user interface with enough flexibility to cater for jurisdictional differences. 

One approach is to have a drop down menu for individuals to select the issuing state, and based on the selection, to provide a customised set of data fields. For example, if Victoria is selected, then the card number field may either not be shown or will be optional (for future use). 

If NSW is selected, then the card number field may be made mandatory before a customer can proceed further with the application. 

Due to the jurisdictional nuances, providing a visual queue for customers will also help ensure that the correct information is provided. Common errors include:

  • Not capturing the name as it appears on the document
  • Providing the card number in the licence number field

New DVS response information

Today, additional information is only available for unsuccessful DVS verification due as a result of a data validation error. A data validation error is when the data provided does not meet the specified field requirements.

The expanded response field will help teams identify and address the root cause of failures faster. It will include failed verification reasons from the document issuer where the data provided did not match the information available at the document issuer. The additional 

information will be returned as part of the Document Verification Service (DVS) result codes for verification transactions across all DVS data sources. 

 

2. FAQs: DVS expanded response field

How will the additional response field information benefit me?

This information will support your analytics, such as diagnosing ‘fail’ transaction results and when optimising verification pass rates. The additional response information returned will provide a lower level of information for unsuccessful document verification transactions. This will be particularly useful if you are also implementing the driver licence card number change. 

How will I be affected?

Business

Technical

Consider how they may want to leverage the enhancement in your organisation.

Partner with technical teams to bring the field to life for business team members. 

The additional information will only be visible in the IDMatrix XML response code.

Equifax returns an XML response for all valid IDMatrix transactions. 

No changes will be made in the IDMatrix portal. 

The additional information will be provided as part of an existing IDMatrix XML response field <service-result-detail> for each DVS document verification. 

No changes are required to receive this information. 

 

 

 

When will I start receiving additional response field information?

At this stage, the additional response field information will be released together with the driver licence card number change. 

 

3. Commonwealth electoral roll changes

The Commonwealth electoral roll is moving to the Document Verification Service (DVS). The Australian Electoral Commission (AEC) anticipates the change to be complete  by Q4 2021. An exact date will be confirmed shortly. 

FAQs: Commonwealth electoral roll

How will the electoral roll moving to the DVS benefit me?

Faster updates and real time data! The Commonwealth electoral roll moving to DVS will mean updates to the Commonwealth electoral roll information will be available in real time, as opposed to updates each quarter . Equifax will no longer receive quarterly updates directly from the AEC, which capture changes made to the Commonwealth electoral roll in the previous 3 months. Instead, Commonwealth electoral roll information will instead be matched against the AEC data source via DVS. 

How will I be affected?

Equifax recommends you review your profile configuration to understand the potential impacts  to your business. Areas for considerations can include:

  • What is your verification rule?
  • What data sources do you currently use?
  • How do the data sources you use contribute to your verification rule?

The Commonwealth electoral roll move to the DVS will result in exact matching on name, DOB and some components of address. This may lead to a significant decrease in dataset match rates. 

IDMatrix utilises ‘fuzzy’ matching for the Commonwealth electoral roll. Unlike exact matching, which requires that the information provided exactly matches the data source, fuzzy matching balances the need to allow for natural variations in data within verification sources along with the need to verify an individual’s identity to a high degree of confidence.

When will the technical specifications and test data be available?

The DVS match specifications for the Commonwealth electoral roll are in a draft state. It will be made available in the DVS portal once it is finalized.

 

 

**EDIT THIS LINK TO GO TO A CONTACT PAGE??

Related Posts

There are changes coming to the DVS that may impact how you would use ID Matrix. Please refer to these FAQ's:

Read more

Cybersecurity readiness doesn't come easily. Reacting to a security breach is vastly different from being ready to act should a breach occur. Many organisations haven't previously focused on proactively protecting their critical information assets, but change is coming. The increased sophistication of today's threat actors heightens the chances that more organisations will find themselves the unlucky targets of cybercrime.

 

Read more