#revathy_code

1 messages ¡ Page 1 of 1 (latest)

raw cedarBOT
#

👋 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.

jovial granite
#

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?

broken coral
#

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

jovial granite
#

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

broken coral
#

if we use prorate with per-seat subscription , then next estimated payment = quantity*unit price + prorate value , it is my exact issue

jovial granite
#

can you explain with reference to an actual Invoice id, the behaviour you are seeing instead?

broken coral
#

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$

jovial granite
#

from what I understand, you want to invoice now? not wait till the upcoming invoice to charge?

broken coral
#

i need in upcoming invoice, but upcoming invoice i get wrong , in above case my expectation for next invoice is 15$

jovial granite
#

can you share the Subscription id? It'll have the prefix sub_

broken coral
#

i am working on test data

#

development mode

jovial granite
#

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

raw cedarBOT