This series of articles gives the best practices to integrate ProAbono. Pass it on to your technical team if you want a perennial integration that allows you to create offers and subscriptions on the fly without technical assistance.

Chap 1. Rights management with ProAbono

Without ProAbono

Traditionally, rights management in an online application is a never-ending file. When the customer subscribes to an offer, rights are released to the user: access to a feature, a number of collaborators, a quota, etc.

These rights will depend on the chosen offer. And with each new offer, the whole rights management code will have to be reviewed to manage the rights of this new offer. And even if you are clever and you have managed the rights transversally, you will have to constantly review the mapping between a new offer and the associated rights.

Behind this, you must then manage all the cases that ‘stick out of the box’: a customer finds himself with two active subscriptions, he no longer pays his bills, he contacts customer service for an immediate interruption, he wants a tailor-made offer with specific rights, he is ready to pay for unlimited rights, he wants to pay for a third party subscription (e.g. a franchise), etc.

All these cases can happen at any time and will have to be managed in a reliable way, otherwise your support will be overloaded or you’ll have clever people using your service without paying.

With ProAbono

ProAbono was designed to solve this problem. You can retrieve all the rights of a client in real time by API. This call is optimized for speed and supports a colossal load.

Better: this call is similar to the one that allows to modify the rights (POST instead of GET), which is useful, for example, when the client wants to add a user. This is described in chapter 5.

What should not be done is to use the API to retrieve the current subscription based on the offer reference (ReferenceOffer). This is a practice that will reduce your scalability (the ability to distribute your service massively) and forces you to manage dozens of cases, or to discover new, unmanaged cases (bugs) while you are in production.

The concept is simple

You declare in ProAbono the features and metrics that define your rights management.
You can retrieve the effective rights of a user in real time with the ProAbono API.

Let’s take a concrete example: ‘Access to the Premium section’:

Whether the user has an active Premium subscription…
or that he has subscribed 2 years earlier to the launch offer at -50%…
or that the customer service has made a commercial gesture…
or that he has purchased your service from your reseller in white mode…
or that he is a tester who hasn’t paid anything at all…
or that it is yourself who test the application…
Whether the subscription is annual, monthly or quarterly…
whether he pays in euros, dollars or rupees…
whether he paid by card, SEPA, check, cash or in exchange of goods…

It doesn’t matter! The ProAbono API will give you the same result: this user must have access to the Premium section.

Yes, you got it: you will be able to manage the licenses of each of your users, feature by feature.

Next chapter : Implementing rights synchronization >