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 4089Archiving an entity takes it out of day-to-day workflows together with its checks, reports, events, notes and identification checks, while keeping every record fully readable through list and show endpoints. It is the documented alternative to deletion when compliance, audit or historical reporting still needs the record.
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 customer who has left, a supplier no longer used, an applicant who withdrew: none of these should keep being screened, and none of their history should disappear. Archiving is the state for that.
An archived entity is not included in monitor runs or default reports. The response carries the entity with its archived at timestamp set.
The entity and its checks, reports, events, notes and identification checks remain visible through list and show endpoints, and the entities list can include or exclude them with the archived parameter.
Archiving an entity that is already archived returns it in its current state without a new audit entry or a second cascade. An Idempotency-Key header is also accepted.
An entity is created active, archived to stop monitoring while keeping history, unarchived to resume, and soft-deleted only when it should leave the working views.
Prefer archiving over deletion where the record must stay accessible for compliance.
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.
Unarchive an entity reverses this call. Delete an entity hides the record instead. List entities in a program filters by archive state.
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