#sayanth-k_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1277565580202999863
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sayanth3609_best-practices, 55 minutes ago, 8 messages
hi! so they pay yearly but you want to charge for something extra in a specific month, or is it ok to just wait and charge for it in the next year's invoice?
Yes, I want to charge them for every month for exceeding specific feature usage, no matter whether their base plan is annual or monthly.
you could use https://docs.stripe.com/billing/subscriptions/usage-based/alerts-and-thresholds#billing-thresholds in that case, for the usage-based price
Let me have a look
Could you explain how can I use this to create an invoice at the end of every month for the reported extra usage?
it doesn't; it detects when the reported usage exceeds a threshold you set, and then it creates an invoice when that happens
But this will trigger only once per customer.
In my case, we offer a certain number of executions for a customer. If they exceed this limit, we charge for each additional execution. Instead of issuing an invoice immediately, we prefer to issue it only at the end of the month. This invoice will include the total number of extra executions multiplied by the price per execution.
it can trigger mulitple times.
In your use case then, maybe it's easier if you track the reported usage on your side and set a cron job to manually create a one-off Invoice when needed : https://docs.stripe.com/invoicing/integration
Only one option is available for frequency.
maybe I'm wrong then
But this seems to be an alert, not a billing threshold. I believe thresholds can only be set via API: https://docs.stripe.com/billing/subscriptions/usage-based/alerts-and-thresholds?dashboard-or-api=api#billing-thresholds
In my case, we offer a certain number of executions for a customer. If they exceed this limit, we charge for each additional execution. Instead of issuing an invoice immediately, we prefer to issue it only at the end of the month. This invoice will include the total number of extra executions multiplied by the price per execution.
issue it only at the end of the month
I think there's a confusion, since my colleague asked: "is it ok to just wait and charge for it in the next year's invoice?" And you answered "Yes ..."
If you have an annual Subscription, you won't be able to get any regular monthly events like this.
It might be easiest to create a parallel, monthly Subscription on the same Customer, and only record the excess usage.
Alternatively, you can have just a monthly Subscription, and then add an extra Invoice Item - the flat fee - every 12th month.
Sorry for the confusion.
I want to charge the customers for extra usage every month. Waiting for the next year's invoice is not the right option for us.
This will create two active subscriptions for a customer, right? I found somewhere in Stripe that one subscription per customer is the recommended setup.
Recommended doesn't always cover everyones needs, that's why I am trying to suggest a fitting solution, since it's not a trivial case.
But with this approach you can keep just one Subscription.
If you don't want your app to need to regularly add an extra Invoice Item, you will need to use 2 Subscriptions, since you can't combine Prices with different billing period - monthly vs yearly - in the same Subscription object.
Okay
Which one do you suggest? Creating parallel monthly subscription for usage or manually (Using API) creating a one-off Invoice at the end of every month?
manually (Using API) creating a one-off Invoice at the end of every month
Are you referring to one of my suggestions? I didn't suggest creating one-off Invoices, sorry for confusion.
It depends on you which one of my 2 suggestions you choose, since they both have their caveats. I would probably go with a single monthly usage-based Subscription, and I would make my app add an anual flat-fee to every 12th Invoice.
In the other case, with 2 Subscriptions, the customer will get 13 Invoices every year, an extra one for a flat fee, and usage during each of 12th months, which is not ideal.