How IaaS-provider helps with the organization of payment acceptance
How to optimize the work of the IaaS-provider - we constantly talk about this in our blog on Habré. A couple of examples of materials with our cases:
Prior to the launch of our project, we assumed that the bulk of clients would be individuals, but as a result, our services are also in demand from legal entities. From the point of view of working with documents, work with the latter had to be carried out in manual mode.
As we have automated other service systems, we have reached accounting tasks - the problem with legal entities has been solved, and for individuals we have connected Money. Online.
')
This tool suited us exactly until it ceased to work stably. Starting from one-off technical problems and to a global fall from 8 to 17 December 2014.
We began to look at additional systems.
We continued to work with Money.Online, but found out that this service temporarily suspended cooperation with the payment system PayPal. Independent study of the documentation showed that working with the PayPal API requires numerous “dances” you know with what.
For example, to import the client ID in the form of payment, we had to resort to various tricks with CSS rules and changes in standard elements. There was no simple solution - PayPal support service could not suggest a way out of the situation.
Anyway, we all set up and added PayPal as a new payment method.
This was followed by another battle with the API of the new payment gateway. This time it was Robokassa. Of course, this is a more familiar method of payment in the Russian-speaking segment of the Network.
Here we are faced with difficulties in parsing the documentation. A number of queries did not fit their description and gave the expected results as described. For example, a similar problem arose when implementing tests for gateway integration.
Communication with colleagues from Robokassa has eliminated a number of outdated descriptions in the documentation and move on. As a result, this gateway was also set up safely.
Our efforts allowed us to provide 1cloud with two additional payment tools. They complement Money.Online quite well and insure the situation in case of the next technological difficulties on the side of the payment gateway.
PS A little more about the work of our virtual infrastructure provider:
- Cloud Pricing Philosophy
- How to save on IT infrastructure
- How we developed our DNS manager
- Pre-installation of the control panel and on-the-fly license ordering
How it all began
Prior to the launch of our project, we assumed that the bulk of clients would be individuals, but as a result, our services are also in demand from legal entities. From the point of view of working with documents, work with the latter had to be carried out in manual mode.
As we have automated other service systems, we have reached accounting tasks - the problem with legal entities has been solved, and for individuals we have connected Money. Online.
')
This tool suited us exactly until it ceased to work stably. Starting from one-off technical problems and to a global fall from 8 to 17 December 2014.
We began to look at additional systems.
Paypal
We continued to work with Money.Online, but found out that this service temporarily suspended cooperation with the payment system PayPal. Independent study of the documentation showed that working with the PayPal API requires numerous “dances” you know with what.
For example, to import the client ID in the form of payment, we had to resort to various tricks with CSS rules and changes in standard elements. There was no simple solution - PayPal support service could not suggest a way out of the situation.
Anyway, we all set up and added PayPal as a new payment method.
Robokassa
This was followed by another battle with the API of the new payment gateway. This time it was Robokassa. Of course, this is a more familiar method of payment in the Russian-speaking segment of the Network.
Here we are faced with difficulties in parsing the documentation. A number of queries did not fit their description and gave the expected results as described. For example, a similar problem arose when implementing tests for gateway integration.
Communication with colleagues from Robokassa has eliminated a number of outdated descriptions in the documentation and move on. As a result, this gateway was also set up safely.
Result
Our efforts allowed us to provide 1cloud with two additional payment tools. They complement Money.Online quite well and insure the situation in case of the next technological difficulties on the side of the payment gateway.
PS A little more about the work of our virtual infrastructure provider:
Source: https://habr.com/ru/post/294184/
All Articles