A Stripe payment is a card or local payment method charge that Stripe checks, sends through the card network to the customer's bank for authorisation, and then captures so the funds reach your account. You see how those payments perform on the Payments analytics page in the Stripe Dashboard, which has reports on acceptance, authentication, disputes and payment methods.
Here's what most people miss. A payment can fail before the customer's bank ever sees it. Stripe Radar can block a high risk payment, and a customer can fail 3D Secure authentication, and both of those count against your payment success rate but not against your authorisation rate. So if your numbers look worse in one report than another, it's usually because the two rates count different things, not because something's broken.
How a card payment moves through Stripe
Stripe's own guide to how cards work splits an online card payment into four stages. Knowing them helps you read every report that comes later, because each failure reason belongs to one of these stages.
- Checking card details. Stripe checks the details are formatted correctly, for example that the expiry date isn't in the past. There's no guarantee yet that the card itself is valid.
- Customer authentication. Some banks, especially in regulated regions such as Europe and India, ask the customer to confirm the purchase, for example with a code sent by text.
- Authorisation. The bank checks for sufficient funds and, if that works, holds the amount on the customer's account to guarantee it for you.
- Capture. The funds move from the issuing bank to your account. An authorised payment isn't the same as a captured one, and Stripe's acceptance data counts authorisations whether or not you went on to capture them.
Success rate or authorisation rate: which one to watch
The Acceptance page in the Dashboard lets you switch between two rates, and as of October 2026 they're calculated like this.
| Rate | What it measures | What it leaves out |
|---|---|---|
| Payment success rate | Charges authorised by the card network divided by every unique payment attempt submitted through Stripe | Only invalid API calls. Failed 3DS, blocked payments and issuer declines all count against it |
| Authorisation rate | Payments authorised by the issuer divided by attempts that reached the card network | Invalid API calls, failed 3D Secure and blocked payments, because those fail before Stripe asks the issuer |
| Raw rate | Every attempt, including retries of the same purchase | Nothing, so a customer who retries after a wrong CVC drags it down |
| Deduplicated rate | Retries grouped together and judged on the final outcome | Earlier failed attempts on the same purchase |
Stripe's worked example makes the gap clear. Out of 103,000 payment requests, 3,000 were invalid, leaving 100,000 valid ones. Another 1,000 failed authentication and 1,000 were blocked, so 98,000 reached the card network and 93,000 were authorised. Same 93,000 approvals, two different rates. Data is processed daily and shown in UTC, which is worth remembering if you're matching it against your own sales report.
Why Stripe payments get declined
Once a payment reaches the bank, the issuer decides. Stripe passes on the reason the issuer gives, but many payments come back as generic declines, and the most common is a plain refusal shown as a don't honour response. For privacy and security, card issuers only discuss the specific details with their cardholders, not with you or Stripe.
| Decline reason | What Stripe suggests |
|---|---|
| Generic response, such as don't honour | Ask the customer to contact their card issuer or try a different payment method |
| Incorrect card information | Make sure automatic card updates are on and ask the customer to re-enter their details |
| Insufficient funds | Ask for a different payment method, or get the customer's approval to retry later |
| Lost or stolen card | Retries won't succeed, and don't tell the customer the reason, in case they're not the real cardholder |
| Transaction not allowed | The customer has to contact their issuer; retries are unlikely to work until they do |
Payments Stripe blocks before the bank sees them
The blocked payments report shows why Stripe stopped a payment. Radar can block on a rule you set up, on a rule that needs the issuer's response first, such as a postal code or CVC check, or by default because of a high risk score that Radar works out using AI. You can adjust the minimum score it blocks. Stripe also blocks cards on deny lists known to be fraudulent, payments from sanctioned countries and payments it suspects are card testing. If you're on IC+ pricing, Adaptive Acceptance can block payments that have a low chance of being authorised, to avoid network costs and retry penalties.
One detail surprised me. When Radar blocks a payment after authorisation, Stripe gets initial authorisation from the card issuer but doesn't charge the card. A failed CVC check is also worth taking seriously, because Stripe says it might point to fraud and you should review the order before you fulfil it.
The quiet features that rescue payments
Authorization Boost is Stripe's name for the features that try to lift success rates on card-not-present payments. Adaptive Acceptance uses AI to reformat requests to suit each card issuer and can retry declined payments in real time. The card account updater pulls new expiry dates and card numbers from the major networks, and network tokens act as more secure stand-ins for card numbers that keep working when the card changes.
Automatic card updates are widely supported in the United States, where Stripe can update most American Express, Visa, Mastercard and Discover cards. International support varies by country, and there's no way to tell in advance which cards support it. Also note that editing a saved card can only change its name, billing address, expiry date or metadata. Anything else means deleting the card and adding a new one. The Optimization page shows estimates, and Stripe is clear they're not guarantees.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
What happens after the payment
If you take payments through Stripe Checkout, the after-payment options are where the customer experience lives. Stripe's docs cover fulfilling orders and shipping products, showing a confirmation page with the customer's order details, recovering abandoned checkout pages, sending payment or refund receipts by email, and analysing your Checkout conversion funnel with Google Analytics 4. Refunds are their own topic, and I've covered them in my guide to refunding a Stripe payment.
My verdict on Stripe payments
I'd watch the payment success rate if you want the honest picture of how many customers who tried to pay ended up paying, and switch to the authorisation rate only when you're judging how banks treat you. I'd turn on automatic card updates if you sell subscriptions, because outdated card details are a common cause of declines. Skip chasing the bank for decline reasons; they won't share them with you, so give the customer another way to pay instead. For the wider view of your account, my walkthrough of the Stripe Dashboard sections is the next stop.
If your team spends hours each week digging through payment reports by hand, that's the kind of job worth automating. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.
Frequently asked questions
What's the difference between Stripe's payment success rate and authorisation rate?
The payment success rate counts every valid payment attempt, including ones that failed 3D Secure or were blocked. The authorisation rate only counts attempts that reached the card network, so it's usually higher.
Why won't Stripe tell me why a card was declined?
Stripe passes on whatever reason the issuer gives, but many declines are generic. Card issuers only discuss specific details with their own cardholders, not with you or Stripe.
Does a blocked payment charge the customer?
When Radar blocks a payment after authorisation, Stripe gets initial authorisation from the card issuer but doesn't charge the card.
Do saved cards keep working when a customer gets a new card?
Often, yes. Stripe works with the card networks to update saved card details automatically, and this is widely supported in the United States. International support varies by country.
Where do I see Stripe payment analytics?
On the Payments analytics page in the Stripe Dashboard, which has reports on acceptance, authentication, disputes and payment methods. Authentication analytics need 3D Secure turned on.
