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 4089Launching an adhoc IDPass creates a remote identity verification for a person with no entity record. Instead of your system submitting document details, the individual opens a secure hosted link to photograph their documents, complete a liveness check and give consent. The call returns 202 with the link, and the result is collected from Show an IDPass once the individual has finished.
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 one-off applicant can be verified without an entity record. They photograph the documents you allow, pass a liveness check if you turn it on, and consent on a page that names your organisation and links your privacy policy. If no date of birth is supplied the documents are still fully DVS-verified and matched to the supplied name only.
The response carries the IDPass UUID, its configuration and delivery details, the hosted link, when it was sent by SMS, the path to poll and the ID check it belongs to. The outcome, summaries, log and images come from Show an IDPass once the individual has finished.
Each configured step accepts the document types you allow: Australian driver licence, passport, Medicare card, a foreign passport with an Australian visa, Centrelink card, birth certificate or New Zealand driver licence. Liveness, a standalone ID photo with its stated purpose, and a return URL are each optional.
The account needs the IDPass product and a DVS identity with a privacy policy URL. A launch missing either returns 403, insufficient credit returns 402, and a configuration error such as a step reusing an earlier step's document type returns 400.
An optional Idempotency-Key header returns the original response on a retry with the same key and body, so a dropped connection cannot create or charge the IDPass twice.
The launch returns 202 with the hosted link. The individual opens it, consents and submits their documents, and the status moves through new, opened and in progress. Your system polls Show an IDPass until the status is terminal, then reads the verification status.
Poll every few seconds at first, then every 30 to 60 seconds; the link validity of 1 to 14 days is the upper bound. Treat the hosted link as opaque and pass it on exactly as returned.
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.
Show an IDPass collects the result. List IDPasses finds them. Download an IDPass certificate as PDF and Download an IDPass image produce the evidence. Launch an IDPass against an entity runs the same flow for a person you monitor.
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