> 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/replays/overview-of-replays/capturing-and-reviewing-replays/replays-paid-in-cash.md).

# Replays Paid in Cash

{% hint style="danger" %}
**Not every Club allows for Cash transactions. If your Club does not accept Cash transactions, skip over this article.**
{% endhint %}

Cash is only available as a payment option inside the Dashboard and should only be used if a Customer does not want to put a card on file.

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

If the a Reservation was booked with the Cash option, the Customer will not be charged for any Quick Replays captured during the Reservation or Event. To allow them to capture Quick Replays, you can deposit Replay Credits on their Profile. The Customer can then use those Replay Credits to capture Quick Replays during their games.

#### To charge a Customer for Quick Replays with Cash

1. Open the Reservation or Event in the Dashboard
2. Open the side panel and click the Purchases tab
3. Click `+ Charge` button
4. Select the Customer's name
5. Click `+ Add Item` button
6. Fill out all fields and enter the rate for the Replays ordered
7. Change the charge type to `Cash` in the pop-up window
8. Complete the charge in the system
9. Collect cash from the Customer (the system does not verify cash, it only tracks the transaction)
10. Open the Customer's Profile
11. Add Quick Replays to the Profile equal in value to the cash paid.

After this, the Customer can capture that quantity of Quick Replays from the kiosk or the Play Button during the Reservation.


---

# 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/replays/overview-of-replays/capturing-and-reviewing-replays/replays-paid-in-cash.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.