Template requirements

When creating your own payment page templates, follow the requirements and file naming rules below.

Core requirements

1. Passing the key and payment parameters. The payment page must contain a hidden Key field with the value {key}. Payment parameters are passed through it.
2. Passing additional parameters. Additional parameters can be passed in the DATA object when the session is initialized. To display their values on the page, use the {param} format, where {param} is the parameter name in lowercase.
3. Error handling. The page HTML must contain a block with the {error} placeholder, which is used to display errors when the server responds in a non-JSON format. To display errors for a JSON response, use a block with id="errorTop".
4. Resource location. All links to the resources used (CSS, images, etc.) must have the following form: /Templates/{Key}/{File}, where {Key} is the Merchant identifier.
5. No external navigation. The template must not contain links that redirect the user to third-party websites.
6. File location when using multiple templates. If multiple templates are used, all resources (CSS, JS, images, etc.) must be stored in a shared folder.
7. No external resources. Resources hosted outside the template must not be included. All images, style sheets, and scripts must be supplied with the templates and stored locally.
8. Multi-language support. You can use multilingual templates if needed. In this case, the language is passed via the {Language} parameter in the DATA object when the session is initialized.

File names

When templates use multiple languages, the {Language} parameter must be inserted into the file path. Two standard values are supported:

• Default: Russian (the default value)
• English: English

The paths to localized files must have the following structure:

/Templates/{Key}/{Language}/{File}

where:

• {Key} is the Merchant identifier
• {Language} is the interface language (Default or English)
• {File} is the name of the template, image, style, or script file

The template file name must follow this pattern:

[CUSTOMERS]VWMerchant-Add-MyCustom-English.template