#itsqwerty-subscription-paymentelement
1 messages · Page 1 of 1 (latest)
Appreciate it, does this flow look correct to you on how the payments should work?
- The customer enters their username, selects plan details
- Enters their email (we have their name from their Instagram username)
- We check the database to see if they are already a customer and have a stripe customer ID
- If they do, we return that otherwise we make them one and save it to their user
- At this point we have their customerId in the FE
- The frontend sends a request to the BE with the plan information, customerId, name, email,
- The backend returns a subscriptionId and a clientSecret
- The front end now displays stripe comps with the clientSecret
- User completes the payment in the frontend and redirects
- Backend receives a web hook and complete an action