#buckets?!?
1 messages · Page 1 of 1 (latest)
Hi, can you share the exact steps that I can reproduce this issue? Also, can you share the request id where this has happened? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
sure, let me work on that
i've reproduced the issue multiple times using test clocks
luckily we have not enabled pause in production yet
i believe it's this request: req_F15XIVY0tVpk6o
it's the one where i unpaused a subscription through the customer portal a day or two after the billing cycle ended (using the test clock to set the day)
here's how i reproduce the issue:
- create test clock at April 1, create associated fake customer, and associated monthly subscription
- advance test clock to April 29
- create a customer portal for the fake customer and pause the subscription indefinitely through it
- advance test clock to May 2 or so, verify a voided invoice was created for the May billing cycle
- unpause the subscription through the customer portal
- verify that a new non-voided invoice was created starting May 2, for a prorated amount
- optionally, advance clock to June and verify that payment continues as normal after that
@proper garden yeah this does sound like a bug, I'd recommend writing in to our support team and providing all those details and they can look into a fix for you. You can contact them at https://support.stripe.com/contact
I think the problem is that the "resume action" ignores proration behaviour in that case though not sure, but our support team can help track this down
i already contacted them and they said it's an existing limitation and that they are sorry it's causing an issue for our current use case
it just seemed like they didn't fully understand that this is a bug that affects all companies that use the customer portal and enable the pause functionality 😆
oh wait what
that's like a report from 6+ months ago
did you find anything different/new?
no, i thought it would get prioritized
but it hasn't, so i reproduced it today just to make sure it's still an issue