> For the complete documentation index, see [llms.txt](https://help.checkoutbuilder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.checkoutbuilder.com/customizations/payment-customizations/remove-a-payment-method.md).

# Remove a Payment Method

#### 📝 Description <a href="#description" id="description"></a>

This widget allows you to hide specific payment methods at checkout, giving you greater control over which options customers can use based on your business needs, location, or promotion strategy.

***

#### ⭐️ Popular / Recommended Use Cases <a href="#popular-recommended-use-cases" id="popular-recommended-use-cases"></a>

* Hide methods that aren’t supported or practical in certain countries.
* Remove high-fee payment options to encourage cost-effective alternatives.
* Eliminate rarely used payment methods to streamline customer decision-making.
* Hide specific methods (like “Buy Now, Pay Later”) for certain sales or discount events.

***

#### 🛠️ How to Set Up <a href="#how-to-set-up" id="how-to-set-up"></a>

Watch the step-by-step guide below:

{% @arcade/embed flowId="Pvmjrd1yrH2vluf0RxgQ" url="<https://app.arcade.software/share/Pvmjrd1yrH2vluf0RxgQ>" %}

***

### 📬 Support

Need help? Our support team is here—just reach out below.

👉 Visit the [Support](https://help.checkoutbuilder.com/support) page\
📧 Email us at <hello@checkoutbuilder.com>\
💬 Or use the chat icon in the bottom right corner of the app dashboard.

We’re here to help!&#x20;


---

# 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://help.checkoutbuilder.com/customizations/payment-customizations/remove-a-payment-method.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.