How does cascading work?
A payment goes to the first eligible provider. If that provider returns a soft decline, such as do-not-honour from a cautious issuer or a technical timeout, the orchestration layer checks which other providers are eligible for the same customer, method and currency, and sends the payment to the next one without the customer re-entering anything. The final status, approved or declined, comes back to the merchant once.
Why does cascading matter for approval rate?
In cross-border e-commerce a large share of declines are soft. The same card can be declined by one acquirer and approved by another because of different MCC policies, issuer relationships or risk models. Cascading turns some of those declines into approvals, which is why it is usually the first lever merchants pull when approval rates drop.
What are the risks?
Unlimited retries look like card testing to issuers and schemes. Good cascading limits the number of attempts, never retries hard declines, keeps 3-D Secure state consistent between routes, and logs every attempt so finance and risk teams can see what happened.
Where does Omno use it?
Omno’s routing rules decide the first provider and the cascade order per customer group, customer verification level, method and currency, and the routing-decision log records each attempt.