> 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/payments/customer-payments/remove-a-credit-card.md).

# Remove a Credit Card

{% hint style="success" %}
**If the Customer has any pending transactions**, like an upcoming Reservation or Event which the system has not yet billed them for, of if they have a Membership, the system WILL NOT allow the credit card to be removed. This is to protect the Club from accidentally removing a Customer’s credit card. If a Customer wants to have their credit card removed, all future Reservations, Event signups, and Memberships must be canceled.
{% endhint %}

### Inside the Dashboard

Even if the system is the most secure technology platform for modern sports venues ([**read more here**](https://help.podplay.app/en/categories/309313-software-security-and-data)), there might still be a Customer who wants to have their credit card removed. To remove a Customer’s credit card:

* Navigate to the Customer page of the Dashboard
* Search and click on the Customer’s Profile
* Scroll down in the Overview tab
* Open the PAYMENT METHOD drawer
* Click on the trash can icon

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FomrzzhSZEtm2xXdAxJ7w%2FScreenshot%202026-06-27%20at%2021.33.10.png?alt=media&amp;token=a976adf9-9ff0-409b-8fa2-2a33d8904db3" alt=""><figcaption></figcaption></figure>

Once the credit card is removed from the Customer’s Profile, they are required to add a credit card again if they want to book in the future

### From the Profile

Customers can delete their credit card from their Profile. For a Customer to do so, they would:

* Navigate to the More tab of the App
* Click on the Account button at the top
* Click on Payment Methods
* Select the credit card they want to delete
* Notice and press the trash can icon in the pop-up window

A confirmation appears, and once confirmed, the credit card is removed from their Profile.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2F29eYyvaiaViFMLrQQ4BJ%2FScreenshot%202026-06-30%20at%2022.31.09.png?alt=media&amp;token=530a83e9-bfa5-4eeb-be73-371df8796cda" alt=""><figcaption></figcaption></figure>


---

# 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/payments/customer-payments/remove-a-credit-card.md?ask=<question>&goal=<user_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.
