Blogs

  • Data & Analytics

How FaceSign Was Rebuilt into an Enterprise-Ready Biometric E-Signature Platform

Published On: 12 October 2026.By .

How FaceSign Was Rebuilt into an Enterprise-Ready Biometric E-Signature Platform

Case Study: Product Engineering and UI/UX
FaceSign Platform
A verified person behind every signatureA government ID connects to a live face check on a phone, then to an identity-bound, digitally sealed agreement. Conceptual illustration. IDENTITY × SIGNATUREFaceSign · Platform concept GOVERNMENT ID Verify your identity Identity verified IDENTITY-BOUND SIGNATURE Government IDSealed agreement Identity verified before signingA live face is verified on a phone and matched to a government ID before the agreement is signed. Verify your identity Identity verified Government ID → verified person → signed agreement
E-Signature
Product Category
USA
Client Location
Face + Gov ID
Verification Method
Tamper-Evident
Document Sealing
45+ Screens
Admin Console
API + Webhooks
Developer Integration
01: The Challenge

A Typed Name Is Not Proof of Who Signed

Most electronic signatures prove that someone clicked a link sent to an email address, not who that person actually is. For organisations whose agreements carry real financial, legal or regulatory weight, that gap is a growing risk.
01
Anyone With Inbox Access Can Sign
Anyone with access to a signer's inbox, or a forwarded link, can sign in their name. A typed name or a drawn signature proves very little about the person behind it.
02
Little Evidence When a Signature Is Disputed
When a signature is disputed, the sender often has little more than an email address and a timestamp to show who signed, which is rarely enough for an auditor or a court.
03
Add-On Checks Confirm Access, Not Identity
Security questions or text-message codes confirm access to an account or a phone, not the identity of the person signing. They are a workaround, not a proof.
04
Remote Signing Removed the In-Person Check
Remote signing has become the norm, removing the in-person ID check that used to happen at a counter or in front of a notary, with nothing reliable put in its place.
05
Identity and Signing Sat in Separate Tools
Identity checks and e-signatures usually live in separate tools, so the proof of who someone is is not tied to the signature itself and has to be pieced together after a dispute.
06
Regulated Businesses Need More Than a Timestamp
Lenders, insurers and law firms must show auditors who signed, how that person was verified and that the document has not changed since. A click timestamp does not meet that bar.
02: The Core Idea

A Signature Should Carry Evidence of Who Made It

Design Principle

One rule shaped every part of the platform: if FaceSign claims something happened, the system enforces it and can prove it afterwards. That means the person is verified at the moment they sign, that verification is bound to the signature, and the signed document is sealed so the whole record can be checked later by anyone: a customer, an auditor or a court. A signature should carry evidence of who made it, not just a record that a link was clicked.

03: The Solution

Four Workflows on One Platform

Each workflow connects to the next. Identity is verified before the document is signed, the signed document is sealed before it is delivered, and the whole chain is available to anyone who needs to check it.

1

Proving Who Signed

An emailed link shows who received it, not who used it. FaceSign confirms the actual person in a few quick steps and keeps the proof tied to the signature, not just the session.

Every step is enforced server-side. If verification fails at any point, signing stops.
Verification Flow in Action
Illustrative View
Live face, enforced verification, verified signatureA live signer passes a liveness challenge and government ID match enforced on the server. A second face check is linked to the signature. Signing stops if verification fails. VERIFICATION BOUND TO THE ACT OF SIGNING Live personLiveness challenge Server-enforced Verified signatureFace checked again If any check fails, signing stops.
  1. 01Live face checkA liveness challenge rules out photos and replays.
  2. 02Government ID matchThe live face is matched to the ID photo.
  3. 03Server enforcementSigning stops if any verification check fails.
  4. 04Face check at signingA second check is tied to that specific signature.
The identity check is enforced at each step. Signing only proceeds when every check passes on the server.
The Face Scan Moment
Live Verification
The face scan momentA biometric face illustration with liveness, government ID matching and repeat verification at signing. Conceptual illustration. A live person.Liveness checked Government ID matchLive face matched to ID photo Checked at signingEvidence tied to the signature THE PERSON BEHIND THE SIGNATURE
  • 01A live personLiveness is checked before face matching.
  • 02Identity matchedThe live face is matched against a government ID.
  • 03Checked again at signingIdentity evidence is bound to the signature.
The signer's live face is matched against their government ID at the moment they sign, not just at the start of the session.
Proof points
Liveness challenge rules out replays Government ID matched on the server Second face check at the moment of signing Verification failure blocks the signature
2

Sending and Signing Agreements

Stronger identity checks only help if preparing and sending an agreement stays simple. Senders get a modern portal that handles one contract or hundreds at once, without training.

An agreement’s journey through FaceSign A sender prepares an agreement, two signers verify and sign in sequence, and the completed agreement returns as a signed copy. AGREEMENT JOURNEY One document. A clear path to completion. 01020304 SenderSigner 01Signer 02Complete Prepare agreementVerify & signVerify & signReceive signed copy IDENTITY CONNECTED TO EVERY SIGNATURE
  1. 01Prepare agreementThe sender prepares a document and places signing fields.
  2. 02Route to signersRecipients sign in sequence or in parallel.
  3. 03Verify and signEach signer completes the identity checks.
  4. 04Complete and deliverA sealed copy is delivered with its evidence.
