Authflow, Inc.

Vol. I  ·  Issue 2026  ·  Identity, infrastructure

Verify a person
the way an editor
reads a manuscript.

Authflow, Inc. is a global identity verification platform. We compose document OCR, biometrics, liveness, AML and KYB into a single, well-written decision — so onboarding feels less like an inspection, and more like a polite handshake.

300ms

avg. decision

99.9%

platform sla

200+

document templates

plate i. verification, in three motions
A document, a face, and the quiet line that joins them.

§ 01  ·  the case

Onboarding is the
first impression
your product makes.

High-risk, high-growth teams — fintechs, exchanges, marketplaces, mobility, gaming — are asked to do something quietly difficult. They have to recognize a person they have never met, in a language they may not read, holding a document from a country they may never have seen, and decide, in seconds, whether to let them in.

Authflow was built for that moment. We compose nine separate checks — database, biometric, liveness, document, AML, KYB, address, age, and risk signal — into one clean verdict, with a paper trail your reviewers and regulators can actually read. It runs at the edge, returns in milliseconds, and asks the user for nothing more than a glance.

The point is not the technology. The point is the handshake.

§ 02  ·  the platform

Nine checks.
One verdict, well-argued.

Mix and match the checks that suit your risk profile. The orchestration, retries and decision logic are ours to worry about.

ID Database Checks

Authoritative lookups across the regions that matter, with deterministic and probabilistic matching, and graceful fallbacks when a source is slow.

chapter · 01

AML Screening

Sanctions, PEP tiers, watchlists, enforcement actions and adverse media — refreshed continuously, fuzzed across transliterations.

chapter · 02

Document OCR & Parsing

Two hundred document templates and counting. MRZ and PDF417. Latin and non-Latin scripts, read with patience.

chapter · 03

Face Match

1:1 selfie-to-portrait comparison with strong anti-spoofing. ISO-aligned quality gates. Edge-optimized capture.

chapter · 04

Face Liveness

Passive liveness — no challenge UX, works in low light, defends against replays and deepfakes.

chapter · 05

Document Authenticity

Texture, tamper and template inspection. Hologram and pattern analysis. MRZ checksum and geometric consistency.

chapter · 06

Address & Age Verification

Proof of address extraction, AVS and postal lookups, country-specific age rules — gated cleanly at the door.

chapter · 07

Phone, Email & IP Risk

Disposable, newly-seen and risky signals across contact and network metadata. Carrier, line type, breach exposure, VPN/Tor.

chapter · 08

KYB Business Verification

Company registries, directors, ultimate beneficial owners, and ongoing sanctions screening — graphed, not flattened.

chapter · 09

§ 03  ·  the motion

From capture
to decision,
in five quiet motions.

Most products treat verification as a single, opaque event. Authflow makes the steps legible — so when a decision is disputed, the trail reads like a paragraph, not a stack trace.

  1. 01

    stage 01

    Capture

    Web and mobile SDKs guide the moment — auto-cropping, glare correction, real-time prompts. The user barely notices.

  2. 02

    stage 02

    Extract

    Auto-classify the document. Read MRZ, PDF417, NFC chip data. Parse Latin and non-Latin scripts with equal patience.

  3. 03

    stage 03

    Validate

    Template, hologram and tamper checks. Geometric consistency. Liveness and 1:1 face match for the person behind the page.

  4. 04

    stage 04

    Screen

    Sanctions, PEP tiers, watchlists, adverse media. Continuous, fuzzy, transliterated, fair.

  5. 05

    stage 05

    Decide

    Rules, scores, case review. A human-readable trail so your reviewers — and regulators — never have to guess.

§ 04  ·  principles

Three working principles, kept on the desk.

i.

Identity is a story, not a checkbox.

An ID is a paragraph. A selfie is a sentence. A risk signal is a footnote. We treat them like a document — read carefully, cross-referenced, and signed off.

ii.

Drop-off is a design failure.

Every extra prompt is a user we lost. Authflow is built so the only thing the user does is hold up a card and look at the camera. The platform takes it from there.

iii.

Compliance must be legible.

Reviewers, auditors and regulators all have to read the same record. Our decision trails are written for human eyes first, machines second.

§ 05  ·  developers

Developer-first,
in the old-fashioned
sense of the word.

Typed SDKs. Idempotent endpoints. Webhooks for decisions and ongoing monitoring. An OpenAPI spec and a Postman collection you can hand to anyone. Sandbox by default; production when you're ready.

  • OpenAPI 3.1, generated typed clients
  • Webhooks for verification & monitoring
  • SDKs: Web, iOS, Android, React Native
  • Sandbox keys, replay tooling, fixtures

authflow.ts  ·  quickstart

v1
// Verify a person, end to end.
const decision = await authflow.verify({
  document: {
    type: "passport",
    image_front: file,
  },
  selfie: selfie,
  checks: [
    "id_database",
    "aml",
    "ocr",
    "face_match",
    "liveness",
  ],
});

// decision.status =>
//   "approved" | "review" | "rejected"
// decision.trail   => audit-grade reasoning
node · ts · zero deps ~ <300ms

data residency

US  ·  EU

certifications

SOC 2 · ISO 27001

privacy

GDPR ready

reliability

99.9% SLA

§ 06  ·  correspondence

Letters,
answered.

A short selection of questions we hear most, answered plainly.

01 What's required to get started?
+
Create an API key, embed the SDK, and choose your checks. Begin in sandbox; promote to production when you're confident.
02 How fast are decisions?
+
Most database checks complete in under 300ms. Document plus selfie flows resolve in under 30 seconds, including liveness.
03 Do you support ongoing AML monitoring?
+
Yes — enable continuous monitoring and receive webhook events whenever a watchlist, sanctions list or adverse media source changes.
04 Can I customize the experience?
+
Use the prebuilt components for a clean, accessible drop-in, or compose your own flow with the low-level SDKs. You own the canvas.
05 Where is data stored?
+
US and EU data residency are both first-class. Retention is configurable per integration. PII access is logged and auditable.

§ 07  ·  talk to us

Tell us about
your use case.

We'll tailor a demo and pricing to your volume, geography and risk profile. Most replies are written, not auto-generated.

by post · by wire

sales@authflow.me

For partnerships, security disclosures, or correspondence of any other kind — write to the same address. A real person will read it.

Compose a message