Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Stripe keeps blocking payments from customers who are real

Short answer

Radar blocks a payment when a rule matches it: its own default rules, optional card-check rules you may have switched on, or custom rules someone added. A good customer can match any of them. Find the rule that blocked a real payment, then narrow or switch that one rule to review instead of turning Radar off.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A customer I know tells me their card was declined, but their bank says it did nothing.
  • I see blocked payments in Stripe for people who are clearly real buyers.
  • Sales dropped after someone changed fraud settings, and nobody remembers what changed.
  • A whole country, card type or large order keeps failing at checkout.
  • Payments are piling up in a review queue and customers are waiting.

Why does this happen?

  1. Radar blocks the highest-risk payments by default

    Every transaction is screened by Radar's default rules. One of them blocks payments with the highest risk level and does not process them, and by default Stripe requires review of payments it considers elevated risk. A genuine customer who looks unusual to the model can land in either group.

  2. Card-check rules can block what the bank approved

    A payment can succeed even when the CVC or postal code check fails, because card issuers weigh many factors. Radar offers rules that block certain payments the issuer approved, and when they are on they also affect attaching a card to a customer. If someone switched them on, honest customers with a typo or a wallet-less checkout can be refused.

  3. A custom rule can be too broad

    Custom rules are written on payment attributes such as country, card type or amount. Stripe's own example is a rule that blocks every card issued outside one country, which it calls too broad because it blocks many legitimate payments. Only the account owner, administrators and developers can create rules, so check who changed them.

  4. Your Radar plan decides what you can see and change

    Custom rules, manual review and risk preferences are listed under the higher Radar plans, while Radar Lite and Standard are not listed with them. That is why one owner can tune the rules and another can only see that payments are blocked.

  5. A review queue can slow good customers down

    Payments placed in review are typically already processed, unless you capture later. Stripe warns that a review step with no natural delay before fulfilment can create a bottleneck for good customers, and that a review rule set too broad fills the queue.

What can I do about it today?

  1. Open one blocked payment and read whyIn the Stripe Dashboard, open a blocked payment of a customer you know is genuine and note which rule or risk level is shown. Change nothing yet. This tells you whether the cause is a default rule or one of yours.
  2. Find out who changed the rulesAsk your team or developer whether anyone edited Radar rules recently. Stripe keeps a rule activity log showing who created, edited, enabled or disabled each rule, for the past 180 days.
  3. Do not switch Radar off or add a broad allow ruleStripe says allow rules override your other rules and the default rules, and that they should be used sparingly. A hasty allow rule can let real fraud through and raise your disputes.
  4. Prefer a review over a block while you investigateIf you are unsure about a pattern, Stripe suggests a review rule first, then looking for false positives before deciding on a block rule. Refunds made from review are permanent, so approve or refund each payment deliberately.
  5. Tell the customer how to try againAsk them to check the card details and billing postal code, or to use another card. Do not ask for card numbers in email or chat.
  6. Write down examplesKeep the payment IDs of three or four wrongly blocked payments and the date. They make any change, or a question to Stripe, much faster.

When should I bring someone in?

  • Blocked good payments keep happening and you cannot tell which rule is responsible.
  • Your developer changed checkout or card collection at about the same time the blocks started.
  • You need rule changes but your plan or role does not let you make them.

How do I handle it?

  1. Trace each block to its ruleI take a sample of wrongly blocked payments and match each to the default rule, card-check rule or custom rule that stopped it.
  2. Check what your checkout sendsI look at whether your integration passes the data the rules rely on, such as postal code, customer and metadata, so good payments are not looking thinner than they should.
  3. Test before enforcingStripe lets a new custom rule run against recent payments and lets you set its traffic allocation to a shadow mode that reports what would have happened. I use that so a change is measured before it touches real customers.
  4. Move from block to review where it fitsWhere a rule catches both good and bad payments, I move it to review and set up the review events so the queue does not stall orders.
  5. Keep a written change recordEach rule change is noted with the reason and the check I made, so the next person can see why it exists.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I just turn Radar off?

I would not. Radar screens payments by default, and the default rules are what stop the highest-risk payments. Fix the specific rule that is wrong instead.

Will changing a rule fix payments that were already blocked?

No. Stripe states that rules only apply to future payments and not to ones already processed. A blocked customer has to try the payment again.

Can a review hold up my customer's money?

A payment in review is typically already processed, unless you capture authorized payments later. Whether it delays delivery depends on how your business ships or provides the service.

Can I see how a rule would have performed first?

On plans with custom rules, Stripe shows how a new rule performs against recent payments before you add it, and you can set a rule to evaluate without applying its action.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.