#dandingman
topaz plover
strange meteor
Hello! It's anchoring today because payment is due now, and it can't go back in time to charge them in the past, so it's billing today.
grim coyote
Got it - How can I achieve the behavior I'm looking for
I'd like to anchor to "June 1" in the future
Bill effective today (now) but anchored to the first of the month
strange meteor
Hm.
grim coyote
Well sorry
Not effective today in this case
I have 2 cases right now for installment plan type things. So subscriptions but only for a set number of iterations or with an end date. which is whuy I'm trying to use sub schedules right... ok
So the two cases are
- backdate to an old effective date and set a custom anchor date
- prorate as of today so effective billing start is today but anchor to some other date in the future not 1 month from now (less than one month)
strange meteor
You probably need to set two phases. The first phase would bill them immediately for the backdated amount due now, and the second phase would be for the next payment due and start on the actual anchor date you want.
grim coyote
If I use 1 phase that starts start of April 1 and ends end of May 31 and then the next phase just has an end date of end of august for this $50 priceId, what would you expect the customer to be charged now and then sequentially in the future?
strange meteor
It depends on your Price and proration settings. You can test the specific behavior easily in test mode to make sure you get the exact flow and pricing you want.
Are you familiar with Test Clocks? https://stripe.com/docs/billing/testing/test-clocks
grim coyote
Ok I'll try splitting the phases up as you're describing
No I've never used them before
strange meteor
Test Clocks let you travel through time in test mode so you don't have to wait for things to happen. Makes it easy to test things like waiting for a phase to end, jumping forward through the next phase, etc.