VerifyMesh
SANDBOX MODE: VerifyMesh currently runs against a simulated (mock) provider with fixture data only. No live identity verification is performed and no real documents or personal data are processed until a live provider contract is signed and configured. KYC/AML obligations remain with you, the regulated entity — VerifyMesh is workflow tooling, not a compliance provider of record.

Features

The orchestration layer, stated honestly: what it does and where the boundary is.

Multi-vendor routing engine

Every check is scored per verification on price, accuracy, latency, and country coverage. Custom routing rules on Scale: pin vendors per country, set price ceilings, accuracy floors.

Automatic failover

Per-vendor health is monitored continuously; when a vendor degrades, traffic reroutes automatically. Growth adds a failover SLA with a public status page.

Pay-per-success metering

The billing meter fires only on definitive vendor PASS verdicts. FAIL, INCONCLUSIVE, and ERROR are never billed; one session bills at most once — failover retries are idempotent.

Session API

POST /v1/sessions creates and runs a verification; GET fetches the redacted public view. Bearer-key auth; HMAC-signed vendor webhooks for async results.

PII redaction

Sessions store a SHA-256 hash of the subject reference — never raw identity data. All logs and timelines pass through redaction; document numbers, names, DOBs, and biometric fields become [REDACTED].

200+ country coverage

Coverage is the union of connected vendor coverage — routed per corridor to the vendor that actually performs there, not a marketing map.

Webhook retries + delivery dashboard

Result webhooks with retries and a delivery dashboard on Growth and up.

Fraud-signal sharing network (Scale)

Anonymized, aggregated signals across the mesh — on the Scale tier.

See pricingRead the docs