#sukatoa-Subscription

1 messages ยท Page 1 of 1 (latest)

smoky fable
#

Hi there, so basically you want to change the subscription status from unpaid to active, am I right?

#

I can see that you are setting a invoice_settings.default_payment_method for a customer

#

Here's how you handle the unpaid subscriptions
https://stripe.com/docs/billing/subscriptions/overview#unpaid-subscriptions

- Collect new payment information.
- Turn automatic collection back on by setting auto advance to true on draft invoices.
- Finalize, then pay the draft invoices. Pay the most recent invoice before its due date to update the status of the subscription to active.
~```
So far you have completed step 1, you should continue step 2 and 3
light viper
#

I apologize for the late reply, had a meeting. That part is what started me to doubt if the current implementation will succeed, and the initial evidence (customer + payment method + subscription on test clock) showed us it's not working.

We will try to make refactors and use the test clock and see if we can successfully make the subscription to "active".

I'll come back here for feedback.

#

By the way, I read this part and started to concern about "invoices continue to be generated". We were able to disable the service on our end but the confusion starts on "invoices continue to be generated".

For example, the payment failure happened on May, and user comes back to us on September (though the user never had the service since May. Does that mean it generated 5 invoices (failed)? I mean invoices for May to September.

Our mechanism is that, when subscription fails (payment failure), we'll stop the service and wait for them to change CC, if the user change credit card let's say September, we will continue the service for them only when they successfully change their credit card, and it will be activated right away.

Meaning, Since May to September, the user don't have access to our service, and during September when they change CC, the service will turn on again for them but we're not longing for the previous invoice that failed

#

And so if it generates 5 invoices, are we allowed to only reconcile the latest invoice only and make the subscription activate again?

light viper
#

@smoky fable

crisp kernel
#

๐Ÿ‘‹ I'm taking over from Jack

light viper
#

Oh, very prompt, thanks man

crisp kernel
#

The invoices will still be generated in draft state (i.e. auto_advance is set to false), so that no payment attempt will be made

light viper
#

aahhh, and so, if I only process the last generate invoice, will it be enough for the subscription to be "active" again?

crisp kernel
#

Yes, after new payment method is collected, you still need to:

- Turn automatic collection back on by setting auto advance to true on draft invoices.
- Finalize, then pay the draft invoices. Pay the most recent invoice before its due date to update the status of the subscription to active.
light viper
#

thank you much, River. will proceed now and will get back to this for feedback

crisp kernel
#

no problem! let me know if you need more help ๐Ÿ™‚