vixverify.atlassian.net
Open in
urlscan Pro
185.166.143.36
Public Scan
Submitted URL: https://email.loqate.com/e3t/Ctc/DJ*113/clx-L04/VVFS9Y96BpnWW403wc21ZrVsFW2L--MX4LylLYN7Cq3wh5nCT_V3Zsc37CgKdxW48YZMx4Fkp...
Effective URL: https://vixverify.atlassian.net/wiki/spaces/GREEN/pages/2130247708/DVS+Driver+s+Licence+Card+Number+Change+-+FAQ+Sheet?utm_campa...
Submission: On June 21 via api from US — Scanned from DE
Effective URL: https://vixverify.atlassian.net/wiki/spaces/GREEN/pages/2130247708/DVS+Driver+s+Licence+Card+Number+Change+-+FAQ+Sheet?utm_campa...
Submission: On June 21 via api from US — Scanned from DE
Form analysis
1 forms found in the DOMName: livesearchForm — POST /wiki/dosearchsite.action
<form class="aui aui-dd-parent" name="livesearchForm" method="POST" action="/wiki/dosearchsite.action">
<fieldset class="search-macro-fields">
<div class="search-macro-query">
<input class="text" type="text" name="queryString" autocomplete="off" placeholder="Search the greenID Knowledge Base...">
</div>
<button type="submit" class="search-macro-button aui-button">
<span class="aui-icon aui-icon-small aui-iconfont-search">Search</span>
</button>
<input type="hidden" name="where" value="GREEN">
<input type="hidden" name="additional" value="page excerpt">
<input type="hidden" name="labels" value="">
<input type="hidden" name="contentType" value="page">
</fieldset>
</form>
Text Content
JUMP TO 1. Confluence navigation 2. Side navigation 3. Page This page was in the background for too long and may not have fully loaded. Try to refresh the page Spaces Apps Templates Create KNOWLEDGE BASE Overview Pages greenID Overview greenID API greenID Web greenID Mobile greenID Business • Encrypted Identifiers Address Handling • Notification of Verification Admin Panel Guide Testing • Demonstration Sites • Contacting Support greenID Additional Services A to Z Index • Quick Start Guide for Developers greenID Business Release Notes greenID Mobile Release Notes DVS Driver's Licence Card Number Change - FAQ Sheet • Tooltips Images for Card Number Hosted Web • AEC (Electoral Roll) Data Source Change - FAQ Sheet • Malicious Activity Prevention System (MAPS) - FAQ Archived pages 1. Knowledge Base restrictions.empty Jira links DVS DRIVER'S LICENCE CARD NUMBER CHANGE - FAQ SHEET * Created by Sharmeen Hussain Last updated: May 24, 2022 6 min read The DVS is rolling out a change to make the ‘card number’ a mandatory field to verify Australian Driver’s Licences. This page provides an overview of the changes coming and what customers need to do to prepare for this change. WHAT IS THE DRIVER’S LICENCE ‘CARD NUMBER’? The card number is a unique number attributed to a new version of a Driver’s Licence in Australia. WHY IS DVS INCLUDING GOING TO CHECK THIS FIELD? Card number is a unique identifier which is updated each time a driver’s licence is re-issued. By including card number in the matching criteria, you can validate that the document being presented is the most recently issued document. This change will help reduce identity crime in Australia. WILL THIS NUMBER REPLACE THE DRIVER’S LICENCE NUMBER? No. It is intended that both fields will be available to limit the changes required to existing business processes. WHEN WILL THE CARD NUMBER BECOME MANDATORY FOR MATCHING? The card number will become mandatory for NSW, ACT, SA, TAS, NT and WA on 1st September. VIC and QLD are expected to be made mandatory in 2023 - date is TBC. WHY IS THE CHANGE NOT MANDATORY FOR ALL STATES? Data readiness varies state to state with different technical challenges and timelines to enable driver licence card number. The intention is for all states to become mandatory. HOW DO I KNOW WHICH STATES ARE READY FOR CARD NUMBER MATCHING? GBG will manage this with the Department of Home Affairs. When a State reaches a critical mass of card number data and becomes a ‘mandatory state’, GBG will activate card number for driver licence matching for that state. States highlighted in green below are on GBG’s ‘supported states’ list i.e. states that have been confirmed by the DHA as being made mandatory on specified dates. The table below was updated as of May 18, 2022 . This will be kept up to date as we receive more information from DHA. Mandatory Date Jurisdiction 1st September 2022 NSW ACT SA TAS WA NT 2023 (Date TBC) VIC QLD I AM GREENID API CUSTOMER, WHAT DO I NEED TO DO BY WHEN? Date Activity Status 2nd Feb 2022 GBG will make a global change to configure DL card number on in customer test environment for all customers. When enabled this field will only work for ‘supported’ states (see table above) and will be optional. Done 3rd May 2022 GBG will make a global change to enable WA and TAS in customer test environments as an optional field. Following this change, card number will be available as an optional field for ACT, SA, NSW, TAS and WA in Test. Done 20th May 2022 GBG will make a global change to enable NT in customer test environments as an optional field. Following this change, card number will be available as an optional field for ACT, SA, NSW, TAS, NT and WA in Test. Done 6th July 2022 Card number becomes a mandatory input in Test for expected mandatory states (ACT, NSW, TAS, SA, NT and WA). As an API customer, you will need to ensure that a card number value is submitted for mandatory states for the DL check to work in Test. 9th August 2022 GBG will make a global change to configure DL number in its production environment for expected mandatory states (ACT, NSW, TAS, SA, NT and WA). At this stage, card number will be optional in production. As an API customer, you will be able to submit card number for mandatory states with your request and greenID will submit it to DVS for checking but it will not be mandatory. 1st September 2022 DHA Deadline (ACT, NSW, TAS, SA, NT and WA) - GBG will make the card number a mandatory field in production for all customers. API customers who are not sending us DL number for ACT, NSW, TAS, SA and WA by this time will experience no matches. HOW CAN I FIND OUT MORE ABOUT THE REQUIRED API CHANGE? * Driver’s Licence as a background source: https://vixverify.atlassian.net/wiki/spaces/GREEN/pages/60482657#BackgroundChecksV3-BackgroundDVSDriver%27sLicenceChecks * Driver’s Licence as an interactive source: https://vixverify.atlassian.net/wiki/spaces/GREEN/pages/8880634 I AM A GREENID WEB, MOBILE, IFRAME OR ADMIN PANEL CUSTOMER, WHAT DO I NEED TO DO BY WHEN? Date Activity Status 2nd Feb 2022 GBG will make a global change to configure DL card number on in customer test environment for all customers. When enabled this field will only work for ‘supported’ states (see table above) and will be optional. Done 3rd May 2022 GBG will make a global change to enable WA and Tasmania in customer test environments. Following this change, card number will be available as an optional field for ACT, SA, NSW, TAS and WA in Test on all screens controlled by greenID. Done 20th May 2022 GBG will make a global change to enable NT in customer test environments as an optional field. Following this change, card number will be available as an optional field for ACT, SA, NSW, TAS, NT and WA in Test. Done 6th July 2022 Card number becomes a mandatory input in Test for expected mandatory states (ACT, NSW, TAS, SA, NT and WA). Following this change, card number will be available as a mandatory field for ACT, SA, NSW, TAS, NT and WA in Test on all screens controlled by greenID. 9th August 2022 GBG will make a global change to configure DL number in it’s production environment for expected mandatory states (ACT, NSW, SA, TAS, NT and WA). At this stage, card number will be optional in production and end users will have the option to submit the number or not. 1st September 2022 DHA Deadline (ACT, NSW, TAS, SA, NT and WA) - GBG will make the card number a mandatory field in production for all customers for ACT, NSW, Tas, SA and WA. HOW DO I HAVE CARD NUMBER ENABLED ON MY GREENID ACCOUNT? The card number field should be enabled on your account in Test now. If you have any questions or require more information, please contact greenid.support@gbgplc.com. HOW DOES MATCH WORKING IN THE NON-MANDATORY PHASE? MATCHING FOR SUPPORTED STATES (IN GREENID) Submitted Data DVS Database Result Empty / Null DL Card Number Available Match Empty / Null DL Card Number Not Available Match DL Card Number DL Card Number Available Match DL Card Number DL Card Number Not Available 'N' - Not Matched or Fail Invalid Card Number Not Checked Check appears as 'failed' in the admin panel but no request is sent to DVS nor is the customer billed* MATCHING FOR UNSUPPORTED STATES (IN GREENID) Submitted Data greenID Empty / Null Ignores field as it is not on the supported states list. greenID will send other ‘required’ data to DVS for checking. DL Card number Ignores field as it is not on the supported states list. greenID will send other ‘required’ data to DVS for checking. HOW DOES MATCHING WORK IN THE MANDATORY PHASE? MATCHING SUPPORTED STATES (IN GREENID) Submitted Data DVS Database Result DL Card Number (valid and correct as on card) DL Card Number Available Match DL Card Number (valid but incorrect) DL Card Number Available 'N' - Not Matched or Fail Invalid Card Number Not Checked Check appears as 'failed' in the admin panel but no request is sent to DVS nor is the customer billed MATCHING FOR UNSUPPORTED STATES (IN GREENID) Submitted Data greenID Empty / Null Ignores field as it is not on the supported states list. greenID will send other ‘required’ data to DVS for checking. DL Card number Ignores field as it is not on the supported states list. greenID will send other ‘required’ data to DVS for checking. IS THE DRIVER’S LICENCE CARD NUMBER ENCRYPTED? Yes, the card number is treated in the same way as the licence number. WHAT WILL HAPPEN IF A CARD NUMBER IS SENT TO GREENID FOR A STATE THAT IS NOT ON THE SUPPORTED STATES LIST? greenID will ignore the card number for any state that is not on the supported states list and continue to send the request to DVS without the card number. I AM ON AN OLDER VERSION OF THE API, DO I NEED TO UPGRADE TO VERSION 3 TO MAKE THIS CHANGE? No, this change is compatible with older versions. WILL TOOLTIPS BE INCLUDED ON THE GREENID SCREENS (EG. WEB, ADMIN PANEL) FOR THIS FIELD? Tooltips are currently available for all states accept for Victoria and Tasmania. I’M AN API CUSTOMER AND I NEED TOOL TIPS IMAGES FOR MY OWN SCREENS? We’ve add sample images and links here: https://vixverify.atlassian.net/wiki/spaces/GREEN/pages/2159345665/Tooltips+Images ARE STUBS AVAILABLE FOR THIS FIELD? We have not introduced specific stubs data to support testing of this field, however, the stubs data available for driver’s licences on https://vixverify.atlassian.net/wiki/spaces/GREEN/pages/8880678 will continue to work. WHAT’S THE EXPECTED FORMAT FOR CARD NUMBER FOR EACH STATE AND TERRITORY? The card number should be entered as it appears on the driver’s licence. State Format ACT Length equal to 10 alphanumeric characters NSW Length equal to 10 numeric characters NT Length between 6 and 8 numeric characters QLD Length equal to 10 alphanumeric characters SA Length equal to 9 alphanumeric characters TAS Length equal to 9 alphanumeric characters VIC Length equal to 8 alphanumeric characters WA Between 8 and 10 alphanumeric characters I’M AN API CUSTOMER USING SETFIELDS AND WANT TO KNOW WHAT ERROR I WILL SEE IF I DON’T SEND CARD NUMBER FOR A MANDATORY STATE? Attached is a sample xml response for setFields when card number is missing in the input: WILL SA DIGITAL DL BE UPDATED TO INCLUDE CARD NUMBER? DHA has confirmed that there is work underway to add the card number to SA digital DL’s. It is expected to be complete ahead of the 1st September mandatory date. Search Home | greenID API | greenID Web | greenID Mobile | greenID Business | greenID Additional Services | Notification of Verification | Admin Panel Guide If you can't find what you need here, email us at greenid.support@gbgplc.com or log a ticket via our portal * 1 What is the Driver’s Licence ‘card number’? * 2 Why is DVS including going to check this field? * 3 Will this number replace the Driver’s Licence number? * 4 When will the card number become mandatory for matching? * 5 Why is the change not mandatory for all states? * 6 How do I know which States are ready for card number matching? * 7 I am greenID API customer, what do I need to do by when? * 8 How can I find out more about the required API change? * 9 I am a greenID Web, Mobile, iFrame or Admin Panel customer, what do I need to do by when? * 10 How do I have card number enabled on my greenID account? * 11 How does match working in the non-mandatory phase? * 11.1 Matching for Supported States (in greenID) * 11.2 Matching for Unsupported States (in greenID) * 12 How does matching work in the mandatory phase? * 12.1 Matching Supported States (in greenID) * 12.2 Matching for Unsupported States (in greenID) * 13 Is the driver’s licence card number encrypted? * 14 What will happen if a card number is sent to greenID for a state that is not on the supported states list? * 15 I am on an older version of the API, do I need to upgrade to version 3 to make this change? * 16 Will tooltips be included on the greenID screens (eg. Web, Admin Panel) for this field? * 17 I’m an API customer and I need tool tips images for my own screens? * 18 Are stubs available for this field? * 19 What’s the expected format for card number for each state and territory? * 20 I’m an API customer using setFields and want to know what error I will see if I don’t send card number for a mandatory state? * 21 Will SA digital DL be updated to include card number? No labels {"serverDuration": 36, "requestCorrelationId": "e551c82b2caffea0"}