#dennis_de - multiple subscriptions
1 messages ยท Page 1 of 1 (latest)
Unfortunately not at the moment. If they all have the same billing cycle you can consolidate all of your subscriptions in to one but otherwise they will need to be separate subscriptions.
Is there a change planned as a feature here?
Not as far as I know. I can put in a feature request but I can't guarantee that this will get added.
We just have monthly or annual base fees and alongside that monthly usage-based billing for consumption. In the case of monthly basic fees, I can pack them together in a subscription, but that's no longer possible with annual fees.
Thank you for the clarification, I was about to ask
One other option that you have is tracking when your subscription goes through 12 cycles and then adding your yearly fee as a one time invoice item
Therefore I thought to be able to represent it technically better, I put the usage-based billing always separately as a separate subscription. No matter whether the basic fee is paid annually or monthly.
How often do you bill on the usage based subscription?
The idea was that the customer books the monthly or yearly basic fee via checkout and then I add the subscription automatically....
monthly
We always calculate the usage in volume from the first day of the month to the last.
We have several tariffs (Pay-As-You-Go for 0โฌ, Company Plan for 299โฌ monthly or yearly in advance) and besides always a fee per transaction which depends on which tariff you have booked. For the Pay-As-You-Go it is 0,20โฌ per transaction and for the Company Plan e.g. 0,10โฌ per transaction. If the info still helps.
We have created individual products for the tariffs and just once for the transactions and dadrunter the different prices.
Ah and perhaps important to know. We settle customers' transactions early when they reach thresholds in euros. Whereby this is supported by Stripe.
Apologies for dropping off this thread for a bit. To clarify, are you using Stripe's built in metered subscription APIs or are you calculating the prices yourself and charging for them?
If I understand this properly, it does sound like you can consolidate this on to one subscription. I believe you can have a monthly fee and monthly metered usage on the same subscription and then all that would be missing is the yearly fee which as I mentioned might have to be done with a bit of custom code.
No problem. Exactly, for the usage we use the Subscription metered api.
I believe you can have a monthly fee and monthly metered usage on the same subscription and then all that would be missing is the yearly fee which as I mentioned might have to be done with a bit of custom code.
Do you have an example for the custom code?
You probably mean Subscription Schedules?
This would be something other than subscription schedules actually. I am not sure if we have an example of it but will check
In the "Usage threshold" function, I can't specify a threshold lower than the base fee even though the overlay info says that only usage-based billing is considered. Is this a bug?
Can you send me the ID of the subscription that that is on?
It's a test subscription (sub_1LK98EKSCBaxYA7anIMGft3b), but here we go ๐
Can you give me a keyword to look for? So with which API endpoint do I get this implemented? You are talking about subscription plans right?
But these are subscription schedules (https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases)
So initially I was just talking about monitoring when 12 cycles happens yourself and then making the API call to create an invoice item for your charge. We don't have example code for the waiting part but it should be our standard invoice item creation call https://stripe.com/docs/api/invoiceitems/create
Basically, when your subscription cycles, it automatically creates an invoice and adds an invoice item for all of your recurring prices. You can also add your own by making that call while the invoice is still in its draft state
Ah I see... okay, that's not really a good option since we're shifting Stripe's logic partly to us....
We use Stripe Billing to avoid having to map complex logics ourselves.
๐ Pompey had to step away
let me know if you have any follow up questions ๐
Please read through the conversation. Pompey was still checking.
It is a little long/complex thread, mind giving me a short summary?
Is the question still
Is there any option that multiple subscriptions that renew on the same day end up on one invoice? So each subscription does not have its own invoice?
@compact marsh ^
@compact marsh ^
@compact marsh ^
Apologies. I've looked but I'm not super familiar with the dashboard as our team mostly work with API questions.
Seems like a limitation in the Dashboard. I'd recommend reporting this to our support team and they can improve this: https://support.stripe.com/contact
The API apparently reports the error on submit as well.
Which parameter would be the right one in the API?
The Discord support is really 1 with asterisk but the normal support is sometimes really bad, because exactly such error reports are often misunderstood or not forwarded.
https://stripe.com/docs/api/subscriptions/create#create_subscription-billing_thresholds-amount_gte
but I assume it will error the same way (though worth testing quickly)
I will try this out later.
Sounds good
Feel free to leave the thread open, I'll let you know once I've tested it.
I'll likely close in a bit (the server can get quite busy) but not for a while
Only I can no longer open a thread again?
You can't reopen the thread but you can ask a follow up question in #dev-help if needed. But I mostly answered your question I think. If you get the same error as the Dashboard but in the API it means it's not something we support yet
It seems that it is really not accepted by the API. And now? But multiple subscriptions?
What are you really trying to do? Like do you have one Price, two, three, more? What are those Prices exactly?
At the beginning, I asked whether one or more invoices are generated for multiple subscriptions with the same cycle. Thereupon the suggestion of your colleague was that one could pack everything into a subscription.
So that multiple invoices are not generated.
In the end, we would like to charge a basic base fee + usage-based transactions and also define a threshold here above which intermediate billing takes place.
that allows you to put the billing thresholds for that specific Price
I have also just discovered and I wanted to test right away ๐
you can't disable the billing cycle anchor reset though
but that might be good enough
That in turn would be a problem?
If the basic fee runs from the first day to the last day of the month and I bill sub-monthly through the threshold limits, then of course the cycle should not be reset.
you explicitly set that one to false, but the per SubscriptionItem one doesn't support it
Ah Ok, understand.
ah yeah you're right
maybe it just doesn't reset at all, which makes a lot of sense in the way you framed it
if we reset we'd charge the whole base fee again which would be... dumb lol
I will build a test case to see how the subscription items behave.
Are there any plans to expand the Billing API? For example, the mapping of real contracts with minimum terms or notice periods? Other providers like Chargebee & Co. can do that, too.
Of course, it would be great if Stripe would also map such things in the long term.
we're thinking about it, but not in the short term at least
So I have successfully deposited billing_thresholds usage_gte on the Subscription Item, however nothing happened after I just registered Usage.
Maybe you can look up -> subscription id: sub_1LK98EKSCBaxYA7anIMGft3b
and sub item id: si_M2DfdymcYD4NAa
I think billing thresholds happen async so I'd wait a bit
Okay, that makes sense. I was just wondering if this was an "amount" or a number. The documentation doesn't say in detail.
What do you think?
well it's an amount that is a number
so $100 USD is amount: 10000 because it's in cents
so if your Price is $0.05 per usage and your threshold is $10 it will fire when you record usage to 200
That was exactly the question... so whether it really is an amount... ๐
Because normally the parameter is then with the "amount" addition, which is missing here.
Therefore, I thought, if necessary, the issue here is quantity.
ah gotcha I thought you were asking whether to pass a number like with the decimal 123.34 as we get that question a lot
No, that Stripe always works with cents, I have now understood, hehe.
๐
When should the process run at the latest? So that I can test whether it is about an amount or the number?
Normally, however, I know that it is always dispatched directly...
I would assume quickly so I'm surprised if it hasn't run yet but I'm deep in something else (for another user) so will take a while
Don't stress, I'm here. I have created a second subscription for testing, the same issue.
It really seems to run via scheduler.... 4 minutes ago the invoice was generated...
Have already no longer believed it ๐
Then I have to make another test case to see if it is an amount or a quantity.
yeah I know it's async but I thought it was faster than that, does it mostly work?
I am testing again... it doesn't seem to be dispatched in a queue but really run via scheduler, at least the timestamps indicate that.
14 minutes it took this time...
So I tested it again now and it seems that "billing_thresholds.usage_gte" is really the quantity and not an amount in cents.
What also fits is that the parameter does not include the word "amount".
Or am I missing something @flat ocean?
huh yeah
that is... so strange to me
it makes sense so that it works across Prices if you switch Prices, but it still "feels" off that this one takes a quantity of usage, versus a final amount
yeah I'm testing but will take a while to confirm since it's all async
but I think your read is right amount_gte is about the final amount, usage_gte is about the number of records reported
Do you have another idea?
It would be useful to describe this in more detail in the API documentation, best to pass this on to the team.
And the info on the dashboard should be updated as well, see screenshots at the very beginning.
another idea of what?