Cascading
Struggling with low acceptance rates and losing out on revenue because of card declines?
Optimise payment acceptance by re-trying declined transactions via alternative routes
The Problem: High transaction decline rates can lead to customer dissatisfaction and potential loss of revenue if merchants are not re-attempting declined transactions.
Our solution:
Automatically re-attempt non-fraudulent declined transactions within milliseconds to convert them into approvals.
Achieve up to 30% success in turning declines into approved transactions, significantly boosting revenue.
Allows routing rules for cascading through the same or alternative acquirer routes to maximise performance.
Preventing revenue loss by automatically turning declined transactions into approvals
The Problem: High transaction decline rates result in significant revenue loss and hinder accurate financial forecasting.
Our solution:
Provides valuable data insights from transaction recovery to improve financial forecasting and strategic planning.
Reduce financial risks by reattempting declined transactions alternative cost-saving routes.
Customise cascading rules to align with financial strategies and minimise revenue loss.
Ensure scheme compliance with Cascading
The Problem: Multiple blanket re-attempts of transactions can cause non-compliance with card schemes and trigger issuer fraud rules.
Our solution:
Only non-fraud based decline codes are re-attempted
Maximum of 4 re-attempts in one go to ensure issuer fraud flags not triggered
Cascading operates fully in compliance with Scheme rules
See how Cascading fits into the Dynamic Routing feature set
Optimise success rates and reduce transaction fees by using our routing products in conjunction with each other.
FAQs
What is Cascading?
Cascading automatically reattempts non-fraud declined transactions, rather than failed ones, through alternative acquirer routes to convert declines into approvals, optimizing revenue and ensuring compliance with payment scheme rules.
Are you compliant with Scheme rules?
Yes, we don't Cascade fraud based declines and we are within the 15 re-attempt limit.
How many Cascades can I do?
Up to 4 to ensure we comply to scheme regulations.
Can you Cascade a failed transaction?
No. A failed transaction indicates that there is an underlying issue with the transaction message. Reattempting a failed transaction would not resolve this and require further investigation.
How can I track cascading performance?
Easily, through the APEXX portal.