Decline Rate

Every payment authorization attempt receives one of three outcomes from the issuing bank: approved (transaction succeeds), declined (transaction rejected with specific reason code), or error (technical failure, no issuer response). Decline rate is calculated as: (Declined Transactions ÷ Total Authorization Attempts) × 100.

Decline codes provide specific rejection reasons. Common codes include: 51 (Insufficient Funds) - customer doesn't have available credit, 05 (Do Not Honor) - generic issuer decline often related to merchant risk profile or MCC code, 59 (Suspected Fraud) - issuer's fraud system flagged transaction, 61 (Exceeds Withdrawal Limit) - customer exceeded daily spending limits, 14 (Invalid Card Number) - customer typo or expired card, 04 (Pick Up Card) - card reported lost/stolen. Understanding code distribution guides optimization - heavy 05 declines suggest routing issues, heavy 59 declines indicate fraud perception problems.

Soft vs. hard declines require different handling. Soft declines are temporary rejections where retry might succeed: insufficient funds (customer adds money), velocity limits (wait 24 hours), network timeouts (retry immediately), "try again" messages. Hard declines are permanent: invalid card, expired card, reported stolen, account closed. Smart payment systems automatically retry soft declines through cascading logic while immediately flagging hard declines for customer contact.

Tracking and analysis should occur at multiple levels: overall decline rate (total declined ÷ total attempts), decline rate by card type (Visa vs. Mastercard vs. Amex), decline rate by geography (domestic vs. international), decline rate by transaction amount (high-ticket vs. low-ticket), decline rate by customer type (new vs. repeat), and decline rate by PSP (comparing routing options). This granular analysis identifies optimization opportunities - if EU Mastercard declines are 45% while US Mastercard declines are 18%, routing EU Mastercards to EU-based acquirers likely recovers 10-15% of those declines.

Real-time optimization requires monitoring decline spikes. A sudden increase from 20% to 35% decline rate indicates problems: PSP outage, fraud filter misconfiguration, issuer bank issues, or network problems. Alert systems should trigger at 10% increase above baseline, enabling immediate investigation and remedy before significant revenue loss.

Decline rates directly translate to lost revenue - every declined transaction is a customer who wanted to buy but couldn't complete purchase. A merchant with $10M attempted annual volume and 25% decline rate loses $2.5M in potential revenue from failed transactions. If optimization reduces decline rate to 18% (recovering 28% of declines), that generates $700K additional annual revenue from the same traffic - pure margin improvement requiring zero customer acquisition cost.

Customer experience suffers from high decline rates. Legitimate customers frustrated by declined purchases rarely retry - studies show only 15-25% of customers attempt purchase after decline, meaning 75-85% abandon permanently. For high-risk merchants spending $50-200 per acquired customer, losing customers at checkout due to preventable declines wastes entire customer acquisition investment. A merchant spending $500K annually on acquisition with 25% decline rate wastes $125K acquiring customers who can't complete purchases.

False positive fraud declines create the most damaging revenue loss. When fraud screening blocks legitimate customers (false positives), you lose revenue from real buyers trying to spend real money. If 30% of your 25% decline rate stems from fraud filter blocks, and 40% of those are false positives, you're blocking 3% of all legitimate customers - costing $300K annually on $10M volume. Fraud scoring optimization recovering those false positives while maintaining fraud prevention generates immediate revenue recovery.

Competitive disadvantage compounds from poor decline rates. Merchants with 25-30% decline rates face 15-30% lower conversion than competitors achieving 15-20% decline rates. In competitive markets where customer acquisition is expensive, the business with better approval rates wins - they extract more revenue from identical traffic, achieve better unit economics, and can afford higher customer acquisition costs. A high-risk merchant improving decline rate from 28% to 19% gains 12.5% more revenue per visitor, enabling 10-12% higher acceptable CAC vs. competitors.

Illustrative example — not a specific client engagement.

• A supplement merchant with 28% decline rate analyzed codes: 62% were "05-Do Not Honor." Investigation revealed their single PSP had poor relationship with issuing bank responsible for 40% of their customer base. Implemented multi-PSP routing sending problem BINs to alternative acquirer. Decline rate dropped to 21% within 30 days, recovering $420K annual revenue on $6M volume.
• A gaming operator set fraud scoring threshold at 65 (auto-decline above 65). Decline rate was 26%, with 8% from fraud blocks. Analyzed and found 35% of fraud blocks were false positives (real customers flagged by overly aggressive rules). Adjusted threshold to 75 and added manual review for 65-75 scores. Decline rate dropped to 21%, recovering 5% of volume ($400K annually on $8M).
• An online course platform ignored decline monitoring. PSP experienced partial outage causing decline spike from 18% to 42% for 6 hours (prime sales period). Lost $48K revenue before noticing. Implemented real-time alerting (trigger at 22% decline rate). Next PSP issue caught within 15 minutes, switched traffic to backup PSP, prevented $40K+ losses.

• Track decline rate by code - analyze top 5 decline codes monthly to identify specific improvement opportunities (route 05s differently, reduce 59s with 3DS)
• Implement cascading for soft declines - automatically retry through backup PSPs, recovering 10-15% of declines with no customer friction
• Optimize fraud thresholds quarterly - A/B test fraud score cutoffs to find balance point: every 1 point change affects 0.5-1% of volume
• Route by BIN intelligence - send cards to PSPs with best approval rates for specific issuing banks (8-12% improvement on optimized segments)
• Monitor real-time with alerts - trigger investigation when decline rate exceeds baseline by 10%+ (e.g., normal 22%, alert at 24.2%)
• Manual outreach for high-value declines - proactively email/call customers with $300+ declined orders offering payment assistance
• Distinguish soft vs. hard declines in reporting - track separately to measure cascade effectiveness and identify permanent vs. temporary issues
• For $500K+ monthly: negotiate fallback with backup PSPs - automatic routing to backup during primary PSP outages prevents 100% decline spikes

• Not tracking decline codes - operating blind to whether declines stem from insufficient funds vs. fraud flags vs. technical issues
• Treating all declines as lost sales - not distinguishing between retryable soft declines (cascade these) and permanent hard declines (contact customer)
• Over-aggressive fraud screening - auto-declining 8-12% of transactions based on fraud scores without manual review recovering false positives
• Single PSP routing - accepting 25-30% decline rates when multi-PSP routing with smart BIN-based selection could reduce to 18-22%
• Not monitoring decline trends - missing sudden spikes (20% → 35%) indicating technical issues or PSP problems requiring immediate attention
• Ignoring high-value declines - treating $50 declined order same as $500 declined order when $500+ declines warrant manual customer outreach