Skip to content
New

Person Report API and New Zealand identity checks are now live.

See what's newarrow_forward
WatchEyeOnboarding & monitoring

Customer onboarding, screening and ongoing monitoring in one system, with real-time KYC and KYB alerts when a customer's risk changes.

Visit WatchEyearrow_forwardcheck_circleIncluded in the Global Data Portal
IDFEX ID CheckIdentity verification

One-to-one identity, document and data checks against the DVS and Australian data sources, run from the Portal or by API.

Visit IDFEX ID Checkarrow_forwardcheck_circleIncluded in the Global Data Portal
ID PassSelf-service verification

Customers verify their own identity and biometrics from a link on their phone. The result comes back to you, and they keep control of their data.

Visit ID Passarrow_forwardcheck_circleIncluded in the Global Data Portal
InsiightData quality

Verifies, corrects and enriches customer records so they stay accurate — one at a time or across your whole database.

Visit Insiightarrow_forwardcheck_circleIncluded in the Global Data Portal
Australian Death CheckDeceased data

The official national death data source. Match your records against it to find and remove deceased individuals.

Visit Australian Death Checkarrow_forwardcheck_circleIncluded in the Global Data Portal
QuesterMarketing lists

Build targeted, privacy-compliant Australian marketing lists with smart filters. Pay only for the records you download.

Visit Questerarrow_forwardcheck_circleIncluded in the Global Data Portal
verified_userVerify identities7 solutions

Confirm a person or business is who they claim to be: government IDs, biometrics, business registries and employment checks against authoritative Australian sources.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
policy_alertStay compliant6 solutions

Meet AUSTRAC obligations and understand customer risk: screening, risk assessment, fraud controls and investigation tools with evidence recorded for each check.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
databaseImprove your data3 solutions

Keep customer records accurate and put them to work: correct and enrich existing data, unify it into a single view, or build compliant marketing lists from opted-in records.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
monitoringWatchEye API14 categories

The WatchEye API gives programmatic access to everything in WatchEye: PEP and sanctions screening, identity checks, IDPass verifications, monitoring programs, events and reports.

View allarrow_forwardcheck_circleSandbox environment for integration testing
policyAML & screening6 use cases

Obligations under the AML/CTF Act, from screening at onboarding through to ongoing monitoring — with the evidence for each check recorded.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
how_to_regOnboarding & identity3 use cases

Verifying who a customer, employee or account holder is — at sign-up and during ongoing checks — against authoritative Australian sources.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
databaseData & enrichment4 use cases

Keeping customer records accurate, current and complete: validate contact detail, fill the gaps, locate people and remove deceased records.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
Global Data
Portalarrow_forward
Productsexpand_more
Solutionsexpand_more
Use casesexpand_more
Dataexpand_more
APIarrow_forwardIndustriesarrow_forwardResourcesarrow_forwardAboutarrow_forwardContactarrow_forward Request a Demo
Talk to the team

9am–5pm AEST, Monday to Friday.

call03 9948 4089
NZ Identity Verification

NZ Driver Licence Check API

NZ Driver Licence Check verifies a person's identity against the New Zealand NZTA driver licence database from the details on their licence. The response is a match status and a flag stating whether NZTA verified the licence details, with an explanatory message when the source supplies one.

  • Verified with the New Zealand Transport Agency licence database, not the Australian DVS
  • Licence number and version from the card, name and date of birth, with consent required on every request
For developers

After the technical detail?

For the technical detail, go to the API documentation. It holds the request and response schema, the integration guides and the error codes for this endpoint.

  • Request and response schema
  • Input rules and sandbox values
View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles
What the check gives you

Confirming a New Zealand driver licence is genuine and belongs to the person presenting it

Australian businesses regularly onboard New Zealand residents whose primary document is their licence. NZ Driver Licence Check sends the details on the licence to NZTA and reports whether they match the record it holds. The same check runs inside ID Pass when nz_licence is an allowed document type.

Whether the identity matched

The match status is Match when the supplied identity was fully verified and NoMatch when verification failed.

Whether NZTA verified the document

A document verified flag states whether NZTA reports the licence details as verified. It defaults to false when the source did not return a verdict.

Why it did not match

Where the source supplied an explanatory message, typically with a NoMatch, it is returned as additional information.

A reference for the record

A reporting reference identifies the transaction.

How a check runs

One call to the NZTA, answered in the same response

Your system sends the licence details with the customer's consent recorded. Global Data queries the New Zealand Transport Agency licence database and returns the match result in the same call. There is no DVS gateway involved; this is a New Zealand source.

The licence number is two upper-case letters and six digits with a check digit; it is converted to upper case before validation. The version is the three-digit number on the front of the licence. A single-name licence holder is sent with the last name only.

Reading the result

What each answer means for the record in front of you

The match status is the decision. The document verified flag says whether NZTA itself confirmed the licence.

Match

The identity was verified

The name, date of birth, licence number and version match the NZTA record. The document verified flag reports whether NZTA itself confirmed the licence details.

NoMatch

Verification failed

The details did not match, or NZTA could not verify the licence. Any explanatory message from the source is returned as additional information. Check the version number and the spelling before running it again.

What it costs

A monthly subscription, drawn down as you run checks

Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.

  • Volume-based pricing
  • No lock-in contract
How billing works
Subscribe monthly, spend it as credits
  • The monthly subscription arrives as credits on your account.
  • Each check draws down credits as it runs.
  • Checks beyond the included credits are billed per check.
  • Higher monthly volume moves you to a lower rate.
Talk to sales about volume
Related checks

Others in NZ Identity Verification

The Australian driver licence is verified through the DVS. ID Pass accepts a New Zealand licence as one of its document types.

Questions

Questions we get asked about NZ Driver Licence Check

Do we need a developer to implement this?
Yes. NZ Driver Licence Check is a REST endpoint that takes a JSON request and returns a JSON result, so a developer connects it to your onboarding system. A sandbox with a deterministic test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.
What does our system need to send?
The last name, date of birth, licence number, licence version and consent set to true, all required. The first name is optional so that single-name licence holders can be checked, and a middle name is optional.
What comes back?
A reporting reference, a match status of Match or NoMatch, a document verified flag, and, where the source returned one, an explanatory message.
Is consent required?
Yes. The consent field must be true.
What happens if NZTA is unavailable?
The check returns a 503 response. The documentation shows a sandbox value that simulates it.
Where does the data come from?
The New Zealand Transport Agency driver licence database.
Are the licence details we send stored by Global Data?
Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.
Getting started

The first step to access is a conversation

New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.

Call 03 9948 4089, 9am–5pm AEST Monday to Friday

Encrypted in transit and at rest
Handled under the Australian Privacy Principles
ISO 27001 Certified