No matter what billing system you choose, you will need to set prices for the services you provide. Let’s have a look at how prices are set in postpaid billing.
It’s not reasonable to simply set the exact price for a feature (for example, 5$) because this approach is not flexible and can’t take into account the following:
- Multiple countries and multiple currencies.
- Different taxation rules across countries.
- Different costs and, as a result, prices in different regions.
- Customers’ discounts.
SolusVM 2 doesn’t store the price-related information mentioned above. It delegates this task to the billing system. This is the reason why every paid feature in SolusVM is tagged not with the real price but with a virtual one, called “token value”. The token is a virtual unit of measurement. It is converted into price after the billing system sends the required price-related information. To show prices, SolusVM 2 interacts with the configured billing system via API. When SolusVM 2 needs to display a price to a customer, SolusVM 2 sends an API request to the billing system’s API endpoint. The billing system then returns the currency, the currency symbol, and the price in this currency.