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
ID Document

Extract ID Document Data and Face Image API

Extract ID Document Data and Face Image reads the fields from an image of a passport, an Australian driver licence or a Medicare card and returns them as data, with a cropped face portrait where a face is found. It extracts; it does not verify. Verification is a separate step through the DVS endpoints.

  • Passport, Australian driver licence with front and back, and Medicare card, read by OCR into named fields
  • A cropped face portrait with adjustable border and a face occluded flag, ready for a Likeness Check
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
  • Fields per document type and error handling
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

Reading a document so the customer does not have to type it

Keying document details by hand is slow and error-prone, and the errors then fail the verification. This endpoint takes a photo of the document and returns the fields as data, plus the portrait cropped from it. Those fields go on to a DVS check and the portrait to a Likeness Check. The documentation is plain that this is extraction, not verification.

The fields on a passport

First and last name, date of birth, expiry date, gender, passport number and country, with the portrait and a face occluded flag.

The fields on a driver licence

First, middle and last name, date of birth, address, expiry date, conditions, licence state and card number, from the front and back images, with the portrait and a face occluded flag.

The fields on a Medicare card

Card colour, card number, expiry, and the people on the card with their reference number and name lines.

The portrait

A base64 face image cropped from the document where a face is detected, with a border you can set from 0 to 50 per cent of the face box, default 15.

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 ID Document

The DVS document endpoints verify the extracted fields with the issuer. Likeness Check compares the extracted portrait with a selfie. ID Pass runs OCR, verification and face match in one hosted flow.

Questions

Questions we get asked about Extract ID Document Data and Face Image

Do we need a developer to implement this?
Yes. The endpoint is a REST call that takes base64 images in a JSON request and returns JSON fields, so a developer connects it to your capture flow. 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 document type, passport, licence or medicare, and the front image as a base64 JPEG of up to 16 MB. A licence also needs the back image. Only JPEG is accepted. Optionally the border percentage for the face crop.
Does this verify the document?
No. It performs OCR and data extraction only. To verify the document, send the extracted fields to the matching DVS endpoint. The documentation notes that fields may be more or fewer depending on document quality.
What comes back?
A result object whose fields depend on the document type. For a passport or a licence, the base64 face image where a face was detected and a face occluded flag are included; a Medicare card has neither. A document with no detectable face, or a processing problem, returns a 400 with a descriptive message.
How is the data handled?
Sensitive fields and raw images are masked in Global Data's internal audit logs. The API response returns the actual extracted values, so your own data handling policies apply to how you persist or redact them.
How many calls can we make?
The API allows 600 requests per minute by default, measured as a rolling average, and returns a 429 response above that rate. A higher limit can be requested through Global Data support with a description of the operational need.
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