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

# Refunds

### Overview

You can Refund a Customer from the Admin Dashboard inside the Customer's Profile. Before processing any Refund, confirm why the Customer is asking for one. If the request conflicts with your Cancellation Policy, follow the policy your business has set. If it does not conflict, process the Refund.

#### How to process a Refund

1. Navigate to the Profile of the Customer who requested the Refund.
2. Click the Purchases tab.
3. Click the specific Purchase you want to Refund.
4. Scroll down to find the three vertical dots next to a captured amount
5. Click on the "Refund" option
6. Click the button and complete the fields:
   * Amount to refund
   * Type of refund: Money or Credits
   * Reason for refund: `Requested by Customer`, `Fraud`, or `Duplicate`
   * Details of refund
7. Click the Refund button in the popup to initiate the Refund.

{% @supademo/embed url="<https://app.supademo.com/demo/cmquarkrh094lqml2d6wz9yyw>" demoId="cmquarkrh094lqml2d6wz9yyw" %}

{% hint style="danger" %}
**If a refund is processed and the option selected is Fraud**, Stripe will automatically flag the Customer's credit card and block it from further fraudulent charges.

Specifically:

* The Customer's credit card and email address are both blocked
* This is intentional, if a Customer is committing fraud, the Club would not want to continue doing business with them

To avoid accidentally blocking a Customer's card, use the reason **"Request by Customer"** or **"Duplicate"** for any non-fraud-related refunds. To learn more, read the [How to Issue a Refund article](https://podplay.gitbook.io/podplay-docs/untitled/~/revisions/mv1QjbTRLBlx2a1a0TgT/cancellations-refunds-and-charge-errors/refunds/how-do-i-issue-a-refund).
{% endhint %}

#### Money or Credits?

A Money refund returns all the Customer's money. The Stripe fee on the original transaction is lost when this happens. A Credit refund puts money on the Customer's Profile in the App, which they can spend on a future Reservation. Credits hold a 1-for-1 dollar value. We suggest Credits for three reasons:

1. The Customer can use Credits right away. A Money refund takes several days depending on the Customer's bank.
2. The Club keeps the [Stripe fee](https://podplay.gitbook.io/docs/owners-playbook/accounting-and-stripe/what-is-stripe#stripe-fees) instead of losing it on the refund transaction.
3. The Refund stays at the Club. Ask the Customer which they prefer. If they want Money, we strongly suggest giving the Money refund.

### FAQs

<details>

<summary>Can I issue a partial Refund?</summary>

Yes. Change the Amount field to the value you want to return rather than the full Purchase amount.

</details>

<details>

<summary>Why detail the reason for a Refund?</summary>

Recording the reason in the Details field is good business practice. If you ever need to revisit why a Refund was issued, the Details section tells you exactly why it was processed.

</details>

<details>

<summary>What are the reasons for a Refund?</summary>

The three most frequent reasons are Requested by Customer, Fraud, and Duplicate charge. These are the options you pick from when refunding a Customer. ONLY select Fraud as the reason for the refund if you want to block the Customer's credit card from working in the future.

</details>

<details open>

<summary>How long does a Refund take?</summary>

A Refund is processed on PodPlay's system immediately. Stripe then begins its refund process, which can take up to 10 business days depending on the Customer's bank. The Customer usually sees the Refund within 2 business days.

<figure><img src="/files/F2SIQM80eIU8tNk2ybBF" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>Will a Customer be Refunded if removed from a Reservation?</summary>

A Customer is not charged for a Reservation until after the booking is over (default process). If a staff member in the Dashboard removes a Customer from a Reservation or deletes the Reservation, there is nothing to Refund. The exception is when a Customer used Credits to book. Credits are applied immediately rather than deducted after the Reservation. If an Admin then removes the Customer or deletes the Reservation, all Credits are returned to the Customer's Profile.

</details>

<details>

<summary>What if a Customer disputes a charge?</summary>

Because the Customer is not charged until after their Reservation (default process), the Club has the Customer on camera attending the Reservation or Event. Read [more about Disputes here](https://podplay.gitbook.io/docs/owners-playbook/accounting-and-stripe/what-is-stripe/stripe-disputes).

</details>

<details>

<summary>Can I Refund through Stripe instead?</summary>

No. Process all Refunds through the PodPlay Dashboard.

</details>


---

# 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.podplay.app/payments/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.
