Payment pages templates

Payture.js library is designed to streamline template management required from Merchant in case of payment at Payture gateway side.

This library contains all functionality that could be needed to obtain and submit Customer’s bank card data during payment or card registration procedure. Payture.js is used by payment, card registration, and redirect webpage templates in Payture InPay and Payture eWallet interfaces.

Please see below for basic examples that will allow you to start using Payture.js in a minimum of time.

Before you start using Payture.js

All you need to do is to embed the following scripts into your payment webpage HTML code:

<script type="text/javascript" src="/Templates/jquery.11.min.js" ></script>
<script type="text/javascript" src="/Templates/jquery.migrate.min.js" ></script>
<script type="text/javascript" src="/Templates/device.min.js" ></script>
<script type="text/javascript" src="/Templates/payture.js" ></script>

Standard templates

To call the card payment script with default parameters, use function:
Payture.InPay();
When calling the script you can enable or disable any available options at your convenience. For example, you can disable card type (Visa of MasterCard) auto-detection:
Payture.InPay({
	DetectCardType : false
});
Download InPay templates
To call the add card script with default parameters, use function:
Payture.eWalletAdd();
To call the card payment script with default parameters, use function «eWalletPay». When calling the script you can enable or disable any available options at your convenience. For example, you can disable card type (Visa of MasterCard) auto-detection:
Payture.eWalletPay({
	DetectDevice : false
});
Download eWallet templates
default
  • Each template must contain a hidden field Key with value {key}; this field is used to submit payment parameters
  • Webpage HTML code must contain {error} text block, which is to be displayed in case of error
  • The template webpage must not contain any hyperlinks redirecting users to external websites
  • The template webpage must not use any external resources; all required image files, style sheets, and script files must be submitted together with the template webpage itself
  • Any additional payment parameters can be sent as a part of DATA parameter, during session initialization. To display them on the payment webpage, please use {param} record, where {param} – name of the submitted parameter, lowercase
  • Links to any resources (images, style sheets) must be in format: /Templates/{Key}/{File}, where {Key} – Merchant’s ID
  • When using multiple templates, it is recommended to store resources for all templates in a common folder
  • If necessary, you can use multiple templates for the same webpage. In this case, you submits {TemplateTag}, {Language} parameters as a part of DATA parameter, during session initialization

Template names must follow this convention:

[{API}]{Key}-{Type}-{TemplateTag}-{Language}.template

[MERCHANT]Merchant-Pay-Default-Default.template
[CUSTOMERS]VWMerchant-Pay-Default-Default.template

ParameterDescriptionValue
{API}Interface usedMERCHANT — for InPay interface
CUSTOMERS — for eWallet interface
{Key}Internal Merchant IDby default, Merchant
{Type}Template typePay — payment template
Add — add card template
Return — return page template
{TemplateTag}Template name, if multiple templates are usedby default, Default
{Language}Template name, if multiple languages are usedby default, Default
en less than more than $