New generation billing. Part 1

    Hello everybody!
    This is our first corporate blog post. I was in a hurry because I found out that tomorrow I will give a presentation of PricePlan at RIW15. Before that, I would like to talk about our product here - if you have questions, suggestions and comments, ask them in the comments or tomorrow at RIW .

    For three years now, my team has been working on a new generation billing platform. I am sure that many readers of Habr have already encountered similar systems in their projects and understand their purpose and functionality. Therefore, now I will not talk about what billing is and how it works. Instead, I would like to tell you about those PricePlan features that allow it to be attributed to a new generation of billing systems. We will be happy to continue this topic at a more “technical” level, if it interests you.


    Firstly, by the new generation of billing we mean the possibility of cloud scalability of the service under load and the presence of the principle of "Multi-tenancy". This allows you to reduce the time of implementation of the system in a typical service company to several days instead of several months. And deploying the full version of billing in the cloud today can take only a few seconds.

    Secondly, a new generation of billing 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 independently configure billing for their model. Most importantly, the user-built logic can be easily changed at any time according to the first requirement of the business.

    Thirdly, a new generation of billing includes the "sandbox" mode - in PricePlan it is enabled by default at the beginning of work. In this mode, the user can change settings, create new rules and test the logic of billing processes. After the user creates tariff plans in the system, sets price levels, 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 write-offs: periodic, one-time, upon use (counters);
    - Create invoices for payment and a package of closing documents;
    - Crediting payments to personal accounts from banks and payment systems;
    - Send out trigger messages by email and SMS;
    - Exchange data with third-party programs through the REST API and Webhooks;
    - In real time, display information in your user account;
    - Calculate data metrics CHURN, MRR, ARPU, LTV;
    - Bilaterally integrate with 1C Accounting and payment systems.


    For whom this service: 
    - SaaS, PaaS;
    - IaaS (Openstack and Azure);
    - Insurance companies;
    - Digital media;
    - Rental Property;
    - Any service operating on a recurrence model.

    Features of the engine.
    In the "sandbox" mode, it is possible to create business rules and move in the "time machine" any day into the future in order to test their logic in test mode. The user will be able to check the history of charges, renewal of subscriptions, notifications and documents submitted. The mode helps to see all the errors, inconsistencies in the rules and correct them before they affect the end users.

    After the system is checked and debugged, the user goes into "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. Closing the day is carried out in 2 steps: Automatic calculation of all operations and Manual confirmation of billing.

    - One-step (full automatic) model. All actions specified in the rules at the close of the day are performed automatically. All customer documents will be created and posted, subscriptions extended, notifications sent. The “Full Automatic” model is the most effective, but also carries the greatest risk. In this mode, there is no way to cancel billing actions, the user can only check the report.

    We recommend using the first model the first 2-3 months after starting work and switching to the automatic model after - if you are fully confident that all the rules work correctly.

    Our team made a lot of efforts to make the platform convenient for developers and integrators. Practical 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’m happy to talk to you personally at RIW. See you!

    Also popular now: