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