CB Subs integration email expiration timing

Is the status of the basket changing when the renewal comes through?

No the basket does not change its status. I think that this is coming from CBSubs emails integration

By the way, that's a problem because for auto recurring with several days like SEPA STRIPE, we don't even know that the basket will be paid, or is pending or is dealt with by STRIPE until STRIPE sends back a payment completed or payment failed (dispute). Could you enhance this process ?

Also we have noticed that the last failed payment did not reverse the payment but only unsubscribed the subscription. Previously the payment was also reversed and indicated as this on CBSubs. Did you change something or did STRIPE change something ?

No the basket does not change its status. I think that this is coming from CBSubs emails integration

I don't see how. Unless the subscription status has changed CBSubs Emails will do nothing. They would've had to actually expire for it to send the expiration email. Regardless there are some differences between the Presentation tab emails and CBSubs Emails conditions that are being corrected as per the below ticket, which might be the cause of the issue.

forge.joomlapolis.com/issues/7658

By the way, that's a problem because for auto recurring with several days like SEPA STRIPE, we don't even know that the basket will be paid, or is pending or is dealt with by STRIPE until STRIPE sends back a payment completed or payment failed (dispute). Could you enhance this process ?

There's nothing to enhance. It's waiting for Stripe to tell CBSubs if the renewal was successful or not. This is how all recurring payments work for all gateways.

Also we have noticed that the last failed payment did not reverse the payment but only unsubscribed the subscription. Previously the payment was also reversed and indicated as this on CBSubs. Did you change something or did STRIPE change something ?

Nothing was changed on our end in regards to dispute handling. If it was a dispute notification it will put the subscription in a reversed status. If it was a failed payment notification then it will fail the renewal and simply expire.

There's nothing to enhance. It's waiting for Stripe to tell CBSubs if the renewal was successful or not. This is how all recurring payments work for all gateways.

Ok understood ! In this case and if the basket does not go in the Pending state during the SEPA renewal period which may go up to 7 days, could you suggest how we can avoid to show such renewal in our lists ?

We use the following in the filter area of the list, to only display baskets which needs to be addressed by our staff :
More precisely should we use autorecurring_type or autorenew_type ? what's the difference exactly ?

Ok understood ! In this case and if the basket does not go in the Pending state during the SEPA renewal period which may go up to 7 days, could you suggest how we can avoid to show such renewal in our lists ?

Your date check would need to take into account the plans grace period, which is stored in the `graceperiod` column in _cbsubs_plans. I don't know if you'll be able to do that strictly through SQL as we've a PHP side function for handling math dates. I guess you could just hardcode the 7 days addition to the date if plan id = X.

More precisely should we use autorecurring_type or autorenew_type ? what's the difference exactly ?

autorecurring_type determines if it's auto recurring with or without notifications. The values for it are as follows.

0 = Not autorecurring
1 = Autorecurring without notifications
2 = Autorecurring with notifications

autorenew_type determines if it's manual renewals, auto recurring renewals, or both (when a plan allows for either/or). The values for it are as follows.

0 = Manual
1 = User-chosen
2 = Mandatory

So for your query if you want manual renewals you'd just filter by autorecurring_type = 0. If you want auto recurring you'd filter by autorecurring_type = 2.

I guess you could just hardcode the 7 days addition to the date if plan id = X.

This is exactly where I am stuck.
If we add say 7 days to the first query it will only include expiring plans 7 days after today, while what we want is only the plans expiring in 7 days

Do you have an idea of how I could find a way to solve this with CBSubs tables ?

You need to add the 7 days to the expiry date. The stored expiry date does not store with the grace period added. Once you've done that you'll be matching against the actual date CBSubs would truly expire them. From there you can do whatever you like as far as comparing against it.