Skip to content
New

Person Report API and New Zealand identity checks are now live.

See what's newarrow_forward
WatchEyeOnboarding & monitoring

Customer onboarding, screening and ongoing monitoring in one system, with real-time KYC and KYB alerts when a customer's risk changes.

Visit WatchEyearrow_forwardcheck_circleIncluded in the Global Data Portal
IDFEX ID CheckIdentity verification

One-to-one identity, document and data checks against the DVS and Australian data sources, run from the Portal or by API.

Visit IDFEX ID Checkarrow_forwardcheck_circleIncluded in the Global Data Portal
ID PassSelf-service verification

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.

Visit ID Passarrow_forwardcheck_circleIncluded in the Global Data Portal
InsiightData quality

Verifies, corrects and enriches customer records so they stay accurate — one at a time or across your whole database.

Visit Insiightarrow_forwardcheck_circleIncluded in the Global Data Portal
Australian Death CheckDeceased data

The official national death data source. Match your records against it to find and remove deceased individuals.

Visit Australian Death Checkarrow_forwardcheck_circleIncluded in the Global Data Portal
QuesterMarketing lists

Build targeted, privacy-compliant Australian marketing lists with smart filters. Pay only for the records you download.

Visit Questerarrow_forwardcheck_circleIncluded in the Global Data Portal
verified_userVerify Identities7 solutions

Confirm a person or business is who they claim to be: government IDs, biometrics, business registries and employment checks against authoritative Australian sources.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
policy_alertScreen & Monitor7 solutions

Meet AUSTRAC obligations and understand customer risk: screening, risk assessment, fraud controls and investigation tools with evidence recorded for each check.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
databaseImprove your data3 solutions

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.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
monitoringWatchEye API14 categories

The WatchEye API gives programmatic access to everything in WatchEye: PEP and sanctions screening, identity checks, IDPass verifications, monitoring programs, events and reports.

View allarrow_forwardcheck_circleSandbox environment for integration testing
policyAML & screening5 use cases

Obligations under the AML/CTF Act, from screening at onboarding through to ongoing monitoring — with the evidence for each check recorded.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
how_to_regOnboarding & identity3 use cases

Verifying who a customer, employee or account holder is — at sign-up and during ongoing checks — against authoritative Australian sources.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
databaseData & enrichment4 use cases

Keeping customer records accurate, current and complete: validate contact detail, fill the gaps, locate people and remove deceased records.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
Global Data
Portalarrow_forward
Productsexpand_more
Solutionsexpand_more
Use casesexpand_more
Dataexpand_more
APIarrow_forwardIndustriesarrow_forwardResourcesarrow_forwardAboutarrow_forwardContactarrow_forward Request a Demo
Talk to the team

9am–5pm AEST, Monday to Friday.

call03 9948 4089
Liveness Check

Create a Liveness Check API

Create a Liveness Check generates a short-lived link. The person opens it in their browser and is guided through a face capture that is evaluated for liveness, that is, whether the face belongs to a live human rather than a photo, screen or mask. The result is retrieved with the token the call returns.

  • A hosted capture flow that runs in the browser, with a link valid for 5 to 30 minutes and a return URL that brings the person back to your site
  • A confidence score against a threshold you set, webhook notifications signed with HMAC SHA-256, and up to four audit frames kept for review
For developers

After the technical detail?

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.

  • Request and response schema
  • Webhook signature, return URL and audit images
View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles
What the check gives you

Confirming a real person is present, without building the capture yourself

A selfie proves nothing if it is a photo of a photo. Create a Liveness Check gives you a hosted capture flow: you create a link, the person completes it, and the evaluation reports whether the face was live. You are notified by webhook or by the person's return to your site, and you fetch the definitive result from the API with the token.

The link and its lifetime

The response carries the capture URL, a token to retrieve the result and a secret. The link is valid for 5 to 30 minutes, default 10, after which the check is marked expired if no result was produced.

The threshold you set

A threshold from 0 to 99 is stored with the check and echoed in the result; the system default is 70.

How you find out

Lifecycle events such as completion and expiry can be posted to your webhook URL with a Signature header, an HMAC SHA-256 digest of the payload using the secret. The person is also redirected to your return URL with an lc_token parameter.

Evidence for review

Up to four additional frame images beyond the probe image can be retained for around 30 minutes, with bounding box metadata, and returned by the result call.

How a check runs

A link the customer completes, then a result you collect

Create the link, send the person to it, and they complete the capture in their browser. The check moves from pending to in progress to complete, or expires, and the result is retrieved by token with a passed flag, the confidence and the threshold applied.

Never trust the lc_token from the redirect on its own. Fetch the result from the API under your authenticated server context, which confirms the token belongs to your account.

What it costs

A monthly subscription, drawn down as you run checks

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.

  • Volume-based pricing
  • No lock-in contract
How billing works
Subscribe monthly, spend it as credits
  • The monthly subscription arrives as credits on your account.
  • Each check draws down credits as it runs.
  • Checks beyond the included credits are billed per check.
  • Higher monthly volume moves you to a lower rate.
Talk to sales about volume
Related checks

Others in Liveness Check

Retrieve a Liveness Check Result returns the outcome for the token this call issues. Likeness Check compares the live face with a document photo. ID Pass runs liveness inside a full identity flow.

Questions

Questions we get asked about Create a Liveness Check

Do we need a developer to implement this?
Yes. Create a Liveness Check is a REST endpoint that returns a link and a token, and the result is fetched with a second call or announced by webhook, so a developer connects the flow to your site. The capture itself is hosted. A sandbox with a deterministic test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.
What does our system need to send?
A return URL, which is required. Optionally a webhook URL, the link validity in minutes from 5 to 30, a threshold from 0 to 99, and the number of audit images to retain from 0 to 4.
What comes back?
A token to reference the check, the user-facing capture URL, a secret used to verify webhook signatures, and the webhook URL echoed back where one was supplied.
How do we verify a webhook is genuine?
Each webhook POST carries a Signature header, an HMAC SHA-256 hex digest of the JSON body generated with the secret returned at creation. Webhooks originate from the IP addresses listed in the documentation, and are not retried indefinitely, so make your handling idempotent.
Can we trust the token on the redirect?
No. The documentation is explicit: treat the lc_token on the return URL as untrusted input and fetch the definitive result from the API under your authenticated server context. A 403 or 400 protects you if the token is not yours.
Are the images captured stored by Global Data?
Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.
Getting started

The first step to access is a conversation

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

Encrypted in transit and at rest
Handled under the Australian Privacy Principles
ISO 27001 Certified