📓
Hosted Checkout integration allows the partner to initiate a payment through our API and receive a checkout link in response.
The partner then redirects the payer to our hosted checkout page, where we manage the payment flow, including payer input, payment method handling, and any required authentication steps.

UI Example

This image is for reference purposes only. The final appearance and configuration of the checkout form may vary and can be customised based on your requirements.

Host-to-Host vs Hosted Checkout - Key Differences

Aspect	Host-to-Host (H2H)	Hosted Checkout
Who handles the checkout flow	Merchant / PSP	Our platform
Main request object	`Payment`	`PaymentIntent`
Payment details provided upfront	Yes	No, payer completes them later on the checkout form
When the actual Payment is created	During the initial API request	After the payer starts and completes the checkout flow
Typical use case	Merchant fully controls the payment experience	Merchant redirects the payer to our hosted checkout form

Supported Payment Methods

Payment Method	Availability Status
Bank Cards	🇷🇺 Russia (RUB) - Available 🇰🇿 Kazakhstan (KZT) - Available 🇺🇿 Uzbekistan (UZS) - Will become available later

Checkout Form Customisation

We can customise the checkout form to meet your business needs. At present, self-service customisation is not available, so all changes are applied by our team on your behalf.
To request any updates, please contact your Integration Manager.
The checkout form supports a range of configurable settings, including language options, displayed information, visual theme, external links, session lifetime, and return behaviour after payment completion.

Setting	Description	Possible values / notes	Default
`checkoutFormLocale`	Defines the language shown to the payer when they open the checkout form	RU, ENG	ENG
`displayLanguageSelector`	Controls whether the payer can switch the checkout form language manually	true / false	true
`displayStoreName`	Controls whether the store name is displayed on the checkout form. To display it, provide the store name in the `merchant` object during Intent creation	true / false	false unless configured and provided
`displayClientRefId`	Controls whether the order number is displayed on the checkout form. The value is taken from `clientReferenceId` provided during Intent creation	true / false	false unless configured
`displayOrderDescription`	Controls whether the order description is displayed on the checkout form. To display it, provide the description in the `Intent description` or `payment Intent description` during Intent creation	true / false	false unless configured and provided
`theme`	Defines the visual theme of the checkout form	light, dark, automatic	automatic
`customColours`	Additional colour customisation can be applied on request. Please contact your Integration Manager to discuss available options	Custom, upon request	Standard theme colours
`displayExternalLinks`	Controls whether links to Legal, Terms and Conditions, and Contacts are displayed	true / false	true
`displayPoweredBySection`	Controls whether the "Powered by" section is displayed	true / false	Configurable
`checkoutSessionLifetime`	Defines how long the checkout form session remains active. Once expired, the session can no longer be used and a new Intent must be created	Configurable duration	20 minutes
`displayBackToStoreButton`	Controls whether the payer sees the "Back to store" button. To use this button, the related return URL parameter must be provided during Intent creation	true / false	false unless configured
`autoRedirectToStore`	Controls whether the payer is redirected automatically back to the store after payment completion	true / false	false unless configured
`autoRedirectToStoreDelay`	Defines how many seconds the completion screen remains visible before the payer is redirected to the return URL provided during Intent creation	Integer value in seconds	Configurable