Skip to main content

A Guide to Stripe Radar for Fraud Protection

By Gruv Editorial Team
Contributor
Updated on
•
18 min read
Route fraud signals through two decision layers: Risk signal, AI score, Business rule, Review queue, and Payment action.

Quick Answer

Start with your enabled Stripe Radar controls and a separate order-release check. Review eligible card payments when a human can add value; ACH and SEPA require supported Allow/Block rules and internal delivery checks. Keep custom Allow overrides narrow, backtest changes, and monitor mature dispute cohorts alongside review workload.

Stop letting one bad payment break your month#

Stripe Radar screens payment risk, but your business must decide when to release work, goods, or access. Start with the controls available on your plan, assign an owner to unusual payments, and connect payment state and fraud decisions to fulfillment. A low risk score cannot make a payment irreversible.

Protect margin while keeping good clients moving#

A small team needs a manageable review queue and clear delivery rules. Broad blocking can reject good clients; broad allow rules can bypass protections.

Decision pathUse it whenOperational move
BlockA payment matches clear high-risk patterns you do not want to serviceDecline and stop fulfillment immediately
ReviewSignals look mixed and manual judgment can prevent a costly mistakeFor supported card payments, review evidence and pause delivery in your own order system
Normal processing or narrow Allow ruleRisk signals look normal and customer context checks outCheck actual payment state and fulfillment policy; monitor later disputes

You can do a practical first pass in a focused setup session if you keep scope tight. Start with a small ruleset, define who reviews flagged payments, and set a clear response standard. Then tune your rules on a regular cadence based on account results to cut false positives and protect good revenue.

Hypothetical example: a new card client requests urgent delivery after a USD 2,000 payment is flagged for review. The charge can already be processed, so your order system holds the final files while the owner checks authorization and client context. Approving the review closes that review; it does not erase later dispute risk.

What is known and what you should verify#

Radar supports allow and block rules across supported methods. Its manual transaction-review queue currently excludes ACH and SEPA Direct Debit, so those methods need an internal fulfillment check rather than a Radar Review rule.

What you should verify in your own account: the exact setup time for your workflow, what improvements you can actually expect, and any market-specific limits that affect how you manage risk.

Keep an audit-friendly log of every rule change, who approved it, and what happened after the change. If chargeback pressure already affects client work, pair this setup with How to Protect Yourself from Chargebacks as a Freelancer.

Build the mental model before touching settings#

Separate the risk signal from your business response. Radar evaluates a payment; supported rules request authentication, allow, block, or flag it for review. Your delivery system must enforce any fulfillment pause independently.

Stripe’s risk-settings documentation retains a classic 0–99 risk score and now recommends risk settings and controls rather than assuming fixed score thresholds. Check which controls are active in your Dashboard; do not treat 65 and 75 as universal current cutoffs.

Separate scoring from policy#

Keep these roles clear before you touch settings:

LayerWhat it doesWhat you decide
Stripe Radar scoringEstimates fraud likelihoodHow much weight you give the score
Radar RulesApplies supported authentication, Allow, Block, or Review actionsWhich business conditions trigger each path
Plan capabilitiesCurrent Plus and Pro plans include custom rules and transaction reviewsWhen baseline behavior no longer fits your risk management needs

Stripe’s current plan comparison lists Lite, Standard, Plus, and Pro. Custom transaction rules, backtesting, and manual transaction reviews are in Plus and Pro. Older materials use “Radar for Fraud Teams”; confirm your account’s current plan and enabled methods before designing around that label.

Use network and issuer signals as inputs#

Adaptive 3D Secure can request additional card authentication. Tune optional requests to your risk and conversion results, while preserving authentication required by an issuer or regulation. 3DS is not available on ACH or SEPA Direct Debit and does not protect against every kind of dispute.

SignalStated useWhat not to assume
Early fraud warningIssuer notification of suspected fraud on an existing card paymentNot a dispute or proof that a refund will prevent one
Visa TC40A report source for early fraud warningsNot a separate pre-payment screening stage
Mastercard SAFEA report source for early fraud warningsNot an additional guarantee of recovery
Pre-dispute notificationA separate notification or prevention product, where enabledNot automatic coverage for every network, reason, or payment method

