Creating a payment system from scratch. How to make a payment in an online store through payment systems? Payment acceptance options

Chapter 4. Payment systems as elements of the national payment system of Russia

§ 1. Procedure for creating a payment system

As already noted, the payment system is an artificial formation, the basis of which is the will of a specific person - the operator of the payment system - and which operates on the basis of contractual relations between all its participants. The rules of the payment system are established by the payment system operator.

Payment system operator is a legal entity that created the payment system. The operator of the payment system may be a credit organization, an organization that is not a credit organization and created in accordance with the legislation of the Russian Federation, the Bank of Russia or Vnesheconombank (Article 15 of the Law on the National Payment System). From the text of the norm of this article it follows that the operator of the payment system cannot be a foreign legal entity. This norm is one of the manifestations of the principle of the national character of the national payment system of Russia. All foreign organizations that provided payment services in any form in Russia are now required to bring their activities into compliance with the requirements of the Law on the National Payment System. The simplest way is for such an organization to obtain the status of a payment system operator.

The Bank of Russia operates as a payment system operator on the basis of the Law on the National Payment System. All other organizations must obtain the status of payment system operator in the manner prescribed by the Law on the National Payment System.

An organization intending to become a payment system operator must send a registration application to the Bank of Russia. The procedure for sending this application is regulated by the Bank of Russia Regulations on the procedure for sending to the Bank of Russia an application for registration of a payment system operator dated May 2, 2012 No. 378-P.

If a credit institution intends to become a payment system operator, the following documents should be attached to the registration application:

• decision of the credit institution’s management body on organizing a payment system;
• payment system rules;
• a list of payment infrastructure service operators that will be engaged to provide payment infrastructure services in the payment system.

If a non-credit organization intends to become a payment system operator, it must meet the following requirements:

• have net assets of at least 10 million rubles;
• individuals holding the positions of the sole executive body and chief accountant of such an organization must have a higher economic, higher legal education or higher education in the field of information and communication technologies, and if they have another higher education, experience in managing a department or other division of a credit institution or payment operator systems for at least two years;
• individuals holding the positions of the sole executive body and chief accountant of such an organization should not have a criminal record for crimes in the economic sphere, as well as facts of termination of an employment contract with them at the initiative of the employer on the basis provided for in paragraph 7 of Part 1 of Art. 81 of the Labor Code of the Russian Federation, during the two years preceding the date of submission of the registration application to the Bank of Russia.

The following documents are attached to the registration application of an organization that is not a credit institution intending to become a payment system operator:

• constituent documents;
• decision of the authorized body of such an organization on the organization of a payment system;
• business plan for the development of the payment system for the next two calendar years, indicating the goals and planned results of organizing the payment system, including an analysis of market and infrastructure factors;
• payment system rules that comply with the requirements of this Federal Law;
• a list of payment infrastructure service operators that will be engaged to provide payment infrastructure services in the payment system;
• written consent of the credit institution, including in the form of an agreement concluded with it, to become a settlement center of the payment system;
• documents containing information on the size of the organization's net assets, with the attachment of financial reporting forms drawn up as of the last reporting date preceding the date of submission of documents to the Bank of Russia for registration;
• documents confirming compliance with the requirements.

Within a period not exceeding 30 calendar days from the date of receipt of a registration application from an organization intending to become a payment system operator, the Bank of Russia makes a decision to register the said organization as a payment system operator or a decision to refuse such registration.

If a decision is made to register an organization as a payment system operator, the Bank of Russia assigns a registration number to the organization, includes information about it in the register of payment system operators and sends the organization a registration certificate no later than five working days from the date of adoption of this decision.

The payment system must have a name specified in the rules of the payment system, containing the words “payment system”. No organization in the Russian Federation, with the exception of an organization registered in the register of payment system operators, may use the words “payment system” in its name (company name) or otherwise indicate the activities of a payment system operator. Operators of payment infrastructure services and payment system participants have the right to indicate their affiliation with the payment system in accordance with the rules of the payment system. The Bank of Russia has the right to use the words “payment system” in relation to the payment system of the Bank of Russia.

The Bank of Russia refuses to register a credit organization as a payment system operator in the following cases:

The Bank of Russia refuses to register an organization that is not a credit institution as a payment system operator in the following cases:

