PLATFORM
Infrastructure for certainty.
Five capabilities, one system of record. Available as a dashboard, an API, and a white-label layer inside your own product.
The document, the person, and the match between them.
Identity verification asks three questions and answers each against source. Document provenance validation establishes that the document is genuine and current — issued, not imitated. Liveness detection establishes that a living person is present, not a photograph or a replay. Holder-match confirmation establishes that the document belongs to the person presenting it. Each answer is recorded together with the method that produced it. A check that cannot state how it was performed is not treated as performed.
- DOCUMENT CLASSES
- PAN · AADHAAR · PASSPORT · DRIVING LICENCE
- CHECKS
- Document provenance validation, liveness detection, holder-match confirmation.
- VERDICT
- CONFIRMED / FLAGGED / FAILED — with the evidence attached, always.
- RESPONSE
- Returned in-session; the verdict and the method that produced it arrive together.
- ENDPOINT
- POST /v1/verify/identity
Background is established, not assumed.
A background is not one lookup. FAEFACT reconciles a subject’s claims across independent source categories — court records for legal standing, employment signals for work history, financial standing through the Account Aggregator framework, and screening across applicable watchlists. Matches are named-party matches, reported with case type and status, never inferred from patterns. Nothing is consulted before consent is recorded, every source consulted is listed in the report, and where sources disagree, the report says so.
- SOURCE CATEGORIES
- COURT RECORDS · EMPLOYMENT · FINANCIAL (AA) · WATCHLISTS
- CONSENT MODEL
- Obtained before processing, referenced in every report, revocable by the subject. A verification without consent does not exist in the system.
- MATCHING
- Named-party matches with case type and status. Matches only — no inference.
- REFRESH
- Re-verifiable on request or on a schedule you set; each run writes its own audit entry.
- ENDPOINT
- POST /v1/verify/background
Every number shows its working.
Scoring on FAEFACT is deterministic: the same evidence produces the same score, every time. There is no opaque model and no hidden weighting. Each score lists every contributing factor with the source behind it, so the reader can weigh the evidence themselves. Thresholds are configurable per client — your risk appetite, stated explicitly. Overrides are supported, require annotation, and are written to the audit trail. If a score cannot show its working, it does not leave the system.
- MODEL
- Deterministic. Identical evidence produces an identical score.
- FACTOR TAXONOMY
- IDENTITY · EMPLOYMENT & INCOME · LEGAL STANDING · FINANCIAL SIGNALS · WATCHLISTS
- SCORE
- A single verdict figure, with every contributing factor listed beneath it.
- THRESHOLDS
- Configurable per client; every change is itself recorded.
- OVERRIDES
- Supported. Annotation required, and the override is written to the record.
What was checked, when, against what, with whose consent.
Every verification writes an entry to an immutable audit trail — timestamped, consent-referenced, permanent. Entries are appended, never edited, never quietly removed. Reports are export-ready and carry their own credentials: report ID, timestamp, consent reference, audit-trail entry. A report can therefore stand alone in a dispute, an audit, or a handover. Any FAEFACT report can be authenticated against our records by its ID. A forged report fails this check. A genuine one proves itself.
- RECORD
- Append-only. Entries are timestamped and never edited or deleted.
- REPORT CONTENTS
- REPORT ID · TIMESTAMP · CONSENT REFERENCE · AUDIT ENTRY
- FORMATS
- Export-ready sealed reports; the dashboard holds the live record.
- RETENTION
- Governed by the consent granted — stated in plain language before processing, honoured on revocation.
- VERIFICATION
- GET /v1/reports/{id}/verify — authenticates any report against our records by its ID.
A dashboard, an API, and a layer inside your product.
The platform is delivered in whichever form your operation already runs. A REST API with webhooks carries verification into your own systems. Integrations connect it to PMS, lease-management, and CRM tools. White-label mode puts your brand in front, our infrastructure underneath, and the audit trail shared. A sandbox with synthetic records lets your team build and test before a single live check runs. And the dashboard requires no integration at all.
- INTERFACE
- REST · WEBHOOKS — verdicts delivered in-session, events on completion.
- AUTH MODEL
- Key-based, scoped by environment and role.
- SANDBOX
- Available. Synthetic records only — no live data is used for testing.
- INTEGRATIONS
- PMS, lease-management, and CRM systems.
- WHITE-LABEL
- Your brand in front, our infrastructure underneath, the audit trail shared.
- SERVICE TERMS
- SLA-backed platform licensing; commitments are stated in the agreement.
Black-box systems ask for faith. FAEFACT shows its working.
Certainty is demonstrable.
Watch a verification travel from claim to seal: on the dashboard, over the API, or inside your own product.