#revathy_code
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/1266278259096551488
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! i'm sorry but i don't understand, can you explain what's the behaviour you're seeing, and what is the behaviour you are expecting instead?
One user created a team for duration July 1 - Aug 1 ,then he paid 5$, he added two user in same day then again charged 10$, 4th user added in July 15 then we need to charge 2.5$. my requirement like this
Stripe charges prorations by the second. I would say that it's possible, but going to be complex. If you want to implement it the way you explained, then you need to set https://docs.stripe.com/api/subscriptions/update#update_subscription-proration_date to exactly X number of days in seconds from the start date
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
in case you haven't seen this yet, you can use test clocks to mimic the passing of time : https://stripe.com/docs/billing/testing/test-clocks
if we use prorate with per-seat subscription , then next estimated payment = quantity*unit price + prorate value , it is my exact issue
can you explain with reference to an actual Invoice id, the behaviour you are seeing instead?
here the my expected output is 15$, and if we add another user on Aug 10 the need to charge 2.5$ again , then total estimated paymement will be 17.5$
from what I understand, you want to invoice now? not wait till the upcoming invoice to charge?
i need in upcoming invoice, but upcoming invoice i get wrong , in above case my expectation for next invoice is 15$
can you share the Subscription id? It'll have the prefix sub_
okay, but test data will also have object ids
so you should have a request id at the very least, if you are making a request to the upcoming invoice API