#_nicolel_
1 messages · Page 1 of 1 (latest)
Hello 👋
The API ref goes over the differences
https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior
hi yes, I did read the docs for this under the update_subscription endpoint which is slightly different than the create_subscriptiondocs that you linked. The docs you linked specifically say "the first invoice" and have a different status than the update docs.
Whoops sorry, meant to link the update ref instead
https://stripe.com/docs/api/subscriptions/update#update_subscription-payment_behavior
Does the ref clarify? What part is causing the confusion?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
The descriptions are almost exactly the same for them, I am struggling to understand what the difference is when reading these docs. Both switch the invoice to status=past_due and say that it allows for addistional user actions. It is unclear to me when I would use one vs the other
Use allow_incomplete to transition the subscription to status=past_due if a payment is required but cannot be paid
Use default_incomplete to transition the subscription to status=past_due when payment is required and await explicit confirmation of the invoice’s payment intent.
I'd recommend running a quick test with both. I think the difference is in how the payment is handled