
When Stripe reports a declined payment, one of three things happened. The customer's bank refused the authorization, Stripe Radar blocked the payment before it reached the bank, or your integration sent a request Stripe could not process. Each one has a different owner and a different fix, so the first job is to sort each failure into the right group. Stripe's outcome object on every charge tells you which group a decline belongs to.
Most issuer declines come back as generic_decline or do_not_honor, and the bank tells only the cardholder why. You can't overturn those. What you can control is your Radar rules, the card data your checkout collects, how your integration retries, and how fast someone notices when the decline rate moves. With Black Friday on 27 November 2026 and Cyber Monday on 30 November 2026, this week is the time to set a baseline and agree who looks at failed payments during peak.
outcome.type before you change anything.generic_decline and do_not_honor mean the bank gave no reason. Stripe's advice is for the customer to contact their card issuer.blocked with network_status: "not_sent_to_network". These are the declines you can tune.Stripe's peak-season guide for 2026 reports figures from the 2025 holiday period. Stripe processed up to 152,000 transactions per minute during Black Friday and Cyber Monday 2025, and fraud started rising from 8 November that year. The guide also says many shoppers do not try again after a declined payment. Stripe concludes that fraud tools set too tight can cut revenue during the busiest sales days of the year, and the loss does not show up as an error anywhere.
The underlying mechanics haven't changed. According to Stripe's declines documentation, the issuer's automated systems decide whether to authorize based on spending patterns, account balance and card data such as expiry, address and CVC. Radar sits in front of that and blocks high-risk payments, for example those where the CVC or postal code does not match. When Stripe blocks a payment, the issuer never sees it.
During peak you get more traffic, more card testing and more first-time customers, and issuers apply more scrutiny. A decline rate that sits steady most of the year can move in either direction. A sudden rise might come from a card-testing run, a checkout change that stopped sending postal codes, or a Radar rule that is too strict for gift buyers shipping to a different address. Without a baseline from this week, you will not know which.
Work through these in order. The first two steps take about 15 minutes in the Stripe Dashboard.
outcome.type. Put each failure in one of three groups: issuer_declined (the bank said no), blocked (Stripe said no before the bank saw it) and invalid (your integration sent something wrong). If you only use the Dashboard, the payment detail page shows the same outcome and a seller message such as "Stripe blocked this charge as too risky."issuer_declined, count the decline_code values. A mix dominated by insufficient_funds, expired_card and generic_decline with no sudden change is normal background. A jump in incorrect_cvc or incorrect_zip points at your checkout form or address fields. A spike of many small declines from new cards points at card testing.advice_code. Stripe returns do_not_try_again, try_again_later or confirm_card_data. Make sure your integration, and any subscription or retry plugin, respects do_not_try_again.invalid failures first. These are bugs. They usually point to a plugin update, an API version change or an expired key, and every one of them is a lost order that the customer cannot fix by trying again.outcome.type and the top five decline codes. During peak, compare against these numbers.| Signal | Likely cause | Owner | Check | Frequency during peak |
|---|---|---|---|---|
Rise in blocked, risk_level "highest" |
Card testing, or a rule tuned too tight | Store owner or fraud lead | Sample 20 blocked payments; look for repeated small amounts and new cards | Twice daily |
Rise in incorrect_cvc or incorrect_zip |
Checkout form change, address autocomplete bug, theme update | Developer or agency | Place a test order with a real card; confirm CVC and postal code reach Stripe | After every deploy |
Any invalid outcomes |
Integration error, expired key, API version mismatch | Developer | Read the error message in the Dashboard logs | Hourly alert, daily review |
Rise in authentication_required |
3-D Secure not completing on some flows | Developer | Test checkout on mobile and with saved cards | Daily |
Rise in generic_decline across many customers |
Issuer-side behaviour, or Radar or Adaptive Acceptance blocking (Stripe's code description covers both) | Store owner | Compare against baseline; check outcome.type for each |
Daily |
fraudulent, lost_card, stolen_card |
Stripe or issuer fraud signal | Store owner | Show the customer a generic decline message only | Weekly |
Paste this into your team's runbook or ticket system and assign each line.
STRIPE DECLINE REVIEW, BLACK FRIDAY WEEK
Store: ______________ Owner: ______________ Backup: ______________
BASELINE (record before 24 Nov 2026)
[ ] Decline rate on unique attempts, last 7 days: ____ %
[ ] Share by outcome.type: issuer_declined ____ % | blocked ____ % | invalid ____ %
[ ] Top 5 decline codes: ______________________________
DAILY CHECK (27 Nov to 1 Dec 2026, morning and evening)
[ ] Decline rate vs baseline. Escalate if it moves by more than ____ points
[ ] Any invalid outcomes since last check? If yes, ticket to developer now
[ ] Sample 10 blocked payments. Any real customers? Note rule name
[ ] incorrect_cvc / incorrect_zip trend flat?
[ ] Small repeated attempts from new cards? If yes, follow card-testing runbook
AFTER ANY DEPLOY OR PLUGIN UPDATE
[ ] One live test payment with a real card, refunded afterwards
[ ] Confirm postal code and CVC appear on the Stripe payment detail page
CUSTOMER MESSAGE FOR DECLINED CARDS (do not reveal fraud or lost/stolen reasons)
"Your bank declined this payment. Please check the card number, expiry date
and security code, try another card or payment method, or contact your bank
to approve the purchase. You have not been charged."
Check the last sentence of the customer message with your gateway setup. If you place authorizations and capture later, a customer may see a pending authorization on their statement, so word that line to match how your store charges.
An agency maintains a WooCommerce store that sells kitchen textiles. On 20 November the store owner says customers are emailing about rejected cards. All figures below are invented for illustration.
The agency exports 7 days of failed payments. On unique attempts the decline rate is 9%, against 6% in the same week of October. Split by outcome, issuer_declined is flat. All of the increase sits in blocked.
Twenty sampled blocked payments show a pattern. Most are full-price orders shipping to an address different from the billing address, with Radar's risk level "elevated" or "highest". A custom rule added in the summer blocks every payment where the shipping and billing countries differ. In November, more customers are sending gifts abroad.
The agency backtests a narrower version of the rule against 6 months of payments, then runs it on part of the traffic for two days and watches the blocked count and dispute notifications. The blocked share returns close to the October level. The agency writes the new baseline into the runbook and sets a reminder to review the rule again in January, after returns and disputes from the peak have come in.
The issuer declines in the export stay at the same level after the change, which is expected, since those decisions sit with the customers' banks.
blocked and invalid.fraudulent, lost_card and stolen_card as a generic decline.advice_code. Card networks limit retries, and Stripe warns that extra attempts can raise declines for legitimate payments.incorrect_zip or in blocks, and the first sign may be customer complaints.Limitations: this procedure tells you where declines come from. It does not raise issuer approval rates, and no setting in Stripe will make a bank approve a card it has declined. Decline rates also vary by product, region and customer mix, so compare against your own baseline rather than a number from another store. Adaptive Acceptance blocks, which Stripe's documentation lists as low_probability_of_authorization, apply only on some pricing plans.
generic_decline mean in Stripe?Stripe's decline code reference says the card was declined for an unknown reason, or that Radar or Adaptive Acceptance blocked the payment. Check outcome.type to tell which. If it is issuer_declined, the customer needs to contact their bank, because issuers share decline details only with the cardholder.
Usually not. Stripe passes on the decline code and, where available, network_decline_code and network_advice_code, whose meaning varies by card network. The full reason stays between the bank and the cardholder.
Switching rules off wholesale is risky, because card testing and fraud attempts rise in the weeks before peak. Instead, review blocked payments, find the specific rule catching good customers, test a narrower version against past payments, and roll it out to part of the traffic first.
The daily check above depends on someone noticing a change. If your store runs WooCommerce, Pingvera's WordPress connector sends order.created and order.failed events in real time, and its anomaly detector compares order flow with an hourly baseline and alerts when the site is up but orders have stopped. Deploys and incidents sit on the same timeline, so a checkout update and a drop in completed orders appear next to each other. It does not read Stripe decline codes; the Dashboard review in this article still covers that.
For related checks, see how to detect a card testing attack, what a spike in WooCommerce failed orders means, and how to plan for a payment gateway outage. For the wider trade-off between blocking fraud and losing sales, read fraud controls vs conversion.
Last reviewed: 19 November 2026
Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.
Start freeRead next: Card Testing Attack on Your Online Store: Detect Stop and Clean Up Before Black Friday · WooCommerce failed orders: what a spike a stall and a silence each mean.
Read next: Merchant Center Misrepresentation: Fix It Before Peak · Stripe API Version Upgrade: A Safe Pre-Peak Plan · PayPal IPN Not Working: Fix Stuck Orders Before Peak · WooCommerce Not Sending Order Emails: Fix It Before Peak · Run a free site check.