Cascading Payments
Automatic retry across alternative acquirers when an initial transaction attempt is not authorized — helping reduce avoidable declines.
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. Each attempt is logged for monitoring and reconciliation.
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.
Where It Applies
Security Benefits
- • Cascading respects 3DS context.
- • Operates on tokenized references where available.
- • Compliant with acquirer cascading rules.
Frequently Asked Questions
Related technology & solutions
Connect this layer with the solutions and integrations that use it in production.
Explore BoxCharge Technology
See how our infrastructure layers fit your payment operations, approval goals, and security requirements.
Request Consultation