> 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/alternative-payment-methods.md).

# Alternative Payment Methods

## Checkout Alternative Payment Methods

Integrate Bex (BKM Express), Garanti Pay (GPay), Cash Register, and Confirmation Payment into your checkout. Each method follows a distinct step sequence—use the one that matches your storefront configuration.

**Bex** is a bank consortium payment method. The flow covers BIN lookup, nonce generation, installment selection, and payment completion.

**Garanti Pay (GPay)** redirects customers to an external page for QR-code or link-based payment and returns them upon completion.

**Cash Register** is a point-of-sale method for store staff. It supports installment selection and in-store payment completion.

**Confirmation Payment** lets the customer place an order first and confirm payment later through a separate channel. The flow includes agreement review and a confirmation step.

### Authentication

These endpoints support both authenticated and anonymous sessions.

* **Authenticated users**: Session cookie (`sessionid`) tracks checkout progress.
* **Anonymous users**: Guest checkout is available when the `CAN_GUEST_PURCHASE` setting is enabled.

### Request Format

Include the following header in all checkout requests:

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

### Dynamic Settings

The following settings are managed at runtime through the admin interface and do not require a server restart.

#### CASH\_REGISTER\_AUTH\_CONF

Authentication credentials for the cash register payment service. Includes the service username and password.

#### INSTALLMENT\_FILTERS

Filters applied during Bex and Cash Register installment selection to restrict the available options.

### Static Settings

The following settings are configured in the server environment and require a restart to take effect.

#### DEFAULT\_CARD\_SLUG

Fallback card identifier used when a Bex BIN number lookup returns no match. Defaults to `other`.

#### GPAY\_BIN\_NUMBER

The identifier used to look up the virtual card for Garanti Pay transactions. Must match a record in the database. Defaults to `GPAY00`.

#### CASH\_REGISTER\_DEFAULTS

Fallback store staff information (staff ID, email address, and store ID) used when the corresponding request headers are absent.


---

# 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/alternative-payment-methods.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.
