> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/online-payments/payment-actions/refunds.md).
# Refunds
## Overview
You can refund a previously captured payment via the API or [Verifone Central](https://test.verifone.cloud/).
{% hint style="warning" %}
Depending on the acquirer, the transaction must have a SALE\_SETTLED status before the payment can be refunded.
{% endhint %}
Multiple refunds can be done on a single transaction until the original authorized amount has been refunded entirely.
Refunds can be matched or unmatched. Matched refunds are processed by providing the identifiers to the original message. These would include the elements within the **related transaction** section of the transaction object. [Unmatched refunds](/online-payments/payment-actions/unmatched-refunds.md) require a new transaction message with a payment instrument.
This documentation page refers to the matched refunds, where the original transaction ID to refund is given.
## Prerequisites
To refund previously captured payments via Verifone Central, you must have a **Merchant supervisor** role.
## Refund a transaction via Verifone Central
1. Log in to the portal and, in the top navigation menu, click on **Orders/Transaction** under *Commerce > Reporting*.
2. From the **Orders** view, select **Transaction ID** in the drop-down filter, and type the transaction ID in the Search bar, then click **Apply**.
3. Click on the transaction to open the Transaction details side panel.
4. In the **Transaction** side panel, go to **Actions**, enter the amount you want to refund and optionally a reason, and then click **Refund**.
## Refund a transaction via the API
To refund a previously captured payment via the API, follow these steps:
1. Send `POST/transactions/{id}/refund`.
2. Required parameters:
| Parameter | Type | Description |
| --------- | ------- | ---------------------------------------------------------- |
| id | String | Original transaction ID to refund. |
| amount | Integer | Amount is charged without a decimal place e.g. $1.5 = 150. |
| reason | String | The reason for refund. |
3. Request example -> Check out the [API reference documentation](https://docs.verifone.com/api-reference/open-api-references/checkout/specification/checkout#post-v2-checkout-refund-preview).
```json
{
"amount":4400
}'
```
4. Response example:
```json
{
"status": "REFUNDED",
"id": "d43ad789-9af3-4878-ba9d-9b7141deb532",
"payment_provider_contract": "9d0e6331-7610-404e-a9cc-f1520d3cf148",
"amount": 4400,
"customer": "41437fbd-29f1-436e-a674-234d0d339740",
"merchant_reference": "327515921647",
"processor_reference": "016153570198200",
"arn": "MjAyMjEwMzEwNTU3MjUcMjIxMDMxNTU3MjUcNjY3MjAzODYyNTExNjc2OTIwNDk1MxxJc0NyZWRpdA==",
"authorization_code": "",
"cvv_result": "0",
"reason_code": "0000",
"status_reason": "Approved",
"rrn": "22103155725",
"shopper_interaction": "ECOMMERCE",
"stan": "55725",
"reversal_status": "NONE",
"additional_data": {
"initiator_trace_id": "55725",
"acquirer_response_code": "000"
}
}
```
---
# 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.verifone.com/online-payments/payment-actions/refunds.md?ask=&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.
