#elianbraja

1 messages · Page 1 of 1 (latest)

fathom nightBOT
hasty heron
#

Hi 👋 no, I don't believe so.

hot swan
#

I wanted to ask another question. Why subscription is passed to status: **unpaid **if no default payment method is present on customer. On the other hand if a payment method exists for customer but does not have funds, the subscription gets status: past_due. Why?

#

I want in both cases to be passes to past_due

#

can I please have a response?

hasty heron
hot swan
hasty heron
#

Looks like you've configured your Subscriptions to move to an unpaid state once your three retry attempts are exhausted. Are the Subscriptions that are moving to an unpaid state doing so after about a week?

hot swan
#

No, are duing on the first attempt

#

sub_1MRv38EMyoEBRsWZcg9HtA6z

#

this is the id of my subscription. I am using test clock to test

#

As you can see the latest invoice created is marked as uncollectible immediately on the first attempt

#

and the subscription is passed to "unpaid"

#

This happens only if customer does not have any payment method. On the other hand, if customer has a failing card, the subscription moves to past_due

hasty heron
#

It looks like this Subscription has gone in and out of an unpaid state many many times. I'm also seeing that multiple Invoices were generated before the Subscription went into an unpaid state the first time.

I'm also seeing the most recent Invoice had multiple failed payments associated with it. I see 4 invoice.payment_failed events that were generated for that Invoice.

#

Looking at the billing clock times, the Invoice was also created 10 days before it was closed, so it doesn't look like the Invoice immediately closed.

hot swan
#

I am thinking about it a bit differently. The subscription renews on Aug 7, 2042. I just moved the test clock to Aug 8, 2023 since this is an annual subscription

#

since has passed only 1 day and I have the rule to pass the subscription to unpaid after 7 days, it should have been in past_due yet

hasty heron
#

I see that the billing clock was set to Aug 7th 2041 when this Invoice was created.

hot swan
#

yes, and it should have not passed to "unpaid"

#

it has not passed 1 week from the first trial

hasty heron
#

I'm seeing that it has, the Invoice was closed when the billing clock's time hit Aug 17 2041. The billing clock's current time is beyond even that, and is currently at Aug 20 2041.

hot swan
#

ok lets try again

#

I updated the subscription to active

#

I do not have any default cards for my customer

#

as you can see the upcoming invoice will be created Aug 7, 2042

#

Can I update the clock to Aug 8, 2042 and expect the subscription to be on status: past_due?

hasty heron
#

Did you create a new billing clock?

#

Sorry, test clock?

hot swan
#

Sorry I miss writed

#

can you please recheck my messages

#

I updated

#

is it correct now?

#

can I update test clock to 8 Aug 2042?

hasty heron
#

Sure, but that is a year and a day beyond when you say the Invoice will be created, so that is well beyond the retry period you have specified so the Subscription should go to unpaid if you do that.

hot swan
#

I re-edited

hasty heron
#

Oh, updated again

hot swan
#

8 Aug 2042

hasty heron
#

Yes, it should stay past_due then

hot swan
#

I should be having my subscription in past_due

#

lets try

#

Yes, it passed to past_due. Maybe I have messed up with dates

#

Thank you for your time

hasty heron
#

Always happy to help, I'm glad to hear that behaved as you were hoping!