• failure to submit required documents;
• establishing the organization’s non-compliance with the requirements provided for organizations that are not credit institutions and intend to become payment system operators;
• inconsistency of the developed rules of the payment system with the requirements of the Law on the National Payment System.

In case of refusal to register as a payment system operator, the Bank of Russia notifies in writing the organization that sent the registration application, indicating the grounds for refusal no later than five working days from the date of the decision.

A payment system operator may be excluded by the Bank of Russia from the register of payment system operators. This may happen:

• on the basis of an application from the payment system operator indicating the working day on which information about the organization is excluded from the register of payment system operators - on the working day specified in the application, but not earlier than the day the application of the payment system operator is submitted;
• in the event of repeated failure to comply with orders requiring the elimination of a violation affecting the uninterrupted functioning of the payment system, within one year from the date of sending the first order of the Bank of Russia to eliminate such a violation - on the business day following the day the Bank of Russia made a decision;
• in the event of repeated application to a payment system operator, which is a credit institution, during the year for violation of legal requirements, if the said violation affects the uninterrupted functioning of the payment system, the measures provided for in Article 74 of the Law on the Bank of Russia - on the working day following the day of adoption decisions by the Bank of Russia;
• if the Bank of Russia, when carrying out supervision, establishes the fact of a significant discrepancy with the information on the basis of which the registration of the payment system operator was carried out - on the working day following the day the decision was made by the Bank of Russia;
• when the Bank of Russia revokes the license to carry out banking operations from a credit institution that is an operator of the payment system - on the business day following the day the license was revoked by the Bank of Russia;
• in the event of liquidation of the payment system operator as a legal entity - on the business day following the day on which the Bank of Russia became aware of the liquidation of the legal entity that is the payment system operator.

Exclusion of information about an organization from the register of payment system operators for other reasons is not permitted.

For a payment system operator that is a credit institution, the Bank of Russia or Vnesheconombank, it is allowed to combine the activities of the payment system operator with the activities of a money transfer operator, an operator of payment infrastructure services and other activities, if this does not contradict the legislation of the Russian Federation. A payment system operator that is not a credit institution may combine its activities with the activities of an operator of payment infrastructure services (with the exception of a settlement center) and with other activities, if this does not contradict the legislation of the Russian Federation. This seems absolutely logical. Thus, the transfer of funds is a banking operation that can be carried out by credit institutions on the basis of a license from the Bank of Russia; The Bank of Russia and Vnesheconombank carry out this operation on the basis of laws defining their status. As for payment infrastructure service operators, for each of their three types, specific requirements and restrictions are established in relation to persons entitled to carry out the activities of a particular operator. So, for example, a settlement center executes orders of payment system participants by debiting and crediting funds to the bank accounts of payment system participants, which is a banking operation, so a settlement center can only be a credit organization, the Bank of Russia or Vnesheconombank. And the functions of an operational center can also be performed by an organization that is not a credit institution, since its activity consists of ensuring the exchange of electronic messages between participants in the payment system and other interested parties and is not related to the provision of banking services.

The payment system operator is obliged to:

• determine the rules of the payment system, organize and monitor their compliance by payment system participants and payment infrastructure service operators;
• engage payment infrastructure service operators, except for the case where the payment system operator combines the functions of a payment infrastructure service operator;
• maintain a list of payment infrastructure service operators, ensure uninterrupted provision of payment infrastructure services to payment system participants;
• organize a risk management system in the payment system, assess and manage risks in the payment system, ensure uninterrupted functioning of the payment system;
• provide the possibility of pre-trial and (or) arbitration consideration of disputes with payment system participants and payment infrastructure service operators in accordance with the rules of the payment system.

A payment system operator that is not a credit organization is obliged to engage a credit organization as a settlement center, which has been transferring funds to bank accounts opened with this credit organization for at least one year.

From the author: Hello, friends! According to statistics, about 10% of online store visitors are eliminated at the stage of paying for their purchase, because they simply cannot understand how to pay for a product or service, or the form of payment presented on the site is inconvenient for them. In our article today you will learn how to make a payment in an online store. And this is perhaps the easiest way to increase the number of sales without investment.

Since most people start creating an online business without legal registration, we will consider the process of connecting payment to an online store for an individual. Our task today is to organize the process of transferring money from site users who want to purchase goods to your bank card. Moreover, everything should work automatically.

If you are creating an online store for the first time, we recommend that you first read about creating effective commercial websites. If you have an online platform ready for sales, you can immediately proceed to consider the question of how to organize payment in the online store.