Early fraud warnings come from issuer reports such as Visa TC40 and Mastercard SAFE. These concern an existing payment, so they are follow-up signals rather than inputs you can always use before acceptance. Check the affected charge, delivery state, and any dispute before deciding whether a refund or other action is appropriate.

Hypothetical example: an early fraud warning arrives after a card charge. The operator checks whether files have been delivered and whether a dispute already exists, contacts the client through a known channel, and records the decision. The warning does not create a new Radar review or guarantee that refunding will avoid a dispute.

When should you block review or allow a payment#

Block known attack patterns, review ambiguous payments fast, and allow repeat low-risk behavior only after your controls stay stable. Now you turn the scoring model into day-to-day decisions so fraud protection protects cashflow instead of slowing good clients.

Use the account’s enabled risk controls as a baseline. For ACH and SEPA, use supported Allow/Block rules and your internal delivery workflow. For card payments, a review rule can add a successful or to-be-captured payment to Radar’s review queue; it does not automatically stop processing or fulfillment.

Choose the action by downside risk and decision speed#

ActionBest fitWhy it worksOperator move
BlockClear attack signals like card testing or other repeat abuse patternsManual review adds little value when loss risk stays highDecline, log pattern, and move on
ReviewHigher-value payment with unclear identity or delivery riskYou keep optionality while protecting marginPause fulfillment, verify quickly, then approve or refund
Normal processing; exceptional Allow ruleRepeat customer behavior that stays clean over time, where your controls support itYou preserve conversion and reduce frictionUsually keep standard protections; test any narrow Allow override separately

A card-only review candidate might target prepaid cards above USD 1,000. The amount is an illustrative business threshold, not a recommended global cutoff. Backtest the predicate against your own payments and check that resulting review volume fits the owner’s capacity before enabling it.

Set rule order and exception policy before you scale#

Radar evaluates action types in order: Request 3DS, Allow, Block, then Review. A 3DS request does not end evaluation. An Allow match can bypass later block and review checks, so moving a block rule visually above an allow rule is not a safety fix. Normal low-risk processing usually needs no custom Allow rule.

Policy elementWhat to define
OwnerOne person approves overrides
Allowed override casesList narrow edge cases you accept
Evidence requiredNote payment context and customer verification
Post-action logRecord reason, action, and result for audit and weekly tuning

Before you scale, define a lightweight exception policy: one person approves overrides, allowed override cases stay narrow, required evidence includes payment context and customer verification, and every action gets logged for audit and weekly tuning.

Hypothetical example: a returning card client triggers a review rule. The owner verifies the changed payment context, checks capture and payment status, approves the review if justified, and explicitly releases the order. A good history supports investigation; it does not justify permanently bypassing risk controls. See Freelance Chargeback Protection for evidence and dispute handling.

How should your risk strategy change for cards vs ACH and SEPA#

Use method-specific release policies. Cards can authorize quickly but remain disputable; bank debits are asynchronous and can fail or be disputed after an initial success. Radar’s ACH and SEPA support does not add a manual transaction-review queue for those methods.

Stripe Radar uses card-network and bank information to assess fraud risk, including signals tied to Visa, Mastercard, and American Express ecosystems. For many card transactions, that can support faster fulfillment decisions.

Use the actual ACH settlement schedule and SEPA timing, not one “up to four days” limit. Stripe says to wait at least six business days before considering a SEPA debit successful. That still does not eliminate later dispute rights.

Set method-specific gates#

Fulfillment gate is the point where you release irreversible work, goods, or access.

Payment methodRisk behaviorSettlement behaviorSafe default gate
CardsRisk signals and eligible authentication help with acceptanceAuthorization, capture, balance availability, and bank payout are separateRelease only after the required payment state and any review approval; retain dispute evidence
ACH Direct DebitAllow/Block rules; no Radar manual transaction reviewAsynchronous funding; failures and later returns remain possibleUse the account-specific payment state and an internal review for high-impact delivery
SEPA Direct DebitAllow/Block rules; no Radar manual transaction reviewMost failures surface within six business days; later disputes remain possibleSet a delivery policy that considers timing, mandate evidence, and recoverability

