> For the complete documentation index, see [llms.txt](https://docs.tiun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiun.io/reference/customer-account/payment-methods.md).

# Payment methods

Payment methods a customer uses at checkout are saved to their tiun account, so they can pay at any tiun business without entering them again. In the [account portal](https://docs.tiun.io/reference/customer-account/overview.md), the **Payment methods** section lists them.

***

## The default method

One saved method is the **default**. It's preselected the next time the customer checks out, at your business or any other. The customer can make another saved method the default from its detail page, or pick a different one in the checkout overlay.

***

## Removing a method

Opening a payment method shows the subscriptions currently charged to it. The customer can remove it with **Remove payment method**, with one exception: a method can't be removed while an **active subscription** uses it. The portal asks the customer to cancel those subscriptions first.

So removing a payment method never stops a running subscription, and never changes what's in `productAccess`.

***

## Expiring cards

When a bank reissues or replaces a card, tiun updates the saved details in the background and the subscription keeps renewing. If a renewal payment fails anyway, access ends as described in [Subscriptions](https://docs.tiun.io/reference/checkout/subscriptions.md#renewal-and-expiration).

***

## Where to go next

* [Subscriptions and transactions](https://docs.tiun.io/reference/customer-account/subscriptions-and-transactions.md) — billing details and cancellation.
* [Checkout / How it works](https://docs.tiun.io/reference/checkout/how-it-works.md) — which payment methods checkout offers.


---

# 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.tiun.io/reference/customer-account/payment-methods.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.
