Skip to main content

SCA Soft-Declines

There are two main types of card transaction declines: hard declines and soft declines.

Hard declines happen when the issuing bank rejects the transaction. Examples include attempting to use a card that has been reported lost or stolen, or the card has expired. Hard declines are permanent, so the payment should not be retried.

Soft declines are temporary authorisation failures. Around 80% to 90% of all declines fall into this category. They occur for a host of reasons including the need to authenticate the Cardholder further or because there are issues with the technical infrastructures that process the transaction. Soft declines are temporary, meaning you can process the transaction again after meeting the requirements that led to the decline the first time around.

If you do not obtain SCA on an eligible payment the issuer may soft decline the payment insisting that SCA be obtained. In which case a responseCode of 65 will be returned by the Gateway[1] and you can choose to resubmit the payment with SCA if required.

Refer to the SCA Using 3-D Secure section for details on how you can use 3-D Secure to obtain SCA and automatically retry payments that have been soft declined for this reason. If 3-D Secure has been used to provide SCA and the issuer still declines insisting that SCA be obtained, then the Gateway will return a normal decline responseCode of 5 to prevent an infinite loop of obtaining SCA and then being declined for lack of SCA.


[1] Mastercard will return an ISO 8583 (1987) code of 65, Visa/Diners/Discover and others will return an ISO 8583 (1987) code of 1A. The Gateway will normalise these and always return a responseCode of 65.

Footnotes​

  1. Mastercard will return an ISO 8583 (1987) code of 65, Visa/Diners/Discover and others will return an ISO 8583 (1987) code of 1A. The Gateway will normalise these and always return a responseCode of 65. ↩