> 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/reservations/admin-creates-reservation/can-a-customer-book-a-reservation-with-cash-or-check.md).

# Book with Cash (or Check)

### Overview

The Cash option is used for bookings when there is a payment from a Customer that is outside the PodPlay system. While the system will track the revenue of this Cash, there is no formalized way for the system to know that Cash was handed from a Customer to an employee.

{% hint style="info" %}
**If your Club does not accept Cash, skip over this article.**
{% endhint %}

### Staff Books for the Customer

{% hint style="warning" %}
A Customer cannot book a Reservation or join an Event using Cash (or Check) unless they are at the Club and assisted by a staff member at the front desk.
{% endhint %}

For a staff member to help a Customer book using Cash, they can create a private Reservation for the Customer from the Overview page of the Dashboard:

1. Click, drag, and highlight the Customer's preferred time
2. Release your mouse
3. Notice the side panel appears
4. Search for the Customer's name (unique by email)
5. Click on the blue `Book` button
6. Select the `Cash` payment method in the pop-up window
7. Finalize the Reservation booking
8. Collect any Cash from the Customer

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

#### End-of-day Reconciliation

Because all Cash payments are tracked by the system, the Club GM should check for any Cash payments at the end of the day and count the Cash received to ensure all payments were collected.


---

# 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.podplay.app/reservations/admin-creates-reservation/can-a-customer-book-a-reservation-with-cash-or-check.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.