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 ASIC Extract collects an extract that was ordered with ASIC Extract, using the reference that call returned. The extract comes back as the full JSON record from ASIC or, on request, as a PDF document ready to file.
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.
This retrieval call is not billable. Production keys are issued once the account is approved.
An ASIC extract is generated in the background after it is ordered, normally within seconds but up to 10 minutes when the ASIC service is busy. Retrieve ASIC Extract is the call that collects it. Your system supplies the reference from the original order and receives either the finished extract or a status telling it to try again.
A 200 response carries the full extract in the exact structure of the ASIC dataset. A company extract carries the entity details, the ASIC extracts, directors and shareholders. A person extract carries the subject details and their related roles and shareholdings.
Adding pdf=true to the call returns the extract as a PDF document in the response body instead of JSON, for a file or for a person to read.
The call waits up to 30 seconds. If the extract is still being generated it returns a 202 response, and your system repeats the call with the same reference until the extract is returned.
Each retrieval carries its own API reference, separate from the reference of the original order, so both calls can be traced in the usage and audit logs.
ASIC Extract returns immediately with a reference. Retrieve ASIC Extract holds the connection for up to 30 seconds and answers with the extract, or with a 202 if it is not ready. Repeat the call with the same reference until the extract is returned.
Poll with an exponential back-off. An extract can only be retrieved for 24 hours after the original ASIC Extract request; after that the call returns 410 and a new order is needed.
The status code tells your system whether it has the extract, should wait, or needs to order again.
A 200 response carries the full ASIC extract as JSON, or as a PDF when pdf=true was sent. Store it against the matter and stop polling.
A 202 response means ASIC is still generating the extract. Repeat the call with the same reference, backing off between attempts. Generation can take up to 10 minutes in busy periods.
A 410 response means more than 24 hours have passed since the extract was ordered. Submit a new ASIC Extract request to obtain a current extract.
A 404 response means no extract was found for the reference supplied, or it belongs to another account or environment. Check the reference from the original order and the environment it was made in.
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.
ASIC Extract is the call that orders the extract this endpoint collects. ASIC Extract Company Search and ASIC Extract Person Search supply the identifiers the order needs.
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