Payroll Check API

POST
/payroll_check
LIVE

Validates a person's identity against Australian payroll records. Each input field comes back as MATCHED or UNMATCHED (name, date of birth, middle name, address, email, phone, employer ABN). Gives you a useful employment-data signal for KYC, particularly for thin-file individuals who don't have a credit history yet.

Example Request

POST
request.json
key Auth: BearerAuth
{
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "address": {
    "street_address": "4/123 Fake Street",
    "suburb": "Fakeville",
    "state": "VIC",
    "postcode": "3987"
  },
  "email": "john@example.com",
  "phone": "0400123456",
  "employer_abn": "12345678901",
  "consent": true
}

Request Schema

consent
Required
boolean

Individual's consent to search payroll records.

first_name last_name birth_date
Required
mixed

Minimum required for a valid lookup.

middle_name
Optional
string

Optional Middle name.

address
Optional
object · (street_address, suburb, state, postcode)

Address components for cross-matching.

email phone employer_abn
Optional
string

Additional fields evaluated for match outcome.

Available Response Data

7 Data Points
01
data_object

Person

returned as MATCHED or UNMATCHED based on first_name + last_name + birth_date

02
person

Middle_name

returned as MATCHED or UNMATCHED.

03
location_on

Address

returned as MATCHED or UNMATCHED.

04
alternate_email

Email

returned as MATCHED or UNMATCHED.

05
alternate_email

Phone

returned as MATCHED or UNMATCHED.

06
data_object

Employer_abn

returned as MATCHED or UNMATCHED.

07
fingerprint

API reference UUID

lock Full API documentation provided after vetting from our compliance team.
By The Numbers

API Data Scale & Coverage tag

Unmatched data depth to power your compliance and verification workflows.

50M+
Phone & Email Records
40M+
Adverse Court Records
2BN+
Australian Universe Records
18M+
Real Estate Records
7M+
Deceased Records
980M+
Social Media & Employment Records
Practical Applications

Technical Use Cases tag

work

KYC for thin-file customers

Younger customers and recent migrants often lack a credit history but do have a payroll trail. A payroll match gives them a verifiable identity path without needing credit data.

account_balance

Income verification

Confirm a stated employer when underwriting lending, BNPL, rental applications or anything else where employment is part of the affordability picture.

policy

Multi-factor identity assurance

Combine a payroll check with DVS and credit data to reach high-assurance identity verification without single-point-of-failure on any one dataset.

Trust & Assurance

Compliance & Security tag

Enterprise-grade infrastructure audited against the standards your regulators require.

verified_user
ISO 27001 Certified
enhanced_encryption
AES-256 Encryption
public
Australian Data Sovereignty
Integration & Support

Common Questions tag

Everything you need to know about implementation details and compliance infrastructure.

gavel Compliance

Is explicit consent required?

add

consent: true is required. The endpoint won’t proceed without the individual’s consent to search payroll records.

rocket_launch Implementation

What's the minimum data for a match?

add

First name, last name, date of birth, and consent. Any additional fields you supply (middle name, address, email, phone, employer ABN) are evaluated independently and returned as MATCHED or UNMATCHED.

help_center General

Does this give me payroll figures or income amounts?

add

No. The response is binary match status per field only. It tells you whether the identity details match a payroll record. It doesn’t disclose any financial detail.

Try it Live

API Testing Sandbox tag

Test the Payroll Check API directly in your browser with live mock data and see instant results.

rocket_launch Request Sandbox Access

Access to live sandbox environments requires manual approval from our compliance team.