midnight-subscription-immediate | Stripe Developers | Page 1

fathom ermine Aug 16, 2022, 3:58 PM

#

@rough tinsel When you create a subscription we charge/finalize the first invoice immediately, no parameter is needed. If you are seeing otherwise, can you give me an example subscription or invoice id to look at?

rough tinsel Aug 16, 2022, 4:00 PM

#

in_1LXS3FDKXn4ivDe33PiXqExf

#

Draft invoice came out minutes after creating the subscription and says it will finalize up to hour

fathom ermine Aug 16, 2022, 4:09 PM

#

sorry discord got bursty suddenly but looking now

#

that's not really what happened here. https://dashboard.stripe.com/test/logs/req_g6S9qEiGPc8ROh this is your Subscription creation request. You explicitly passed custom parameters that disabled the first invoice proration_behavior: "none", billing_cycle_anchor: "1660664895",
So you need to not to that. If you explicitly anchor your subscription to a future date and disable proration then there's no first invoice until that specific future date.

rough tinsel Aug 16, 2022, 4:14 PM

#

I'm not following. The billing_cycle_anchor needs to be in the future, I have no other option. And I don't want to prorate anything when creating a new subscription.

fathom ermine Aug 16, 2022, 4:15 PM

#

that... doesn't make any sense 😅

#

Let's take a step back: I am signing up on August 16 at 02:17:00 UTC. When exactly do I need to get charged for the first time?

rough tinsel Aug 16, 2022, 4:16 PM

#

August 16 at 02:17:00 UTC

#

I think I know where I'm going wrong, I need to set the billing anchor to 30 days out (lets say for a monthly subscription) and not to 'now'? I was setting it to essentially now, so they get billing immediately.

fathom ermine Aug 16, 2022, 4:20 PM

#

I'm sorry but that is still totally wrong

#

you need to not set that parameter at all

#

You are creating a Subscription, you want that Subscription to immediately charge for the billing cycle, so you do not pass any specific parameter for it

#

The reason to pass billing_cycle_anchor is when you want a billing cycle anchor that isn't "now" (which is the default). Say you want to charge on August 16 at 02:17:00 UTC but you want the next payment to be on September 1st 00:00:00 UTC and the next one to be on October 1st 00:00:00 UTC

#

in that case the billing cycle anchor is the 1st of the month, and you want to charge upfront for the Aug 16 - Sep 1st prorated time

fathom ermine Aug 16, 2022, 4:43 PM

#

@rough tinsel does that make sense? Did you have any follow up questions?

rough tinsel Aug 16, 2022, 4:43 PM

#

Trying to test now. I see the issue ty. My understanding of billing_cycle_anchor is wrong. If I want to emulate billing_cycle_anchor: 'now', then I need to not have it in the parameters I send in when creating the subscription?

#midnight-subscription-immediate