tymm | Stripe Developers | Page 1

drifting sluiceBOT Nov 21, 2023, 2:01 AM

#

Hello! We'll be with you shortly. 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.

tymm, 15 hours ago, 15 messages
tymm, 21 hours ago, 34 messages
tymm, 3 days ago, 14 messages
tymm, 3 days ago, 26 messages
tymm, 3 days ago, 14 messages
tymm, 5 days ago, 5 messages

limber elbow Nov 21, 2023, 2:02 AM

#

https://stripe.com/docs/billing/subscriptions/prorations yes Stripe prorates to the second

Prorations

Learn about prorations.

sudden cloud Nov 21, 2023, 2:03 AM

#

limber elbow https://stripe.com/docs/billing/subscriptions/prorations yes Stripe prorates to ...

however it seems like it is not the case for the request that i made

#

in the update i changed the subscriptionitem to a higher priced one, if stripe prorates to second i would expect the update to refund an amount with cents? because im getting a full refund of 100myr for the unused time

limber elbow Nov 21, 2023, 2:05 AM

#

Let me take a closer look

sudden cloud Nov 21, 2023, 2:05 AM

#

sure

limber elbow Nov 21, 2023, 2:07 AM

#

Is this the invoice that you have doubt? in_1OEispLouXJU4FDJ8rMZho8a

sudden cloud Nov 21, 2023, 2:07 AM

#

yes

limber elbow Nov 21, 2023, 2:09 AM

#

So you are expecting Stripe to create two invoices for two subscription update requests?

sudden cloud Nov 21, 2023, 2:13 AM

#

i am expecting the following:

if stripe prorates to second i would expect the update to refund an amount with cents? because im getting a full refund of 100myr for the unused time

with the billing_cycle_anchor set to now, i would expect the final payable amount to be different between these 2 calls, but they are the same.
"these 2 calls" being the InvoiceUpcoming and SubscriptionUpdate call. they both returns a payable amount for the update. except they are both done at a different time, so naturally i expects their amount to be different

limber elbow Nov 21, 2023, 2:14 AM

#

What's the ID of the request of InvoiceUpcoming ?

sudden cloud Nov 21, 2023, 2:14 AM

#

limber elbow What's the ID of the request of InvoiceUpcoming ?

i did an InvoiceUpcoming request to get the upcoming invoice of a subscription update. req_T23E89KsvIopnq
about 5 minutes later i did a SubscriptionUpdate request with the same params as the previous call. req_6QQZHxuOJL7Zlr

limber elbow Nov 21, 2023, 2:16 AM

#

Ok, the proration_date is the same in both requests

sudden cloud Nov 21, 2023, 2:17 AM

#

does that mean the billing_cycle_anchor is not a part of the equation for proration in this case?
so this is true?

limber elbow Nov 21, 2023, 2:21 AM

#

This is conditional, you are getting the same amount for invoice because you've set the proration_date. You can try again with billing_cycle_anchor set to now without proration_date set and you should see different amount.

sudden cloud Nov 21, 2023, 2:22 AM

#

ok i guess its fine since the outcome is what i actually want, just am unsure if this is an intended behavior.

#

what about the proration amount?

#

doesnt stripe calculates proration down to second precision? because the final amount doesnt seem to reflect that

#

the proration_date is about a minute after the old billing cycle/ first subscription start date, so by right stripe shouldnt be giving a full price refund in the proration calculation?

#

ok i think it got rounded up since the amount could be 99.99 or something like that

#tymm