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 Pass

Read an ID Pass API

Read an ID Pass returns where an ID Pass is in its flow, the verification result once it is complete, and the identity that was verified. With the cipher key, sensitive fields are decrypted and returned in plain text; without it, they are returned encrypted for local decryption.

  • A status from new through opened, in progress and complete to expired, failed or cancelled, and a verification status of passed or failed with a written reason
  • The verified identity and a per-document validation summary, with the full DVS results, captured images and step logs available on 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
  • Encryption, decryption and the validation summary
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

Getting the result of a verification your customer has completed

Once a customer has completed an ID Pass, or at any point before, Read an ID Pass returns its state and result. The verification status is the decision: passed when every document matched its issuer and the identity was consistent across documents, failed otherwise, with a description of why. The verified identity gives you the name and date of birth that were established, and the per-document summary shows what was checked.

Where the ID Pass is

The status runs new, opened when the customer passes the welcome page, in_progress once consent is given, then complete, expired, failed or cancelled. The timestamps of creation, consent and completion are returned with the consent text shown.

Whether the customer passed

The verification status is passed or failed, or null while in progress, with a human-readable description of the reason, for example that a document had biographic edits before verification.

Who was verified

The validation summary carries the verified identity and, per document, whether the biographic data and biometric face match were validated, the validated fields and any changes the customer made.

The detail, when you ask for it

Return documents adds each document's OCR data and validation result, including the DVS result code and request number under the DVS strategy. Return images adds the liveness probe image and document images. Return logs adds the step-by-step log for support.

How a check runs

One call reads the status, the result and the detail

Your system sends the ID Pass ID and reads the status ladder: new before the link is opened, opened once the customer is past the welcome page, in progress once consent is given, then complete, expired, failed or cancelled. Once the status is complete, the verification status reads passed or failed.

Personal information is encrypted with the cipher key from registration. Supply the key to have the response decrypted, or leave it out and decrypt locally. Global Data discards its copy once the ID Pass reaches a final status, so only your copy can unlock the record from then on.

Reading the result

What each answer means for the record in front of you

Read the status first, then the verification status. The description explains a failure in plain words.

Passed

The identity was verified

Every document matched its issuer, the face matched where liveness was on, and the name and date of birth were consistent across documents and with any requested identity. The verified identity is in the validation summary.

Failed

The identity was not verified

A document did not verify, the face did not match, or the identity was inconsistent. The verification description says which. Under the DVS strategy, return documents gives the DVS code and detail per document.

In progress

The customer has not finished

The status is new, opened or in_progress and the verification status is null. Use webhooks or read again later.

Expired or cancelled

No result will come

The link reached its validity period without completion, or the ID Pass was cancelled. Create a new ID Pass if the customer still needs to be verified.

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.

  • Pay as you go available
  • 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 Pass

Create an ID Pass generates the link this call reads. Cancel an ID Pass stops one that has not been completed.

Questions

Questions we get asked about Read an ID Pass

Do we need a developer to implement this?
Yes. Read an ID Pass is a REST endpoint that takes the ID Pass ID and returns a JSON result, and decrypting the sensitive fields locally needs the documented AES-256-CBC procedure if you do not send the cipher key, 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 ID Pass ID. Optionally the cipher key, so sensitive fields are decrypted before they are returned; and flags to return the documents, the images and the logs.
Should we send the cipher key?
If you send it, sensitive fields are decrypted and returned in plain text. If you do not, the encrypted data is returned for you to decrypt locally with the key, using AES-256-CBC as documented, with a MAC to validate integrity. The documentation says the choice should align with your compliance and security policies.
What comes back?
The ID, link, status, verification status and description, the original configuration, the timestamps and consent text, the validation summary with the verified identity, and, when requested, the documents, images and logs.
Why did a verification fail?
The verification description gives the reason in plain words. Under the DVS strategy, requesting the documents adds each document's DVS result code, Y, N or D, the DVS request number for official queries, and any mismatch detail such as a card number that did not match.
How long are images kept?
For the number of days set when the ID Pass was created, up to 365. After that the images are no longer returned.
How is the customer's data protected?
All stored data is encrypted at rest with the cipher key, which Global Data deletes once the ID Pass reaches a final status, so it cannot decrypt the data afterwards. Data in transit is encrypted and handling follows the Australian Privacy Principles.
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