Technical side of the issue

From a technical point of view, the process of creating a payment in an online store is as follows. The customer makes a purchase and is issued an invoice. Next, he selects a suitable payment system and enters the necessary data to make the payment.

If the user has specified everything correctly, then the payment system server sends a request to the pre-specified URL of the online store, and the trading platform, in turn, transfers money to the client’s account. In case of incorrectly specified data or other technical failures, the system will notify the person that the payment has not gone through.

If the operation is successful, the person will be redirected to a special page where there will be a comment indicating that the payment has been made and the money has been credited.

Selecting a payment system

There are a lot of different payment systems, however, let's focus on how to set up payment in an online store based on the 5 most popular of them.

Robokassa

Connection takes place in a few simple steps: register on the website, provide online store details, and set up a payment form on your website. The specifics of working with Robokassa also require special moderation. The system requires the following specific details to be present on your website:

contact information with store representatives.

The payment fee varies depending on the chosen payment system and can reach 12%.

W1

Connection occurs in a similar way: registration, specifying personal data, setting parameters to suit your own needs. Commission - from 3%.

Qiwi wallet

The basic connection procedure is also simple. You go through a quick registration, then you are assigned a specific manager, with whom you undergo further consultation on technical issues. The specifics of the Qiwi wallet require, in addition to entering standard data by the user, also checking the validity of the phone number.

Qiwi commission is 1% on all transfers.

Yandex money

This is one of the most popular types of payment systems, so we decided to mention it so that you don’t have any questions about this. The Yandex.Money system does not involve working with individuals. Moreover, even if you are a legal entity, there is still a minimum financial limit below which cooperation with an online store seems impossible.

Therefore, you will have to wait a little while connecting Yandex.Money until the store gains proper momentum. If the availability of this payment method is important for you, then give preference to Robokassa as the main payment system for your online store. This is the only external platform that supports Yandex.Money.

WebMoney

Organizing automatic payment acceptance in the WebMoney system will require a little more time. First of all, you need to register your personal passport. This may take about a week, because WebMoney requires sending a notarized application using Russian Post.

After this, add the online store to the site catalog on megastock.ru. It will take another 1-3 days. The advantage of the system is that you can test the payment (in fact, everything goes in a standard way, only money is not withdrawn). This advantage allows you to catch errors in the code in advance.

The funds transferred by the client go to the WebMoney wallet specified during registration. The commission is provided only for making the payment itself (it is withdrawn from the client).

What is the value of connecting online payment?

However, owners of physical goods will also benefit significantly from connecting the payment system to the online store. The latter will save a lot of time from sending account numbers to clients and unnecessary waiting for people to deposit the required amount. In turn, payment systems will allow customers to save on delivery and save them from financial red tape.

It is worth noting that we have not studied all existing payment systems, but only the most popular ones.

What should legal entities do?

To connect online payment to an online store for a legal entity, you need to perform almost the same steps. Just keep in mind that it will take a little more time to organize the process. This is due to the need to conclude a formal agreement providing for more thorough checks of your activities.

You received a detailed answer on how to choose a payment system for an online store and connect it properly. The procedure is not complicated, the main thing is to carefully fill out the data when registering, otherwise you will then spend a lot of time correcting them in support.

If you want to learn more about the functionality of your online store, we recommend taking note of several useful online courses from.

Not a single person who works on the Internet can do without electronic payment systems. After all, you need to store your earned money somewhere and somehow get it in cash! Many websites for making money provide several payment systems for withdrawing money, and from the payment system you can easily withdraw money to any bank card.

They are one of the main services for non-cash payments around the world. Using payment systems, you can make online purchases, transfer and exchange money, pay for various services and much more. In other words, electronic payment systems perform the same financial transactions as the Internet services of various banks. Therefore, payment systems and banks are very closely related and often cooperate with each other. This allows you to transfer money both from the payment system to the bank and from the bank to the payment system without any problems. I suggest you familiarize yourself with the main electronic payment systems that are used on almost all sites for making money.

The best electronic wallet for Russian citizens. After registration, you need to identify yourself in order to enjoy all the privileges of this payment system. You will receive various bonuses and discounts on many products, as well as pay for most services. But most importantly, you can apply for a Yandex.Money card and withdraw cash from any ATM without commission! You can order a card in the "Yandex.Money Cards" section.

