> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/payments/issuing-refunds.md).

# Issuing refunds

Sometimes you need to return a payment to a vendor, whether due to a cancellation, a pricing error, or a change of plans. Vendor Space lets you process refunds directly from the Transactions page without needing to log into Stripe separately.

***

## How to issue a refund

1. Go to **Transactions** in the sidebar.
2. Find the transaction you want to refund. Use the filters or search to locate it quickly.
3. Click **Refund** on the transaction.
4. Enter the **refund amount**. You can issue a full or partial refund.
5. Enter a **reason** for the refund. This is for your own records.
6. Click **Confirm** to process the refund.

The refund is submitted to Stripe and the vendor is notified by email once it has been processed.

> **Tip:** Partial refunds are useful when a vendor cancels an add-on but keeps their booth, or when you need to adjust pricing after the fact.

***

## Refund statuses

After you initiate a refund, it moves through the following stages:

| Status         | Meaning                                                      |
| -------------- | ------------------------------------------------------------ |
| **Pending**    | Refund has been submitted and is waiting to be processed     |
| **Processing** | Stripe is actively processing the refund                     |
| **Succeeded**  | Refund has been completed and funds returned to the vendor   |
| **Failed**     | Refund could not be processed (see below for common reasons) |

> **Tip:** Most refunds are processed within 5 to 10 business days, depending on the vendor's bank. If a vendor asks when they will see the funds, let them know it may take up to 10 business days to appear on their statement.

***

## What the vendor sees

When a refund is processed:

* The vendor receives an **email notification** confirming the refund amount and the associated event.
* The refunded amount appears on their card or bank statement, typically within 5 to 10 business days.

***

## Common reasons a refund might fail

* The vendor's original payment method is no longer valid (expired card, closed account).
* The refund amount exceeds the original transaction amount.
* Too much time has passed since the original charge (Stripe typically allows refunds up to 180 days after the payment).

If a refund fails, you will see the "Failed" status on the transaction. In that case, you may need to arrange an alternative method of reimbursement with the vendor directly.

***

## Things to keep in mind

* **Transaction fees are not refunded.** When you issue a refund, the Vendor Space transaction fee from the original payment is not returned. Stripe's processing fees follow Stripe's own refund policy.
* **Refunds cannot be undone.** Once confirmed, a refund cannot be reversed. Double-check the amount and vendor before clicking Confirm.
* **Partial refunds** can be issued multiple times on the same transaction, as long as the total refunded does not exceed the original payment amount.

> **Tip:** Before issuing a refund, communicate with the vendor first to confirm the details. This helps avoid any confusion about the amount or reason.


---

# 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://vendorspace.gitbook.io/docs/payments/issuing-refunds.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.