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 4089Read an ID Pass returns where an ID Pass is in its flow, the verification result once it is complete, and the identity that was verified. With the cipher key, sensitive fields are decrypted and returned in plain text; without it, they are returned encrypted for local decryption.
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.
Once a customer has completed an ID Pass, or at any point before, Read an ID Pass returns its state and result. The verification status is the decision: passed when every document matched its issuer and the identity was consistent across documents, failed otherwise, with a description of why. The verified identity gives you the name and date of birth that were established, and the per-document summary shows what was checked.
The status runs new, opened when the customer passes the welcome page, in_progress once consent is given, then complete, expired, failed or cancelled. The timestamps of creation, consent and completion are returned with the consent text shown.
The verification status is passed or failed, or null while in progress, with a human-readable description of the reason, for example that a document had biographic edits before verification.
The validation summary carries the verified identity and, per document, whether the biographic data and biometric face match were validated, the validated fields and any changes the customer made.
Return documents adds each document's OCR data and validation result, including the DVS result code and request number under the DVS strategy. Return images adds the liveness probe image and document images. Return logs adds the step-by-step log for support.
Your system sends the ID Pass ID and reads the status ladder: new before the link is opened, opened once the customer is past the welcome page, in progress once consent is given, then complete, expired, failed or cancelled. Once the status is complete, the verification status reads passed or failed.
Personal information is encrypted with the cipher key from registration. Supply the key to have the response decrypted, or leave it out and decrypt locally. Global Data discards its copy once the ID Pass reaches a final status, so only your copy can unlock the record from then on.
Read the status first, then the verification status. The description explains a failure in plain words.
Every document matched its issuer, the face matched where liveness was on, and the name and date of birth were consistent across documents and with any requested identity. The verified identity is in the validation summary.
A document did not verify, the face did not match, or the identity was inconsistent. The verification description says which. Under the DVS strategy, return documents gives the DVS code and detail per document.
The status is new, opened or in_progress and the verification status is null. Use webhooks or read again later.
The link reached its validity period without completion, or the ID Pass was cancelled. Create a new ID Pass if the customer still needs to be verified.
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 an ID Pass generates the link this call reads. Cancel an ID Pass stops one that has not been completed.
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