BIOMatch.cloudBIOVAULT

Proving that the person on the other side of the transaction is really them

Every transaction carries the same risk: an identity claimed, not confirmed. BIOMatch.cloud answers the claim in milliseconds — with the person's consent, against the authorities that hold the truth, without your business ever holding confidential biometric data.

Step 01

A person transacts

Opening an account, collecting a payout, signing a contract, entering a site. They present an identity — and give consent for it to be verified.

▶
Step 02

Your application asks

Your web, mobile or branch application captures a face, voice or fingerprint and calls BIOMatch.cloud over a secure API. No change to how your business already works.

▶
Step 03

BIOMatch.cloud verifies

Liveness is checked, the biometric is matched, and the identity is confirmed against the sources that hold the record.

Held in
BIOVAULT

The secure store of biometric templates — mathematical representations, never images, and useless to anyone else. Nothing confidential sits with your business.

Checked against
DHA — Home AffairsSAFPSAfriGISCredit bureauxand more
▶
Step 04

You get a decision

Verified or declined, returned to your application in milliseconds — with a full audit trail of who was verified, when, and against what.

Consent comes first

A verification only happens when the person agrees to it. Consent is captured at the point of the transaction and recorded with the result.

Templates, not images

BIOVAULT stores a template of a biometric, not a photograph or a print. It cannot be reversed into an image or reused anywhere else.

Nothing confidential on site

Your business holds the result, not the biometric. BIOMatch.cloud is POPIA compliant by design.

iPulse Labs · BIOMatch.cloud & BIOVAULT · Verification as a service