#abdulmannanbutt
1 messages · Page 1 of 1 (latest)
Yes, you will want to line up the Stripe subscription IDs with users on your server and the content that you are unlocking for them
Most common is that each item on a subscription will represent some content for a user https://stripe.com/docs/api/subscription_items
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Usually based on the product of the invoice item
And the customer would be represented by a Customer object
So the most common pattern I know of is unlocking content based on product IDs for the user connected to the subscription's Customer ID
hm... So, It means, for each subscription type, we have to make modifications in the code to enable/disable the features. and If we want to introduce a new payment plan, we have to update the code again.
So, if we add a new Product ID, we have to do the coding and release the feature. And enable the product after that.
Yes, that sounds like a sensible way to impliment that
OK. Can you please share the appropriate guide to implement the subscription?
Our use case if, We want to give 3 plans to a user
1: 10 tries per user/month
2: 20 tries per user/month
3: Unlimited tries per user/month