> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/data-model/payments-and-tax/payment-methods.md).
# Payment methods
The payment source types you can offer per market and how they connect to payment gateways
{% hint style="info" icon="lightbulb" %}
Each market's checkout payment experience is driven by its payment methods — they determine which gateway processes each payment and what options customers see.
{% endhint %}
## What is a payment method?
[Payment methods](/core-api-reference/payment_methods.md) are the types of payment sources you can offer in a market or a store. They let you provide different payment options to customers. Payment methods can carry a price charge and must be present before a customer places an order.
Each payment method is associated with a [payment gateway](/data-model/payments-and-tax/payment-gateways.md). The payment source type used with a payment method must match the parent gateway. You can differentiate the available payment method options by market. Supported payment source types include Adyen, Axerve, Braintree, Checkout.com, credit card, external payment, Klarna, PayPal, Satispay, Stripe, and wire transfer.
A payment method not already associated with a market or a store can be set as the default payment method for one or more markets.
---
# 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.commercelayer.io/data-model/payments-and-tax/payment-methods.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.
