Customer 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 4089Listing audit entries returns the account's audit log as a paginated list: who did what, when, from which IP address and against which resource. Every API call is written to it. Use it to feed a SIEM or compliance system, to reconstruct an entity's history, or to surface activity in your own interface.
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.
Compliance teams need to answer who changed a record and when, and security teams need to feed logins and key usage into their monitoring. The audit log carries both, and the entity filter pulls everything that touched one customer, including their checks, events and notes.
A machine-readable action key such as created_watcheye_entity, a stable human-readable label, an optional sub-type such as the password or SAML variant of a login, and a description recorded at the time.
The agent, a user or an API key with name and UUID where available and null for system actions, the originating IP address, and the subject resource with its UUID where the record still exists.
Filter by action, action type, user, API key, entity, and created between two times. Newest first by default. The list omits each entry's properties object because it can run to many kilobytes; read it with Show an audit entry.
Show an audit entry reads one entry with its full properties. List users and Show the calling account name the actors that appear here.
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