> 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/team-signup.md). # Team Signup ### Team Signup Appears to Overcharge the Customer Who Signs Up the Team When a Customer signs up a team for an Event, the App authorizes a hold on their card for the full team total (their spot plus their teammate's spot at the non-member rate). This hold can look like an overcharge, but no money has actually moved yet — the hold is released and the final charges are split out when the system bills the team on the day of the Event. #### Symptoms * Customer signs up a team for an Event and is shown a total that covers both spots (e.g. $35 for a $15 member + $20 non-member Event). * Customer agrees to the total, then sends an invite to a teammate. * Customer believes they are being charged the full team total in addition to the teammate's spot being charged separately, and reports an overcharge. * The invited teammate accepts and is shown their own spot rate. #### Cause The Hold for Teammates function places a pending authorization on the team-signup Customer's card for the full team total at the non-member rate. This is a hold, not a charge — no funds are captured at signup. The hold exists so that if the teammate fails to pay on the day of the Event, the team-signup Customer is "on the hook" and the spot is still paid for. Play passes can cover the team leader's own seat at signup, and guest passes can reduce the teammate hold. A teammate who pays for their own spot (split payment) can also redeem their own play pass when accepting the invite. The hold is released **upon charging**, which happens on the day of the Event: 1. The system first attempts to charge the teammate for their own spot. 2. If the teammate's charge succeeds, the hold on the team-signup Customer's card is released, and the team-signup Customer is then charged only their own portion. 3. If the teammate's charge fails, the full team total falls back onto the team-signup Customer's card, which is why the original hold was placed. #### Resolution Steps 1. Open the Event in the Admin Web App and locate the team's order(s). 2. Confirm the team-signup Customer'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. Explain to the Customer that the larger amount they saw at signup is a hold, not a charge, and that it will be released automatically when the teammate is successfully charged on the day of the Event. 5. After the Event has been billed, verify in the order history that the team-signup Customer was charged only their own portion and the teammate was charged their own spot. > **Note:** Holds can take several business days to disappear from the Customer's bank or card statement after release, depending on their card issuer. This is normal and not a PodPlay-side issue. #### If This Doesn't Fix It * If the Event has already been billed and the team-signup Customer was charged more than their own spot rate while the teammate was also successfully charged, that is a real overcharge and should be escalated — pull both order IDs and the Event ID and send to engineering. * If the teammate never accepted the invite and the Event was billed, expect the full team total on the team-signup Customer's card; this is the fallback behavior, not an overcharge. --- # 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/team-signup.md?ask=&goal= ``` `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.