#yestix_best-practices

1 messages ¡ Page 1 of 1 (latest)

native pikeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1441335747272773652

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

tulip bone
#

Yes it's not supported for now. You would want to build your own page for letting your customer upgrading / downgarding

#

Sorry if this is not the answer you are looking for

outer monolith
#

I figured out it is not supported but I was looking for best practices on how to build it myself since it is has a lot of logic and components to implement something with the same functionality

tulip bone
#

We don't have particular "official" guidance on replicating Customer Portal, but as a developer I would start by a feature of "showing all existing Metered Usage Subs on a given Customer", and code it up using Stripe API

outer monolith
#

Hmm, ok. I will further look into it.

native pikeBOT