#jemmons-subs-incomplete
1 messages · Page 1 of 1 (latest)
The difference is that allow_incomplete will actually attempt payment, while default_incomplete will not.
As an example - if you had a customer that already had a Payment Method set up as their default and you created a new Subscription for them:
- Using
allow_incompletewould create the Subscription and immediately attempt payment for the first Invoice with the default PM. If payment succeeds it'll immediately transition toactive - Using
default_incompletewould crreate the Subscription and if it needs payment it'll have a status ofincomplete.
Ah, so in the default_incomplete case, I’d have to explicitly… finalize the invoice? Or set it to auto_advance to kick things off?
No, the finalization still happens - what you need to do is confirm the underlying Payment Intent
Gotcha. Thanks a bunch!