#brandon-savka_best-practices

1 messages ยท Page 1 of 1 (latest)

tawdry raptorBOT
#

๐Ÿ‘‹ 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/1333876297054552085

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

shadow glade
#

A little more info for context: I already have a fix underway to simply not create the $0 invoice in our system in this case, but wanted to see if there is a more recommended solution from your end (aside from using subscriptions for something they were not intended to be used for, of course ๐Ÿ˜‚ )

quick peak
#

Hi, with free trials a zero amount invoice will be created and there is not a way around it. Unless, you own that on your end and just create the subscription without a free trial

shadow glade
#

Got it. I am not using the free trials, it is kind of a perpetual subscription plan that is just set up to cost $0. The way our paid plans work is that they pay their monthly or yearly fee for the subscription and can buy additional products as they go which always bill monthly. The use case for us here was that the $0 subscription has less out of the box features for when they want to drop down into it from the paid plan, but still be able to retain their monthly billing cycle if they have any additional purchases.

I realize that is a slightly goofy use case, but just trying to see if there was any config I am missing since the test envs using the local listeners for webhooks to not send the invoice.created while the production setup does, or if we are just better off handling in our code that receives the webhook.

quick peak
#

Yeah, there is not an explicit configuration that you're missing. You'd want to handle this on your end.

shadow glade
#

sounds good, thanks!