RU

Payment cascading: dynamic routing to reduce declines

Automatic failover
to backup channels when the primary
acquiring bank has issues

Keep your payment success rate
high without worrying
about infrastructure issues

Fewer
declines

One or more backup
channels almost completely
eliminate the risk
of declines on the side
of the primary acquiring bank

Fast
failover

A delay of just 200–500 ms: your customer
won’t notice a thing

Single API

Unlimited backup banks
within a single integration

Additional
acquiring banks
connected
free of charge
for all
Payture clients

How payment cascading
works

Payment
Acquirer A
Declined
Acquirer B
Declined
Acquirer C
Payment successful

benefit

Stable payment acceptance with no losses
thanks to backup channels

According to Payture internal
statistics, two backup channels
can reduce lost traffic

to 0%

* The statistics do not account for possible
issues caused by failure or outage
of the telecommunications infrastructure

due to bank-side issues, %
share of lost traffic

0.1%

0 backup banks

0.01%

1 backup bank

0%

2 backup banks

payment methods

Payment methods supported by this solution

Submit a request
to get started

Accept online payments with modern payment methods in the currency you need on your website, marketplace, online store or app

FAQ

Still have questions?
We may have already answered them

There’s no limit on the number of banks you can connect.

We configure the order of acquirers in the cascade on our side, based on Payture’s technical capabilities and your preferences.

Setup is free and there’s no monthly fee. A fee is charged for each successful transaction, and only by the acquirer that processed that online transaction.

Our internal statistics show that connecting two backup acquiring banks is enough to reduce declines caused by infrastructure issues on the bank’s side to almost zero. Note, however, that these statistics don’t account for possible issues on the side of telecom or power providers. Such incidents are considered force majeure.