> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/transactions/refund.md).

# Refund

![(click to enlarge)](https://3537448238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fzpi9teY7Tm2pCZ1Bw8zO%2Fuploads%2Fugg2QXmTuTkTk0VWAtFl%2FTransactions_Refund_EN.jpg?alt=media\&token=b7e342e5-940c-4419-8ac6-31c5a7bbb756)

While [a refund from within an existing transaction](/home/interfaces/backoffice/transactions/journal-details.md#refund) is also possible, credit cards offer a manual way to do a refund using the card data directly through the **Refund** option inside the Saferpay Backoffice.

This option shares a lot of similar inputs to the normal [Authorization](/home/interfaces/backoffice/transactions/authorization-and-payment.md) or [Payment](/home/interfaces/backoffice/transactions/authorization-and-payment.md), as it technically is a Payment, just in the opposite direction.

* **Card Number:** This is the card number or PAN of the credit card you want to authorize. **This field is mandatory.**
* **Expiry date:** This is the expiration date of the card. **This field is mandatory.**
* **Owner Name:** This is the name of the owner of the card.
* **Card Verification Code (CVC):** Also called Card Verification Value (CVV), from the back side of the credit card.
* **Amount:** This is the amount you want to authorize. It also includes the currency. **This field is mandatory.**
* **Reference number:** This is the reference number of the transaction, also called **OrderId**. While optional, we recommend that you set one, as it is also forwarded to the processor and will show up on your reconciliation files.

{% hint style="warning" %}
Make sure that the Reference Number is unique.
{% endhint %}

* **Sales Description:** A simple description of this transaction.
* **Payer note on statement:** This is the text that will show up on your customer's bank statement. Normally, Saferpay will use the Reference number. However, sometimes, you may want to use a different text.

{% hint style="info" %}
This feature has to be activated before you can use it. Please contact your sales contact for activation.

**Furthermore:** While Saferpay does support quite a long text, processors and banks often do not support more than 12 characters.
{% endhint %}

* **The purchaser's email address:** If you want to, you can send a confirmation e-mail to your customer. The text is largely premade by Saferpay; however, you can choose the language from the dropdown.
* **Your email address:** Likewise, you can also send an e-mail to one of your e-mail addresses.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.saferpay.com/home/interfaces/backoffice/transactions/refund.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.