#bammy-subscription-proration
1 messages · Page 1 of 1 (latest)
bammy-subscription-proration
Hey @unreal brook! That's expected behaviour, we need to charge upfront for the time until that anchor. This is covered in details in our docs https://stripe.com/docs/billing/subscriptions/billing-cycle including how to disable proration if you don't want any upfront using proration_behavior
the exact amount was deducted
like the product price was deducted
thanks for your quick response
Can you give me a lot more specific details? Exact Subscription and Invoice id sub_123 and in_123 what you see on those, whether proration happened, what billing_cycle_anchor you set, etc.
Ok
Thanks.
I created a subscription endpoint for users to subscribe, I set a billing cycle anchor to 8pm, May 15th
so I tried to test it
I clicked the subscribe button and I added my card details
Please try to give me all information summarized all in one message
I created a subscription endpoint for users to subscribe, I set a billing cycle anchor to 8 pm, May 15th, 2023.
I tried to test it,
I clicked the subscribe button, I added my card details, and the product price was deducted from the account.
I was expecting Stripe to deduct the money at 8 pm not immediately.
This is unfortunately really abstract/theoretical. Please share exact object ids. If you look at the exact Invoice it would tell you what's happening for example
Once you give me an Invoice id in_123 I can work backwards from it and explain what is causing this
@unreal brook are you still around?