#thomasst

1 messages · Page 1 of 1 (latest)

finite irisBOT
icy tendon
#

Hi 👋 it looks like it is because that is not how you have your Subscription settings configured.

Check the Manage failed payments section on this page:
https://dashboard.stripe.com/settings/billing/automatic

The status change is set to occur once the retry schedule is exhausted, and the Invoice with the failed payment (which I assume is the one you're referring to) has yet to exhaust its retries.

Additionally, there seems to have been successfully paid Invoices after the one that failed, which I'm pretty sure will also prevent the status change as we check the most recent Invoice.

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

misty orchid
#

The "managed failed payments" is configured properly, we want it to change into unpaid status when all retries fail.

#

But we want it to be past_due when a single payment attempt afils.

#

*fails

#

So you are saying a single subsequent successful payment will put the subscription back in active status even if it's just a pro-rate?

#

Also, does that mean that when all retries are exceeded the subscription will go straight unpaid despite the recent successful charges?

icy tendon
#

Apologies, you're right, failed payments do move the Subscription to the past_due state. Which failed payment are you referring to that you expected to change the state of the Subscription but didn't see that change occur?

misty orchid
#

The subscription changed to past_due in evt_0LxJjH4rOYBvHyzsyLbOXS3q and back to active in evt_0LxgCV4rOYBvHyzsfTfz1IWA because a subsequent invoice succeeded, but invoice that caused the subscription to past_due is still not paid.

#

So in my opinion this subscription should be past_due still.

icy tendon
#

Understandable, but that's not currently how our system works. We reference the newest Invoice for the Subscription, so when the new Invoice was created and it's payment succeeded the Subscription was expectedly moved back to an active state.

If you would prefer that these Subscriptions are still considered past due, then you'll need to write custom code to monitor and maintain a status for these objects, separate from the one that we maintain, that follows the logic you'd like to see.

misty orchid
#

To be clear, that means that this subscription will not go unpaid / past_due when further payment retries fail on the older invoice?

icy tendon
misty orchid
#

Thanks

icy tendon
#

Any time!