Waiting for settlement reduces some failure exposure but does not make a debit final. SEPA customers can dispute without giving a reason within eight weeks; unauthorized debits can be disputed up to 13 months. ACH also has return and dispute rights that depend on account and reason. Preserve mandate and delivery evidence and maintain a recovery budget.

Communicate timing before friction starts#

Set expectations before the client pays. Tell clients that payment method affects fulfillment timing and that review checks protect both sides from avoidable fraud and failed-payment risk.

Use a simple operator script:

  • Confirm payment method in your intake or invoice notes.
  • State the fulfillment gate for that method before work starts.
  • Use Radar review for supported cards; use an internal delivery check for ACH/SEPA, and log the decision.

Hypothetical example: a new client pays an urgent invoice by SEPA. Your order system keeps the debit pending while the team verifies mandate and client context, explains the expected timing, and decides how much reversible work can begin. No Radar Review rule is assumed, and reaching a settlement date does not erase later debit disputes.

Want a quick next step while you put these gates in place? Try the free invoice generator to tighten up your billing workflow.

Launch your first safe default in day 1 and harden it by day 30#

Start with Stripe Radar defaults, add a minimal rule set, and only tighten controls after your own review and backtesting confirm the tradeoff. If you've already separated fulfillment gates, use a practical 30-day loop to improve fraud protection, protect margin, and keep good revenue moving.

On day 1, inspect the enabled Radar plan and risk controls, then define the order-release check. Default screening can run through Stripe, but connecting fraud review to an automated delivery system requires your own configuration or integration.

For card payments, inspect whether the elevated-risk review rule is enabled and supported on your plan. Do not apply that review-queue assumption to bank debits.

Use a 30-day hardening loop#

PhaseFocusWhat to doDecision rule
Day 1Safe baselineKeep native Stripe Radar protections enabled. Add a few targeted rules for card testing bursts and other clear abuse patterns. Define a conservative handling step for suspicious high-risk payments before irreversible delivery.If a rule does not protect a known risk, do not ship it yet.
Day 7Signal qualityReview queue outcomes, suspected false positives, and early warnings; retain cohorts for later dispute maturationChange one logic cluster at a time so you can attribute impact.
Day 30Structured promotionBacktest candidates, examine legitimate matches and owner capacity, and enable justified rules gradually with a rollback planThirty days is a suggested review cadence, not proof that disputes or false positives have fully matured

Internally, keep your runbook short and strict:

  • Owner: one person approves urgent rule changes.
  • SLA: set a response target for payment reviews.
  • Escalation path: define who handles edge cases when volume spikes.
  • Change log: record what changed, why, and the observed impact.

Example: card testing volume jumps and a new client submits a large first payment. Your runbook tightens controls on the attack, holds irreversible fulfillment until your gate clears, and keeps the process consistent under pressure. That is mature risk management, not reactive firefighting.

What should you measure every week to reduce fraud without choking growth#

Review a weekly scorecard before changing rules. Compare like-for-like cohorts by payment method, age, amount, and customer history: disputes can arrive weeks later, and a blocked attempt is not proof of fraud.

MetricWhy it mattersSegment it byWhat to do when it worsens
Approved payments that later become fraud disputesShows where risk slips through your allow pathACH, SEPA, and card rails such as Visa and MastercardInvestigate cohort and reason; change targeted acceptance or delivery controls if evidence supports it
Blocked payment attemptsMeasures blocked activity, not confirmed fraud preventedPayment method and high-risk customer cohortsInvestigate attack bursts and legitimate-client impact before tightening
Payments sent to reviewMeasures manual workload and queue pressureMethod, amount band, first-time vs repeatReduce noisy triggers and keep only high-value ambiguity in review
Estimated false positive rate on block rulesStripe’s modeled estimate can highlight rejected legitimate traffic; it is not verified ground truthMethod and key rule familiesLoosen or narrow rules that block legitimate traffic
Early fraud warning and pre-dispute volumeGives early risk signals before formal disputesCard network patterns including TC40 and SAFE linked flowsInvestigate affected charges and delivery state; do not assume every warning becomes a dispute

Run a weekly audit that ties risk to cashflow#

