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 4089Retrieve a Liveness Check Result returns the current status or the final result of a liveness check from its token. It can be polled safely until the check is complete, and returns whether the face was live, the confidence score, the threshold applied and, while they are held, the captured images.
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.
Accounts start in the sandbox. Production keys are issued once the account is approved.
A liveness check runs in the person's browser, so your system waits for it. Retrieve a Liveness Check Result is the call that collects the outcome. It reports whether the check is still pending or in progress, returns the result once it is complete, and says when the link expired without one.
The result carries a passed flag, the confidence score from the liveness provider, the threshold applied and the time the result was finalised.
On a failed or expired check the result carries an error code, failed or expired.
The probe image and any audit frames requested at creation are returned as data URIs with bounding box metadata while they are held, around 30 minutes. After that the same result is returned without images.
A 202 response with a message says whether the check is pending, not yet claimed, or in progress. The documentation recommends polling every 2 to 3 seconds with back-off.
Create a Liveness Check returns a token and a link straight away. Once the person has completed the capture, this call returns the result for that token. While the capture is pending or in progress it returns 202, so your system asks again.
The recommended polling interval is 2 to 3 seconds, with exponential backoff. Fetch the result under your own authenticated server context rather than trusting the token from a redirect on its own.
The status code says whether there is a result. The passed flag says what it is.
A 200 response with passed true. The confidence score reached the threshold. Store the result and, if needed, the images before they expire from the cache.
A 200 response with passed false and the error code failed. Ask for a new capture before declining.
A 202 response. The check is pending or the person is still capturing. Poll again in 2 to 3 seconds.
A 410 response. The validity period elapsed without completion. Create a new liveness check.
Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.
Create a Liveness Check issues the token this call takes.
New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.
Call 03 9948 4089, 9am–5pm AEST Monday to Friday