CB Subs integration email expiration timing

Failed payments are typically just ignored. The basket will be left in a pending state if it's in a pending state otherwise if it's a renewal it'll simply expire when the expiration date is reached. There's no reason to do anything with them. They're not a dispute so reversal handling is not planned for failed payments (there's nothing to reverse as it failed).

The problem is for auto renewal. We have a lot of customers with autorenewal and Stripe and when the payment is failed this way, there is no indication for us or them for an immediate action.

It is needed that we or them can address the failed payment and either ask for an alternate way to pay or decide that it's really a will to expire the subscription

But as there is simply no indication nowhere in CBSubs for failed renewal it's pretty difficult to do for now.

Could you add a failed state or something somewhere ?

The subscr_failed event with a Denied status is meant to log a failed payment row, but isn't currently being handled in the notification handling. Will review implementing handling of those events in the notification behavior, but it doesn't do anything except log a failed payment row.

forge.joomlapolis.com/issues/7678

For now I suggest just enabling the notifications at Stripe, which you can do under Settings > Subscriptions and emails then toggle "Send emails when card payments fail" on.

OK.

Notification via email is already activated at Stripe. That may be good to advise the customer but it does not let our staff to be advised of a failure.

What we are seeking is a quick way to be advised and take the appropriate steps.

Any suggestion ?

No idea, you'd need to check with Stripe to see if they have a setting to notify you of a failed payment. Since CBSubs has no payment method management (e.g. for users to update their card on file) the failed payment handling isn't particularly useful to CBSubs.

Once/If payment method management is implemented there would likely be official notifications specifically for failed payments since users would be able to do something about such an issue. Have to keep in mind CBSubs was originally designed specifically for PayPal where none of this is an issue since they'd manage all of that from their PayPal account directly. It's a slow process decoupling that dependency to make CBSubs more gateway agnostic.