Billing a new generation. Part 1
Hello to all!
This is our first corporate blog post. I was in a hurry, because I learned that tomorrow I would give a presentation on PricePlan at RIW15. Before that, I would like to talk about our product here - if you have any questions, suggestions or comments, ask them in the comments or tomorrow at RIW .
For three years now, my team has been working on creating a new generation of billing platform. I am sure that many Habr readers have already encountered similar systems in their projects and understand their purpose and functionality. So now I will not talk about what billing is and how it works. Instead, I would like to tell you about those functions of PricePlan, which allow to refer it to a new generation of billing systems. We are happy to continue this topic at a more "technical" level, if it interests you.
Firstly, by billing a new generation, we mean the possibility of cloud-scale scalability of the service under load and the presence of the principle of “Multi-tenancy”. This allows you to reduce the time of introduction of the system in a typical service company to several days instead of several months. A scan of the full version of billing in the cloud today can take only a few seconds.
')
Secondly, the billing of a new generation is isolated from the business processes of a particular industry. The basis of our platform is a system of events, triggers and rules, which allows the user to customize the billing for his model. The most important thing is that the user-built logic can be easily changed at any time upon the first demand of the business.
Thirdly, the billing of the new generation includes the sandbox mode - in PricePlan it is enabled by default at the beginning of work. In this mode, the user can change the settings, create new rules and test the logic of billing processes. After the user creates tariff plans in the system, sets price limits, determines discount models and business rules, our robot will be able to automatically perform all actions on a specific personalized system built by the user.
What can we do today:
- Declare and create new business logic in the rules module;
- Create charges: periodic, one-time, upon use (counters);
- Create invoices for payment and a package of closing documents;
- credit payments to personal accounts from banks and payment systems;
- Send trigger messages by email and SMS;
- Exchange data with third-party programs through the REST API and Webhooks;
- In real time, display information in the user's personal account;
- Calculate data metrics CHURN, MRR, ARPU, LTV;
- Bilateral integration with 1C Accounting and payment systems.
Who this service is for:
- SaaS, PaaS;
- IaaS (Openstack and Azure);
- Insurance companies;
- Digital media;
- Rental Property;
- Any service working on a recurrent model.
Features of the engine.
In the sandbox mode, it is possible to create business rules and move in a time machine any day to the future in order to test their logic in a test mode. The user can check the history of write-offs, renewals of subscriptions, notifications and submitted documents. The mode helps to see all errors, inconsistencies in the rules and correct them before they affect the end users.
After the system is tested and debugged, the user enters the “combat” mode. The current date and time are synchronized with GMT. Here you can act on two models:
- Two-step (semi-automatic, with confirmation of each operation) model. The closing of the day is done here in 2 steps: Automatic calculation of all operations and Manual confirmation of billing.
- One-step (full automatic) model. All actions specified in the rules are automatically executed at the close of the day. All customer documents will be created and maintained, subscriptions renewed, notifications sent out. The Full Automatic model is most effective, but also accompanied by the greatest risk. In this mode, there is no possibility to cancel billing actions, the user can only check the report.
We recommend using the first model for the first 2-3 months after the start of work and switch to the automatic model after - with full confidence in the correct operation of all rules.
Our team has made a lot of efforts to make the platform convenient for developers and integrators. Practically everything that you find in the interface can be implemented through the rest API . I will wait for your questions and suggestions here in the comments. And I will be happy to talk to you personally at RIW. See you!
This is our first corporate blog post. I was in a hurry, because I learned that tomorrow I would give a presentation on PricePlan at RIW15. Before that, I would like to talk about our product here - if you have any questions, suggestions or comments, ask them in the comments or tomorrow at RIW .
For three years now, my team has been working on creating a new generation of billing platform. I am sure that many Habr readers have already encountered similar systems in their projects and understand their purpose and functionality. So now I will not talk about what billing is and how it works. Instead, I would like to tell you about those functions of PricePlan, which allow to refer it to a new generation of billing systems. We are happy to continue this topic at a more "technical" level, if it interests you.
Firstly, by billing a new generation, we mean the possibility of cloud-scale scalability of the service under load and the presence of the principle of “Multi-tenancy”. This allows you to reduce the time of introduction of the system in a typical service company to several days instead of several months. A scan of the full version of billing in the cloud today can take only a few seconds.
')
Secondly, the billing of a new generation is isolated from the business processes of a particular industry. The basis of our platform is a system of events, triggers and rules, which allows the user to customize the billing for his model. The most important thing is that the user-built logic can be easily changed at any time upon the first demand of the business.
Thirdly, the billing of the new generation includes the sandbox mode - in PricePlan it is enabled by default at the beginning of work. In this mode, the user can change the settings, create new rules and test the logic of billing processes. After the user creates tariff plans in the system, sets price limits, determines discount models and business rules, our robot will be able to automatically perform all actions on a specific personalized system built by the user.
What can we do today:
- Declare and create new business logic in the rules module;
- Create charges: periodic, one-time, upon use (counters);
- Create invoices for payment and a package of closing documents;
- credit payments to personal accounts from banks and payment systems;
- Send trigger messages by email and SMS;
- Exchange data with third-party programs through the REST API and Webhooks;
- In real time, display information in the user's personal account;
- Calculate data metrics CHURN, MRR, ARPU, LTV;
- Bilateral integration with 1C Accounting and payment systems.
Who this service is for:
- SaaS, PaaS;
- IaaS (Openstack and Azure);
- Insurance companies;
- Digital media;
- Rental Property;
- Any service working on a recurrent model.
Features of the engine.
In the sandbox mode, it is possible to create business rules and move in a time machine any day to the future in order to test their logic in a test mode. The user can check the history of write-offs, renewals of subscriptions, notifications and submitted documents. The mode helps to see all errors, inconsistencies in the rules and correct them before they affect the end users.
After the system is tested and debugged, the user enters the “combat” mode. The current date and time are synchronized with GMT. Here you can act on two models:
- Two-step (semi-automatic, with confirmation of each operation) model. The closing of the day is done here in 2 steps: Automatic calculation of all operations and Manual confirmation of billing.
- One-step (full automatic) model. All actions specified in the rules are automatically executed at the close of the day. All customer documents will be created and maintained, subscriptions renewed, notifications sent out. The Full Automatic model is most effective, but also accompanied by the greatest risk. In this mode, there is no possibility to cancel billing actions, the user can only check the report.
We recommend using the first model for the first 2-3 months after the start of work and switch to the automatic model after - with full confidence in the correct operation of all rules.
Our team has made a lot of efforts to make the platform convenient for developers and integrators. Practically everything that you find in the interface can be implemented through the rest API . I will wait for your questions and suggestions here in the comments. And I will be happy to talk to you personally at RIW. See you!
Source: https://habr.com/ru/post/269201/
All Articles