#natalieh-subscriptions
1 messages · Page 1 of 1 (latest)
Hello 👋
Can you provide a brief summary so that I'm caught up with context from your previous conversation?
ah I see you've edited the ask, thanks
The subscription in question for example: https://dashboard.stripe.com/logs/req_d2fgRAN2OIS8TD
Conversation with Bismarck: https://docs.google.com/document/d/1QtzKmqnfVxfmFhKkL3dVnrGqOoQq6or-y5nL8tO4gWs/edit?usp=sharing
I'd recommend using Subscription Schedules for this use-case
as cancel_at will always prorate
Yeah, but we don't have the time or resources to rewrite our code right now.
Perhaps the cancel_at date should be set days before the next charge date…
So if it’s a 2 week interval and there’s supposed to be 3 installments we set the cancel_at date to be BEFORE the 4th charge, so technically it never happens but we make sure charges 1,2 and 3 did happen.
Maybe setting proration_behavior to 'none', that might work. Possibly use in conjunction billing_cycle_anchor?
Hmm I'd recommend trying it out in test mode to be honest as I haven't tried this flow personally. I'd test it myself but server is a little busy at the moment.
As far as I know cancel_at will always cause proration to happen regardless of proration_behavior due to the way its built