ORCHESTRATION
Never go down because a provider did.
Every idto API runs on multiple provider partners. idto routes each request to the best provider for success rate and cost, and fails over automatically when one slows down or fails.
- Automatic routing
- Automatic failover
- Bring your own provider
- Standard responses
Orchestration
Every API, multiple providers. Never down.
to the best provider
The problem
One provider is one point of failure.
Downtime becomes drop-off
When a single provider slows down, customers can’t finish signing up.
Retry logic you have to build
Engineering teams end up writing fallbacks, retries and health checks themselves.
Different output for every provider
Switching providers means remapping fields and error codes.
No view of provider performance
Hard to see which provider succeeds, fails or costs more.
What you get
Routing, failover and visibility, built in.
Smart routing
Each request goes to the provider most likely to succeed at the best cost.
Automatic failover
If a provider fails, idto reroutes within the same call. No retry for your user.
Bring your own contracts
Use idto’s providers, your existing contracts, or a mix of both.
Standard response schema
One set of fields, whichever provider answered.
Clear error codes
Know exactly why a check failed and what to do next.
Provider analytics
Track success rates, retries and cost by provider in one dashboard.
How it works
One request in, one answer out
- 01
Send one request
Your app calls idto once, for a single check or a full journey.
- 02
idto picks the provider
Routing weighs success rate, latency and cost.
- 03
Failover if needed
A slow or failed provider is skipped automatically.
- 04
One standard response
Plus analytics on every provider decision.
Use cases
Built for high-impact journeys
- Bank account checks at scale
- KYC during peak traffic
- Payout and disbursal checks
- Multi-country verification
- Switching providers without downtime
- Cost optimisation across providers
Works with every verification API
Bring any check into the platform
Questions about Orchestration
Is orchestration live across all APIs?
Yes. Automated routing and failover are live across idto’s APIs.
How is this different from building it ourselves?
You skip building and maintaining routing, retries, health checks and response mapping for every provider.
Can we keep our existing providers?
Yes. Bring your own contracts for supported providers, use ours, or combine both.
Do we need to change our integration to switch providers?
No. Provider changes happen behind the API; your integration stays the same.
Stop depending on a single provider.
Build on idto and focus on your product, not verification overhead.