📄️ Pricing
A pricing is a part of a SaaS customer agreement (GarcĂa et al., 2021). According to GarcĂa-Fernández et al., 2024, it structures the features of a service —i.e., distinctive characteristics whose presence or absence may guide a user’s decision toward a particular subscription— into plans and/or add-ons to control users' access to such features. When the pricing includes plans, users must subscribe to one of them and may subscribe to as many add-ons as are available for the selected plan. In pricings without plans, where only add-ons are offered, users can subscribe to the allowed combination of add-ons of their choice.
📄️ The iPricing Metamodel
The iPricing metamodel represents one of the first attempts to formalize pricing, so that they can all be designed following the same structure, which favors the creation of automated tools for their generation, analysis, validation, operation, etc.
📄️ Pricing4SaaS Architecture
Pricing4SaaS is presented as a specification of a reference architecture that addresses some of the challenges outlined in A. GarcĂa-Fernández et al.. In particular:
📄️ Communication Strategy
Pricing4SaaS relies on JSON Web Tokens (JWT) to send from the backend (Pricing4Java) the evaluation of different pricing features for the user that makes the request. In order to be used by Pricing4React, the JWT must be stored as a String in the local storage of the browser, with the name pricingToken.