> 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/profiles/creating-a-customer-profile/add-and-use-different-credit-card-s.md).
# Change Credit Card(s)
### Adding a Credit Card
For a Customer to add a credit card to their Profile, they will:
* Navigate to the More tab of the app (most frequently 1bottom right)
* Click on the `Account Info` button (top button)
* Click on the button called `Payment methods`
### Using multiple Credit Cards
Once a credit card has been added, the Customer has the option to use different payment methods for various purchases. As an example:
* One credit card for booking Reservations or Event signups (default card)
* Another credit card for their Membership subscription
If the Customer wants to have the same payment method for all purchases, the card they add on file will become the default.
If the Customer wants to use different credit cards, they can click on the “Payment methods” button inside the Account Info section of the app and add another credit card. They can do so by:
* Clicking on the Default Payment Method
* Notice a pop-up appears
* Select “ADD PAYMENT METHOD”
* Completing the visible boxes to add their new credit card
Once a 2nd credit card is on file, the Customer can choose which credit card is for which purchase.
In the below screenshot, there is one card used as the Default Payment Method and another card used as the Membership Payment Method.
Adding or selecting a different credit card is also available during the booking flow.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.podplay.app/profiles/creating-a-customer-profile/add-and-use-different-credit-card-s.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
