Verify a client's identity without re-keying a thing.
Electronic ID checks read an uploaded document and match it to your client, satisfying AML and customer due diligence as part of onboarding — with a compliance engine tracking obligations underneath.
AML onboarding is where practices carry real risk, and doing it by hand — chasing a licence, eyeballing it and re-typing the details — is tedious and easy to skip under pressure. Finye does it for you: a client uploads their identity document through a secure link, and Finye reads it, judges whether it looks genuine, and checks the printed name and date of birth against the person on file.
A KYC profile then tracks each client's verification status, so you can see at a glance who is onboarded and who still has checks outstanding — and sensitive identifiers like TFNs stay encrypted at rest and out of the audit log.
The challenge
ID verification is manual and slow
Chasing a licence, eyeballing it and re-typing the details is tedious and easy to skip under pressure.
Checks skipped under pressure
When onboarding is rushed, the identity check is the first thing to quietly fall off the list.
No clear view of who is verified
Without a status on each client, it is hard to tell who is fully onboarded and who still has checks outstanding.
Sensitive identifiers leak into logs
TFNs and ID data end up in emails and change histories where they should never be.
What you get
AI-read ID verification
The client uploads their ID through a token-only link and Finye reads it, assesses authenticity, and matches the name and date of birth to the client — auto-satisfying the identity check.
AML and KYC onboarding
A KYC profile tracks each client's verification status, so you can see at a glance who is onboarded and who still has checks outstanding.
No-login document upload
Clients submit their identity document through a secure, signed, token-scoped link — no account and no password to create.
Matched to the client
The details read from the document are matched against the person on file, so verification is tied to the right client record.
Third-party providers
Run verification through Finye's built-in AI reader, with support for external providers such as GreenID and Sumsub when you connect them.
TFN-safe by design
TFNs are encrypted at rest and kept out of the audit log, and identity documents are handled through signed, token-scoped links.
Outcomes
- Electronic ID checks completed without re-keying
- A clear verification status on every client
- AML and customer due diligence handled at onboarding
- Sensitive identifiers kept out of logs and email
FAQ
How does the electronic ID check work?
The client uploads their identity document through a secure link, and Finye reads it, assesses authenticity, and matches the name and date of birth against the client to satisfy the identity check.
Can I use a third-party verification provider?
Finye can run verification through its built-in AI reader, and the framework supports external providers such as GreenID and Sumsub when you connect them.
Is sensitive data like a TFN protected?
Yes. TFNs are encrypted at rest and deliberately excluded from the audit log, and identity documents are handled through signed, token-scoped links.