Agreement workflowOne agreement moves from preparation through verified signing to completion.
Prepare
Template or new document, fields placed
→
Send
Single or bulk, parties in order or parallel
→
Sign
Signer verified, guided on any device
→
Track
Status, reminders, expiry, decline handling
Sender Portal
Dashboard, envelopes grouped by status, contacts and reusable templates, designed so any sender is productive without training
Multi-Party Signing
Sequential or parallel signing with approvers, and a full set of field types: signature, initials, date, name, text and checkbox
Bulk Send
High-volume agreements sent from a spreadsheet, each recipient getting their own personalised envelope
Automatic Reminders
Reminders, expiry dates and decline handling run automatically, with email notifications and delivery tracking
Teams and Usage
Multiple accounts and team management for organisations with several senders, with usage views per account
Encrypted Mail and File Transfer
Secure sharing of sensitive documents outside a signing flow, for organisations that need encrypted communication alongside agreements
Sender Portal
Platform Screenshot
FaceSign sender portal dashboard showing envelopes grouped by status with contacts and templates
Envelopes grouped by status, contacts and reusable templates, all in one portal designed so any sender is productive from day one.
3

Evidence That Holds Up

A signed agreement is only as strong as the evidence behind it. FaceSign records who signed, how they were verified and what happened at each step, and makes any later change to the document detectable.

Independent Verification
Signed documents can be verified with standard PDF tools, without relying on FaceSign's word, which matters when a third party needs to check
E-Signature Consent
Signers give electronic-signature consent before signing, in line with US e-signature law
Retention and Erasure
Retention and deletion rules support data-protection requests including GDPR erasure
Digitally Sealed Document
Illustrative View
A sealed document and its evidenceA signed document is connected to a digital seal, trusted timestamp, authenticity certificate and tamper-evident audit log. Conceptual illustration. Completed agreement IDENTITY + SIGNATURE + EVIDENCE Digital sealChanges become detectable Trusted timestampSigning time recorded Authenticity certificateSigner and verification evidence Tamper-evident audit logIntegrity checks on every record VERIFIABLE WITH STANDARD PDF TOOLS
  • 01Digital sealChanges after signing can be detected in standard PDF readers.
  • 02Trusted timestampA trusted authority records the signing time.
  • 03Certificate of authenticitySigner details and verification evidence travel with the record.
  • 04Tamper-evident audit logIntegrity checks detect altered records.
Every completed document carries a digital seal and a trusted timestamp. Any change after signing is detectable in a standard PDF reader.
Tamper-Evident Audit Log
Illustrative View
An audit trail connected to the signed documentA completed agreement connects to timestamped liveness, ID matching, face-at-signing and sealing events, with automatic integrity checks. No real customer data is shown. ONE AGREEMENT. A CONNECTED RECORD. Sealed agreement Signing event recordCONCEPT VIEW Liveness challenge passedGovernment ID matchedFace verified at signingDocument sealed Timestamped actionsAutomatic integrity checks
  1. 01Liveness challenge passedThe signer is confirmed as a live person.
  2. 02Government ID matchedThe live face is compared with the ID photo.
  3. 03Face verified at signingThe second face check is linked to the signature.
  4. 04Document sealedThe event record and document can be checked later.
Every action in a signing session is logged with a timestamp. Automatic integrity checks alert if any record has been altered.
Proof points
Digital seal detectable in standard PDF readers Trusted timestamp from an authority Tamper-evident audit log with integrity alerts Independent document verification GDPR erasure support
4

Running the Business and the Platform

Running an e-signature service means managing customers, plans, payments and support every day. FaceSign gives the operating team one console and enterprise-grade security underneath everything.

FaceSign enterprise platform operations A central FaceSign platform connects to tenant management, billing, administration and API integration modules. ENTERPRISE OPERATIONS A connected platform, built to scale. Tenant managementBilling AdministrationAPI integrations Organizations & accessPlans & subscriptions Roles & oversightConnected workflows FaceSign Enterprise platform CONNECTED CORE ONE PLATFORM · COORDINATED OPERATIONS
  • 01Tenant managementCustomer data is checked at application and database level.
  • 02Billing and plansSubscriptions, plans, invoices and add-ons.
  • 03AdministrationRoles and permissions govern console access.
  • 04API integrationsAccess keys and signed webhooks connect customer systems.
Platform architectureCustomer operations and developer integrations connect through one platform, with permissions and tenant checks enforced throughout.
Admin Console
Around 45 screens covering users, organisations, teams, envelopes, ID records, billing, subscriptions, invoices, plan requests, promotions, campaigns, referrals and system health
Role-Based Permissions
Permissions on every admin screen and action, with two-step sign-in for every admin user and clear limits on what support staff can view
Billing and Plans
Plans, add-ons, invoices and promo codes, with card payments handled by the payment provider so card numbers never pass through FaceSign's servers
Tenant Isolation
Every request is checked against the customer it belongs to at both application and database level, so one customer can never see another's data
Secure Sign-In
Password plus a one-time code, with authenticator app support and Google or Microsoft sign-in, and every uploaded file scanned for viruses before it is accepted
Developer API
Access keys and signed webhooks so customers can connect FaceSign to their own systems, with a developer portal and automated release pipeline
Admin Console
Platform Screenshot
FaceSign admin console showing users, envelopes, billing, plans and system health across around 45 screens
The operating team manages customers, plans, support and system health from one console, without engineering involvement.
04: What Was Built

