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 4089List adhoc ID checks returns the one-off identity checks on the calling account as a paginated list. Each record is a compact envelope with the type, the outcome and who launched it: a portal user or an API key. Filters narrow the list by id type, check type, outcome, creator and date.
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.
Adhoc ID checks accumulate from quick checks in the portal and from integrations verifying on demand. The list is how a reviewer or a reconciliation job finds them and sees who ran them.
Each record carries the id type and the underlying check type with display names, the outcome of pass, fail or pending, and a one-line outcome summary and data summary.
The created by block names the portal user or the API key. Filter by creator kind, by user UUID or by API key UUID to isolate one source of checks.
Filters cover id type, check type, outcome, creator, checked after and checked before, with a sort field and a leading minus for descending order.
An adhoc ID check is a synchronous verification with no program or entity. Every call that touches it is written to the audit log.
Pending appears only on a check satisfied by an IDPass that the individual has not yet completed.
Each ID check launch is charged to your WatchEye account at run time, after a successful call to the upstream verification source. The rate for each check type is set for your account and communicated by your Global Data account manager. Statements with a breakdown of API calls and their costs are available in the WatchEye portal.
Show an adhoc ID check reads one record in full. Launch an adhoc ID check creates them. List ID checks covers the checks that ran against entities in your programs.
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