Transactions are classified into two decline categories based on whether they can be successfully retried.
Hard Decline vs Soft Decline
Aspect | Hard Decline | Soft Decline |
|---|---|---|
Meaning | Permanent rejection | Temporary rejection |
Can be retried? | ❌ No - will fail again | ✅ Yes - may succeed later |
Root Cause | Card/account status issue | Temporary condition |
Examples | Expired card, fraud, lost/stolen | Insufficient funds, network timeout |
Resolution | Customer must take action | May resolve automatically |
Dunning Retry | ❌ Will not retry | ✅ Can retry |
Hard Declines
Primary reasons for hard declines
1. Card Validity Issues
Expired Card:
Card has passed its expiration date
Card cannot be used until customer provides new card details
Card Not Found:
Payment method reference no longer exists
Card may have been deleted from the issuer's system
2. Security & Fraud Issues
Lost or Stolen Card:
Card has been reported lost or stolen by cardholder
Issuer has blocked the card permanently
Suspected Fraud:
Issuer's fraud detection flagged the transaction
Card is blocked due to suspicious activity pattern
Fraud/Risk Blocks:
Merchant's or processor's fraud prevention system blocked the transaction
Transaction characteristics match fraud patterns
3. Account Status Issues
Card Account Closed:
The bank account linked to the card is closed
Card cannot be used for any transactions
Authorization Issues:
Previous authorization has expired and cannot be used
Attempt to settle more than authorized
Authorization was canceled/voided
4. Payment Processor Rejections
Acquirer Rejected:
Payment processor permanently rejected the transaction
May be due to merchant account restrictions or card type incompatibility
5. Compliance Issues
SCA Required:
Strong Customer Authentication (3D Secure) is required but wasn't completed
Regulatory requirement (PSD2 in Europe) was not met
How Frisbii handles hard declines
For Subscription Invoices:
Dunning retries are stopped - Hard declines won't succeed on retry
Customer notification - Must update payment method
Subscription at risk - May expire if issue is not resolved
Manual intervention needed
For One-Time/Charge Invoices:
Immediate failure - Transaction cannot be completed
Alternative payment required - New payment method must be provided
Manual follow-up needed
Best Practices for Hard Declines
1. Don't retry automatically
Hard declines indicate permanent issues
Retrying wastes processing fees and resources
May trigger additional fraud alerts
2. Immediate Customer Communication
Notify customer of the specific issue
Request updated payment information
Provide clear steps to resolve the issue
3. Update Payment Method workflows
For expired cards, proactively request updates before expiration
For fraud blocks, direct customer to contact their bank
For lost/stolen cards, require new payment method immediately
4. Monitor Hard Decline Patterns
High hard decline rates may indicate:
Outdated payment methods on file
Customer base with high fraud risk
Need for proactive payment method updates
5. Distinguish in Dunning Plans
Configure dunning to recognize hard vs soft declines
Skip retries for known hard decline error codes
Focus recovery efforts on resolvable issues
Soft Decline Examples
insufficient_funds- Temporary; customer may add fundsdeclined_by_acquirer- May be temporary network/system issueacquirer_communication_error- Technical issue, retry may workprocessing_error- Transient technical problem
Summary
Transactions are hard declined when there's a permanent, unresolvable issue with the payment method or transaction that makes it impossible to succeed without customer intervention. Unlike soft declines (temporary issues), hard declines require the customer to take action, such as updating their card, resolving fraud blocks, or providing an alternative payment method, before any payment can be successfully processed.