> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/marketing/emails/email-variables/refund-approved.md).

# Refund approved

Use the variables in the list below to customize the **Refund approved** shopper email according to your needs.&#x20;

{% hint style="info" %}
Check the **Mandatory** column to see the variables that are required in your customized version of the e-mail.
{% endhint %}

<table><thead><tr><th width="237">Variable name</th><th width="315.9998779296875">Description &#x26; Test values</th><th>Mandatory</th></tr></thead><tbody><tr><td><code>AVANGATE_LOGO</code></td><td>Avangate logo URL.<br><strong>Test value</strong>: https://secure.avangate.com/images/email/vendor_logo.png</td><td>Yes</td></tr><tr><td><code>BUSINESS_COMPANY</code></td><td>Avangate company name.<br><strong>Test value</strong>: 0</td><td>Yes</td></tr><tr><td><code>CURRENCY</code></td><td>Order billing currency.<br><strong>Test value</strong>: USD</td><td>Yes</td></tr><tr><td><code>ENCRYPTED_MERCHANT_CODE</code></td><td>Encrypted merchant code.<br><strong>Test value</strong>: 0</td><td>No</td></tr><tr><td><code>PAYTYPE</code></td><td>Identification number for the payment method selected during ordering process.<br><strong>Test value</strong>: CC</td><td>No</td></tr><tr><td><code>PRODUCTS[index1].CODE</code></td><td>Product code.<br><strong>Test value</strong>: P_CODE</td><td>No</td></tr><tr><td><code>PRODUCTS[index1].SKU</code></td><td>Product SKU.<br><strong>Test value</strong>: SKU1234</td><td>No</td></tr><tr><td><code>REFNO</code></td><td>Order reference number.<br><strong>Test value</strong>: [9xxxxxx]</td><td>Yes</td></tr><tr><td><code>SELLER_BUSINESS_COMPANY</code></td><td>Merchant commercial name.<br><strong>Test value</strong>: Seller company</td><td>No</td></tr><tr><td><code>SELLER_SITE</code></td><td>Order website.<br><strong>Test value</strong>: http://www.software-company-website.com/</td><td>Yes</td></tr><tr><td><code>SHOPPER_NAME</code></td><td>First name and last name of the shopper associated to the refund order.<br><strong>Test value</strong>: [John Doe]</td><td>No</td></tr><tr><td><code>TOTAL_AMOUNT</code></td><td>Total refund amount.<br><strong>Test value</strong>: 56.5</td><td>Yes</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.2checkout.com/marketing/emails/email-variables/refund-approved.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