Review trends over time in Stripe Radar analytics, then compare fraud metrics with business outcomes. Track delayed fulfillment, refund or recovery outcomes, and support load so risk decisions stay tied to cashflow reality.

Use this short audit checklist:

  • Remove stale rules that no longer map to current attack patterns.
  • Check action-type precedence and narrow any Allow rule that bypasses intended protections.
  • Compare ACH and SEPA drift separately from card behavior.
  • Log every rule change with reason and expected impact.

Hypothetical example: card results are stable but a mature SEPA cohort shows more disputes. Investigate the debit mandates, client segments, and fulfillment decisions; test targeted SEPA Allow/Block changes and update the internal release check. Keep card controls stable unless their own evidence calls for a change.

Check plan capabilities and operating costs before upgrading#

Upgrade when the added controls solve a defined problem and someone can maintain them. Compare review workload, losses, legitimate acceptance, and screened-transaction costs before making a plan decision.

What you can treat as known right now#

AreaWhat is knownWhy it matters
Custom controlsCurrent Stripe docs list custom transaction rules in Plus and Pro; verify the enabled account plan.You need the right plan before you design rule logic.
AI baselineRisk controls depend on plan and configuration; inspect current settings rather than assume universal score cutoffs.You start with a working baseline before adding manual logic.
Payment methodsCards, ACH and SEPA are supported, but bank debits lack Radar manual transaction review.You can design method-specific controls without treating every rail the same way.
Rule executionRule hierarchy matters because action type affects evaluation order.Bad ordering can block good payments or let risky ones pass.
Commercial modelPaid-plan fees depend on screened transactions and account terms; some subscription renewals may be skipped by configuration.You must model cost against volume before rollout.

What you still need to verify before commitment#

AreaWhat to confirm
PricingExact pricing for your account country and entity
Tier boundariesDetailed tier boundaries and any account-level limits
EligibilityEligibility and payment-method support for your market and program
Performance claimsMeasurement windows behind performance claims
ComplianceIf you sell across borders, validate compliance constraints, including EU geo-blocking limits where relevant

Before you commit, confirm exact pricing for your account country and entity, detailed tier boundaries and any account-level limits, eligibility and payment-method support for your market and program, the measurement windows behind performance claims, and any compliance constraints that apply if you sell across borders, including EU geo-blocking limits where relevant.

Hypothetical example: a trusted client’s bank debit is blocked by a broad rule. The owner checks the reason and mandate, tests a narrower future rule, and agrees a legitimate payment route with the client if needed. Changing a rule does not retroactively process the blocked payment; resolve its state before retrying.

Use this go-live checklist for chargebacks control:

  • Log each rule decision with action path, reason, approver, and fulfillment outcome.
  • Require a written reason for every manual override.
  • Keep method-specific playbooks for card, ACH, and SEPA so operators act consistently.
  • Approve rollout only after your Stripe dashboard and account docs resolve every unknown above.

Run Stripe Radar as a repeatable operating rhythm#

Keep acceptance decisions and delivery decisions connected. A sustainable review queue, a tested method-specific release policy, and traceable rule changes protect cashflow without relying on maximum blocking.

Start with built-in Stripe Radar protections, then layer focused Radar Rules only where your business logic needs more control. If you upgrade to Radar Plus or Pro, use customization to narrow risk logic, not to build a giant rule stack you cannot maintain. Keep the rule set lean and review dashboard trends before you scale changes.

Payment methodFirst control patternOperator note
Card paymentsUse Block, Review, and Allow with clear criteriaUse the review queue for unusual card payments instead of reviewing everything
ACH and SEPA Direct DebitUse method-specific Allow/Block rules, then test before rolloutACH/SEPA have no Radar manual transaction review; use a separate internal delivery check

Run this recurring checklist to manage fraud risk without choking conversions:

  • Keep Allow rules narrow, because allow logic can bypass later block and review checks.
  • Track successful, blocked, and flagged-for-review outcomes by method inside Stripe Radar analytics.
  • Log every override with reason, owner, and expected outcome.
  • Capture complete payment context in your integration so Stripe Radar can score risk with better signal quality.
  • Flag unknowns early, including market constraints and account-level eligibility, before you expand coverage.

