> For the complete documentation index, see [llms.txt](https://hollow-peak.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://hollow-peak.gitbook.io/docs/payments/refunds.md).

# Refunds

Refunding an order, in full or in part.

## Issuing one

Open the order, or **Payments → Overview**, and choose **Refund**.

You can refund the full amount or part of it — useful when one item is returned from a larger order.

Refunding requires the `payments.refund` permission. It is worth restricting.

## What happens

| Provider   | Behaviour                                                          |
| ---------- | ------------------------------------------------------------------ |
| **Stripe** | Sent to Stripe immediately; reaches the card in 5–10 working days  |
| **PayPal** | Sent to PayPal immediately                                         |
| **Manual** | **You** send the money back through your bank, then record it here |

The order's payment status updates, the refund is recorded against it, and the event appears in the order history.

## Effects elsewhere

**Digital downloads.** A refunded order's download entitlements are withdrawn. Someone who already downloaded the file still has the file — that cannot be undone — but they cannot download it again.

**Reviews.** If the customer left a review, its **verified purchase** badge is withdrawn, while the review itself remains. A refund does not silence a customer, but it does stop a refunded purchase vouching for a product.

**Stock.** Not returned automatically. Physical goods may not come back, or may come back damaged, so returning stock is a deliberate act — adjust it on the product if the item is resaleable.

## Partial refunds

Enter the amount rather than the full total. Multiple partial refunds are allowed up to the original amount.

## Refunds and fees

Most providers do not return their processing fee on a refund. Check your provider's policy — this is between you and them, and Hollow Peak cannot change it.

## Common problems

| Symptom                       | Cause                                                                 |
| ----------------------------- | --------------------------------------------------------------------- |
| Refund button missing         | Missing `payments.refund` permission, or the payment never completed  |
| Provider refuses              | Too old — most providers limit refunds to 90–180 days                 |
| Refunded but customer says no | Card refunds take days to appear; ask them to check the original card |


---

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