Identity Verification

All 14 document types available through the government's Document Verification Service. Each check goes to the authority that issued the document and returns a match or no-match against their own record:

• Driver licences — all states and territories
• Australian passports and travel documents — DFAT
• Medicare cards and Centrelink concession cards — Services Australia
• Birth, marriage, death and change-of-name certificates — state Births, Deaths and Marriages registries
• Citizenship certificates, registration by descent, ImmiCards and visas — Home Affairs
• ASIC and MSIC aviation and maritime security cards

The AEC electoral roll is also available as a document-free check, for customers who can't produce an accepted document. Note that the DVS confirms whether the details match the issuer's record; it does not return a photograph or a copy of the record itself.

They answer two different questions, and most KYC programs use both.

Document verification confirms a credential is genuine: the details on the licence or passport are checked against the issuing authority's record through the DVS. It proves the document is real and current.

Data verification confirms the person is real: name, address, date of birth, phone and email are matched field by field against Australian data sources, with a separate result for each field.

The gap each one leaves is the reason to run both. A genuine document can be presented by someone who isn't its holder, and a real set of details won't always come with a document you can check. Together, the document proves the credential and the data check proves the details belong to a real, living person.

A separate, graded result for every field, not a single pass or fail:

• Full name — matched against the Australian data universe, graded exact, alias, partial or fuzzy
• Residential address — matched against GNAF and the data universe, graded exact, partial or fuzzy
• Date of birth — match or no match
• Phone — a live connectivity check plus a match against the universe
• Email — a deliverability check plus a match against the universe
• Deceased status — screened against the Australian Death Check, returned clear or flagged

Grading each field on its own is what lets you tell a customer who mistyped a unit number from one whose identity doesn't resolve at all. You set which combination of grades counts as a pass for each customer type.

Yes. A DVS check can only be run with the customer's consent, and you confirm that you hold it before the check will run.

Be precise about who holds what. The platform records your confirmation, the check details and the result. Obtaining and retaining the consent evidence itself remains your responsibility, and you may be audited and required to produce evidence of consent for any DVS check you have run.

That means your own onboarding flow needs to capture consent in a durable form and store it against the customer, instead of treating the tick box at check time as the record. The check trail shows a check was authorised; your records show what the customer agreed to.

Image retention is configurable, and in ID Pass the default is zero days: captured images are deleted the moment the verification completes. Where you do choose to retain them, sensitive fields are encrypted at rest under a key unique to that single verification.

The evidence record is kept separately and is not the same thing as the images. It records what was checked, against which source, the result, the timestamp and the operator. That is the part an auditor asks for, and it contains no document photographs.

The AML/CTF Act requires identity to be verified against reliable and independent sources. DVS checks go to the issuing authority's own record, and data verification runs against independent Australian data sources. Both satisfy that sourcing standard.

What the Act deliberately doesn't do is prescribe one fixed set of checks for everyone. Your AML/CTF program defines your customer types and risk-based procedures, and decides which checks apply to each. What we provide is verification against sources that qualify, plus a complete evidence trail recorded automatically for every check, so you can produce it when you're asked.

Through ID Pass. You send the customer a secure link and they complete the whole flow on their own phone, with no app to install. They photograph their ID and take a selfie; OCR extracts the document fields, the DVS check runs against the issuing authority, and face matching confirms the selfie belongs to the document.

The result returns to your workflow or webhook, and the customer's part typically takes under two minutes. If someone can't complete the selfie step, the same identity can still be verified through document and data checks, or run by your own team in IDFEX ID Check.

Document and data checks return in seconds, so a customer who verifies cleanly finishes sign-up in a single sitting instead of waiting on manual review.

A failure isn't a dead end. Because results come back per field, you can see precisely what didn't match (a superseded address, a transposed licence number) instead of an unexplained rejection. Common designs retry with a different document type, escalate to a selfie and liveness check, or route the case to a reviewer in IDFEX. Your policy decides which path applies, and the evidence is recorded either way.

Yes. Every check on this page is available as an API endpoint:

• DVS — 14 document endpoints, one per document type
• Global Data Check — per-field identity matching
• Person — identity and KYC lookups
• ID Pass — create and read a hosted verification flow
• Liveness — liveness and likeness checks

Request schemas and worked examples are in the API reference, and a sandbox is available so your team can build and test the integration before any of it touches a real customer.