# The Mystery Decline

## “Do Not Honor” Is a Black Box  
Decline code 05: “Do Not Honor.” The most frustrating response in payments because it tells you nothing. But it hides patterns. Slicker's AI decodes what issuers won't reveal and recovers 67% of these mysterious declines.

30%  
Of all soft declines  
67%  
Actually recoverable  
5+  
Hidden reasons identified  
87%  
Cause prediction accuracy

## Decoding the “Do Not Honor” Mystery  
Code 05 is a catch-all. Issuers use it to mask the real reason. Slicker's AI analyzes transaction context to predict what's actually happening behind every “Do Not Honor.”

- Most "Do Not Honor" declines are actually soft declines in disguise: insufficient funds, velocity limits, or temporary holds  
- Issuers hide the real reason for privacy, security, and liability reasons, making generic retries ineffective  
- Our AI classifies the true cause by analyzing issuer patterns, transaction context, BIN data, and historical outcomes  
- Once decoded, each decline gets the right recovery strategy, not a one-size-fits-all retry

### What “Do Not Honor” actually means:

| Reason | Classification | Percentage |
|--------|----------------|------------|
| Insufficient Funds | Recoverable | 35% |
| Fraud Screening | Partial | 25% |
| Card Restrictions | Recoverable | 20% |
| Issuer Unavailable | Recoverable | 12% |
| Genuine Rejection | Hard | 8% |

67% of these are actually recoverable

## Strategy by Hidden Cause  
Different underlying causes require different recovery approaches. Once we decode the true reason, we apply the optimal strategy.

### Hidden Insufficient Funds  
Many issuers return 'Do Not Honor' instead of revealing the customer has insufficient funds. Privacy protection at play.

**Strategy:**  
Apply pay-cycle timing optimization as if it were a known NSF decline.

### Fraud Prevention Triggers  
The transaction triggered issuer fraud algorithms. Not actual fraud, just unusual pattern for that card.

**Strategy:**  
Retry with different parameters (time, amount splitting) to avoid false-positive triggers.

### Velocity/Limit Issues  
Daily spending limits or transaction velocity checks. The card is valid but temporarily restricted.

**Strategy:**  
Wait for limit reset (usually 24h) and retry at optimal time within customer's typical usage window.

### Network Connectivity  
Issuer system was temporarily unavailable or timed out. The decline has nothing to do with the card itself.

**Strategy:**  
Immediate retry (within minutes) through alternative routing if available.

## Issuer Behavior Patterns  
Different types of issuers use “Do Not Honor” for different reasons. Our AI learns the patterns from transaction context and issuer behavior, applying the right recovery strategy for each.

#### Large National Issuers  
Typically masks insufficient funds or velocity limits  
#### Regional & Community Banks  
Often indicates fraud screening false positives  
#### Digital-First Issuers  
Usually reflects account restrictions or holds

### Why Issuers Hide the Real Reason  
- **Privacy:** Revealing “insufficient funds” exposes customer financial status  
- **Security:** Detailed decline reasons could help fraudsters refine attacks  
- **Liability:** Generic codes reduce issuer exposure to disputes  
- **Legacy:** Many systems were built before detailed codes existed

### How Slicker Decodes Them  
We analyze transaction context (timing, amount, card type, geography, merchant category, and historical patterns) to predict the true underlying cause with high accuracy.

87% prediction accuracy on cause classification

## Complete Payment Recovery  
Explore our other products to maximize your payment recovery.

### Smart Retries  
AI-Powered Optimization  
For every failed payment, we answer three questions: whether to retry, when to retry, and how much to retry. Our ensemble of machine learning models reads network-level messages, gateway error codes, and customer behavioral signals.

### Dunning Emails  
Hyper-Personalized Messaging  
No unnecessary emails - we only reach out when customer action is the only path to recovery. Each message is tailored to the failure reason, sequence stage, and required action.

### Evaluation  
Unrivaled Transparency  
Every vendor claims impressive recovery rates - but we actually prove it. We run rigorous AABB testing, the same crossover methodology used in clinical drug trials, to guarantee statistically significant results.

> 1M  
Recovered payment failures  
20%  
Recovery rate uplift  
< 5min  
Time to go live  
SOC 2 in progress  
Enterprise-grade security  
Global coverage  
Stop the revenue leak

## Never Worry About Payment Failures Again  
Retain your customers with the best-in-class AI payment recovery platform. Guaranteed ROI with success-based pricing.