How to Set Up a Custom Payment Gateway
Developer’s guide to integrating a custom payment gateway with Tilda
Tilda is integrated with popular payment systems like Stripe, PayPal, and 2Checkout. Here's how to integrate a custom payment system with your website using the Custom Payment Gateway.
All approved and tested integration templates are available in the public list of templates. All integrations have been created by the developers of payment systems. When you select a template, you can find a link to the payment system documentation and the developers’ email address for questions about integration. Tilda Support won’t be able to help with any questions regarding third-party integrations.
- ArsenalPay https://arsenalpay.ru/
- Best2Pay – https://best2pay.net
- PSCB – https://pscb.ru
- ENOTio – https://enot.io
- Express-pay – https://express-pay.by
- Prodamus – https://payform.ru
- CapustaSpace – https://capusta.space
- EPAY Halyk Bank – https://epay.kkb.kz
- UCS – https://ucscards.ru
- Paymo – https://paymo.ru
- PayOnline – https://www.payonline.ru
- Net Pay – https://netpay.ru
- Intercards – https://intercards.ru
- Paykeeper - https://paykeeper.ru/
- IPS - https://ips.su/ru_RU/
- Unitpay https://unitpay.ru/
- Invoicebox https://www.invoicebox.ru/ru/
- Express-pay – https://express-pay.by
- Modulbank – https://modulbank.ru
- Fondy - https://fondy.ru/
- Concordpay - https://pay.concord.ua/
- Monopay https://monobank.ua/
- Payboxmoney https://paybox.money/
To set up a full-fledged integration with a custom payment gateway, go to the Site Settings → Payment Systems and select "Custom Payment Gateway."
Important: If there is no template among the payment solution templates that suits you, contact the payment system developer team and send them a link to this guide. Creating a new template requires developers' participation.
You can select an integration template or create a custom one.
Templates are the presets of parameters for integrating a particular system. They may include unchangeable settings like the API URL or order number field and changeable settings ("Advanced settings").
If you see a template for your payment solution among the options, that means the developers have contacted us, so you can easily set up an integration with your payment system.
Templates are the presets of parameters for integrating a particular system. They may include unchangeable settings like the API URL or order number field and changeable settings ("Advanced settings").
If you see a template for your payment solution among the options, that means the developers have contacted us, so you can easily set up an integration with your payment system.
Please note that Tilda Publishing bears no responsibility for the operation and security of any third-party payment system integration.
Read the official Disclaimer Of Liability →
Read the official Disclaimer Of Liability →
DISCLAIMER OF LIABILITY
By expressing their intention to integrate with the Custom Payment Gateway service (hereinafter — CP Gateway) and/or by carrying out the actions for connection and further use of the selected payment resource (hereinafter — Payment system), the legal entity or individual entrepreneur who sent an application for integration (hereinafter — Applicant) and Tilda Publishing Platform User (hereinafter — User) hereby confirm their agreement with the following:
1. The Administration of the Tilda Publishing Platform (hereinafter — the Administration) does its best to provide Users with accurate and reliable information.
1.1. The Administration shall not be responsible for controlling the legitimacy of the information provided by the Applicants as well as for determining their legal rights and/or obligations.
1.2. By sending an application for integration, the Applicant guarantees and confirms that they have the legal status necessary and sufficient to carry out the activities on providing the execution of payment transactions as specified in the application, including the necessary permissions required by the national legislation.
1.3. The Applicant guarantees the legitimacy of using the claimed Payment system and confirms that its integration and further use do not infringe the rights and legitimate interests of third parties, including the rights to the results of intellectual effort.
2. In accordance with the applicable law, the Administration waives any guarantees and warranties, the provision of which may otherwise be implied, and liability with respect to the use of Payment systems integrated with the CP Gateway.
2.1. The Administration of the Platform does not guarantee the security of the Payment systems' use and their continuous work.
2.2. The Administration of the Platform provides only the necessary computing capacities that allow to integrate one or another Payment system with the CP Gateway with the purpose of its further use by the Users of the Platform on their projects.
2.3. The Administration is not a subject or stakeholder in the relationships arising between the Applicant, the User of the Platform, and third parties.
2.4. The Administration of the Platform is not liable for:
a) any actions and/or inactions of the providers of services, networks, software, or equipment;
b) any damage (direct/indirect damage, lost profits) that may occur as a result of the Payment systems' use, including but not limited to damage to any User's devices and information storage media and/or software, as well as to their business activities suspension.
3. The User is solely responsible for their choice and further use of a Payment system, as well as any activities associated with electronic commerce.
3.1. The User is responsible for ensuring compliance with any laws applicable to them and their activities on their own.
3.2. The User agrees that the use of the Payment system selected by them may be subject to additional fees.
3.3. The User uses their selected Payment system solely at their risk and responsibility, taking into account that they may be subject to legal and financial terms and conditions that regulate the activities of applicants and that the User is recommended to familiarize themselves with before using the selected Payment system.
4. Acting in compliance with the requirements of the law/ requirements (notifications, claims) of the competent authorities and/or their officials, the Administration of the Platform has the right at any moment to suspend or block access to any Payment system or delete it from the CP Gateway — irrespective of whether the relevant Payment system is connected in the User's project at a given moment with no obligations arising to the User themselves and/or their clients.
1. The Administration of the Tilda Publishing Platform (hereinafter — the Administration) does its best to provide Users with accurate and reliable information.
1.1. The Administration shall not be responsible for controlling the legitimacy of the information provided by the Applicants as well as for determining their legal rights and/or obligations.
1.2. By sending an application for integration, the Applicant guarantees and confirms that they have the legal status necessary and sufficient to carry out the activities on providing the execution of payment transactions as specified in the application, including the necessary permissions required by the national legislation.
1.3. The Applicant guarantees the legitimacy of using the claimed Payment system and confirms that its integration and further use do not infringe the rights and legitimate interests of third parties, including the rights to the results of intellectual effort.
2. In accordance with the applicable law, the Administration waives any guarantees and warranties, the provision of which may otherwise be implied, and liability with respect to the use of Payment systems integrated with the CP Gateway.
2.1. The Administration of the Platform does not guarantee the security of the Payment systems' use and their continuous work.
2.2. The Administration of the Platform provides only the necessary computing capacities that allow to integrate one or another Payment system with the CP Gateway with the purpose of its further use by the Users of the Platform on their projects.
2.3. The Administration is not a subject or stakeholder in the relationships arising between the Applicant, the User of the Platform, and third parties.
2.4. The Administration of the Platform is not liable for:
a) any actions and/or inactions of the providers of services, networks, software, or equipment;
b) any damage (direct/indirect damage, lost profits) that may occur as a result of the Payment systems' use, including but not limited to damage to any User's devices and information storage media and/or software, as well as to their business activities suspension.
3. The User is solely responsible for their choice and further use of a Payment system, as well as any activities associated with electronic commerce.
3.1. The User is responsible for ensuring compliance with any laws applicable to them and their activities on their own.
3.2. The User agrees that the use of the Payment system selected by them may be subject to additional fees.
3.3. The User uses their selected Payment system solely at their risk and responsibility, taking into account that they may be subject to legal and financial terms and conditions that regulate the activities of applicants and that the User is recommended to familiarize themselves with before using the selected Payment system.
4. Acting in compliance with the requirements of the law/ requirements (notifications, claims) of the competent authorities and/or their officials, the Administration of the Platform has the right at any moment to suspend or block access to any Payment system or delete it from the CP Gateway — irrespective of whether the relevant Payment system is connected in the User's project at a given moment with no obligations arising to the User themselves and/or their clients.
If your payment system isn't on the list, you need to contact the developers of the payment solution so that they request to create one.
To start the procedure, you need to specify the name and the URL of the payment system the user should be redirected to with a POST request to complete payment, a contact email, and any additional information that could help with the integration, such as links to the payment system's documentation.
To start the procedure, you need to specify the name and the URL of the payment system the user should be redirected to with a POST request to complete payment, a contact email, and any additional information that could help with the integration, such as links to the payment system's documentation.
Important: Creating a new template requires in-depth knowledge of payment gateway integration and programming. To make a template, you need to be a payment solution developer or have in-depth knowledge of the integration details.
As soon as the moderation team approves the template, it will become available in the list for a specific project. After that, you can modify the additional settings, change the names of the variables passed with customers' orders, and debug the integration.
First, you need to specify the names of all the critical and required fields whose data should be passed along with the customers' orders and modify the additional settings like case, format, and field length.
First, you need to specify the names of all the critical and required fields whose data should be passed along with the customers' orders and modify the additional settings like case, format, and field length.
After configuring the required fields, you may need to specify other variables passed when an order is created. You can add them in the "Additional field list" section. The number of list items depends on the integration needs.
You also need to set up the order signature and specify the rules for its formation (the excluded fields, sorting principle, delimiter, and encryption algorithm).
First, you need to select the signature rules or select "All fields" and specify the excluded fields, sorting principle, and delimiter. If you need a custom data format, select "Special rules" and set the rules of the custom format.
First, you need to select the signature rules or select "All fields" and specify the excluded fields, sorting principle, and delimiter. If you need a custom data format, select "Special rules" and set the rules of the custom format.
After that, you need to configure the successful payment indicator (the name and value of the parameter) and specify what the system should return in response to successful or declined payments.
Interaction format
1. The buyer adds a product to the shopping cart, fills out the form, and clicks on Checkout.
2. Tilda receives a request to save the new order and returns a set of parameters that will be included in the request for the payment system following the Mapping field list and the Additional field list from the Advanced integration settings.
2. Tilda receives a request to save the new order and returns a set of parameters that will be included in the request for the payment system following the Mapping field list and the Additional field list from the Advanced integration settings.
Important: Among the parameters, there must always be a field containing the order signature. The signature is generated from the other fields' values using a specific algorithm and the payment key. You can configure this algorithm in the "Order signature" section of the Advanced integration settings.
The user is redirected to the API URL of the template. The parameters are transferred using the POST method.
The payment system processes the parameters and, if the signature is correct, displays the payment form, processes the payment, and communicates with other systems if necessary.
The payment system can redirect the user to the success page after successful payment (if specified in the settings) or send a notification.
The payment system must also send a request to the notification URL—a dedicated Tilda server URL. This request must also transfer parameters and the signature using the POST method (the signature algorithms may differ). In the Advanced settings, you also need to add a field (and specify its value) used in verifying the payment status—that will be a successful payment indicator.
The order will be marked as paid on Tilda only after a request with the correct signature, order number, amount, and successful payment indicator has been sent to the notification URL.
The payment system processes the parameters and, if the signature is correct, displays the payment form, processes the payment, and communicates with other systems if necessary.
The payment system can redirect the user to the success page after successful payment (if specified in the settings) or send a notification.
The payment system must also send a request to the notification URL—a dedicated Tilda server URL. This request must also transfer parameters and the signature using the POST method (the signature algorithms may differ). In the Advanced settings, you also need to add a field (and specify its value) used in verifying the payment status—that will be a successful payment indicator.
The order will be marked as paid on Tilda only after a request with the correct signature, order number, amount, and successful payment indicator has been sent to the notification URL.
How to customize fields
To make it easier for users to understand which Tilda fields payment system fields correspond to, we provide you with the option to rename some fields and tooltips in the "Form Settings" section in the Advanced settings.
How to debug an integration
To debug an integration, create a page and configure it according to How to Set Up a Shopping Cart guide: Add the shopping cart and the product block to the page and publish it.
We suggest making a test payment and seeing if the payment goes through. If everything is fine, contact the moderation team and your template will be added to the public list.
We suggest making a test payment and seeing if the payment goes through. If everything is fine, contact the moderation team and your template will be added to the public list.
