smokey-subscription-creation | Stripe Developers | Page 1

frigid sphinxBOT Nov 28, 2023, 4:30 PM

#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

smokey0477, 12 hours ago, 10 messages
smokey0477, 5 days ago, 7 messages

sudden cypress Nov 28, 2023, 4:32 PM

#

Yes, the payment intent status will tell you if the initial payment succeeded or not

#

If you try that call in test mode it should charge the customer properly as long as they have a default payment method set

hot glen Nov 28, 2023, 4:33 PM

#

Well it seems to create an invoice with the status incomplete. The test card I'm using has no restrictions like 3ds, and is the users default method

frigid sphinxBOT Nov 28, 2023, 4:34 PM

#

hot glen Nov 28, 2023, 4:35 PM

#

Reviewing the payment intent object, it has a status of requires_payment_method. However, the customer has a payment card and is set as default

#

I wonder if its because of default_incomplete

sudden cypress Nov 28, 2023, 4:37 PM

#

If you try again but with allow_incomplete do you see different behavior?

hot glen Nov 28, 2023, 4:39 PM

#

Yes now I seem to get the prompt for 3ds on a non 3ds card... but that's fine

#

I don't understand the difference between allow_incomplete and default_complete though

#

Because according to the docs, allow_incomplete should be used when the first invoice can not be paid

#

So in my case, I should be using default_incomplete as the first invoice requires payment

sudden cypress Nov 28, 2023, 4:45 PM

#

The API reference explains the difference https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior
I thought they both tried the first charge immediately for charge_automatically subscriptions. Let me see if I can find more info on that

#

Ah that is a key difference between the behaviors allow_incomplete will attempt the first payment immediately, with default_incomplete you need to make a separate API call to confirm that payment https://stripe.com/docs/billing/collection-method#failed-subscription-payments

#

I think either can work for your usecase, they will both allow you to handle situations where the first payment requires further action like 3DS or fails

#smokey-subscription-creation