The most widespread payment system, founded in 1998. Currently, the number of its users exceeds 30 million people. This payment system is ideal for withdrawing money from all Russian-language sites for earning money. In the Webmoney payment system you can register electronic wallets of many currencies: rubles (WMR), hryvnia (WMU), dollars (WMZ), euros (WME) and others. Webmoney is a very serious system that has many levels of protection to ensure the safety of its clients' cash accounts. Therefore, the registration process has quite a lot of stages, but it's worth it!

This payment system was founded in Georgia 4 years ago and has its representative offices in Russia and the UK. In this short period of time, it has become very popular and has a number of significant advantages compared to other payment systems. Withdrawal of funds to the Payeer wallet is available on Russian-language sites for earning money and on some foreign ones. After simply registering in this system, you will have access to an electronic account into which you can transfer rubles, dollars and euros. Also, the Payeer payment system has its own internal exchanger, which will allow you to exchange currencies from various electronic wallets.

A foreign payment system in which you can open a dollar wallet. If you are going to make money on foreign sites, then this system will become indispensable for you. The Payza payment system is used on almost all sites that pay in dollars. Registering in this system is not difficult. The only obstacle is that the site is entirely in English, but you can use the translator in your browser to do this.

A universal payment system that is used in many foreign and Russian-language sites for earning money. On Perfect Money you will have access to electronic accounts in dollars, euros, precious metals (gold) and Bitcoin, which can be exchanged between each other. The electronic payment system is very convenient and easy to use, and it also has a Russian interface. I advise everyone to register with Perfect Money, since, based on practice, this payment system has to be used quite often.

October 29, 2010 at 5:28 pm

How payment systems are created: part one

• Blog of the Mail.ru Group company

In the summer of 2009, the Mail.Ru company announced the launch of a new payment system created by its own developers (remember that before this, the MoneyMail payment system provided technological and service support for the [email protected] project). The new project was supposed, among other things, to offer portal users a single, convenient and secure mechanism for paying for the company’s various services - from entertainment projects (Games, Applications in My World) to e-commerce projects (Products, Real Estate, Mailings).

A year has passed. [email protected] continues to develop, increasing the number of financial instruments for both users and stores. For users, this is the opportunity to make transfers within the system, pay for various services and goods (from paying for numerous games, cellular communications, the Internet and housing and communal services to purchasing clothes and tickets), the ability to deposit from bank cards and withdraw to virtual Visa cards. Tools for automating payment acceptance or replenishing user accounts are being actively developed for stores - many functions of the payment system are available via API.

In addition to the obvious functions mentioned, there are also technological ones, which are talked about much less often, but which are no less significant for the company as a whole. For example, portal services and stores connected to [email protected] have the ability to accept payments from users who keep their electronic funds in other payment systems - WebMoney, Yandex.Money and a number of others. An equally important part of the system is SMS processing, with the help of which visitors from many countries can pay for the services of various portal services without having to open an account in the payment system.

With this article we open a whole series of stories about how our payment system works from the inside, what tools we use to ensure its reliable operation, how we work with dozens of external systems, what problems we encountered, how we solved them and what conclusions we drew . In addition to technical articles, we will try to talk about how to use our payment system to expand the financially active audience of your online stores and social networking applications. If you are interested in any other topics regarding [email protected], ask, we will try to cover it.

As the Steel Was Tempered

The task of starting work on a new project was assigned to our department at the end of 2008. At that time, payment systems were not the types of projects that Mail.Ru was accustomed to developing, launching and successfully operating. However, already at the stage of setting the problem there was an understanding What had to be taken into account and implemented during the development process.

We called these requirements “MMM” (this is, of course, a joke) after the first letters. Here they are:

• M scalability
• M multi-currency
• M novelty

A little more about each of them.

Scalability

It is no secret that sometimes a project takes off unexpectedly for the people who created it, receives a large number of users, and the developers are faced with the problem of how to quickly cope with the sharply increased loads. Covering the project with memcache, raising master-slave replication - these concepts are familiar to many people who have tried to do something so that the project does not slow down. Unfortunately, even these simple methods usually cannot help quickly - you need to teach system components to access the cache, use one database server for writing and many for reading, and so on. Quickly providing good horizontal scaling (scale-out) is not always a trivial task. And we didn’t want to face, a week, a month, or a year after the launch, the fact that in order to solve this problem we would have to rewrite the project, which all this time would not cope with its main task - electronic payments. Therefore, already at the system design stage it was necessary to lay the foundation for simple scaling of [email protected].

