What is Payment Failover?
Also known as: Fallback routing
Payment failover is the automatic transfer of a transaction to an alternative channel when the bank or payment channel selected for it is unreachable, times out or returns a technical error. Its purpose is to keep bank-side outages from reaching the customer and causing lost sales.
How does Payment Failover work?
- The system monitors each channel's response time and error codes, detecting technical errors such as maintenance, connectivity issues or timeouts.
- When a technical error occurs, the transaction is resent to the next suitable channel according to the defined rules.
- Declines caused by the card itself — such as insufficient funds or a stolen card — are not retried on another channel; failover applies only to channel-side errors.
Key points
- Collections continue during bank maintenance and outages
- Prevents revenue loss at peak times (bill due dates, campaigns)
- Channel-side errors must be distinguished from card-side declines
Payment Failover with Treps
When a bank or POS is unreachable — due to timeouts, technical errors or maintenance — Treps automatically routes the transaction to an alternative POS. Working together with smart routing, this removes the outage risk of depending on a single bank.
Frequently asked questions
Does failover retry every declined transaction?
No. A properly designed failover triggers only on channel-side (technical) errors. For declines caused by the cardholder, such as insufficient limit, sending the transaction to another bank does not change the outcome and creates unnecessary attempts.
Do I need agreements with multiple banks for failover?
Yes. To switch to a backup channel, the business needs active agreements with at least two banks or payment institutions.