#yagnesh_unexpected
tacit beaconBOT
👋 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/1503616497681961092
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
⛔️ Stripe developers have stepped away for a short while
Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.
random aurora
hi there 👋 give me a moment to catch up on the question
Are you referring to the prorated charge of 1.53 USD on this invoice: in_1TW2NXHpMtJXvyJglBYqGb9w?
abstract locust
Yes true
Also this charge is higher then the amount at which other charges happened: ch_3S6JzsHpMtJXvyJg0SJUAVib
tacit beaconBOT
Hello @abstract locust, we have sent you a direct message, please check it at https://discord.com/channels/@me/1499312465354293343
- 🔗 The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
random aurora
I will need additional access to look up this subscription. I just sent you a request for access, may I ask you to check your DM
abstract locust
Sorry, I am afraid even i do not have access to main account, i only receive webhook events from that, all i had is webhook data and i found discrepancy in charge hence i had to come to support
random aurora
Okay no worries
I'm still looking into the logs of this subscription, give me some time to get back to you
abstract locust
sure sure
random aurora
@abstract locust thanks for waiting. The issue is due to the subscription schedule attached to the subscription. The schedule ID is sub_sched_1Rv4GQHpMtJXvyJgmxdyOIc1
There are a few things I want to call out about this schedule using its latest update request as a reference: https://dashboard.stripe.com/acct_1IflgUHpMtJXvyJg/logs/req_LUO1HzsOB3EVJS
Firstly, this schedule has it's end_behaviour is set to "cancel" [0]. This means that once when the schedule has completed what its configured to do, the schedule will cancel the subscription.
Secondly, Phase 0 on the schedule, which dictates the current state the subscription is in, has its duration configured to
interval: "day", interval_count: "242" — this means that the Phase 0 will only run from 242 days.
- With this configuration, given req_LUO1HzsOB3EVJS shows
start_date: "1757633638", it means the schedule started on 2025-09-11 23:33:58, ran its Phase 0 for 242 days, and at the end of this duration, it will cancel the subscription since there are no other phases in the schedule. - 242 days from 2025-09-11 will give us 2026-05-11, which is essentially when in_1TW2NXHpMtJXvyJglBYqGb9w was created.
In simplier terms, sub_1Rv4GCHpMtJXvyJgJgo6UJnD had a subscription schedule governing it, which was set to cancel the subscription 242 days from 2025-09-11. in_1TW2NXHpMtJXvyJglBYqGb9w is created as a prorated invoice as a result of sub_1Rv4GCHpMtJXvyJgJgo6UJnD's cancellation.
[0] https://docs.stripe.com/api/subscription_schedules/create#create_subscription_schedule-end_behavior
abstract locust
Thanks, I understand the schedule completed and canceled the subscription as configured. However, since the cancellation happened at the expected end of the 242-day phase, could you clarify why Stripe still generated a prorated invoice (in_1TW2NXHpMtJXvyJglBYqGb9w)? Was there an actual billing adjustment involved, as per my understanding if the governing schedule cancel , then subscription also cancel, where does the proration comes into picture, please bear with me, i am processing these things.
Does stripe always creates prorated invoice for adjustment of the billing period after subscription cancel?
random aurora
No worries, appreciate you taking the time to stay with me.
To answer "why is proration happening", this is because its actually not possible to "disable proration" in the future.
Using Subscription Schedule to control a subscriptions does make managing a subscription quite complex. But essentially, this API request (req_LUO1HzsOB3EVJS) is trying to disable proration in the future when the subscritions gets cancelled, but proration cannot be prevented because the last (and only) phase on the subscription schedule is 242 days, which is more than 1 cycle in length - in such scenarios, proration will always happen when the subscription gets cancelled
abstract locust
which is more than 1 cycle in length? can you please tell me what is this cycle.
random aurora
"this cycle" refers to billing cycles on a subscription, depending on the cadence set on the price.
For example, the two prices on the subscription (price_1Rv4AvHpMtJXvyJgCO7fYOGI, price_1Rv49LHpMtJXvyJgMjCBVxzS) charges on a monthly basis, which means the subscriptions runs on a monthly cycle. And based on the billing cycle anchor on sub_1Rv4GCHpMtJXvyJgJgo6UJnD, which is 2025-08-11 22:32:06 UTC, this subscription is set to charge the customer 11th of every month at this time.
abstract locust
Okay okay, i really appreciate for helping me to navigate through this, i am trying to generate this case in test mode, maybe i can understand better in that
random aurora
No problem, you will need to look into the change history of sub_sched_1Rv4GQHpMtJXvyJgmxdyOIc1 to fully replicate this
abstract locust
okay
in_1S6J30HpMtJXvyJgfBHyfDPR
this invoice has higher amount then usual charge, it is in the same subscription, may i know if user has updated the price or something else
random aurora
It is because of the invoice item called "Amale Sefiani". On in_1S6J30HpMtJXvyJgfBHyfDPR, this invoice item costs $1,125.66 / month. But on the subscrition's first and third invoice (also subsequent invoices are that), it costs 1,000.00 / month.
abstract locust
that means first was 1k and then user changed to 1125 and then again they changed to 1k
what are the chances that chaning in the subscription items invites the proration
random aurora
No, the customer didn't change it to 1125. This price update was made on the subscription schedule by one of the user on your Stripe account (m____d__s@yahoo.com) from the Dashboard. This is the API request triggered: https://dashboard.stripe.com/acct_1IflgUHpMtJXvyJg/logs/req_VIDby30VmCX16b — noticed this request passed unit_amount_decimal: "112566"
abstract locust
sub_1TW9UjIJwnu749YFAthQJxE9
this is test mode suscription and there is no prorated invoice charged