Australia Consumer Verification API
Validate Australia address and residential data against authoritative residential and consumer data sources in real time, billed only on conclusive results. Endpoint, parameters, response schema, pricing, and integration.

Onboarding users in Australia means confirming they are who they claim to be. Verifies input data to a lead generation database. A document or a typed-in detail only proves the data exists — not that it is genuine or belongs to the person in front of you. Australia Consumer Verification closes that gap by checking the data against authoritative residential and consumer data sources. This guide explains what the check does, the exact technical details, and how to integrate it in minutes.
Key takeaways:
- What it checks — Australia Consumer Verification validates address and residential data against authoritative residential and consumer data sources.
- What you get back — a normalized
match_typeplus field-level results you can route straight into approve / review / reject logic. - Why it matters — Address verification against authoritative data confirms an applicant actually lives where they claim — a core anti-fraud and compliance signal.
- How to use it — one
POSTto Didit's database-validation endpoint, or a no-code workflow module. $0.06 per conclusive query, results in seconds.
What Australia Consumer Verification validates
Verifies input data to a lead generation database. Didit exposes it through a single endpoint so you can verify the submitted data against authoritative residential and consumer data sources and receive a structured, normalized result — not a raw registry dump you have to parse yourself.
A conclusive response returns the matched source_data and a per-field validation block, so your risk engine gets a clear, machine-readable verdict.
Why it matters
Address verification against authoritative data confirms an applicant actually lives where they claim — a core anti-fraud and compliance signal.
For regulated businesses in Australia — fintechs, crypto platforms, lenders, marketplaces, and gaming operators — checking against an authoritative source produces a defensible, auditable record that identity was confirmed at the source, not merely captured from a form or a photo.
Technical details
Didit exposes this service through the unified database-validation endpoint. It is a single POST — no SDK required.
Endpoint
POST /v3/database-validation/
Request parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
issuing_state | string | Yes | ISO 3166-1 alpha-3 country code. Use AUS. |
services | string | Yes | Service identifier. Use aus_consumer. |
first_name | string | Yes | First name. |
last_name | string | Yes | Last name. |
date_of_birth | string | Yes | Date of birth. |
address | string | No | Address (optional cross-check). |
phone | string | No | Phone (optional cross-check). |
email | string | No | Email (optional cross-check). |
Example request
curl -X POST "https://verification.didit.me/v3/database-validation/" \
-H "x-api-key: YOUR_API_KEY" \
-F "issuing_state=AUS" \
-F "services=aus_consumer" \
-F "first_name=John" \
-F "last_name=Doe" \
-F "date_of_birth=1990-01-01"
Example response (conclusive match)
{
"request_id": "req_01H...",
"status": "Approved",
"issuing_state": "AUS",
"match_type": "full_match",
"validations": [
{
"outcome_code": "MATCH",
"service_id": "aus_consumer",
"service_name": "Australia Consumer",
"source_data": {
"address": "123 Sample Street",
"address_match_score": "1.000",
"city": "Sample City",
"date_of_birth": "1990-01-01",
"first_name": "John",
"full_name": "John Doe",
"last_name": "Doe",
"name_match_score": "1.000",
"postal_code": "10001",
"state": "Sample State",
"street": "sample_value",
"verifications": {
"address": true,
"date_of_birth": true,
"full_name": true
}
},
"validation": {
"address": "full_match",
"date_of_birth": "full_match",
"full_name": "full_match"
}
}
]
}
Performance and billing
- Latency: typically a couple of seconds.
- Cost: $0.06 per conclusive query. You are billed only on conclusive results — no charge for source downtime, missing fields, or pre-source rejections.
- Reliability: runs on Didit's infrastructure with a 99.9% quarterly uptime target.
Use cases
- Fintech & neobanks — confirm a real, verifiable account holder before opening a wallet or extending credit in Australia.
- Crypto & Web3 — meet VASP onboarding requirements with authoritative-source identity proof.
- Lending — reduce synthetic-identity and first-party fraud with source-verified data.
- Marketplaces & gig platforms — verify users against authoritative data, not just a self-reported form.
- iGaming — satisfy identity and eligibility checks for Australia players with an auditable trail.
How to integrate with Didit
You can run Australia Consumer Verification two ways:
- No-code workflow. In the Didit Business Console, open the Workflow Builder, add the Database Validation module, select Australia → Australia Consumer Verification, and activate it. Matching users are routed automatically — no engineering required.
- Direct API. Call the
/v3/database-validation/endpoint shown above withservices=aus_consumer. Readmatch_typeand the per-fieldvalidationblock to drive your approve / review / reject logic.
Every Didit account includes 500 free verifications per month, so you can test the full flow end-to-end before you pay for a single query.
Frequently asked questions
What does the Australia Consumer Verification check confirm?
It validates the submitted data against authoritative residential and consumer data sources and returns a normalized match result, so you learn whether the address and residential data exists at the authoritative source and which fields matched.
What happens if the source is temporarily unavailable?
You are not charged. Billing applies only to conclusive results — source downtime, missing fields, and pre-source rejections are free.
How fast is the check?
Database validation typically returns in a couple of seconds, so it fits inside a real-time onboarding flow.
Do I need an SDK?
No. The check is a single HTTPS POST to one endpoint. You can also wire it into a no-code workflow in the Business Console.
Ready to get started?
Validate your first Australia address and residential data today.
- Read the API reference: Australia Consumer Verification
- See all database validations: Database Validation pricing & coverage
- Start building: Create a free Didit account — 500 verifications a month, free.