Read First
Before creating your rules, read through these sections to ensure you set up rules correctly.
1. Critical to Know
Read this section, first.
1A. Check your settings
By default, RDR only auto-refunds USD.
If you have transactions in additional currencies (e.g., GBP), tell our customer support which currency(ies) you want to add and the auto-refund threshold ASAP.
Otherwise, you may receive Declined-status RDR alerts, which can result in disputes.
1B. Rare CDRN duplicates
In extremely rare scenarios, you may receive an RDR alert with a Declined status even though it meets your rules.
If this happens, check whether you also have a CDRN alert for the same transaction, since a prior CDRN alert for the same transaction can prevent an RDR alert.
This is a duplicate. File a Manual Credit Request, and we’ll credit you for the duplicate alert.
2. Rule Considerations
Review these rule considerations to avoid delays when creating rules:
One BIN+CAID (merchant account) can have up to 10 different rules, and each rule can have up to 7 conditions.
All rules must have an Attribute, Operator, and Value to be valid.
Rules are evaluated in sequence (rule one is evaluated first, then rule two, etc.).
If there are five rules and the conditions of the first rule are met, the remaining rules are not evaluated.
If the conditions of any rule are met, the RDR alert will be delivered.
Transactions that do not meet the criteria of your RDR rules will automatically be set to Declined status.
Most Declined-status RDR alerts cannot be credited.
Rules can result in some transactions not being refunded, which can lead to chargebacks. When setting rules, keep this in mind because you will need to fight the chargeback, which will contribute to your chargeback rate.
ℹ️ See this guide to learn more about chargeback rates.
Adjusting RDR Auto-Refund Amount
By default, Chargeback.io only allows you to adjust the Transaction Amount setting for your Rapid Dispute Resolution (RDR) rules directly in the dashboard.
To change your RDR auto-refund amount:
Go to Business settings.
Find the row labeled Auto-refund and click Edit.
Enter the maximum transaction amount you want refunded automatically.
Click Confirm.
RDR will not auto-refund any transactions above this amount. Changes can take up to 5 business days to take effect.
If you want RDR to be stricter or more lenient about which transactions get automatically refunded, keep reading. We’ll walk you through all the available rule options.
How to Create Rules in RDR
There is no setting in the Chargeback.io dashboard to fine-tune RDR rules. You will need to send your specific rule requests to our customer support.
With that in mind, you’ll need to define your rule conditions:
Select an Attribute you want the rule to act on.
If you want to add more than one Attribute, submit each as a separate condition or create a new rule.
Choose an Operator based on how you want the rule to match Values.
Refer to the “Operator Table” later in this guide.
Set a Value for the Attribute.
Some Attributes have predefined options. Others allow free-form input.
Once you’ve completed the form, send it to your Chargeback.io support contact. We’ll review the information and submit the rule request to Verifi for you.
Here’s an example of what you could send:
Rule Name: Transactions in Euros
Condition | Attribute | Operator | Value |
1 | Currency Code | EqualTo | EUR |
2 | Dispute Category Code (Reason Code) | EqualTo | 13 - Customer Disputes |
3 | Dispute Sub-Category Code | EqualTo | 13.1 - Merchandise/Services Not Received |
In this example, you’ll refund a transaction if it’s paid in EUROs, tied to a customer disputes dispute (code 13), and classified under the “Merchandise / Services Not Received” sub-category (sub-code 1).
Best Practices for Creating Rules
Follow these best practices to prevent issues further down the road:
Don’t include contradictory dispute categories and condition codes.
E.g., a Dispute Category = “10” and a Dispute Condition Code = “12.1”).
A rule shouldn’t conflict with another rule.
E.g. “Transaction Date IsGreaterThan 02/02/2025” in one rule and “Transaction Date IsLessThan 02/02/2025” in another.
Keep rule names within 30 characters and clear enough to reference in RDR communications.
Read on to learn what Attributes, Operators, and Values you can include in your rules.
How RDR Rules Work
Conditions are made up of these elements:
Attributes
Operator
Values
We’ll cover each of these in detail throughout the following sections.
1. Attributes
You can set the following conditions for RDR to automatically refund transactions:
Attribute | Description | Use Case |
Dispute Category | The reason the customer gave for disputing the transaction. | Resolve disputes by dispute category. |
Dispute Condition Code | Extra details to better explain the dispute reason. | Resolve disputes by chargeback code. |
Personal Account BIN | The 6-digit number that identifies the bank tied to a card. | Resolve disputes on all Visa BINs except select issuer(s). |
Transaction Date | The date when the purchase happened. | Avoid disputes for transactions after a certain date. |
Transaction Amount | The total amount the customer was charged. | Resolve disputes for transactions more or less than a certain amount. |
Transaction Currency Code | The three-letter currency code for the transaction. | Resolve disputes for transactions made with non-USD currencies. |
Purchase Identifier | A unique ID assigned to each transaction to help match orders during dispute resolution. | Prevent disputes for preferred customers or if the merchant is a part of a special program. |
We will provide more examples of these Attributes later under the Values section.
Here’s a reference image for all of Visa’s chargeback dispute categories and dispute category condition (reason codes):
See this guide for more information on all Visa’s chargeback reason codes.
2. Operators
The following Operators act on the Value of your Attributes to determine whether a transaction will be automatically refunded:
Operator | Description |
Contains | Must include the specified value. |
EqualTo | Must match the specified value. |
GreaterThan | Greater than the specified value. |
GreaterThanOrEquals | Greater than or equal to the specified value. |
IsBlank | No value present. Can be True or False. |
LessThan | Less than the specified value. |
LessThanOrEquals | Less than or equal to the specified value. |
NotEqualTo | Must not match the specified value. |
StartsWith | Must begin with the specified value. |
IsIn | Must match one of the allowed values. |
IsNotIn | Must not match any of the allowed values. |
Notes:
Some Attributes can use approximate-match operators like StartsWith or Contains. The minimum input for these fields is at least one character or digit.
For IsIn and IsNotIn operators:
Example values for Transaction Date: 30, 60, or 90 days.
These operators check if the Value matches (or doesn’t match) one of the listed options.
3. Values
This provides more information regarding the Attributes and their acceptable formats, along with usable operators:
Attribute | Format | Value(s) | Usable Operators |
BIN | Number | 6-digit issuer BIN | Contains, EqualTo, IsBlank, NotEqualTo, StartsWith |
Transaction Date | Date | Format: MM/DD/YYYY | EqualTo, NotEqualTo, GreaterThan, GreaterThanOrEqual, IsIn, IsNotIn, LessThanOrEquals, LessThan |
Transaction Amount | Number (must be greater than zero) | Set this to accept all pre-dispute values above, below, or equal to a dollar amount. | EqualTo, NotEqualTo, GreaterThan, GreaterThanOrEquals, LessThanOrEquals, LessThan |
Currency Code | ISO 4217 | Alphanumeric | Contains, EqualTo, IsBlank, IsIn, IsNotIn, NotEqualTo, StartsWith |
Purchase Identifier | Alphanumeric | Order identifier assigned to every transaction | Contains, EqualTo, IsBlank, IsIn, IsNotIn, NotEqualTo, StartsWith |
Dispute Category | Chargeback Reason Code | Choose one of the following: 10 - Fraud; 11 - Authorization; 12 - Processing Error; 13 - Consumer | Contains, EqualTo, NotEqualTo, IsBlank, IsIn, IsNotIn |
Dispute Condition Code | NA | Choose a sub-category | Contains, EqualTo, NotEqualTo, IsBlank, IsIn, IsNotIn |
Notes:
Refer to this guide to find ISO 4217 currency codes.
Dispute category and condition codes must be from Visa, not Mastercard and other card issuers.
ℹ️ Regardless of what rules you have, RDR may appear as chargebacks in your payment processor when they actually aren’t. Read this guide for clarity.
💬 Still need help? Chargeback.io Support is here.