> 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/sign-up-for-an-event/team-signup/overcharge-confusion.md).

# Overcharge Confusion

### Overview

When a Customer signs up a team for an Event, the App authorizes a hold on their card for the full team total (their own spot plus every teammate's spot at the Non-member rate). The hold looks like an overcharge on a bank statement, and no money has moved. PodPlay releases the hold and splits out the final charges when it bills the team on the day of the Event.

### Symptoms

* The Customer signs up a team for an Event and sees a total that covers both spots (for example, $35 for an Event priced at $15 Member and $20 Non-member).
* The Customer agrees to the total, then sends an invite to a teammate.
* The invited teammate accepts and sees their own spot rate.
* The Customer believes they are charged the full team total on top of the teammate's separate charge, and reports an overcharge.

### Cause

The Hold for Teammates function places a pending authorization on the team lead's card for the full team total at the Non-member rate. This is a hold, not a charge, and PodPlay captures no funds at signup. The hold exists so that the spot is still paid for if the teammate fails to pay on the day of the Event. The team lead stays on the hook for it.

A Play Pass can cover the team lead's own spot at signup, and a guest pass reduces the teammate hold. A teammate who pays their own share on a bill split invite can redeem their own Play Pass when they accept the invite.

PodPlay releases the hold at charge time, on the day of the Event:

1. PodPlay first attempts to charge the teammate for their own spot.
2. If the teammate's charge succeeds, PodPlay releases the hold on the team lead's card. PodPlay then charges the team lead only their own portion.
3. If the teammate's charge fails, the full team total falls back onto the team lead's card. This is why PodPlay placed the original hold.

### Resolution Steps

1. Open the Event in the Admin Web App and locate the team's order or orders.
2. Confirm the team lead's order shows an authorization hold, not a captured charge, for the full team total at the Non-member rate.
3. Confirm the teammate's order shows their own spot rate as a separate order once they accept the invite.
4. Tell the Customer that the larger amount at signup is a hold, not a charge. PodPlay releases it automatically when it charges the teammate on the day of the Event.

After PodPlay bills the Event, check the order history. Confirm PodPlay charged the team lead only their own portion, and charged the teammate their own spot.

{% hint style="info" %}
A released hold can take several business days to disappear from the Customer's bank or card statement. The delay depends on the card issuer. This is normal and is not a PodPlay-side issue.
{% endhint %}

### If This Doesn't Fix It

* **The teammate never accepted the invite and PodPlay billed the Event.** Expect the full team total on the team lead's card. This is the fallback behavior, not an overcharge.
* **The teammate joined on a covered ("free") invite.** The team lead stays liable for that spot at the invitee's Member or Non-member rate. If the teammate is a Member, the hold shrinks by the membership discount when they accept. See Team Signup.


---

# 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/sign-up-for-an-event/team-signup/overcharge-confusion.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.