#stripe_connect_platform-subscription
1 messages · Page 1 of 1 (latest)
holy crap. really bad
So basically we increased the price and wanted them to be charged on their next scheduled billing cycle and totally NOT TODAY!!!!!!! We just charged 200 people right now!!!!!!!
Every payment in my account that occurred in the last 20 minutes.
You can look at any of them
Again, can you share one of the requests? I don't have your account on hand
here is 1 of like 200
req_lEuEIpqgLtiP5b
req_oxOt9vyi2ppup1
req_ftVmJpVLFGo2ic
req_VYJ6em8ouDvryK
req_8lIvauiy9Wq7Z9
yup i'm looking - give me a minute
etc.
Anyway to reverse all of those?
And refund.
And then set them all up to pay on the next scheduled billing cycle?
I tested this all day yesterday. Everyone I tested was set up to be charged on the next scheduled billing.
😦
Then we ran the code and charged everyone today and worse yet, we didn't prorate so it was the full charge. 😦
I thought per your docs that when you set proration_behavior: 'none' that it upgrades without charging them. 😦
And they will just pay the new price on the next billing cycle. Eeek!!!!!!
Ah I see why the billing cycle reset now - just looking at one of the examples it's because you migrated from an annual price to a monthly one
No that might be an error. That should not be the case.
Which we call out as being one of the conditions that would immediately trigger a billing cycle anchor reset https://stripe.com/docs/api/subscriptions/update
I'm looking at subscription sub_JaVJT5BTGHhOzW
Which moved from pl_1CfTSGHnzkM7EAuHjtLdPcyx (annual) to price_1LKki9HnzkM7EAuHz3jeisPQ (monthly)
?
fug
that is wrong
so bad
Hmmm
It is possible we have something in our db where I got all the people on monthly plans but they weren't really on monthly plans or annual plans and they weren't really on annual plans.
Is there a way to refund all those charges?
I need to take 3 minutes and walk away and will be right back.
You can definitely refund those charges - but that would be on you to identify everything that needs to be refunded and write a script that refunds each of them
and yeah, something seems to be off - in the same subscription I shared earlier you can see it actually had two update requests.
- req_hL4vaba6Y24QME (migrated from annual -> monthly price)
- req_MkqlaRzZoNZqJE (migration from the new monthly price -> new annual price)