> 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/wallet-and-redirection-payments.md).

# Wallet & Redirection Payments

## Checkout Wallet & Redirection Payments

Integrate digital wallet payments and external payment provider redirects into your checkout.

**Wallet** payments let customers pay using a pre-funded account balance. The flow covers wallet selection, payment initiation, redirect-based completion, and a return callback page.

**Redirection payments** redirect the customer to an external payment provider. On return, the result is processed via a callback URL.

**Confirmation Payment Complete** is the final step of the deferred confirmation payment flow initiated in the alternative payments section.

### 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.

#### USE\_ONE\_TIME\_TOKEN

Controls whether a single-use token is appended to redirect callback URLs to prevent replay attacks. When enabled, the token is validated on return before the payment result is processed.

### Static Settings

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

#### ORDERS\_USE\_ISOLATED\_PRE\_ORDER\_ON\_RETURN

When enabled, an encoded order number is embedded in callback URLs so the correct session can be restored after a redirect, even if the browser session has changed (for example, in mobile app redirect flows).


---

# 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/wallet-and-redirection-payments.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.