> 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/what-happens-if-theres-an-issue-with-a-customers-credit-card.md).

# What happens if there’s an issue with a Customer’s Credit Card

* **All Customers will need to have their phone number and credit card (cc) entered into their account** before joining any Event or booking any Reservation.
  * The PodPlay system will require the cc information, including the full 16-digit card number, the expiration, the security number, and the zip code.
  * If this information is incorrect, there will be a purchasing error, and the Customer will be unable to participate in an Event.
* The Customer will also experience an error if they have not entered their phone number, and the Customer will be prompted to enter the proper information to complete the booking.
* This is how the Customer will experience the booking flow when they have not provided their phone number and credit card:
* If a Customer signs up for an Event and they have the proper information, an Admin will be able to see their information in the Admin Dashboard when clicking into that 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/what-happens-if-theres-an-issue-with-a-customers-credit-card.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.