[#7239] CBsubs Stripe Dispute no feed back

OK got it, so can you tell me when #7239 will be addressed ?

I don't know. I'm currently working on our PMS plugin rewrite then immediately after that Joomla 3.9 will be going into RC and will be working on our privacy plugin to integrate with Joomla 3.9 privacy component for easier GDPR compliance. Likely after that will be time to improve the IPN handling of CBSubs Stripe.

hello and happy new year

I am coming back on this subject as this is a problem for us now.
We have about 10 customers this month which had SEPA not working. This led to 10 disputes and we still have 10 completed baskets and 10 active subscriptions even if they did not pay.

Can you suggest a procedure so that we can move back the basket to a pending state, cancel the active subscription and cancel the payment ,
Can we do it by an auto action during the time you implement a correct dispute handling in CBSubs ?

This is a very annoying problem to deal with for our team

Thanks in advance

Edit them within CB > User Management and force the subscription cancelled. I'm already working on improving CBSubs Stripe for the past week so dispute event handling should be implemented in the next few weeks as I work through the various CBSubs Stripe tickets.

Edit them within CB > User Management and force the subscription cancelled

Doing so cancel the subscription but the basket is still marked as completed.
We tried to suppress the payment in order to try to get the basket back to pending but no success.

Is it possible to keep the basket and get it back to Pending state manually ?

There's no functionality in CBSubs to change the basket state. That'd have to be done in the database. Recommend just cancelling the entire process and the user will have to purchase again. Why is it going into a dispute state? Is their payment being rejected by Stripe? The only reason a payment should ever going into a dispute state is they opened a dispute with their bank in which case you should just cancel their subscription, which is exactly what the dispute event handling is going to do when implemented.