In the fast-paced world of digital transactions, navigating the complexities of dispute resolution can be a daunting task for merchants. With the Resolve (RDR) feature offered by Chargebackhit, businesses can transform the approach to Visa pre-dispute cases, accessing swift and automated resolutions.
RDR allows for auto-decision of Visa pre-dispute cases with participating issuers using a robust decision engine, enabling real-time resolution without the need for manual refund processing by a merchant. RDR operates according to a predefined set of rules established by a merchant. It evaluates the attributes of each dispute against the specified response criteria. Based on this comparison, the dispute either results in a refund or proceeds to a chargeback.
RDR merchant-defined rules:
- require a unique rule name
- allow up to eight conditions per rule
- must have at least one rule condition that specifies a transaction factor with an operator and a value
- must have each rule condition based on a specific operator, such as
EqualTo,GreaterThan,GreaterThanOrEquals,LessThan,LessThanOrEquals, andNotEqualTo - can have conditions with transaction factors that allow to evaluate multiple values, such as the Transaction currency code factor
RDR rules may be based on several transaction factors that collectively serve as unique attributes of the solution. These factors can include various elements such as transaction amount, transaction date, currency code, dispute categories, and others.
It is important to highlight that all alerts accepted through these RDR rules incur charges. This means that sellers will be billed for every alert automatically resolved using these predefined rules.
| Transaction factor | Description | Example |
|---|---|---|
| Transaction amount | Merchants can set rules to resolve eligible disputes for transactions above or below a specified amount. | A merchant may automatically issue a refund for any disputed transaction below $25 to avoid the time and cost of fighting small-value disputes. They also can fight harder against high-value disputes above a certain amount. |
| Transaction date | Similar to the authorization date, merchants can base their rules on the actual transaction date when the purchase was made. This date may differ from the authorization date but can serve as an equally valuable criterion. | A merchant may set up an automated refund rule for any disputes raised within 10 days of the transaction date to resolve claims related to non-delivery, wrong items received, and others. |
| Transaction currency code | Merchants can set rules based on the currency code, which can be useful for businesses operating in multiple countries or currencies. | If the transaction currency code is not USD, a merchant might choose to automatically accept liability. |
| Dispute categories | Visa dispute categories classify the nature or reason for the dispute raised by the customer or card issuer. Merchants have the option to customize rules for automatically accepting liability for specific Visa dispute categories. | Merchants can automatically refund disputes in the Customer disputes category for low-value transactions but provide compelling evidence for high-value disputes in the same category. |
| Dispute condition codes | Visa dispute condition codes are reason codes to indicate the exact reason for the dispute. These codes provide details about the dispute, such as the 13.2 - Cancelled Recurring of the Customer disputes category. | A merchant may automatically issue a refund for disputes with the 13.3 - Not as Described or Defective Merchandise/Services condition code for transactions below $30, if they decide that fighting such low-value disputes may not be cost-effective. |
| Issuer BIN | Merchants may set rules for automatic response based on the Bank Identification Number (BIN) assigned to the card issuer. | Merchants can choose to automatically refund disputes raised by customers of issuers from a particular region that tend to cause them the most difficulties or pose a higher risk of chargebacks. |
| Purchase identifier | Merchants can set up automatic responses based on a unique purchase identifier the merchant assigns to a specific purchase. | A merchant may have received multiple disputes regarding a particular product line or batch of orders with some issues or defects. In such cases, the merchant can set up a rule to automatically issue refunds for any disputes involving the purchase identifiers of that product line or batch. |
| Authorization date | Merchants can configure rules based on the date when a transaction was authorized. This can be a valuable criterion for setting rules, especially for time-sensitive disputes or refund policies. | A merchant may have a policy to automatically issue refunds for disputed transactions that occurred within the last 14 days, combining this factor with other relevant ones. |
For RDR, the only available
Guide
Summarize complex Chargebackhit outcomes and responses, ensuring accurate transaction reconciliation.
outcome type
is acknowledged. This means that when dealing with RDR cases, merchants should note that their response options are limited to acknowledging the situation, as no other outcome types are applicable in these instances.