> 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.md).

# Event Payments

### Overview

Every Event requires its own pricing, set separately from the Member vs. Non-member pricing used for Court Bookings. Pricing is configured in the **Admission Rate** section during Event creation.

To set pricing:

1. Create an Event and choose the Event type
2. In the **Admission Rate** section, enter the price for Members and the price for Non-members
3. Complete the remaining Event details and publish

Once set, Customers pay the configured amount when they sign up, based on their Non-member status or Membership tier.

### When Customers are charged

Customers are not charged at the moment of signup. Instead, the system places a hold on their credit card (cc) to verify sufficient funds. The actual charge processes **45 minutes after the Event ends** by default. A Customer who signs up for a Tournament two weeks out will see the hold in their Purchase History and on their cc statement, and the charge does not settle until the day of the Tournament.

**For Series:** The Customer is charged after the first Event session ends, for the whole Series.

#### Refunds when a Customer cancels

Because Customers are not charged until after the Event ends, canceling before the Event does not require a refund — there is nothing yet to refund. The hold is released when the Customer cancels.

The Dashboard shows a **Settling in X days** status on the purchase until the Event ends and the charge settles.

If a Customer cancels, they may still be subject to a Cancellation Policy fee depending on how the Event is configured. See [Is the Cancellation Policy Different for Events?](https://help.podplay.app/en/articles/1038593)

#### Payment issues at signup

All Customers must have a phone number and full credit card details (16-digit number, expiration, security code, and zip code) on file before signing up for any Event. Missing or incorrect information triggers an error and blocks the signup.

**Less than 6 days before the Event:** If a Customer's cc cannot be authorized at signup, they see an error immediately and cannot secure a spot until the issue is resolved.

**More than 6 days before the Event:** The hold is placed 24 hours before the Event, not at signup. If the hold fails at that point, the Customer receives an email to update their cc. An Admin will also see a flag in the Attendee list and may need to manually charge the Customer through the Dashboard. See [Situations when an Admin needs to charge a Customer](https://help.podplay.app/en/articles/1826433).

#### Charge Failed in the Purchase tab

If a Customer secured a spot but their payment failed, a **Charge Failed** tag appears in the **Purchases** tab of the Event. The Customer is also notified in the App. In most cases they update their cc and retry — the Purchase tab will then show **Charge Failed** followed by **Confirmed** or **Settling in X days**.

A **Canceled** tag means the Customer signed up and then canceled. That spot is available for someone else.

#### Charging for a Private Event

When hosting a Private Event, an Admin typically charges the Event Planner (the organizer) a lump sum rather than charging each attendee. See \[Private Events → Charge an Event Planner] for the full workflow.

#### Series pricing

See \[Series → Series pricing] for how to price a Series, set unit pricing, and configure prorated costs for late joiners.


---

# 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.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.