What is Cascading?
Also: cascade
Retrying a declined transaction on a second acquirer or scheme to recover authorisation, subject to scheme rules on retry frequency and reason codes.
Cascading is the automatic submission of a credit or debit card transaction authorisation request to a second or subsequent acquirer after the initial attempt with the primary acquirer results in a decline.
This process is typically triggered by soft declines, such as an issuer decline response of 'Do not honour' (ISO 8583 response code 05) where the card itself is valid and not reported lost or stolen.
The payment gateway orchestrates this by submitting a fresh authorisation request, identical to the first, to an alternative acquiring bank configured by the merchant, rather than resubmitting to the original declining acquirer, which would likely yield the same decline.
For a merchant, cascading can improve authorisation rates by recovering sales that would otherwise be lost to soft declines, particularly when the initial decline is due to transient issuer-side issues or risk thresholds rather than insufficient funds or fraud.
Merchants configure cascading rules within their payment gateway, specifying which decline codes should trigger a cascade and the order of acquirers to attempt.
A common pitfall is to cascade aggressively on hard declines or to re-attempt too quickly, which can lead to unnecessary processing fees for the merchant and potential issuer monitoring for excessive decline retries from the cardholder's perspective.
Worked example
A merchant reviews a €900 transaction where Cascading is the deciding factor. The first path returns a recoverable response, the orchestration layer applies the routing rule, and the retry is sent through a better-performing acquirer or MID.
The operational cost is modelled at 12 basis points saved, or €1.08, and the relevant action must complete the same authorisation session. Step 1 is to capture the original request data, including amount, currency, issuer country, MID, and response or status code.
Step 2 is to apply the merchant's rule set, for example whether to retry, challenge, refund, release goods, or hold for review. Step 3 is to reconcile the result against acquirer reporting so finance can see the cash impact.
If the rule improves the outcome by even 50 basis points on 2,000 similar monthly transactions, the merchant protects roughly 10 extra orders from avoidable failure or loss.
Scheme notes
Routing is not a card-scheme product in itself, but scheme rules constrain which data may be changed between attempts and how stored credentials, 3DS results, and authorisation advice codes must be respected.
Visa and Mastercard issuer response codes are not perfectly interchangeable, so retry and routing rules should map scheme-specific codes before making decisions. Acquirer performance can also vary by scheme, issuer country, MCC, and transaction type.
Why it matters for merchants
Commercially, this affects recovered revenue, failover resilience, acquirer cost, and the ability to route each payment to the strongest available path.
For a merchant processing £500,000 per month, a 25 basis point movement is worth £1,250 before secondary effects such as disputes, reserves, support tickets, or failed delivery costs.
The impact is larger in high-risk, subscription, travel, digital-goods, and cross-border models because issuer decisions and scheme monitoring can compound quickly.
Cardflo can help by combining acquiring access, MID routing, orchestration rules, KYB review, and chargeback tooling where relevant, so the merchant is not dependent on one processor interpretation or one fixed transaction path.
Frequently asked
Which data should a merchant store for Cascading?
Store the transaction ID, MID, acquirer, amount, currency, issuer country, card scheme, response or status code, timestamp, and any 3DS, exemption, refund, or dispute reference. For card transactions, keep authorisation and Clearing identifiers because settlement or chargeback questions may arrive 30 to 120 days later.
For regulated flows, keep customer consent and evidence records for at least the period required by local law or scheme rules. Good records reduce investigation time from hours to minutes when acquirer reporting does not match the order system.
How often should Cascading be reviewed?
High-volume merchants should review exception rates weekly and trend the main metric monthly by scheme, acquirer, issuer country, MCC, and payment method. A movement of 20 to 50 basis points can be material if the merchant processes thousands of orders.
Finance should reconcile the cash impact at settlement level, while risk or payment operations should analyse the root cause. Reviewing only blended totals hides problems that appear on a single BIN range, region, or MID.
What threshold usually triggers action on Cascading?
The threshold depends on the category, but merchants should investigate any sudden change above 10% relative movement or 25 basis points absolute movement. For disputes and fraud, scheme thresholds such as 0.9% under Visa monitoring or 1.5% under Mastercard ECM can create immediate escalation risk.
For settlement or pricing items, even 5 to 15 basis points can justify routing or contract review. The key is to set thresholds before month-end, not after a processor invoice or scheme notice arrives.
Can Cascading differ between acquirers?
Yes. Acquirers can map response codes differently, apply different risk rules, support different data fields, and settle on different cycles.
One acquirer may return a generic decline while another exposes issuer advice that allows a safe retry. Fee treatment can also vary by contract, especially for cross-border, FX, premium cards, and alternative payment methods.
This is why merchants using orchestration should compare performance by acquirer and scheme rather than relying on a single blended approval or cost figure.
What is the first remediation step when Cascading creates losses?
Start with a 30-day sample and split it by scheme, issuer country, card product, payment method, MID, and response or dispute code. Quantify the value at risk in cash terms, not just percentage points.
Then decide whether the fix is operational, such as better evidence or customer communication, technical, such as richer data or 3DS indicators, or commercial, such as a different acquirer route.
Recheck the same metric after one full settlement or dispute cycle to confirm the change worked.
See how Cascading plays out in practice
Industries and regions where this term drives real acquiring, routing, or dispute decisions.
Related terms
Rules that re-attempt a declined transaction across time windows, acquirers, or authentication levels to recover revenue.
Algorithmic selection of an acquirer or MID per transaction to maximise approval rate, minimise cost, or both.
A platform layer that lets a merchant connect to multiple acquirers, APMs, and risk tools through one integration and route transactions intelligently.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.