Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
OverviewExplore all products
Start building
Start developing
Sample projects
About the APIs
Building with LLMs
Use Stripe without code
Set up Stripe
Create an account
Products and prices
Web Dashboard
Mobile Dashboard
Migrate to Stripe
Migrate customer data
Migrate payment data
Migrate subscriptions
Manage fraud risk
Understand fraud
Radar fraud protection
    Overview
    Integration
    Radar Session
    Risk evaluation
    Multiprocessor Radar scores
    Risk settings
    Reviews
    Lists
    Rules
      Reference
      Supported attributes
      Test rules
      Dispute resolution rules
    Radar analytics
    Radar for Platforms
Manage disputes
Verify identities
Regulatory support
HomeGet startedRadar fraud protectionRules

Dispute resolution rules

Learn about writing dispute resolution rules in Radar.

Copy page

Starting May 1, 2025, you can use Radar to automatically resolve specific disputes. If you’re using either Stripe Radar or Radar for Fraud Teams, and signed up for dispute prevention, you can write resolution rules to refund a dispute. Radar evaluates each incoming dispute against the dispute resolution rules you create. If a dispute matches the criteria for any rule, we automatically resolve it.

Rule structure

Dispute resolution rules follow the same rules structure as other Radar rules. The rule structure has two components—the action to take and the condition to evaluate:

{action} if {condition}

Together they represent the predicate. A rule to automatically resolve all incoming disputes with a disputed amount of 10 USD or less appears as:

Resolve dispute if :amount_in_usd: <= 10.00

  • The action is Resolve dispute
  • The condition is :amount_in_usd: < 10.00

For all dispute resolution rules, the action is Resolve dispute. Learn more about writing effective rules in Radar.

Supported attributes

Use the following attributes within Radar to write dispute rules.

Attribute
Type
Example Value
amount_in_xyz
Numeric
50
The amount of the dispute, which could be different than the amount of the payment, converted to the currency specified by xyz (for example, amount_in_usd). Specify one of the following supported currencies and Stripe automatically calculates a converted amount to use: aed, ars, aud, brl, cad, chf, clp, cop, czk, dkk, eur, gbp, hkd, huf, idr, ils, inr, jpy, khr, krw, mxn, myr, nok, nzd, php, pln, ron, rub, sek, sgd, thb, try, twd, or usd. For decimal currencies (for example, usd), rules use the base currency unit rather than sub units (for example, dollars, not cents).
card_brand
Case Insensitive String
visa
The brand of the card associated with the dispute. The supported values are: visa (Visa) and mc (Mastercard)
card_bin
Case Insensitive String
483312
The Bank Identification Number (BIN) of the card associated with the dispute. The BIN is the first six digits of the card number.
card_country
Case Insensitive Country
US
The two-letter code corresponding to the country where the card was issued.
currency
Case Insensitive String
usd
The 3-digit currency code representing the currency in which the customer paid for the transaction.
is_fraudulent
Boolean
true
Identifies whether the dispute was filed as fraudulent or non-fraudulent. Non-fraudulent disputes include disputes that were filed for reason code categories such as Product not received, Product unacceptable, and Subscription cancelled.
network_reason_code
Case Insensitive String
10.4
The reason code from the network. Currently, only Visa dispute network reason codes are supported.
statement_descriptor
Case Insensitive String
example descriptor
The statement descriptor provided on a payment.

See also

  • Query disputes and fraud data
  • Dispute prevention
  • Radar 101 Guide
  • Fraud prevention rules
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc
Related Guides
Rules reference
All supported rule attributes
Dispute prevention
Products Used
Radar
Payments
Checkout
Connect