#stripe_connect_platform-subs-proration
undone marsh
ok. thank you.
silk lodge
Can you clarify - what legacy billing anchor feature are you on?
Alternatively, do you have an example of a subscription that does behave like you expect it to?
undone marsh
We are a Stripe Connect platform.
It should set the billing anchor date for that subscription to the 1st of the month and just do a proration for the 1st charge since today is the 23rd of the month. Can you look...
Can you look at the API call and see why it didn't prorate the first charge and set up a billing cycle that hits on the first?
I can do a test charge on my end that is similar. Give me a few minutes please.
OK, this is weird. Our customer states that her customers are being redirected to the failed payment URL rather than the success URL. I tried a test payment and I was also redirected to the failed payment URL. And no subscription was set up. But for our customer, a sub was set up but the billing anchor was not honored. Hm.
The customer I just set up is this one:
cus_KpcBXs6XhzGkUC
Yeah, this is pretty bad. This should have been working now for more than a few years. ?
silk lodge
Let's focus on the billing cycle anchor issue first - looking at the creation request for the Subscription you sent over, you're not setting billing_cycle_anchor at all and I don't know of any specific legacy feature that would do this anchoring for you. Do you have an already existing/older subscription that you know anchored correctly?
undone marsh
We have tests that create them I could run. Weird.
silk lodge
Yeah, if you show me an example of a Subscription that anchors at a different date WITHOUT also setting billing_cycle_anchor I can take a closer look, but otherwise I think the issue is just that you need to set billing_cycle_anchor when you create the subscription
undone marsh
evt_1K9xVeGkntF0z1iAArLgmVNu
OK, I fixed it.
It looks like we switched the calendar widget the customer uses to actually pick the date to anchor on and the date wasn't being recognized since it just switched from "%m/%d/%Y" to something else so the billing anchor was failing. Not sure if that is the right event i sent but that was one of the events in the process - the Customer was created and the initial payment was prorated and the billing cycle is correct.
silk lodge
Awesome - glad to hear you got it sorted out 🙂
I'm heading out, but if you need anything else @flint furnace can help
flint furnace
Also glad to hear you sorted it out. Any further questions on this at the moment?
undone marsh
Case closed on this one. Thank you!