Hard Decline
What Is a Hard Decline? Definition and How It Works
Definition
A hard decline is an authorisation response indicating that the transaction was permanently rejected due to a definitive card-level condition such as a stolen, restricted, or invalid card, and must not be retried.
How it works
Hard declines communicate that retrying the transaction on the same card would be futile and is prohibited by card scheme rules. The issuer or card network has determined a permanent condition that prevents authorisation: the card has been reported stolen, is restricted from use, has an invalid number, or the account has been closed.
Common hard decline codes include 41 (Lost Card), 43 (Stolen Card), 04 and 07 (Pick Up Card), 14 (Invalid Card Number), 54 (Expired Card), 62 (Restricted Card), and 78 (No Account). Each code identifies a specific terminal condition.
Card scheme retry rules explicitly prohibit retrying hard declines. A merchant who resubmits an authorisation for a card returned with a stolen card decline code is violating scheme rules with every retry attempt. This violation is detectable by networks through authorisation attempt monitoring and can result in fines per violating transaction.
Hard declines on stored credentials indicate that the stored card data should be removed from the merchant's credential database. Continuing to attempt charges against a stolen, expired, or restricted card wastes processing costs, violates scheme rules, and may trigger fraud or AML signals at the issuer.
Why it matters
Hard decline handling is a hygiene issue with financial consequences: the most common hard decline violations involve merchants retrying hard declines through automated billing systems that treat all declines equally. Scheme fines for retry violations can be $0.10-$0.25 per violating transaction, at high retry volumes this accumulates quickly.
Hard declines in stored credential contexts require immediate action: when a subscription billing system receives a hard decline on a stored credential, the correct action is to immediately remove that credential from the active billing pool and notify the customer to update their payment method. Continuing to bill generates fines and does not produce revenue.
Hard decline codes on new transactions indicate potential fraud: a new transaction returning a stolen card code means the card was reported stolen before the authorisation attempt. If the merchant's fraud system did not catch this, it suggests either the card was very recently reported or fraud signals were insufficient. Hard decline analysis for new transactions can inform fraud model tuning.
Hard decline rates by card type and BIN range can reveal data quality issues: a concentration of invalid card number (code 14) hard declines on new card entry flows suggests data entry errors, potential card testing activity, or integration issues with card validation before submission.
With PXP
PXP's platform classifies hard declines at the point of receipt and prevents automated retry. Hard decline codes are flagged in stored credential management to prevent future charge attempts on affected tokens. Hard decline data is surfaced in PXP's analytics with code-level breakdowns to support stored credential hygiene and fraud pattern analysis.
Frequently asked questions
What is the difference between a hard decline and a soft decline?
A soft decline indicates a temporary condition, the transaction may succeed on retry with appropriate timing or after additional authentication. A hard decline indicates a permanent condition, the card is stolen, restricted, or invalid, and cannot be used for future transactions. Hard declines must not be retried under card scheme rules. Soft declines may be retried within scheme-mandated timing and frequency limits.
What should merchants do when they receive a hard decline on a stored credential?
The merchant should immediately flag the stored credential (token) as invalid and remove it from the active billing database. The customer should be notified and prompted to provide a new payment method. Continuing to attempt charges on a known hard-declined card wastes processing costs, violates scheme retry rules, and generates negative signals at the issuer. Automated billing systems must enforce hard decline classification to prevent inadvertent violations.
Are all 'do not honor' declines hard declines?
No. Do Not Honor (code 05) is typically a soft decline, it is one of the most common soft decline codes. Hard declines are identified by specific codes that indicate permanent card conditions: lost, stolen, restricted, expired, invalid number, or closed account. Soft declines are characterised by the temporary or conditional nature of the reason, while hard declines reflect permanent card states.
How do hard decline rates affect scheme monitoring programs?
Hard decline rates are not directly monitored by scheme programs in the same way chargeback ratios are, but high volumes of specific hard decline codes can indicate fraud patterns that attract network attention. A sudden increase in stolen card declines (code 43) may indicate the merchant is being targeted with confirmed stolen card data. Monitoring hard decline code distribution helps merchants and their fraud teams identify and respond to these patterns proactively.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started