What is payment fallback?

Payment fallback is the automatic switch to a backup route when a payment fails. The backup can be another acquirer, another gateway, another credential or, in some flows, another payment method. It recovers payments lost to outages, timeouts and soft declines without asking the customer to start again.

When fallback helps

• A provider is unavailable or times out.
• An issuer returns a soft decline that may succeed on another route.
• A technical error interrupts the authorization.

Fallback does not help with hard declines, such as a stolen card or a closed account. Those will fail everywhere, and retrying them breaks scheme rules and adds fees.

What a good fallback setup needs

Several provider connections, decline codes normalized across providers, rules that decide which codes deserve a retry and where, and limits that respect scheme retry rules.

What it means for payment operators

On the platform, each merchant account carries its own fallback policy: an active state, maximum attempts and retries, and a choice on whether attempts during provider downtime count. A return code mapping decides, code by code, whether to retry, on the same provider or another, and with which authentication behavior. Your merchants recover what can be recovered, within the boundaries you set.