Route
every
payment
Connect all of your acquirers and PSPs to one API. Alderone picks the provider for each payment, retries declines on another one and moves traffic away from providers that fail.
- ifCard issued in BrazilLatAm PSP
- ifAmexAcquirer US
- ifGBP and amount > £1,000Acquirer UK
- ifCard country in EEABest approval: EU or UK
- ifEverything elseAcquirer EU
Higher approval
Each payment goes to the provider most likely to approve it.
Lower cost
Route to cheaper providers wherever approval stays the same.
No single point of failure
If one provider fails, the next one takes the traffic.
No lock-in
Add, test and drop providers without touching your checkout.
Choose how each payment is routed
Combine strategies in one routing profile: rules first, then approval or cost, with failover underneath.
Rules are checked from top to bottom. The first one that matches picks the provider, and a default catches everything else.
Alderone tracks approval rates per provider for each card type, country and amount band, and sends the payment to the current leader.
Your fee schedules are loaded per provider. Among providers above your approval threshold, the cheapest one wins.
Keep volume commitments with each acquirer, test a new provider on 5% of traffic, or spread risk across merchant accounts.
When errors or latency cross a threshold, the provider is taken out of rotation and put back after it recovers.
A decline is not the last word
- Retry soft declines and technical errors on the next provider
- Retry rules per decline code, never on hard declines
- One payment ID and one webhook for the customer's order
Cards that belong to you, not to a PSP
- PCI DSS vault independent of any provider
- Network tokens kept up to date after card reissue
- Export tokens if you ever leave
Spread volume the way your contracts need
- Weights per currency, method or merchant account
- Volume caps per provider per day or month
- Ramp a new provider from 5% to 50%
Local methods from every provider, in one checkout
- Methods by country: cards, wallets and local methods from all connected providers
- Provider per method: Pix through one PSP, cards through another
- Same API: the integration doesn't change when a provider does
Hosted payment page
A page we host under your brand and domain. The fastest way to go live.
Embedded fields
Card fields inside your own checkout, with card data kept out of your systems.
Server-to-server API
Full control for teams that already have a PCI DSS scope.
Mobile SDKs
Native iOS and Android components for in-app payments.
Built to stay up when providers don't
Orchestration only helps if the layer itself is never the reason a payment fails.
Health monitoring
Approval, error rate and latency checked per provider every minute.
Idempotent retries
Every attempt has its own key, so a payment is never charged twice.
Changes without deploys
Edit routing in the dashboard, test it on past traffic, then publish.
Your credentials, encrypted
Provider API keys are stored encrypted and used only for your traffic.
3DS from any server
Run 3D Secure through your provider or a standalone 3DS server.
Audit trail
Every routing change and every attempt is logged with who and why.
Frequently asked questions
Do I need contracts with several providers?
Routing pays off from the second provider. If you work with one today, we can introduce providers that fit your markets, and you sign with them directly.
Which declines are retried?
Only soft declines and technical errors, such as do-not-honor, issuer unavailable or timeouts. Hard declines like stolen card or closed account are never retried, which keeps you within card scheme rules.
Can I test routing before it goes live?
Yes. Any routing profile can be replayed against your past transactions to see how many payments would have gone where, and what the approval rate would have been.
Does orchestration add latency?
A routing decision takes a few milliseconds. Most of the payment time is still spent at the provider and the issuer.
See routing on your own traffic
Share a month of anonymized transactions and we'll show you which payments a second provider would have saved.