> 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/customer-had-a-payment-issue-when-signing-up-for-an-event.md).

# Customer had a payment issue when signing up for an event

* If a Customer has signed up for and secured a spot at an Event, they will be marked as a participant for that Event.
  * If there is an issue during sign-up, the Customer will receive an error message about their credit card (cc) and will be asked to update their cc information. Once the Customer has updated their cc information, they can attempt to sign up again and secure their participation in the Event.
  * If there is an issue after sign-up, an Admin will see a tag labeled Charge Failed in the Event’s Purchase tab.
    * If an Admin notices this, please note that the Customer is also aware the signup failed, as the Customer is provided an error message in the front of the App.
    * Normally, a Customer will update their cc on file and try again, so the Purchase tab of the Event will look like a Customer had a Charge Failed, then Confirmed (or Settling in x-time if the Event has yet to finish).
* If the Customer has a Canceled tag next to their name, the Customer signed up for the Event and then canceled their participation in the Event. That spot be free for another Customer to join the Event.


---

# 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/customer-had-a-payment-issue-when-signing-up-for-an-event.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.