# RDR

***

**Visa Rapid Dispute Resolution (RDR)** involves refunding a consumer prior to chargeback.

{% hint style="warning" %}
The refund occurs outside of Konnektive.
{% endhint %}

{% hint style="info" %}
The refund will not be sent to the gateway if these instructions are followed.

This is the desired result.

Most gateways will accept the refund even though RDR has already given a refund.

It is imperative that users be properly trained on RDR procedures to prevent this.
{% endhint %}

***

## Add RDR as a Refund Reason <a href="#rdr-addrdrasarefundreason" id="rdr-addrdrasarefundreason"></a>

Go to **CRM → Call Centers** and scroll down to the Refund Reasons panel.

<figure><img src="/files/l9PGKWK9oslagMisswLv" alt=""><figcaption></figcaption></figure>

Press the green + button on the far right and add **RDR** as a reason.

<figure><img src="/files/sEp1SB4CUV3K61wA5B5R" alt=""><figcaption></figcaption></figure>

***

## Add RDR Fees into Gateway configuration <a href="#rdr-addrdrfeesintogatewayconfiguration" id="rdr-addrdrfeesintogatewayconfiguration"></a>

Go to **Gateways → Gateway List** and edit your gateways to add the **RDR Fee**.

<figure><img src="/files/wwRyNnHSyWrym97YOczk" alt=""><figcaption></figcaption></figure>

***

## Mark transactions as RDR <a href="#rdr-marktransactionsasrdr" id="rdr-marktransactionsasrdr"></a>

You can mark the transaction as having been refunded via RDR either manually in the CRM or via the Refund Transaction API.

***

### Set the RDR manually <a href="#rdr-settherdrmanually" id="rdr-settherdrmanually"></a>

1. Find the customer in CRM using the [Customer Service Search](/konnektive-crm/customer-service.md).

<figure><img src="/files/leDxnffneapxOsmmpbed" alt=""><figcaption></figcaption></figure>

2. Find the transaction which to refund.

<figure><img src="/files/HJnQZdKRGueY95RifM03" alt=""><figcaption></figcaption></figure>

3. On the transaction **Actions**, choose **Refund.**

<figure><img src="/files/RWhgAGhhhJSiu6YBMnxE" alt=""><figcaption></figcaption></figure>

4. Choose **RDR** for the **Refund Reason**.

<figure><img src="/files/c8Nc7Ii1UldPDc7dz50j" alt=""><figcaption></figcaption></figure>

5. Check the **Refunded Externally?** box and fill in the **Refund Transaction Id** (from your gateway) if known.
6. Press **Refund** button

***

### Set the RDR via API <a href="#rdr-settherdrviaapi" id="rdr-settherdrviaapi"></a>

1. Review the **Refund Transaction API** [here](https://apidocs.checkoutchamp.com/#9a74cdd2-0b0d-4894-89df-772ecc85d252)
2. Create an API user with access to the **Refund Transactions** endpoint. Be sure to whitelist as needed.
3. Call the **Refund Transactions API** with
   1. **transactionId**
   2. `refundReason=RDR`
   3. `externalRefund=1`
   4. `fullRefund=1`
   5. **loginId** = API user username
   6. **password** = API user password

***

## Reporting <a href="#rdr-reporting" id="rdr-reporting"></a>

### Refund Details Report

If the steps above are followed properly, the [Refund Details Report](#refund-details-report) will display the RDR transactions. These transactions will be displayed as **External** (Externally Refunded).

You will see **RDR** in the **Refund Reason** column.

<figure><img src="/files/LfdB1S7GORYcDGEQzewq" alt=""><figcaption></figcaption></figure>

### Transaction Summary Report

Additionally, the **RDR Fee** is calculated as an expense on your [Transaction Summary Report](#transaction-summary-report).

<figure><img src="/files/MHIDn37DLu8VLK5XfIhh" alt=""><figcaption></figcaption></figure>

Hover over the Expenses value to see the breakdown.

<figure><img src="/files/aqWQmb5CplOEBuEXNWyZ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.konnektive.com/konnektive-crm/gateway-setup/rdr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.