Risk

Card decline

An authorisation response refusing to fund a transaction, returned by the issuer with a reason code.

A decline occurs when an issuing bank or the card scheme refuses to authorise a transaction during the real-time payment flow. The refusal is transmitted via the acquirer to the merchant, accompanied by a specific response code that indicates why the payment failed. These codes distinguish between terminal issues like stolen cards or closed accounts and transient problems such as insufficient funds or technical timeouts. Processing banks and schemes like Visa and Mastercard impose strict monitoring on decline rates, often penalising merchants who exceed specific thresholds through excessive retries. Furthermore, under Strong Customer Authentication (SCA) requirements, an issuer may issue a soft decline specifically to request 3D Secure step-up authentication. Understanding the nuance between hard and soft declines is essential for maintaining a healthy Merchant Identification (MID) standing and ensuring optimal settlement timing by avoiding unnecessary fraud reviews.

Frequently asked

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

A soft decline suggests a temporary issue where a retry might succeed, such as insufficient funds or a request for 3DS authentication. A hard decline represents a permanent failure, such as an invalid card number or a lost card status, where further attempts are prohibited by scheme rules.

Can high decline rates result in fines from payment schemes?

Yes, both Visa and Mastercard have integrity programmes that monitor decline patterns and retry attempts. Merchants who repeatedly attempt to authorise transactions against the same card after receiving a hard decline code may face scheme fees or potential revocation of their processing capabilities.

Related terms

Get started

Ready for velocity?

Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.

Apply now