The same face opened 14 accounts in your base. Did you cross-check?
Kavuka Biometrics runs 1:1 Face Match (selfie × document or record) and 1:N search (a face against the entire base) with embedded anti-deepfake liveness — biometrics sized to today's threat, risk-calibrated and auditable.
- Seconds
- per match, with risk-based threshold
- 1:N
- against multi-accounting across the base
- Liveness
- embedded in every match
- Guided capture
- conversion preserved
Biometric engine in production: 1:1 and 1:N Face Match with embedded liveness, risk-calibrated and connected to the platform's identity graph — thousands of verifications per day, with audit trail.
Weak biometrics give the "verified" badge to exactly the people who should not have it.
The repeated face nobody cross-checks
The same face across 14 accounts, with 14 names and 14 tax IDs, devouring promotions and bonuses — because each record is reviewed in isolation, with no 1:N search against the base.
The deepfake approved with a verified badge
A naive match accepts a photo of a photo and a synthetic video injected into the camera feed. The deepfake passes the "biometrics-enabled" onboarding and stamps "verified" onto a synthetic identity.
The rejected selfie that killed conversion
Poor capture rejects the legitimate customer over quality and drops them mid-sign-up. The poorly resolved trade-off between a strict threshold (friction) and a loose one (fraud) costs revenue on both sides.
Cost Brazil saw an 830% surge in deepfakes in a single year and concentrates nearly half of Latin America's facial-manipulation cases, while deepfakes already account for roughly 40% of biometric fraud attempts. Biometrics without liveness is a lock with no door: it gives the confidence without the protection.
From the captured face to the fraud factory lit up, in one pipeline.
- 01
Capture
Guided capture that delivers the right photo on the first try — conversion protected instead of rejected over quality.
- 02
Prove
Embedded liveness: presentation detection (photo, screen, mask) and injection detection (synthetic video inserted into the camera). No match without proof of life.
- 03
Compare
1:1 Face Match against the document or the record, with a threshold calibrated to the operation's risk and an auditable similarity metric.
- 04
Cross-check
1:N search: the face against the whole base. The same face across N accounts lights up instantly, connected to the platform's identity graph.
The engine behind every match
Facial recognition is not a black box of isolated accuracy: it is calibrated matching, liveness and base search, connected to the identity backbone and the relationship graph of the platform.
1:1 Face Match
Selfie × document or record
1:N search
The face against the whole base
Liveness
Presentation and injection covered
Anti-deepfake defense
Photo-of-photo, screen, mask and synthetic video
Guided capture
The photo that works on the first try
Biometrics as a factor
MFA step-up on sensitive operations
Identity graph
Face + phone + device linking the ring
Risk-based threshold
Strict where it hurts, fluid where it converts
Who decides with Kavuka Biometrics
Digital Pipelines
The selfie × document match as the central module of the onboarding pipeline, with liveness and guided capture that preserve conversion.
Betting & Marketplaces
1:N against multi-accounting and bonus abuse — the hottest use case of the regulatory wave, before each campaign becomes a bonus giveaway to the same ring.
Operation Authentication
The face as an MFA factor in approving sensitive transactions — the biometric step-up where a password is not enough.
Gates & Yards
The face in physical access control, bridged with Vehicle OCR in yards — the identity of the person and the vehicle in the same perimeter.
Biometric data is sensitive data — and the pipeline is born aware of it
Facial biometrics became the country's identity infrastructure, and biometric data is sensitive data under data-protection law: collection without a legal basis and without governance is a liability. Kavuka Biometrics tackles this head-on, with documented governance and bias mitigation as practice — not a promise.
- Documented legal basis for processing sensitive data, with explicit purpose per use case.
- Minimization: biometric template instead of the raw image where possible, with configurable retention.
- Encryption in transit and at rest, and an audit trail of every match and every decision.
- Bias mitigation: models evaluated for balanced accuracy across demographic groups, with human review in uncertainty zones.
- Accuracy standards referenced to international technical benchmarks (NIST FRVT), the bar the enterprise buyer cites.
We ran 1:N on the base on day one and the same face showed up across dozens of accounts claiming bonuses. We dismantled the factory in an afternoon.
The anti-injection liveness blocked the deepfake our old match was approving as "verified". Trust in the badge came back.
Guided capture stopped rejecting good customers over photo quality. Onboarding conversion rose without loosening the threshold.
Run 1:N on your base: how many repeated faces will you find?
In 15 minutes you see the calibrated match, the anti-deepfake liveness and 1:N lighting up the repeated faces — on your scenario, with your volume.
- For businesses only. No purchase commitment.
- Data used solely for commercial contact.
- Enterprise leads answered within 1 business day.
What facial biometrics is and how to operate it in the age of deepfakes
Biometrics is the verification of a person by what they are — and, centrally, by facial recognition. It operates in two modes. 1:1 Face Match compares one face with another: the selfie against the document at onboarding, or the selfie against the enrolled face at authentication. The question is "is this the same person?", and the answer is a similarity score with a configurable threshold. The 1:N search compares one face against an entire base: the question becomes "who is this person?" or "has this face appeared in another account?". This 1:N search arms the defense against multi-accounting, serial fraud and bonus abuse — and against the face of a known fraud returning under a different name and tax ID.
Neither of these modes is worth anything without its inseparable companion: liveness, the proof of life. In an era when deepfakes account for roughly 40% of biometric fraud attempts, biometrics without liveness is a lock with no door. Modern defense covers two fronts: presentation — the photo of a photo, the screen, the mask presented to the camera — and injection — the synthetic video inserted directly into the camera feed, never passing through the lens. That is why, in Kavuka Biometrics, no match is accepted without embedded liveness: liveness is not an optional step, it is the condition of the match.
In Brazil, facial biometrics became the identity infrastructure — from bank onboarding to the social-security proof of life — and, precisely for that reason, it became the target. The country saw an 830% surge in deepfakes in a single year and concentrates nearly half of Latin America's facial-manipulation cases. Biometrics remains the best identity anchor there is; what changed is the bar for those who operate it. Isolated accuracy, measured in benchmarks like NIST FRVT, became a commodity: the differentiator is now the integrated system — the match that talks to the identity backbone (because the right face on a fabricated identity is still fraud), the 1:N tied to the relationship graph (the face + phone + device connecting the ring) and anti-injection liveness.
Operating biometrics well, finally, means operating it under data-protection law. Biometric data is sensitive data: collection without a legal basis and without governance is a legal and reputational liability, and the discriminatory false negative (the demographic bias that rejects one group more than another) is a real risk. Kavuka Biometrics is born with a documented legal basis, minimization (template instead of image where possible), configurable retention, encryption and an audit trail — the governance the DPO approves. And it treats bias as documented practice: models evaluated for balanced accuracy across groups, calibratable thresholds and human review in uncertainty zones. The result is biometrics sized to today's threat: the deepfake blocked, multi-accounting dismantled, conversion preserved and sensitive data governed.
What is the difference between 1:1 and 1:N?
1:1 compares one face with another (selfie × document, selfie × record): "is this the same person?". 1:N searches one face against the entire base: "does this face already exist here?" — the weapon against multi-accounting, serial fraud and the known face returning under another name.
Is biometrics alone enough to verify identity?
No — the right face on a fabricated identity is still fraud. That is why Kavuka Biometrics operates within the system: the match talks to the identity backbone, the relationship graph and liveness — the face, the person and the context verified together.
How does the defense against deepfakes work?
Through liveness embedded in every match: presentation detection (photo, screen, mask) and injection detection (the synthetic video inserted into the camera feed) — the two fronts of modern facial fraud. No match is accepted without proof of life.
What about data-protection law for biometric data?
Biometric data is sensitive data: the solution is born with a documented legal basis, minimization (template instead of image where possible), configurable retention, encryption and an audit trail — the governance the DPO approves.
Does the match have demographic bias?
We work with models evaluated for balanced accuracy across demographic groups, calibratable thresholds and human review in uncertainty zones — bias mitigation as documented practice, not a promise.
How does guided capture protect conversion?
Guided capture coaches the user to deliver the right photo on the first try — instead of rejecting the legitimate customer over quality mid-sign-up. Fewer rejected selfies means more completed onboarding, without loosening the security threshold.
How does Biometrics integrate with my current onboarding?
Via a documented REST API and capture SDKs for web and mobile, with the selfie × document match as a module of the onboarding pipeline. 1:N can also run in batch over the existing portfolio, to surface the repeated faces already in the base.
Let's talk
Your next high-impact decision starts with the right data.
Talk to a GUÉP specialist and find where applied intelligence creates the most value in your operation.