On this page
In short
- A blocked payment never goes to the card issuer.
- The Add to allow list button does not retry the payment.
- Allow lists and rules apply only to future payments.
What a block is
Stripe says Radar evaluates each payment and blocks high risk ones, including those that break your custom rules or have high risk scores, and that this happens without any action from you. When Stripe blocks a payment it does not ask the card issuer for authorization. In the API the outcome says the charge was blocked as too risky. Stripe's default rules also send payments with elevated risk to a review queue, where the payment still goes through for a person to look at.
Why good customers get blocked
Stripe says its default rules use AI risk levels and, for some accounts, account-level models. You can also turn on card check rules that block when the CVC or postal code check fails. Stripe explains that a payment can succeed even if those checks fail, because issuers weigh many factors, so these optional rules can block payments the bank would have approved. Custom rules that are too broad can have the same effect, and Stripe says they can negatively affect your business if set up poorly.
What to do tonight
- Find the payment in the Dashboard and read the reason Radar gave.
- If a rule you set blocked a customer you recognize, click Add to allow list on the payment. Stripe says this overrides your other rules for future attempts matching that attribute, but does not retry the payment. If you do not see the button, Stripe says to contact it.
- Ask the customer to try again, or take another payment method.
- Review your rules. Stripe's rule editor tests a new rule against recent payments, and its example block rule on all non-US cards was called too broad.
Worked example
Example: a local customer buys a $400 item and is blocked after a typo in the postal code. The shop has the optional postal code rule turned on. The owner adds the customer's card to a trusted list, narrows the rule so it blocks only when risk is also elevated, and asks the customer to pay again. Stripe lists allow list entries on default fingerprint lists as lasting at most 30 days, so the owner checks the list again later. Details are invented.
What to avoid
- Do not write broad allow rules. Stripe says they override its default rules and your other rules, and suggests adding that risk level is not highest.
- Do not turn on a block rule you have not tested. Stripe suggests starting with a review rule, or rolling out gradually with traffic allocation.
- Do not tell the customer why they were blocked. Stripe advises presenting fraud-related declines like a generic decline.
Pricing note: Stripe lists Radar from $10.00 a month or from 5 cents per screened transaction, as of 2026-11-08.
How a second way to take cards helps
MazalPOS payments run through your store's own Stripe account, so Radar and your rules still apply to card payments. When a good customer is blocked, the register can take cash, another card, or a pay link (3% fee) so the sale is not lost, and the sale stays on one ticket. See payments.
Common questions
Stripe says Radar blocks payments it rates high risk or that break a rule. The payment page shows the reason.
No. Stripe says Add to allow list does not retry it. It only stops future matching payments from being blocked by your rules.
Yes. Stripe says the rule editor tests a rule against recent payments and lets you set a traffic percentage or 0% to observe only.
No. Radar runs inside your own Stripe account.
Sources
Checked on 2026-11-08. Rules and prices change, so confirm on the official page before you act.
Related
Stripe declined payment: why cards get declined and what to doStripe chargeback: what to do when a customer disputes a paymentStripe fees explained: what a sale really costs
Written by Mike Akop, founder of MazalPOS. We build and support the register, online store and staff app that stores from Las Vegas to Honolulu run on. Questions? Talk to a real person.