Multicurrency

Again, it’s no secret that sometimes code that works great with apples refuses to work when bananas appear in the warehouse it serves. Well, the code does not provide for working with different entities! In many cases that we have seen, the problem was often solved by creating a new set of tables for oranges, similar to the “apple” ones, and copying the previously written code with replacement $iApples on $iBananas. In other cases, the solution to the problem was more adequate - additional fields appeared in the database, classes were inherited from ready-made ones with the addition of some new methods and properties (for example, the “peel” attribute for an apple is processed completely differently than for a banana). But even this solution sometimes required quite large changes to the code. Therefore, it was necessary to incorporate multicurrency into the system immediately.

Multiple displays

The most mysterious property at first glance, but the explanation is very, very simple. We call a storefront a system entry point that can work with settings independent from the main entry point - from a different domain address and its own currency to its own user authorization method and its own interface. Launching such a new storefront should also be very simple - no more difficult than adding a couple of lines to the system configuration files and, if necessary, new user interface templates.

Of course, these are not all the requirements for the payment system, but they were the ones that most influenced the system architecture. The new project had to be quite flexible and fault-tolerant.

Did we manage to do this? Yes, it was completely successful.

Now, according to our estimates, we can easily scale the system to hundreds of nodes by literally simply installing and configuring new hardware and entering information about the nodes into the project configuration.

We can process all the currencies in the world (national banks, ouch!) without thinking about how the system will behave. Not to be unfounded - now the system already uses several currencies (oh, these legal troubles!).

Well, as an example of storefronts, you can give a version of the site for debugging stores, which uses a test currency; mobile version of the site, which has its own set of available actions and its own templates. Another example is a showcase for stores with an API, where an authorization method is used that is different from the one with which portal users are identified in [email protected]. The launch of these storefronts for the system really looked like nothing more than the appearance in the configuration files of blocks describing the storefronts and a couple of folders with templates. In exactly the same way, we can provide, for example, work on our engine for the [email protected] payment system or any other that expresses such a desire.

I think many people are interested in how we managed to implement all this from a technical point of view. Therefore, in the next article we will talk about the tools and technologies that allowed us to make our payment system what it is, and we will also focus on the general architecture of the project. Stay with us!

Team [email protected]

Tags:

• payment systems
• Mail.ru
• how it was

Add tags

Hello, Habr! We at RBKmoney have written a new payment processing. From scratch. Well, isn't it a dream?

We will tell you how we wrote the entire processing of RBKmoney Payments, that’s what we called it. How they made it resistant to loads and equipment failures, how they came up with the possibility of almost linear horizontal scaling.

And, in the end, how we took off with all this, not forgetting about the comfort of those who are inside - our payment system was created with the idea of ​​​​being interesting primarily for developers, those who create it.

With this post we are opening a series of articles in which we will share both specific technical things, approaches and implementations, as well as experience in developing large distributed systems in principle. The first article is a review, in it we will outline milestones that we will cover in detail, and sometimes in great detail.

Disclaimer

No less than 5 years have passed since the last publication on our blog. During this time, our development team has been significantly updated; there are now new people at the helm of the company.

When you create a payment system, you need to take into account a lot of different things and develop many solutions. From processing capable of processing thousands of simultaneous parallel requests to write off money, to user-friendly and user-friendly interfaces. Trivial, if you don’t take into account the small nuances.

The harsh reality is that behind payment processing there are payment organizations that do not accept such traffic with open arms, and sometimes even ask “to send us no more than 3 requests per second.” And the interfaces are looked at by people who, perhaps for the first time on the Internet, decided to pay for something. And any UX jamb, incomprehensibility and delay is a reason to panic.

A shopping cart you can put your groceries in even during a tornado

Our approach to creating payment processing is to provide the opportunity Always start payment. It doesn’t matter what’s going on inside us - the server burned down, the admin got confused in the networks, the electricity in the building/district/city was turned off, we hmm... lost diesel. Doesn't matter. The service will still allow you to start the payment.

The approach sounds familiar, doesn't it?

Yes, we were inspired by the concept described in Amazon Dynamo Paper. The guys from Amazon also built everything so that the user should be able to put the book in the cart, no matter what horror was happening on the other side of his monitor.

