Loading saved preview data.

HomeBriefingBlocks

A Blocked Card Payment Is Not a Frozen Stripe Account

Stripe Radar blocks, 3D Secure failures and issuer declines hit one payment. Here is how to tell them from an account freeze or a disabled charge capability.

Updated 7 November 2026 · 9 min read · Blocks

On this page

Support inboxes fill with “Stripe blocked me” from merchants whose accounts are fine and whose last three payments were declined. The customer says the card was blocked. The merchant hears that their processor has frozen them. The dashboard, unread, still shows charges enabled. The repair is on the payment. The panic is about the account. Those are different afternoons.

Where a single block comes from

  • The issuer declines. Insufficient funds, a stolen-card suspicion at the bank, a limit, a international switch the bank refuses. Stripe did not take the money because the bank said no. Retrying ten times does not create a freeze. It can create a fraud pattern.
  • 3D Secure or another authentication step fails or is abandoned. The customer never completed the challenge. That is not a restricted account.
  • Radar, Stripe’s fraud tooling, blocks because a rule fired: high risk score, a country you excluded, a velocity rule, a block list, CVC or postcode failure if you require them. The payment is stopped before capture. The account remains yours.
  • A Stripe limitation on a payment method, for example a method not enabled in that country. Still an account configuration, not a freeze, unless the banner says the capability itself is inactive.

How to read one payment

Open it. Note the amount, the card country, the outcome, the Radar rule if one is named, and whether 3D Secure was attempted. If you can see a risk score, record the band, not a screenshot full of card digits. You do not need the full card number to understand a decline, and you should not export it to a chat.

Then ask a plainer question. Is this one customer, or fifty this morning? One customer is support and, if the rule was yours and wrong, a rule edit. Fifty, from one campaign, with fraud warnings attached, is a traffic problem. Pause the campaign. Do not open a second Stripe account to see if the traffic “works better” somewhere else.

The sentence that keeps the two problems apart

A frozen or restricted account is a state of the account: a banner, an email, a capability turned off for the whole account. A blocked payment is a state of one charge. You can have a week of blocked payments and a healthy account. You can have a frozen account on which no individual Radar rule ever fired — the payments simply are not allowed to be created, or payouts are not allowed to leave.

If you are writing to RevRouters, say which one you have. “Customers can’t pay” is the start. The next sentence should be either “the account banner says payouts are paused” or “charges are enabled and these payments show blocked by Radar / declined by the bank”. The assessment is different. In neither case is the remedy another business’s account.

Card numbers stay out of the ticket

When you ask anyone for help, send the payment identifier Stripe gives you, the outcome and the date. Do not send the full card number, the CVC or a photograph of the customer’s card. Nobody who can legitimately explain a decline needs those.

What this briefing is not

It is not legal, tax or card-scheme advice, and it is not Stripe’s policy. Your notice and Stripe’s terms control the account. RevRouters does not process payments, does not lift a freeze, and does not offer another business’s account as a remedy.

Questions on this note

Where do I see whether the account or the payment was blocked?

Open the payment. The outcome and the reason sit on that charge: blocked by Radar, failed authentication, declined by the issuer, or similar. Then open the account status or the banner. If charges are enabled and payouts are on their normal schedule, the account is not frozen. You had a payment problem.

Should I turn Radar off if good customers are blocked?

Look at the rule that fired before you loosen anything. A custom rule can be too broad and still be your rule. Turning protection off to lift a conversion rate also lifts fraud. Change the specific rule, watch the result, and do not “solve” blocked good customers by sending them to a second account with no rules.

Can lots of blocked payments freeze the account?

A pattern can draw a review: high block rates, fraud warnings, or customers retrying in a way that looks like fraud. The pattern is not itself the freeze. If a review starts, you will get an account state, not just a red payment.