Get started

Zyphe Australia  /  Choosing a provider

Before you choose a provider, test it on your hardest buyer.

Every AML provider selling to developers now lists much the same things. Identity checks, liveness, ownership tracing, screening, workflows, reusable identity, Australian hosting. The lists overlap almost completely — and a list tells you nothing about how a provider handles the family trust buying three lots on launch weekend. The way to find out is to run the same cases through each provider and look at what comes back. This page is the test set.

Written for property developers who sell direct. General information, not legal advice. Last reviewed October 2026.

What every provider will tell you

Eight capabilities, on almost every brochure. Including ours.

Identity verificationdocuments, electronic sources
Liveness and biometricsis this a real person, present now
Ownership tracingcompanies, layers, beneficial owners
Sanctions and PEP screeningat onboarding and after
Configurable workflowsdifferent paths for different buyers
Reusable identityverify once, share with consent
Australian hostingdata held onshore
IntegrationsAPIs, CRM connections

None of these is unique to anyone. Overlap in the category doesn't mean equal accuracy, coverage, price or effort to implement — and it doesn't mean any of it has been set up for a property release. What separates providers is how each capability behaves on your cases, so that's what the tests below look at.

Before any demo

Start with what you're actually obliged to do.

AUSTRAC treats selling real estate in the course of a business, without an independent real estate agent, as a designated service — off-the-plan apartments, house-and-land packages and subdivision lots included, and in-house sales teams included. The buyer is your customer. AUSTRAC says the service typically starts when the sale agreement is entered into.

So start by mapping your own sales model: who sells, through which entity, when a deposit is taken, and when contracts are exchanged. A provider can't be tested against a process you haven't written down. Whether a particular project or entity is captured is a question for your lawyer, not your software vendor — including us.

The test set

Eight tests. The same cases for every provider.

Use real (de-identified) buyers from your last release, run the identical set through each provider, and agree the pass criteria before anyone sees results. Put one person in charge of compliance sign-off, one of privacy, and one of integration.

An Australian buyer, and an overseas one

Most of your release, and the part of it that's hardest to verify remotely.

Ask to see

  • Which Australian documents and electronic sources are checked, and how
  • What happens with a name mismatch, a failed liveness check, or a buyer who can't use a phone
  • Where an overseas buyer's data is processed and held — not just an Australian buyer's
  • For liveness: what was independently tested, to which level, and whether that applies to the provider or an underlying engine — and the test report

A company, and a family trust

The buyers a checklist tool hands back — and where most of the risk sits.

Ask to see

  • Where each register result came from
  • Who owns and who controls the buyer, and whether the person signing is authorised to
  • What the file shows when a branch of ownership can't be resolved
  • How trust roles are handled — trustee, appointor, beneficiaries — not just companies
  • That a default ownership threshold isn't being passed off as a finished determination
  • Whether the people found on a register are actually verified, or just screened by name

A false match, and a genuine high risk

Where automation helps most, and can do the most damage.

Ask to see

  • A case the automation was not allowed to clear, and why
  • A human overriding a decision, and the record that leaves
  • That decision history can't be edited after the fact
  • Which AI models are used, where they run, and what they're allowed to do
  • In writing: which decisions the automation can make on its own, and which always go to a person
  • What's recorded about each automated decision, so your privacy policy can explain it from 10 December 2026

Deposit through to settlement

Off-the-plan contracts stay open for years, and payment is where problems surface.

Ask to see

  • How payer and deposit information gets in — and who has to enter it
  • What happens when someone other than the buyer pays
  • A source-of-funds request on a third-party deposit: what the buyer is asked, what evidence comes back, and who assesses it
  • A nomination or assignment triggering a fresh review
  • What a "hold" actually stops in your own systems, and who can release it
  • What ships today, what needs configuring, and what's on a roadmap

Reusable identity, in the real order of events

"Verify once" earns its keep when it still works as the other parties turn up.

Ask to see

  • A lawyer or conveyancer who joins after the buyer verified — can they see it?
  • A buyer refusing to share, then withdrawing consent
  • A buyer whose details changed since they verified
  • How old a verification can be before it's no longer accepted
  • When another party sends you their checks: who did them, when, on what evidence — and whether you can actually use them

Sharing a verification is not the same as formally relying on another business's due diligence under the Act. Treat any reliance claim as a question for your lawyer.

Privacy, residency and records

Australian hosting is a start, not the whole answer.

Ask to see

  • The security certificate itself, and its scope: which entity, which systems, which certification body, and the expiry date
  • The data processing agreement and every subprocessor's location
  • Where AI processing, backups and support access happen
  • What happens to data on deletion, and at the end of the contract
  • That the records you're legally required to keep stay retrievable — even after a buyer withdraws consent or you change provider

What it really costs, across a release

A per-check price tells you little about a layered buyer or a three-year settlement.

Ask to see

  • Like-for-like quotes: verification, each extra registry lookup, screening, re-screening to settlement, implementation, support
  • Whether each beneficial owner is charged separately
  • On a monthly package: how many checks are included, and what a launch weekend costs once you're over
  • How much manual review your test cases created, and who did it
  • A live property deployment — not a demo environment

Everything else your compliance function needs

