jasonkuhrt-requires-confirmation

[stiff karma]

Hi 👋 can you clarify which part of the flow is getting stuck at requires_confirmation?

[glossy lava]

👋 stepping in here as toby needs to step away. Can you provide me an example subscription ID that I can look at?

[hard cipher]

sub_1LBJt3IhnflvQVbikpQCveDD

[glossy lava]

Thanks, looking!

[hard cipher]

These docs pointed to by the api docs talk about payment intents api but oriented toward using them from the frontend. It says nothing about our case of 1) a backend situation where 2) the payment intent was created automatically by stripe

https://stripe.com/docs/payments/payment-intents

[glossy lava]

Okay so the reason here is the payment_behavior that you are using.

You have it set for default_incomplete

Whereas if you want the invoice to attempt a charge automatically using the default payment method then you want to use allow_incomplete

[hard cipher]

Oh wow

Are you saying the default payment method is not used if default_incomplete is chosen?

And another question: What are the downsides to allow_incomplete?

(versus default_incomplete)

[glossy lava]

You must still confirm the PaymentIntent in a separate request if you use default_incomplete.

The downside is that if you attempt to create a Sub with allow_incomplete and there is no paymentmethod attached to the customer or Sub then the request will fail.

[hard cipher]

Ok, given our control of the flow in the application its not a problem in our case I think

Thanks, I guess the issue is as simple as that. I will give your suggestion a try.