rp

[eternal raven]

Hi
Checking...

[plain pelican]

Thank you!

Ah is this expected when PaymentBehavior is default_incomplete? Maybe what I want is allow_incomplete so the subscription charges immediately

[eternal raven]

nope default_incomplete is the recommended behavior
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements#create-subscription

You are using a test clock for this Subscription

I have a doubt about billing_cycle_anchor and backdate_start_date you are passing

[plain pelican]

The docs say both fields are supported when used together

Would a test clock affect the auto advance property?

[eternal raven]

No I'm not sure that's the cause of that. checking...

[plain pelican]

Looks like changing it to "allow_incomplete" did cause it to charge the first invoice immediately, which is the behaviour I want

What's the reason "default_incomplete" is recommended?

[eternal raven]

One of the reasons behind is to make the subscription incomplete as there is no payment method yet collected when creating a Subscription.

[plain pelican]

Ah I see, we're collecting the payment method separately, so we have it available when creating the subscription. Does that avoid the drawbacks of allow_incomplete?

[eternal raven]

probably in your use case allow_incomplete is the right choice, it will tries to pay the first invoice as mentioned in the doc
https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior

[plain pelican]

Got it, thank you!