[#7172] Still problems with Reactivation of user plan

Strange, payment failed notifications are working fine in my tests. At any rate my recommendation at this time is to just disable retries. It doesn't really benefit the user at this time anyway since there's no means of updating the card on file in CBSubs. Will review this further once investigating the bug when time permits (in the middle of upgrading all of CBSubs to Bootstrap 4 styling).

Will do. Just to clarify before I disable that feature and a users card expires, will their card update before it fails for the first time, or does it usually fail and then update the expiration information?
Meaning as you've mentioned before, these days expiration dates are generally handled by the card companies and aren't much of a problem even if they expire, in this case should it update and allow the initial attempt to go through or fail & then work on the second attempt?

Once I disable that feature it will affect more users based on expiration etc... than the unusual scenario that we're experiencing. So I want to make sure I don't cause a worse case by trying to alleviate the more unusual of the scenarios. Thank you

If the expiration date is updated per Stripes agreement with Visa for example then it will be done before it actually expires (you typically get your new card a good month or more before it actually expires). So there won't be any negative impact there. This is strictly if the card expires at Stripe and Stripe was unable to update expiration per agreement with the card provider. So it doesn't really benefit CBSubs at all to have it retry at this time since we've no functionality to update cards on file.