Payment page templates
Payment page templates let the Merchant customize the look of the Payture payment page to match its brand. This section covers working with the Payture.js library, the standard InPay and eWallet templates and their configuration parameters, enabling additional payment methods, widget templates, and template requirements and file naming rules.
Using the Payture.js library
The Payture.js library is designed for working with payment templates on the payment gateway side and ensures that bank card data is collected and transmitted correctly. It is used in payment templates, for card binding, and on the return page in the Payture InPay and Payture eWallet interfaces.
All library templates are responsive and display correctly on devices with various screen sizes and resolutions.
Connecting the library
To work with the library, add the following resources to the HTML code of the payment page:
<link rel="stylesheet" href="/Templates/_Resources/css/css.css">
<!-- Main library -->
<script type="text/javascript" src="/Templates/_Resources/js-min/payture.min.js"></script>
<!-- Helper library -->
<script type="text/javascript" src="/Templates/_Resources/js-min/payture-helper-utils.min.js"></script>Once the libraries are connected, you can use the tools they provide to work with card data and interact with payment templates.
Sections
| Section | Description |
|---|---|
| Standard templates | Connecting the basic InPay and eWallet templates and their configuration parameters |
| Additional payment methods | Enabling Mir Pay, SBP (Russia's Faster Payments System), T-Pay, SberPay, and Podeli in InPay and eWallet templates |
| Widget templates | Templates for payment via the Payture payment widget |
| Template requirements | Mandatory requirements for custom templates and file naming rules |
Faster Payments System (SBP)
Accepting QR code payments via Russia's Faster Payments System (SBP). The GetQRCode method, status polling recommendations, test scenarios.
Standard templates
Standard InPay and eWallet payment templates and their configuration parameters: language, visibility of interface elements, additional fields.
