#rock_code

1 messages ¡ Page 1 of 1 (latest)

misty stirrupBOT
#

👋 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/1363867759490105585

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

woven widget
glass anvil
#

Yes, so we currently have annual and monthly subscriptions on the platform

#

What we want to achieve is if the user reaches a threashold we want them to pay for another month/year based on their sub type.

#

Since we want the ongoing subscription to continue as is, since we also increase the prices (and wants users to stay of same subscription prices), we will ask users to pay through this link (that i shared initially , manual invoice payment link)

#

Once user pays I will them update the current subscription billing cycle accordingly.

woven widget
glass anvil
#

This will not solve our use-case, as I am talking a bit more about advance payments or rather getting the upcoming cycle payment beforehand.

Updating the current subscription will change the price and other details of the ongoing subscription which I then again have to revert back at some point.

woven widget
#

I highly recommend that you use Test Clock, https://docs.stripe.com/billing/testing/test-clocks to test this behavior. One of your questions is around the impact on taxes which we would not be able to assist directly. As for the first question, the invoice should should not impact subscriptions as this would be a separate product/ API