Detect. · Orchestration

One integration.
Every provider.
The best one, every time.

No single provider is best at everything. Detekta routes every document to the one most likely to clear it — per document, per country — and recovers the good users others reject.

detekta · orchestration routing live
Proof of addressBR · 🇧🇷
✓ cleared · routed automaticallymanual review avoided: 90%+
The problem

The best provider changes every time.

Pass rates swing wildly by document type and country. A provider that nails Brazilian proof-of-address may fail an Australian passport. Pick one vendor and you lose users on everything they're weak at.

The winning cell moves across every column. Detekta reads this in real time and routes each check to the column's best — automatically.
The routing engine

How a check gets routed.

01

Ingest

A check comes in with its document type, country and risk context.

02

Score

Each provider is scored on live pass rate, cost, latency and coverage for that exact case.

03

Route

The check goes to the highest-scoring provider — no fixed waterfall, no guessing.

04

Verify

Result returns, normalized into one schema so downstream rails read it the same way.

05

Fallback

If it's a borderline reject, Detekta re-routes to the next-best provider to recover the user.

Scored on what matters

Routing you can tune.

Weight the engine toward acceptance, cost, or speed — Detekta routes to your priorities, not a vendor's default.

Pass rate

Live acceptance for this document type and country — the real number, updated continuously.

💰

Cost

Per-check price across providers, so you don't overpay a premium vendor for an easy case.

Latency

Response time — route time-sensitive onboarding to the fastest provider that still clears.

🌍

Coverage

Which provider actually supports that ID type in that jurisdiction at all.

Recovery

Stop losing good users to the wrong provider.

A rejection is often the provider's blind spot, not a bad customer. When a check fails on a borderline case, Detekta automatically re-routes to the next-best provider — clearing users a single-vendor stack would have lost at the door.

0%of borderline rejects recovered through automatic re-routing*

*Illustrative — replace with your measured recovery rate.

👤
K. Almeida · onboarding
Passport · AU 🇦🇺
🅰️
Provider Atlas
MRZ read failed · low confidence
rejected
↻ auto re-route to next-best
🅱️
Provider Onfis
NFC chip read · 96% confidence
recovered ✓
One integration — every provider, swappable without touching your stack
What it buys you

Better acceptance, less work, no lock-in.

−90%

Manual review

Fewer rejects bounced to a human means your team works exceptions, not volume.

+pp

Acceptance rate

Every check clears at the best provider's rate for that case — not your single vendor's average.

0

Vendor lock-in

Add, drop or swap providers from a dashboard. No re-integration, no engineering ticket.

Detect. Decide. Defend.

Bring your worst-performing document type.

We'll show you, live, which provider clears it best — and how many users you're losing today by not routing.