Technology
Cascading Payments
Automatic retry across alternative acquirers when an initial transaction attempt is not authorized.
Overview
Cascading Payments Overview
Cascading payments retry declined transactions through alternative acquirers configured for the merchant, helping reduce avoidable declines while respecting card network and acquirer rules.
How It Works
Inside the Layer
Initial Attempt
Transaction is routed to the primary acquirer based on rules.
Cascade Trigger
When eligible, declined attempts cascade to a secondary acquirer.
Outcome Logging
Each attempt is logged for monitoring and reconciliation.
Use Cases
Where It Applies
Soft-decline recovery
Acquirer outages
Corridor-specific failover
Security
Security Benefits
- • Cascading respects 3DS context.
- • Operates on tokenized references where available.
- • Compliant with acquirer cascading rules.
FAQ
Frequently Asked Questions
No. Cascading runs only for eligible decline reasons and configured fallback paths.
Explore BoxCharge Technology
See how our infrastructure layers fit your payment operations.
Request Consultation