Need a way to link user and user subscriptions

[franck-boullier]

Overview:

In order to manage user subscriptions, we need a way to record the subscription information for each user.

The information we need:

• User id
• Subscription plan id (default is the subscription id for the Unee-T Standard plan)
• Subscription start date
• Subscription end date (default is NULL)
• Payment platform id: how was this subscription paid for. This is the id in the table which will list all our payment options.
• Payment confirmation id: the id of the transaction on the payment platform. This will allow us to find detailed transaction information if and when needed.
• Payment confirmation datetime: the timestamp when we received confirmation from the payment platform that the payment was OK

[nbiton]

We need to integrate a payment solution first

[franck-boullier]

We need to integrate a payment solution first

@nbiton: no happy to discuss this if need be

[nbiton]

Do you mean it should be done manually? (adding this information)

[kaihendry]

Can we get a Stripe setup first, it's possible to bill users manually without any integration at first which is really nice.

[franck-boullier]

Can we get a Stripe setup first, it's possible to bill users manually without any integration at first which is really nice.

Absolutely: we already have a Stripe account and the plans we need are already configured there

[franck-boullier]

Do you mean it should be done manually? (adding this information)

You only need to have a place somewhere in Unee-T to record the association user/subscription plan. Then you only need to include a payment link somewhere to be able to process that payment Integration can be done at a later stage

[kaihendry]

Ok, then we perhaps setup a subscription where some user (sandbox) and then decide if or how that is shown in the application. I.e. define what we want the user to do or rather user's UX.

To get off the ground, you could setup a billing@unee-t email that could do the stuff manually. Happy to help here.

[kaihendry]

This may well lead to a bit of "lock in" to the Stripe service, but I suggest we defer to using Stripe as the canonical data store for subscription info. Of course we can keep good copies of the status quo via Web hooks as demonstrated here: https://media.dev.unee-t.com/2018-10-12/ubilling.mp4