Selfie-to-ID Face Matching for Fintech

Compare a live selfie with the photo on an ID using FACEIO ID Match. Get a face-match result, liveness result, and optional document fields. KYC, AML, document authentication, and onboarding decisions remain separate.

OPEN FACEIO Console

Connect to the FACEIO Console to create applications, manage APIs, and configure webhooks for enrollment, authentication, and Facial ID events.

Why Fintech Identity Verification Needs More Than Document Checks

Fintech onboarding commonly combines document checks, customer data, sanctions or risk screening, and a comparison between the applicant and the document portrait. For background on the broader obligations, see Know Your Customer and anti-money laundering.

Document and Face Checks Are Different

Document authentication evaluates the document itself. Face matching compares a selfie with the portrait extracted from that document. A complete onboarding policy may require both, plus additional checks selected by your organization.

Add a Selfie-to-Portrait Match

FACEIO ID Match captures a live selfie and a photo ID in a browser widget, checks liveness, and compares the two faces. PixLab DOCSCAN extracts the ID portrait and, optionally, document fields. A match indicates facial similarity, not document authenticity, ownership, or legal identity.

Why Passwords and OTPs Are Not Identity Proof

If someone can receive an OTP by email or phone, it only proves they control that channel. It does not prove who they are. Depending on passwords or OTPs alone leaves fintech products exposed to account takeover. See passwordless authentication strategy for migration options.

Where FACEIO Fits in a Fintech eKYC Stack

FACEIO ID Match supplies a 1:1 selfie-to-ID comparison, not a KYC service. Your organization can use the result within its own onboarding process, alongside separate identity, document, and compliance checks. FACEIO facial authentication is a separate capability for returning enrolled users.

Selfie-to-ID Portrait Matching

For a browser popup that captures a live selfie and an ID, use FACEIO ID Match. For backend-driven workflows that already have two face images, use the /faceverify endpoint. Your application is responsible for capture quality, consent, document checks, and the approval, retry, or review decision.

Return Access & Step-Up Authentication

After a user enrolls with consent, returning sessions can call faceio.authenticate(). Your backend compares the returned Facial ID with the one associated with the current account and applies its own access or step-up policy.

Liveness Checks and Presentation Risks

Live browser capture can be targeted with printed photos, screen replays, recorded video, or virtual-camera input. FACEIO liveness and anti-spoofing checks assess presentation indicators during supported browser flows, but no detection system can guarantee that every attempt will be identified.

Replay Attacks

A previously captured image or video may be presented to the camera instead of a live person completing the current session.

Screen-Based Presentation Attacks

A photograph or video may be displayed on another screen and presented to the capture device.

Virtual-Camera Input

Modified or generated video can be supplied through virtual-camera software instead of a physical camera feed.

Layer the Result With Your Security Controls

Use the liveness and face-match results with your own rate limits, retry rules, PIN Code policy, account recovery, backend authorization, and manual-review process. Review the security best practices and the face anti-spoofing guide before production use.

Result Handling and Customer Responsibilities

FACEIO returns technical face-match, liveness, and authentication results. Your organization decides what to record, how long to retain it, which thresholds or policies to apply, and how the result fits into its legal and regulatory process.

Face-Match Signals
The /faceverify endpoint returns dist, sim, and the same_person boolean. Your backend decides whether and how to record those values with its own session context.
Decision Policy You Control
Your backend interprets the documented response fields and applies the retry, review, or continuation policy defined for your product. FACEIO does not make the KYC, AML, account, or transaction decision.
Application-Controlled Event Records
Your application can trigger facial authentication before selected actions and record its own decision context. Use webhooks to receive supported FACEIO events in your backend workflow.
Transient Processing
ID Match processes selfie images, ID images, and extracted data in RAM, then deletes them immediately after the result is ready or the session fails. The processing pipeline retains no images, document data, or scan logs. Separately, facial authentication uses biometrics hashes managed by the selected recognition engine, as explained in the privacy best practices.
Consent Obligations Sit With You
The SDK does not initiate camera access until your application explicitly calls it, giving you full control to obtain and record explicit, informed consent before triggering a biometric capture.

Review the Developer Guides, Privacy Best Practices, and Trust Center. Your organization should obtain its own legal and regulatory advice for KYC, AML, consent, retention, and deployment obligations.

Getting FACEIO Into Your Onboarding Flow

For a browser capture flow, set up a FACEIO application, load fio.js, and call idmatch() to open ID Match. It compares a live selfie with the ID portrait and can return optional fields extracted by PixLab DOCSCAN. If your backend already has two face images, use the FACE-VERIFY REST API for image comparison. Neither option authenticates the document or performs KYC or AML checks.

ID Capture

Capture the ID under your consent and document policy.

Selfie Capture

Capture a live selfie in the browser.

Face Match

Use ID Match or send two face images to /faceverify.

Your Decision

Your backend applies its retry, review, or continuation policy.

Conclusion

FACEIO contributes a liveness result, a selfie-to-portrait face-match result, or a returning-user authentication result to your wider workflow. It does not authenticate documents, establish legal identity, perform sanctions screening, or decide KYC/AML outcomes. For adjacent account controls, see risk-triggered step-up patterns.

Add Face Matching to a Fintech Workflow

Use these implementation resources to connect live selfie capture, ID portrait matching, facial authentication, backend result handling, and customer-controlled review rules.

Getting Started Create an app, get its Public ID, and prepare your FACEIO integration. Integration Guide Add browser-based facial authentication or the ID Match popup to your web flow. Developer Center Review API validation, security, webhooks, and deployment patterns. FACEIO Console Create apps, manage settings, and test your FACEIO flow in staging.

Add Face Matching to Your Fintech Flow

Create a FACEIO app, then choose the ID Match browser widget or the FACE-VERIFY API according to the images and capture flow your application already controls.

Open FACEIO Console → Developer Guides

Selfie-to-portrait matching

Transient processing

Liveness checks in ID Match