nikochiko
commented
4 years ago I did some research. There's a few things we need to do. The big picture:
- The frontend will interact with stripe directly
- The frontend and backend will communicate via cors for events like when subscription is initiated and the user's stripe details are required from DB or when the payment is successful
- There will be an additional webhook setup on backend side to listen for events which the frontend might miss (when the user exits before the frontend could send payment successful notification)
Implementing:
- We can have the products and prices set up on stripe. Also store these in db for easy access
- Create stripe customers (also store them in db) when the user signs up for hyperlog.
- Creating a stripe customer only needs the email so we won't have to ask for other details.
- Storing in db will help because then we can have access to the latest payment date or the last mode of payment.
- The frontend will have to look after the direct interaction with stripe and handling stripe events (payment successful, payment failed, other errors)
- Setup endpoints on backend to pickup events from frontend
- Setup webhook on backend - https://stripe.com/docs/webhooks
There will also be a subscription model which can be accessed from customer model.
Reference: https://stripe.com/docs/billing/subscriptions/fixed-price
BrainBuzzer
Since the platform will have the option to subscribe to a particular plan, we need to add the memberships. There are going to be 2 different subscription options for now. One will be free, another will be paid. In paid subscriptions, there will be monthly and annual subscription plans.
We will use Stripe for payments. I think there is already available logic for memberships in Stripe called Billing. Need to research about this first. Post your rough idea of how this can/should be implemented here, and we'll move along this.
PS. Need to launch this for beta testing for some early registrations on 1 July, so next week is gonna be a rough ride.