lyria
Orchestration

Approve more. Lose less.

Lyria Orchestration connects you to a managed network of acquirers and payment methods, scores each transaction in real time and sends it where it is most likely to be approved. When a provider falters, traffic moves on its own.

Route performanceIllustrative
ProviderStatusShare
Acquirer AHealthy41%
Acquirer BHealthy33%
Provider CDegraded4%
Local rail DHealthy22%
Sample data. Traffic shifts away from degraded providers automatically.

Higher approval rates without more integrations.

Routing, retries and failover run inside Lyria, so your checkout stays simple while the network behind it gets smarter.

Multi-acquirer routing

Route by card BIN, issuer country, currency, amount, method and merchant category, or let the engine choose by approval likelihood.

Cascading retries

Soft declines retry on the next best route in the same session, before the customer sees an error.

Automatic failover

Provider health is measured continuously. Degraded routes are drained and restored without manual switching.

Rules and priorities

Set priority orders, volume splits, caps and exclusions per market and method, and change them without a release.

Network tokens and vault

Cards are tokenised once and usable across every acquirer, with network tokens where schemes support them.

3-D Secure orchestration

Request exemptions where they apply and challenge only where liability shift matters.

How it works

What happens in the milliseconds after checkout.

  1. Score

    Risk and routing signals are evaluated together.

  2. Route

    The payment goes to the provider most likely to approve it.

  3. Recover

    Soft declines cascade to the next route automatically.

  4. Record

    The outcome is written to the ledger and reported.

Details

Orchestration at a glance.

Payment methods
Cards, bank transfers, open banking, wallets, local methods and stablecoins, through contracted partners.
Providers
150+ acquiring banks and payment providers reachable through one integration.
Routing inputs
BIN, issuer country, currency, amount, method, merchant category, provider health, cost and approval history.
Integration options
REST API, hosted checkout or hosted card fields.
Card data
Tokenised in a PCI DSS-compliant vault. Hosted components keep card data out of your environment.
Reporting
Approval and decline analysis by provider, BIN, country and reason code.

Who Orchestration is built for.

High-volume merchants

Spread volume across acquirers, recover declines and keep processing when a provider has a bad day.

Payment brands & PSPs

Give every merchant on your brand access to a multi-acquirer network from their first transaction.

Integrate

Route your first payment today.

One request style across every Lyria product, with idempotency, signed webhooks and a sandbox that mirrors production.

  • Approval-optimised routing on every request
  • Soft declines cascade within the same session
  • One request shape for every provider
Route a payment
POST /v1/payments
Idempotency-Key: 7f1c2e0a-9b54
{
  "amount": 12500,
  "currency": "EUR",
  "routing": { "strategy": "approval", "cascade": true }
}

Questions about Orchestration.

Do we need our own acquiring contracts?
No. You can use the providers already contracted through Lyria, bring your own agreements, or combine both. Routing works the same way across all of them.
How quickly does failover happen?
Provider health is measured on live traffic. When error or decline patterns cross a threshold, new transactions stop going to that route and soft declines in flight retry elsewhere.
Can we control the routing ourselves?
Yes. You can set fixed priorities, splits and exclusions, let the engine optimise, or mix the two by market and method.
Does routing change the customer experience?
No. Retries happen within the same session. The customer completes one checkout and sees one result.

Stop depending on a single acquirer.

Tell us about your flows and volumes, and we will show you how Orchestration fits alongside the rest of your stack.