Payment orchestration

Every payment
on its best
route

Alderone sits between your checkout and your payment providers. Connect every acquirer and PSP through one API, send each payment where it is most likely to be approved, and run fraud checks and analytics across all of them.

Card acquirersPSPsApple PayGoogle PayOpen bankingSEPAPixiDEALBLIK3DS serversFraud toolsPayout rails

One layer over all your providers

Keep your PSP contracts and merchant accounts. Alderone adds routing, retries, risk checks and data on top of them.

Send each payment where it clears

Pick the provider for every transaction by the data you already have about it.
  • Rules by card country, BIN, currency, amount and method
  • Approval-rate, cost and weighted strategies
  • Change routing without a deploy
Explore orchestration
Routing rulesEvaluated in order · first match wins
Live
  1. ifCard issued in BrazilLatAm PSP
  2. ifAmexAcquirer US
  3. ifGBP and amount > £1,000Acquirer UK
  4. ifCard country in EEABest approval: EU or UK
  5. ifEverything elseAcquirer EU
Spotlight

Approval
rate, raised

Routing, cascading retries and network tokens work together on every transaction to turn more attempts into approved payments.

Approval rate, all providersLast 30 days
+2.4 pts
Approval rate93.8%
Saved by retries€48,210
Failovers3
Spotlight

No provider
lock-in

Cards are vaulted with Alderone, not with a PSP. Add a new acquirer, move volume or leave one without asking customers to re-enter their card.

See connectors

Any
provider.
One API.

Find out how many declines you could recover

Send us a month of transaction data and we'll model routing on your own traffic.

Developers

One integration. Every provider behind it.

Integrate once, then add or switch providers in the dashboard. Your code doesn't change.
  • One payment API, whichever provider runs it
  • Normalized statuses and decline codes
  • Webhooks for every attempt and status change
  • Sandbox with simulated providers and failures
POST /v1/payments
curl https://api.alderone.tech/v1/payments \
  -H "Authorization: Bearer sk_test_•••" \
  -d '{
    "amount": 4900,
    "currency": "EUR",
    "source": { "token": "tok_al_•••" },
    "routing": { "profile": "eu_cards", "retries": 2 }
  }'

# → 201 Created
{ "id": "pay_8f2k…", "status": "authorized",
  "provider": "acquirer_uk", "attempts": 2 }

Get started

Create a sandbox and send a test payment through two simulated providers.

Connect a provider

Add your merchant account credentials and set it live in minutes.

Handle events

One webhook format for every provider, attempt and refund.

Frequently asked questions

How is Alderone different from a PSP?

A PSP processes payments under its own contracts. Alderone is a technology layer between your checkout and the providers you already work with: it decides which provider handles each payment, retries declines on another one and gives you data across all of them.

Do I keep my contracts with providers?

Yes. You keep your merchant accounts, pricing and settlement with each acquirer or PSP. Alderone connects to them with your credentials.

Does Alderone hold my funds?

No. Funds settle directly from your providers to your bank accounts. Alderone sees transaction data, not money.

What happens if a provider goes down?

Health checks detect errors and timeouts within a minute and traffic moves to the next provider in your routing profile. Payments that already failed with a technical error are retried automatically.

How long does integration take?

A hosted payment page can go live in days. A server-to-server integration usually takes a few weeks. Adding further providers later needs no code.

What about PCI DSS?

Card data is tokenized in the Alderone vault. With the hosted page or embedded fields, card numbers never touch your servers.