StripeDev100-prorations

[opal bramble]

Hey, not sure I understand the Q. What's the alternative to not prorating or charging the full amount?

What are you doing that's generating prorations and what's the desired outcome?

[winged sandal]

Hi - a customer paused their subscription, then 30 days later came back and unpaused. To unpause I use the subscription update API with this:

billing_cycle_anchor: 'now',
collection_method : 'charge_automatically',

The problem is - the user got charged twice - once for the billing_cycle change - then proration kicked in and charged them again.

Does this make sense?

Thanks 🙂

[opal bramble]

Can you share the subscription ID?

[winged sandal]

sub_1KMJHnHu0tdCRNQPgI9Np7m4

This subscription has two invoices at the same time 03:00.

Thanks

[opal bramble]

My initial guess is that this update made whilst the subscription was paused is what triggered the additional invoice: https://dashboard.stripe.com/logs/req_gK8WLCqMvfBAlL

Confirming

[winged sandal]

Yeah - can you send me more information on that

It is possible to unpause and change the billing cycle at the same time using the same call:

pause_collection: null,
proration_behavior: 'none',
billing_cycle_anchor: 'now',
collection_method : 'charge_automatically',

But I can't find any documentation on why it would charge a user twice?

Thanks

[opal bramble]

Just checking with a colleague

[sullen iron]

Hey, unfortunately we are still looking in to this and I don't know if we will have an answer while you are still on. Would you mind writing in with the info you supplied to [e-mail] and then DM me your email? I can pick up the ticket and we can update you on the investigation from there. I can see that both invoices came from that update but exactly why is unclear. Still figuring out how that happened and how you can avoid it.

[winged sandal]

Thanks