#gl_subscription-proration

1 messages ¡ Page 1 of 1 (latest)

celest tinselBOT
#

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

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

brazen stirrup
#

gl_subscription-proration

lethal venture
#

One of our product managers also stated:

I debugged with Stripe Help and it looks like the two you had to manually send were both created due to subscription updates (proration adjustments when the subscription quantity changed) and these types of invoices don't automatically generate receipt numbers or send email receipts in the same way as regular subscription renewal invoices. This is a stripe specific limitation, they don't generate email receipts for subscription updates so we would need to do additional eng work to check for those changes and generate an email receipt

#

Here is the relevant Stripe API call in our codebase, and we've verified via application logs that this call is succeeding:

                await stripeClient.subscriptionItems.update(subscriptionItem.id, {
                  quantity: activeUserCount,
                  proration_behavior: 'always_invoice'
                })
brazen stirrup
#

I looked at that Invoice and we sent an email

lethal venture
#

does your logs show whether we sent the email manually (via the dashboard) or if it was automatically sent?

brazen stirrup
#

I think you need to go talk to our support team instead about this https://support.stripe.com/contact so they can share more details. This is more a 1:1 support investigation and not really about your code at this point

lethal venture
#

Oh okay, fair enough.

brazen stirrup
#

ah yeah maybe it was done by hand since it was a day after

#

but yeah our support team would need to debug the why especially if you have multiple examples

lethal venture
#

okay, thanks koopah! Have a good rest of your day.