What is the difference between a soft decline and a hard decline?

A soft decline is temporary or route-related. An issuer timeout, a technical error or a temporary limit can cause it, and the payment may succeed on a retry or through another acquirer. A hard decline, such as a stolen card or a closed account, will fail everywhere and must not be retried.

Why the distinction matters

Retrying a soft decline at the right moment, or on the right route, recovers revenue. Retrying a hard decline does the opposite: it adds fees, can breach scheme retry rules and may raise fraud flags with the issuer.

The difficulty

Decline codes are not uniform. Each provider returns its own codes and messages, and the same issuer response can look different from one acquirer to another. Some codes also sit in between, such as insufficient funds, where a later retry may work but an immediate one will not.

What it means for payment operators

Your merchants need decline codes normalized across providers and a clear rule for each. On the platform, the return code mapping sets, per code, whether a retry happens, whether it targets the same provider or another, and how the attempt behaves. Codes governed by scheme rules are locked, so a hard decline cannot be retried by mistake, and each row shows whether it holds a default or custom value.