Payment Page
This section provides the information about working with the Payment Page payment form.
Overview
This article introduces the information about the payment form, the general workflow of using the form, and the capabilities overview—Overview.
Integration
The information about setting up Payment Page in different cases:
- Quickstart—about quick and easy ways to organise payment processing with the application of ready-to-use solutions, such as SDKs and source code examples, to their fullest extent.
- Interaction concepts—about organising the work with Payment Page on the web service side in various cases based on the principles of the payment platform operation.
- Integration using SDK—about using SDKs for mobile applications and data signing.
- Integration via CMS—about embedding the payment form into the websites on the basis of various CMSs and with the help of plug-ins.
UX configuration
The information about various options of the payment form UX configuration:
- Options for opening Payment Page—about the ways of opening the form, including its opening in a separate tab, modal window, and an iframe object.
- Options for redirecting customers to third-party services—about the ways of opening auxiliary pages when working with different payment methods.
- Options for redirecting customers to the web service—about the ways of redirecting customers from the payment form to the web service via the specified URLs.
Basic actions
The information about the basic actions that can be performed via the payment form, with the description of logical models, user scenarios, as well as the request and callback formats:
- Payment models and statuses—about the types of the payments that can be processed via Payment Page, payment workflows, as well as possible payment and operation statuses.
- Purchase processing—about processing purchases that result in immediate debiting of funds.
- Authorisation hold—about placing a hold on funds within a two-step purchase.
- COF purchase registration—about registering purchases followed by a series of recurring debitis.
- Payment instrument verification—about debiting of a zero amount or placing a hold on funds for validating the payment instrument.
- Tokenization—about opening the payment form for registering payment data and forming a token for this data.
Additional capabilities
The information about various capabilities for boosting payment acceptance rates, customer convenience, and the quality of the provided services—Auxiliary procedures and additional capabilities and Customisation.
Additional integration options
The information about integration via Telegram and integration via the merchant's in-house payment form by implementing an encryption script in this form—Payments by using Telegram bot and Card data encryption script.
Technical aspects
The information about various technical aspects of working with program requests, digital signature, callbacks, and Payment Page in general—Payment Page API Description.