Tranche 2 started 1 July — AML/CTF obligations now extend beyond financial services.
See who is coveredarrow_forwardCustomer onboarding, screening and ongoing monitoring in one system, with real-time KYC and KYB alerts when a customer's risk changes.
One-to-one identity, document and data checks against the DVS and Australian data sources, run from the Portal or by API.
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.
Find, verify and identify consumers, with background and contact detail drawn from about 2 billion Australian records.
Verifies, corrects and enriches customer records so they stay accurate — one at a time or across your whole database.
The official national death data source. Match your records against it to find and remove deceased individuals.
Use cases
deceasedDeceased suppressionBuild targeted, privacy-compliant Australian marketing lists with smart filters. Pay only for the records you download.
Solutions
campaignB2C marketing listsUse cases
contact_phoneContact data validationConfirm a person or business is who they claim to be: government IDs, biometrics, business registries and employment checks against authoritative Australian sources.
Meet AUSTRAC obligations and understand customer risk: screening, risk assessment, fraud controls and investigation tools with evidence recorded for each check.
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.
Run the same checks from your own systems. See the developer docs for the full reference.
The WatchEye API gives programmatic access to everything in WatchEye: PEP and sanctions screening, identity checks, IDPass verifications, monitoring programs, events and reports.
Obligations under the AML/CTF Act, from screening at onboarding through to ongoing monitoring — with the evidence for each check recorded.
Verifying who a customer, employee or account holder is — at sign-up and during ongoing checks — against authoritative Australian sources.
Keeping customer records accurate, current and complete: validate contact detail, fill the gaps, locate people and remove deceased records.
9am–5pm AEST, Monday to Friday.
call03 9948 4089Show 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.
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.
New accounts begin with sandbox access.
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.
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.
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.
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 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.
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.
The status says where the individual is in the hosted flow. Once it reaches a terminal value, the verification status carries the outcome.
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.
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.
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.
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.
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.
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