> 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/pricing-payments-and-billing-issues/when-are-customers-charged-for-events.md).

# When are Customers charged for Events

* The default time when Customers are charged for an Event is 45 minutes after the Event ends.
  * By contacting your PodPlay Customer Success Manager (CSM), you can change the charge's default timing relative to the Event's end.
* This means that if an Event is a Tournament that is two weeks away, the customer may sign up and reserve a spot in the Tournament today. While their Purchase History on the app will show they have made a purchase, the charge is a hold on the Customer’s credit card, and they will not be charged on their credit card (cc) until the day of the Tournament, 45 minutes after it ends.
  * This applies to all types of Events, including an Event Series.
    * A Customer who signs up for a Series will have a hold placed on their cc the day before the first day of the Series. On the day of the first event in the Series, the customer will be charged after the first event.
    * As an example, if a Customer signs up, on Monday, for a Series that starts on Saturday, a hold will be placed on their cc on Friday, and the Customer will be charged after the first day of the Series, on Saturday.

NOTES BELOW

* When are Customers charged for an event?
  * The Customer is charged 30 minutes after the Reservation ends. The exact time when the Customer is charged depends on the configuration the Club set up during onboarding.
  * To delete: 15 minutes before the reservation ends (Picklemall) (@Gerardo Bort to check in with Brian)


---

# 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/pricing-payments-and-billing-issues/when-are-customers-charged-for-events.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.