> 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/events/create-an-event/manage-attendees/how-is-the-customer-notified-if-they-dont-have-the-app.md).

# How is the Customer notified if they don’t have the app

* There are a few scenarios of what could happen and how the PodPlay system notifies the Customer they were unable to join an Event.
  * If a Customer signs up for an Event <6 days before the Event, and does not have the necessary funds at the time of sign-up, the PodPlay system will not allow the Customer to join and will give them an error.
  * If a Customer signs up for an Event >6 days before the Event, Stripe will put a hold on the Customer’s credit card (cc) 24 hours before the Event.
    * A hold is not put on the Customer’s cc at the time of sign-up because the Customer might change their mind and cancel their Reservation or participation in said Event. This allows the Customer to remain flexible with their plans.
    * In situations where a hold is put on a Customer’s cc 24 hours before an event and the Customer doesn’t have the necessary funds. The Customer will receive an email saying they need to update their cc on file.
    * The Admin will also see the Customer’s account in the Attendee list of the Reservation or Event.
      * If an Admin sees this, they will need to charge the Customer for their participation in the Event through the Dashboard.
        * Read here to understand more [**situations when an Admin needs to charge a Customer**](https://help.podplay.app/en/articles/1826433).


---

# 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/events/create-an-event/manage-attendees/how-is-the-customer-notified-if-they-dont-have-the-app.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.