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 4089Show a monitor returns one monitor by its UUID with its operation, status, in-flight process status and any comment on it, schedule, configuration, when it last ran and whether it has run before. It is the endpoint to poll after Run a monitor on demand until the process status leaves pending and processing.
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.
Before a run, a system checks the configuration and schedule. During a run, it polls the process status. After a run, it reads when the monitor last ran and whether the run failed or paused. One read answers all three.
The check type with its display name and the per-operation configuration in force. The portal's monitor screens render the same fields.
Status is active or paused. Process status is pending, processing, failed or paused while a run is in flight or has just ended badly, and null when the monitor is idle, with a comment carrying any failure message.
The schedule with its display name, the last run time or null if it has never run, and whether it has processed at least one entity, which the new run type uses to know where to resume.
Run a monitor on demand returns 202 once the run is scheduled. Your system polls this endpoint until the process status is no longer pending or processing, then reads the new events.
A run across thousands of entities can take several minutes. Poll every 2 to 5 seconds for the first 30 seconds, then every 15 to 30 seconds.
Charges arise when screening runs against the entities in a program: each check type launched against an entity is charged at launch, and a monitor run is charged for each entity eligible for its operation. Rates are set for your account and communicated by your Global Data account manager, and statements with a per-call breakdown are in the WatchEye portal.
Run a monitor on demand starts the run this call reports on. Update a monitor changes what it reads. List monitors in a program finds it. List events shows what a run raised.
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