Hypothetical example: a repeat card client passes standard protections, while a first-time bank debit needs an internal delivery check. The team verifies each payment’s actual state and uses the appropriate method policy rather than adding a broad Allow override for either client.

Run this checklist now, schedule regular backtesting on your calendar, and refine from real payment behavior. If disputes still create friction in your workflow, pair this playbook with How to Protect Yourself from Chargebacks as a Freelancer.

Frequently Asked Questions

What is Stripe Radar and how does it prevent fraud?

Stripe Radar evaluates payment risk and applies the controls available on your plan. It can block risky attempts, request supported card authentication, or add eligible card payments to manual review. Your business still owns fulfillment timing, evidence, and later dispute handling.

Which Radar plan supports custom rules?

Stripe’s current plan comparison lists custom transaction rules in Radar Plus and Pro. Older pages may use Radar for Fraud Teams or Radar for Platforms terminology. Confirm your enabled plan, methods, and permissions in the account before relying on custom rules.

How does Stripe Radar treat ACH and SEPA differently from card payments?

Radar supports ACH and SEPA risk controls, but its manual transaction-review queue currently excludes those debits. Use supported Allow/Block rules plus an internal delivery policy. Bank-debit success or settlement does not eliminate later returns or disputes; verify actual timing for the method and account.

When should a freelancer choose Block vs Review vs Allow?

Block a well-supported abuse pattern, review ambiguous supported card payments when a human can add value, and usually let legitimate payments proceed under standard protections. Custom Allow rules are exceptions because they can bypass risk assessment and later rules. ACH/SEPA need internal review rather than a Radar Review action.

Can Adaptive 3D Secure reduce chargeback risk without hurting approvals?

Targeted 3DS can reduce eligible card-fraud exposure, but extra authentication may affect conversion and issuer outcomes. Preserve required authentication and measure approvals, abandonment, and dispute reasons together. A fraud-liability shift does not cover every dispute, including disputes over delivery.

What should I do first to stop card testing attacks?

Use Stripe’s recommended Checkout or Payment Element integration and investigate the attack endpoints. Combine appropriate server-side validation, rate limits, session checks, CAPTCHA, and supported velocity rules. Do not create a large manual review queue for automated attack traffic or keep retrying known abusive attempts.

What important details are still unknown before implementation?

You still need to verify country-level pricing, tier boundaries, and account eligibility directly in your Stripe account. You also need to confirm methodology windows behind published performance claims before you model ROI. Keep those unknowns in your launch checklist so your plan stays audit-ready.

Watch

How to Use Stripe Radar to Protect Cashflow

Gruv Editorial Team

Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.

Sources

  1. docs.stripe.com/radar/how-radar-workstrusted
  2. docs.stripe.com/radar/risk-settingstrusted
  3. stripe.com/guides/radar-rules-101trusted
  4. support.stripe.com/questions/radar-rulestrusted
  5. support.stripe.com/questions/monitoring-program-faqtrusted

Educational content only. Not legal, tax, or financial advice.

Related Posts

Value-Based Pricing for Freelancers Under Real Payment Risk
Financial Planning26 min read

Value-Based Pricing for Freelancers Under Real Payment Risk

Value-based pricing starts with the client’s expected benefit and willingness to pay. It still needs a deliverable, scope and payment agreement you can perform. Use a discovery phase when the benefit or effort is too uncertain to support a defensible quote.

value-based pricingfreelance pricingpayment terms
Read
Opening a Bank Account in Spain as a Foreigner
International Finance24 min read

Opening a Bank Account in Spain as a Foreigner

You can open a Spanish account as a foreign resident or non-resident, but the available product depends on where you live, your documents and the account holder. Start by separating a personal account, an autónomo account in your own name and an incorporated company account. The account must support the client payments you intend to receive.

spain bank accountnie numberexpat banking
Read
How to Protect Yourself from Chargebacks as a Freelancer
Risk Management30 min read

How to Protect Yourself from Chargebacks as a Freelancer

**Chargeback prep can reduce avoidable losses, but it cannot guarantee a win.** The real goal is narrower and more useful: build a repeatable sequence you can follow before, during, and after a dispute so cash flow is less fragile and decisions are less reactive.

chargebackspayment disputesstripe
Read