> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/checkout/payment-method-selection.md).

# Payment Method Selection

## Checkout Payment Method Selection

Present available payment methods to the customer and route them into the appropriate payment flow. This section also covers the entry points for cash on delivery, bank transfer (funds transfer), pay later, and external checkout provider shipping confirmation.

### Request Format

Include the following header in all checkout requests:

* **x-requested-with**: `XMLHttpRequest`

### Authentication

A valid session cookie is required. The checkout URL token mechanism is also supported for external redirect flows.

### Dynamic Settings

#### CHECKOUT\_WITH\_TOKEN\_ALLOW\_ANONYMOUS

Controls whether anonymous users may access checkout via token-based URLs. When disabled, only authenticated users can use token checkout links.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apidocs.akinon.com/commerce-openapis/checkout/payment-method-selection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.