Named Capabilities

Marketing website
Sender portal: dashboard, envelopes, templates, contacts, teams and usage
Public signing experience with face and government ID verification on any device
Sequential and parallel multi-party signing with approvers
Bulk send from spreadsheet
Digitally sealed and timestamped documents
Certificate of authenticity per completed document
Tamper-evident audit trail with integrity alerts
Face-mismatch alerts for senders
Encrypted mail and secure file transfer
Admin console with role-based permissions and two-step sign-in
Billing: plans, subscriptions, add-ons, invoices, promo codes and referrals
Developer portal and API with access keys and webhooks
Sign-in with one-time codes, authenticator apps and Google or Microsoft accounts
Data retention and GDPR erasure handling
Automated tests, release pipeline and monitoring
05: Business Impact

What the Platform Makes Possible

For Regulated Businesses
Organisations can show exactly who signed, how that person was verified and that the document has not changed, which helps settle disputes and satisfy auditors without assembling separate records from separate tools.
For Senders
Every signature is backed by identity evidence the server itself verified, which the sender can review and a third party can check. Signed documents can be verified independently with standard PDF tools, without relying on FaceSign's word.
For the Operating Team
Customers, plans, offers and support are managed from the admin console without engineering involvement. The documented, tested and monitored platform gives enterprise customers and acquirers something to review with confidence.
For Developers and Integrators
The API and webhooks let customers connect FaceSign to their own systems. New capabilities can be added quickly and safely as customer needs change, because the release pipeline and automated tests catch problems before customers do.
Client Voice

In the Client's Words

You've been so helpful and wonderful. You almost make me feel like you're my family. Let the sales people know if they need me and this is forever. They can contact me to help close a deal if they're communicating with someone who's not sure about using your company.

Steven R. Schwartz · FaceSign LLC
06: Technology and Engagement

Platform and Delivery

CategoryTechnologyRole
APITypeScript, Node.js, ExpressCore backend API for all platform workflows
FrontendNext.js and ReactMarketing website, sender portal and admin console
DatabaseMongoDBPrimary data store for envelopes, users and documents
JobsRedis-backed queuesBackground processing with automatic retries for reminders, scheduled jobs and notifications
HostingAWS, ECS containersContainerised deployment with automated build and release pipelines
StorageAmazon S3Document storage with encryption at rest
Face MatchingAmazon RekognitionLive face matched against the government ID photo
ID ReadingAmazon TextractID details read automatically, so signers do not type them in
SecretsSecure secret storageSecrets rotated and held outside application code; payment notifications verified before action
EngagementAuriga ITUI/UX redesign, product engineering, platform rewrite and security hardening. Team of two to five engineers under an Auriga delivery lead.
Why This Case Matters
Industry Context

For Any Business Where the Identity Behind a Signature Is the Point

Lenders, insurers, law firms and regulated services all face the same problem FaceSign was built to solve: a click on an emailed link is not a verified identity, and a disputed signature with no evidence behind it is a liability. Joining identity verification and signing into a single enforced step, sealing the result, and giving the operating team one console to run the business is what makes an e-signature product usable by an enterprise rather than just a startup. The same stack, TypeScript, Next.js, AWS, Rekognition and Textract, is well-suited to any product that needs identity-gated workflows.

What This Proves

Identity and Signing Can Be One Enforced Step, Not Two Separate Tools

Building a verifiable biometric e-signature platform means solving four things at once: enforcing identity checks so they cannot be skipped, binding the check to the specific signature rather than just the session, sealing the result so any later change is detectable, and making the whole thing fast enough that signers finish rather than abandon. FaceSign proves all four are achievable on a TypeScript and AWS stack, with a team of two to five engineers, and the result is a platform an enterprise buyer can review and an auditor can rely on.

More Related Work
ERP · Agribusiness Manufacturing
Five Plants on One Cloud ERP: Kapila Krishi Udyog Ltd
ERPNext · Frappe Framework · India
ERP · HRMS · Facility Management
Workforce Operations, Payroll and Finance on One Platform: A2Z Group
ERPNext · Frappe HR · India

Building a Product That Needs Identity-Gated Workflows?

Auriga IT designs and engineers platforms where identity verification, document workflows and enterprise security need to work as one system. Talk to our product engineering team about what that looks like for your product.

Talk to Our Engineering Team

Related content

Stay Close to What We’re Building

Get insights on product engineering, AI, and real-world technology decisions shaping modern businesses.

Get regular updates of our latest insights

Services

Products

Resources

© 2026 Auriga. All rights reserved.

16+ Years of Excellence • 1000+ Projects Delivered

Go to Top