Checking buyers is one part of the job. Know what you'll still need alongside.

Ask to see

  • Whether the provider writes or maintains an AML/CTF program — and a sample of what it produces
  • Whether staff training is included, and how it's tailored to your roles
  • How suspicious matter reports get prepared, and who lodges them with AUSTRAC
  • What you'd still need to buy or build separately, and who joins the pieces up

Where developers get caught

Five assumptions worth testing.

"All in one" means everything's covered

A package that bundles a program, training and checks is convenient, and for a developer starting from scratch it may be the right call. Check the substance of each part: a generated program still has to fit your business, and a completed upload isn't the same as a sound decision.

"Hosted in Australia" settles privacy

It helps, but it doesn't settle who can access the data from overseas, where AI processing happens, or how overseas buyers are treated. Ask for the processing schedule, not the headline.

A higher test level means safer

A liveness test result describes a test, not guaranteed real-world performance. Check what was tested, by whom, on which devices, and whether the version you'd use is the version that was tested.

The software makes you compliant

No provider's software, hosting or consent screen discharges your obligations. AUSTRAC doesn't approve products. Accountability, records and exception handling stay with you, whoever you choose.

Privacy and record keeping pull the same way

They can pull against each other. An architecture built to minimise data still has to leave you able to produce the records the Act requires. Test both, together.

The same tests, applied to us

How we'd answer — including where we can't yet.

We'd rather you heard the limits from us than found them in a pilot.

Documented — in Zyphe's documentation or written confirmationTo be tested — ask us to show it on your casesGap — not there yet, or not confirmed

Liveness

Liveness detection with presentation attack controls: the underlying liveness engine is independently tested to ISO/IEC 30107-3 PAD Level 3, with a 0 per cent attack acceptance rate. That's the engine's result, not a certification of Zyphe. The test report is available under NDA.

Documented

Automation that can't clear what it shouldn't

Your organisation configures the decision workflow. In Suggestion mode, a person approves or sends back the case. In Autopilot mode, eligible checks can clear automatically under the configured rules. Results, reasons and reviewer decisions can be exported.

Configurable

Unresolved ownership

Branches that can't be resolved are marked unresolved on the file, not dropped.

Documented

Australian residency

For Australian clients, the verification environment runs in AWS Sydney: documents and biometrics are processed there, then encrypted, split into fragments and held on Australian nodes, and verification records and audit logs stay in the Australian region. Zyphe will write the commitment into the data processing agreement.

Documented

Overseas buyers' data

The Australian deployment covers Australian and overseas customers and associated parties. The residency and retained-record arrangements are defined in the data-processing terms.

Confirmed

Family trusts and SMSFs

Companies, trusts and SMSFs are supported, including trustees, appointors, beneficiaries and relevant controllers. Test a representative structure and inspect the evidence for each role.

Confirmed

A party who joins late

KYC Passport supports individual and entity results. Test late invitations, consent changes and access withdrawal on your actual partner workflow before launch.

Gap

Your CRM and systems

APIs, webhooks and integrations are documented. Whether your particular CRM or sales platform connects has to be shown on your setup.

To be tested

Security certification

Zyphe holds ISO/IEC 27001 certification and has completed a SOC 2 Type II report. Request the assurance documents and their scope for your deployment.

Confirmed

Source of funds on a third-party deposit

Source-of-funds questions and supporting-document collection are supported. Test a representative third-party deposit and inspect the resulting evidence and review.

Confirmed

People found on a register

Directors and owners identified from registers are screened. Whether each one is also taken through full identity verification depends on how the workflow is configured — ask us to show it on your case.

To be tested

What the automation decides alone

Your organisation configures the decision workflow. In Suggestion mode, a person approves or sends back the case. In Autopilot mode, eligible checks can clear automatically under the configured rules. Results, reasons and reviewer decisions can be exported.

Configurable

What it costs

KYC with Passport is A$8. Keystone is A$45, including director and beneficial-owner KYC, screening and the company extract. Layered Foreign Companies is A$45 per entity traced, with costs shown before the trace runs. Australian extracts purchased separately are A$22; additional overseas extracts are charged at cost. Ongoing screening is included, with its duration and schedule defined in the agreement. Groundwork is free to start; Enterprise pricing is tailored to volume. Prices are in AUD excluding any applicable GST. Billing events follow the agreement.

Confirmed

Program, training and lodgement

Zyphe provides platform training and prepares records for review. Your business remains responsible for its AML/CTF program, role-specific compliance training and lodgement of reports. The annual compliance report is prepared for your review and lodgement.

Not included

A live property deployment

Ask us to demonstrate the complete workflow you need, from initial verification through later reviews and settlement, with representative cases.

Gap

Start with one file

Bring us the buyer you'd least like to test.

Twenty minutes, one real structure from your last release, de-identified. You'll see the file that comes back — and you'll have the other seven tests ready for whoever else you're talking to.

Book a 20-minute call

This guide is general information about evaluating AML/CTF providers. It is not legal advice and does not tell you whether you are a reporting entity or what your obligations are. Descriptions of capabilities reflect publicly available information and Zyphe's written statements as at October 2026, and may change. Liability for compliance rests with the reporting entity.