By default, Chargeback.io only lets you adjust the Transaction Amount attribute for your Rapid Dispute Resolution (RDR) rules directly in the dashboard.
If you want RDR to be stricter or more lenient with which transactions get automatically refunded, keep reading — we’ll walk you through all the available rule options.
⚠️ Warning: If a transaction exceeds your RDR rule, you will not get an alert before the chargeback. Thus, there will be no chance to prevent it.
This is unlike Ethoca and CDRN, which still send an alert before the chargeback. Even if the transaction is above the threshold.
How RDR Rules Work
RDR rules are one or more conditions you set to automatically refund transactions through RDR. If you create more than one rule, all conditions must be met for the refund to happen automatically.
If none of the conditions you set are met, the transaction will result in a chargeback, which you’ll need to fight manually.
Conditions are made up of four elements:
Attributes
Operator
Values
We’ll cover each of these in detail throughout the following sections.
⚠️ Attributes, Operator, and Values are mandatory when creating rules. Make sure you don’t leave any of these fields blank.
First, let’s dive into the Attributes.
1. Attributes
You can set the following conditions for RDR to automatically refund transactions:
Attribute | Descriptions |
Dispute Category | The reason the customer gave for disputing the transaction. |
Dispute Condition Code | Extra details to better explain the dispute reason. |
Personal Account BIN | The 6-digit number that identifies the bank tied to your merchant account. |
Transaction Date | The date when the purchase happened. |
Transaction Amount | The total amount the customer was charged. |
Transaction Currency Code | The three-letter currency code for the transaction. |
Purchase Identifier | A unique ID assigned to each transaction to help match orders during dispute resolution. |
We will provide more examples of these Attributes later under the Values section.
Let’s move onto how RDR measures these Attributes.
2. Operators
The following Operators act on the Value of your Attributes to determine whether a transaction will be automatically refunded:
Operator | Descriptions |
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.
And here are the Values.
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 - GreaterThanOrEquals - 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. | - Equal to - NotEqualTo - GreaterThan - GreaterThanOrEquals - LessThanOrEquals - LessThan |
Currency Code | ISO 4217 | Alphanumeric | - Contains - EqualTo - IsBlank - IsIn - IsNotIn - NotEqualTo - StartsWith |
Purchase Identifier | Alphanumeric | Billing descriptor | - 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 (AKA chargeback reason codes) must be from Visa — not American Express, Mastercard, etc.
Let’s start creating rules.
Creating Rules
To create or update your RDR rules, you’ll need to send your desired rule to a Chargeback.io support specialist. We’ll handle the rule configuration with Verifi on your behalf.
First off, 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" earlier 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 in:
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 |
All three conditions must be met for the refund to happen: the transaction must be in EUR, tied to a customer disputes dispute (code 13), and specifically classified under the "Merchandise/Services Not Received" sub-category (sub-code 1).
Here's an image that summarizes that category/chargeback codes you can use:
⚠️ Each BIN/CAID (business) can have up to 10 different rules. Each rule can have up to 7 conditions. When creating a rule, tell the support specialist which business you’d like the rule to be for.
FAQs (Click Each Section to Expand the Answers)
What is RDR?
What is RDR?
Rapid Dispute Resolution (RDR) is an automated system from Verifi that gives merchants the ability to resolve Visa disputes instantly before they turn into chargebacks. Merchants create custom rules that automatically refund transactions when a dispute is filed.
When a Visa cardholder disputes a charge, RDR reviews the merchant’s rules and handles the case on the spot. If the rules approve a refund, the transaction is resolved immediately without a formal chargeback.
Want to learn how RDR alerts actually work? Keep reading our full guide.
How Do I Activate RDR?
How Do I Activate RDR?
To activate RDR alerts, go to Enrollments, find the RDR section, and click + Enroll More Descriptors.
On the next page, you’ll see a section for ARNs. Add four or more ARNs here. For most payment gateways, you’ll pull ARNs from refunded Visa transactions.
Here are guides on finding ARNs for different payment gateways:
If you don’t have any ARNs yet, you have a couple of options:
Request your BINs and CAID from your payment gateway’s customer support.
Refer to our guide on getting your BINs and CAID for more detailed steps.
Create and perform four refunds of any value using a Visa card.
Keep in mind it may take a few business days for ARNs to generate.
⚠️ ARNs must start with the number 2 or 7, and each ARN must be 23 digits long.
Why Do RDR Alerts Show Up as Chargebacks?
Why Do RDR Alerts Show Up as Chargebacks?
RDR alerts will always show up as 'lost' chargebacks in your payment gateway dashboard. For example, you might see a chargeback appear without the option to submit evidence, and even though you refunded the transaction, it will still show as lost.
This happens because your payment gateway hasn’t received the full RDR case information. Many processors' systems are based on TC40 data that Visa shares, which doesn’t fully sync with RDR cases.
Don’t worry.
Even though these chargebacks show as ‘lost,’ they won’t impact your chargeback rate. Plus, you won’t be charged chargeback fees for them — they won’t show up on your billing statement at all.
I Want to Change My RDR Rules. What Do I Do?
I Want to Change My RDR Rules. What Do I Do?
Reach out to a Chargeback.io support specialist and let them know which Attributes, Operators, and Values you want to update for your RDR rules.
Be as detailed as possible when making your request — missing information can cause unnecessary back-and-forth, which could delay the rule change process.
If I’m Signed Up For CDRN Also, Will I Get Duplicate Alerts?
If I’m Signed Up For CDRN Also, Will I Get Duplicate Alerts?
Using RDR and CDRN at the same time will never create duplicate alerts. If a situation arises where both enrollments could apply to the same transaction, you’ll receive a CDRN alert. Make sure to monitor your dashboard, especially if you have CDRN alerts set to manual refunds.
However, you could receive duplicate alerts if you have CDRN and Ethoca enabled together. If that happens, let us know — we’ll promptly refund you for the duplicate alert.
Just provide the alert IDs when you reach out.
💡 Tip
Need more help? Get support from our representatives at Chargeback.
We’re here to help with any questions you may have.