Skip to content
In force

Tranche 2 started 1 July — AML/CTF obligations now extend beyond financial services.

See who is coveredarrow_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
WatchEye · IDPass

Show an IDPass

Show an IDPass returns one remote identity verification by its UUID: its configuration, where the individual is in the hosted flow, the verification outcome once they have finished, what happened with each document, the biometric result, the activity log, metadata for any retained images and the path to the certificate. It is the endpoint to poll after a launch.

  • The status ladder from new to a terminal value, and the verification status of passed, review or failed
  • Per-document OCR and DVS results, the liveness result and the identity established across the documents
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
  • Status values and summary objects
Go to the API docs

New accounts begin with sandbox access.

ISO 27001 certified Handled under Australian privacy law Every API call written to the audit log
What the check gives you

Following a verification the individual is completing on their own device

A launch hands the verification to the person. This call tells you where they are, and once they are done, what was established. Your system polls it until the status is terminal, then reads the verification status and the summaries.

Where the individual is

The status is new until the link is opened, opened once the welcome page is passed, in progress once consent is given, then complete, expired, failed or cancelled. The completed flag is true at any terminal status, and consent given at records when the individual accepted the consent statement.

Whether the identity was verified

The verification status is passed, review or failed once the status is terminal, with a verification description giving the reason. Review means verified but flagged in the portal; treat it as not yet passed.

What each document showed

The document summary records, for each step, the document type, how the photo was read, how the document was verified with the DVS result code and any additional information, the biometric comparison where liveness was on, and the fields read and the fields submitted after any corrections.

The identity as a whole

The validation summary carries the liveness result, the ID photo result, the per-step results, the verified identity established across the documents, and whether the identity you supplied at launch differed from it. The activity log lists each step the individual attempted.

How a check runs

The launch hands over the link; this call carries the answer

After the launch returns 202, the individual completes the hosted flow in their own time. Repeat this call with the same UUID until the status is terminal, then read the verification status and the summaries.

Poll every few seconds at first, then every 30 to 60 seconds, with the link validity as the upper bound. The images array holds metadata only; the bytes come from the image endpoint, and the certificate from the PDF endpoint once the status is terminal.

Reading the result

What each answer means for the record in front of you

The status says where the individual is in the hosted flow. Once it reaches a terminal value, the verification status carries the outcome.

Passed

The identity was verified

The status is complete and the verification status is passed. The validation summary carries the verified identity established across the documents, the per-document results and, where liveness was on, the biometric comparison. The certificate PDF is available.

Review

Verified, but flagged for review

The identity was verified but has been flagged for review in the portal. Treat it as not yet passed until it has been looked at. Manual correction of the result is a portal-only function.

Failed

Not verified, or the link was not completed

The verification status is failed when the identity was not verified, and also when the IDPass expired or was cancelled. The verification description gives the reason, and the activity log shows each step the individual attempted.

What it costs

Charged at creation, by the number of document steps configured

Each IDPass launch is charged to your WatchEye account when it is created. The product billed depends on how many document verification steps are configured, from one to three. If the link is never used and expires, the launch charge is refunded. Rates are set for your account and communicated by your Global Data account manager.

  • Billed at creation
  • Refunded if the link expires unused
How billing works
Credits drawn down against your account balance
  • A launch is charged when the IDPass is created.
  • The product billed follows the number of document steps: one, two or three.
  • A link that lapses unused moves the IDPass to expired and the launch charge is refunded.
  • A 402 response means the account has reached its credit or call limit. Nothing is run and nothing is charged.
Talk to us about rates
Related checks

Others in WatchEye IDPass

Launch an IDPass against an entity and Launch an adhoc IDPass create the record this call reads. List IDPasses finds it. Download an IDPass certificate as PDF and Download an IDPass image produce the evidence.

Questions

Questions we get asked about reading an IDPass

Do we need a developer to implement this?
Yes. This is a REST read by UUID that your system polls, so a developer connects it to the workflow that waits for the individual to finish. A sandbox account is available for development at no charge. It is a separate account with its own API keys, it returns test data in the same response shapes as live, and the same base URL serves both environments.
What does our system need to send?
The IDPass UUID in the path, as returned by the launch, the list or the ID check that embeds it. Nothing else.
What comes back?
The IDPass with its UUID and source, status and completed flag, verification status and description, the configuration as applied, the requester name, privacy policy URL and OAC shown to the individual, the hosted link and delivery details, the document and validation summaries, the activity log, image metadata, the originating ID check and the certificate path.
How long does it take?
As long as the individual takes. Poll Show an IDPass every few seconds at first, then back off to every 30 to 60 seconds, with the link validity of 1 to 14 days as the upper bound. The status moves from new to opened when the link is opened, to in progress once consent is given, and then to complete, expired, failed or cancelled.
What does a review outcome mean?
The identity was verified but has been flagged for review in the portal. Treat it as not yet passed until it has been looked at. Correcting an IDPass result and cancelling one in flight are portal-only functions; they are not exposed through the API.
Is reading an IDPass billed?
No. The charge is made when the IDPass is launched. Reading it, listing it, and downloading the certificate and images are not billed.
What happens to the personal information in the response?
Personal information stored in WatchEye is covered by Global Data's security policies for the platform. Once your integration copies it into your own applications, databases, logs or backups, protecting it becomes your responsibility. Retrieve only the fields you need and treat any logs that capture API payloads as sensitive.
Getting started

The first step to access is a conversation

Sandbox accounts are provisioned by your Global Data account manager. API keys are created and managed in the WatchEye portal, and the same endpoints serve sandbox and live; the account behind the key decides which environment you are in.

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

ISO 27001 certified
Handled under Australian privacy law
Every API call written to the audit log