#dharavathkarthik
flint moat
paper timber
Sounds like pricing table is a good starting point: https://stripe.com/docs/payments/checkout/pricing-table
formal steeple
Does it dynamically shows which is current plan and the plans that user can upgrade
paper timber
No it does not, you'd use the portal for that: https://stripe.com/docs/customer-management
formal steeple
Is there a strategy which combines both or any better alternatives?
paper timber
There is not, you'd use them together
formal steeple
Can you share some references on how to combine the together
paper timber
They'd be bound together by a single Customer object (cus_xxx) that would map to a user in your application