Of course, we do not violate the laws of physics and have not figured out how to disprove the CAP theorem. It is not a fact that the payment will be processed immediately - after all, there may be problems on the banks’ side, but the service will create a request, and the user will see that everything worked. Yes, and we still have a dozen backlog listings with technical debt before the ideal, to be honest, we can answer 504 occasionally.

Let's look into the bunker, since there's a tornado outside the window

It was necessary to make our payment gateway always available. Whether the peak load has increased, something has dropped, or has gone to the DC for maintenance, the end user should not notice this at all.

This was solved by minimizing the places where the system state is stored - obviously, stateless applications are easy to scale to the horizon.

Our applications themselves run in Docker containers, the logs from which we reliably merge into the central Elasticsearch storage; they find each other through Service Discovery, and transmit data via IPv6 internally Macroservice .

All microservices assembled and working together, together with related services, form a Macroservice, which ultimately provides you with the payment gateway as you see it from the outside in the form of our public API.

The order is maintained by SaltStack, which describes the entire state of the Macroservice.

We will return with a detailed description of this entire farm.

It's easier with apps.

But if you store the state somewhere, then it must be in a database in which the cost of failure of part of the nodes is minimal. Also, there should be no master nodes with data in it. So that it can respond to requests with predictable waiting times. Are they dreaming here? Back then, it didn’t require much maintenance, and so that Erlang developers would like it.

Yes, haven’t we already said that the entire online part of our processing is written in Erlang?

As many have probably already guessed, we didn’t have a choice as such.

All state of the online part of our system is stored in Basho Riak. We'll tell you how to cook Riak without breaking your fingers (because you'll definitely break your brain), but for now we'll move on.

Where's the money, Lebowski?

If you take an infinite amount of money, you might be able to build an infinitely reliable processing facility. But it is not exactly. And they didn’t give us much money. Exactly like servers of the “high-quality, but China” level.

Fortunately, this led to positive effects. When you realize that it will be somewhat difficult for you, as a developer, to get 40 physical cores addressing 512GB of RAM, you have to get out and write small applications. But they can be deployed as many as you like - the servers are still inexpensive.

Even in our world, any servers tend not to come back to life after a reboot, or even experience a power supply failure at the most inopportune moment.

With an eye on all these horrors, we learned to build a system with the expectation that any part of it Necessarily will suddenly break. It is difficult to remember whether this approach caused any inconvenience for the development of the online part of the processing. Perhaps this has something to do with the Erlangist philosophy and their famous LetItCrash concept?

But it’s easier with servers.

We figured out where to place applications, there are many of them, they are scalable. The database is also distributed, there is no master, we don’t mind burned out nodes, we can quickly load the cart with servers, come to the DC and leave them with pitchforks in the racks.

But you can’t do that with disk arrays! The failure of even a small disk storage is a failure of part of the payment service, which we cannot afford. Duplicate storage system? Too impractical.

But we don’t want to afford expensive branded disk arrays. Even out of a simple sense of beauty, they will not look next to the racks where nonames are crammed in neat rows. And all this is unreasonably expensive.

As a result, we decided not to use disk arrays at all. All our block devices run under CEPH on identical inexpensive servers - we can put them in racks in large quantities as needed.

With network hardware, the approach is not much different. We take average people and get good equipment suitable for the task at very low cost. In the event of a switch failure, a second one works in parallel, and OSPF is configured on the servers, convergence is ensured.

Thus, we have a convenient, fault-tolerant and universal system - a rack full of simple, cheap servers, several switches. Next stand. And so on.

Simple, convenient and overall very reliable.

Listen to the rules of conduct on board

We never wanted to come to the office, do work and get paid in money. The financial component is very important, but it cannot replace the satisfaction of a job well done. We have already written payment systems, including at previous places of work. And we had a rough idea of ​​what we didn’t want to do. I didn’t want standard but proven solutions, I didn’t want a boring enterprise.

And we decided to bring maximum freshness into the work. In the development of payment systems, new solutions are often limited, they say, why do you need a docker at all, let’s go without it. And generally speaking. Unsecured. Ban.

We decided not to prohibit anything, but on the contrary, to encourage everything new. This is how we built a Macroservice in production from a huge bunch of applications in Docker containers, managed through SaltStack, Riak clusters, Consul as a Service Discovery, an original implementation of request tracing in a distributed system, and many other wonderful technologies.

erlang/otp Add tags