Question 1

What is Didit?

Accepted Answer

Didit is **infrastructure for identity and fraud** — the platform we wished existed when we were building products ourselves: **open, flexible, and developer-friendly**, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (**KYC**, *know your customer*), verifying businesses (**KYB**, *know your business*), screening crypto wallets (**KYT**, *know your transaction*), and monitoring transactions in real time — on a stack built to be:

- **Fast** — sub-2-second p99 on every session
- **Reliable** — in production with **1,500+ companies** across **220+ countries**
- **Secure** — SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: **14,000+ document types** in **48+ languages**, **1,000+ data sources**, and **200+ fraud signals** on every session.

Question 2

How fast is a face-pay auth at the POS?

Accepted Answer

Sub-2-second end-to-end inference per session — passive liveness + 1:1 face match against the bound template, returns approve/decline before the customer steps away from the terminal.

Question 3

Is biometric payment legal in the EU under PSD3?

Accepted Answer

Yes when consent and lawful basis (Article 9 GDPR) are explicit and the template is stored under your control. Didit ships the consent UX, the audit trail, and the PSD3 SCA-compliant binding (inherence factor via passive liveness + face match, possession via Device & IP Analysis). The stack is iBeta Level 1 PAD certified and validated by Spain's Tesoro / Banco de España / SEPBLAC as safer than verifying someone in person.

Question 4

How does a customer bind their face the first time?

Accepted Answer

One ID Verification + Passive Liveness + Face Match 1:1 session on the customer's phone or at the kiosk. We extract a template, encrypt it under a separate Customer Master Key, and return the template id to your system. From that moment, every subsequent terminal auth is just the 1:1 match against that template — no document, no app needed.

Question 5

Can the same face template be reused across terminals and brands?

Accepted Answer

Yes — the bound template is yours, scoped to your application. Across terminals on the same account, the customer auths with one face. Across separate brands, Reusable Identity lets the user opt in to share their verified template with a trusted partner. eIDAS 2.0 aligned, user-owned credential.

Question 6

What hardware does the gate camera need?

Accepted Answer

Any commercial-grade RGB camera at ≥720p with reasonable light. Our SDK runs inference cloud-side, so no specialised on-prem appliance is required. Existing POS terminals integrate via a REST webhook to call `/v3/session/` or `/v3/face-match/`.

Question 7

Compliance — what certifications cover biometric payments?

Accepted Answer

**PCI DSS 4.0** for card-data adjacency, **PSD3 + PSR** for strong customer authentication, **iBeta Level 1 PAD** for spoof resistance, **eIDAS 2.0** for cross-border identity wallet alignment, **GDPR + UK GDPR** for biometric data handling, **SOC 2 Type 1** and **ISO/IEC 27001:2022** for the platform stack. Full memo + every certificate at [/security-compliance](/security-compliance).

Question 8

Where does the biometric template live and how is it protected?

Accepted Answer

**Production data is processed and stored in the European Union by default** on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.

**Encryption everywhere.** AES-256 at rest, TLS 1.3 in transit, biometric data encrypted under a separate Customer Master Key. **Retention is yours to control** — between **30 days and 10 years per application**, and you can delete any individual session at any time from the dashboard or the API.

Question 9

What happens if a face match fails at the terminal?

Accepted Answer

Every session lands on one of seven clear statuses. `Approved` lets the user pay. `Declined` lets you fall back to card + PIN or step up to a fresh ID re-check (resubmittable without re-running the whole flow). `In Review` routes the case to the dashboard for compliance. A signed webhook fires on every status change so your POS state stays in sync.

Question 10

How much does biometric payment auth cost per transaction?

Accepted Answer

**$0.05 per face-pay auth** (passive liveness + 1:1 match) on top of a one-time **$0.33 KYC enrolment** per customer. 500 verifications free every month — most pilots stay inside the free tier. No minimums, no annual commitment, no per-terminal pricing.

Question 11

Can I run it side-by-side with my existing card-and-PIN flow?

Accepted Answer

Yes. Biometric payment is an additive factor — the customer who opts in walks up and pays with their face, the customer who doesn't keeps the card-and-PIN flow you already have. Same POS terminal, same dashboard, same billing.

Question 12

How fast can I integrate biometric payments?

Accepted Answer

**60 seconds** to a sandbox account at [business.didit.me](https://business.didit.me) — no credit card.

**5 minutes** to a working enrolment + auth via Claude Code, Cursor, or any coding agent through our MCP server.

**A weekend** to a production-ready POS integration with signed-webhook verification, retries, and a fallback flow to card-and-PIN when the user is declined. Step-by-step guide at [docs.didit.me/integration/integration-prompt](https://docs.didit.me/integration/integration-prompt).

translation_v1.solutions.biometricPayments.hero.payWithBlueYour

translation_v1.solutions.biometricPayments.skipTheCardBlue

From card-and-PIN to face-at-the-till in four steps.

Enrol the customer once

Wire the POS to Face Search 1:N

Customer walks up and pays

Audit + monitor

translation_v1.solutions.biometricPayments.sectionintro.033EnrolmentBlue

One $0.33 session binds a face to a payer.

The customer walks up. The till finds them.

Two SCA factors. One biometric prompt.

Amount + payee echo on every signed webhook.

Transaction Monitoring + Ongoing AML, optional.

Face-pay adds. Nothing breaks.

Open a new country in one click. We do the hard work.

Common questions

Biometric Authentication

Face Match 1:1

Passive Liveness

Device & IP Analysis

PSD3 SCA

Access control

Infrastructure for identity and fraud.