[#6647] CBSubs recurring payment with only one basket

Hello

Some of our customers use now recurring payments with Visa credit card and Ogone gateway.
We have noticed that the payments were made correctly each month with monthly IPN successes from Ogone/Ingenico, but the basket only exists once in CBSubs backend.
This means that these customers may have only one invoice with the first basket id which does not reflect the reality of their history.
For instance, they have been charged 5 months but only got the monthly invoice of the first month.
Did we miss something ? How can they retrieve their 5 monthly invoices ?

Thanks a lot
Regards
Jean

Manual renewals always generate a new basket. It's likely that auto recurring payments don't as they have to be linked to a basket to validate (their IPNs always include the basket id).

I have noticed that auto recurring payments add a figure after the basket id such as 3000R1 3000R2, ..aso,
Can you use these to generate invoices accordingly to that our customer would get the correct invoices for their payments ?

Where are you looking for invoices? They should be on the invoices page that you can reach from the bottom of the subscriptions tab. They should also ideally get an invoice from the payment gateway directly.

They should be on the invoices page that you can reach from the bottom of the subscriptions tab

Yes that's the problem, there is only one invoice, the first one corresponding to the basket first id.
Then no invoices for the next recurring periods appear.
In the backend, there is only one basket for the initial period and then several payments for the recurring periods.

Are the invoices displayed in front end based on baskets or on payments ?

For CBSubs the basket and the invoice are the same thing. Payments are tied to a basket. Invoices are not based off payments. It creates a new basket for manual renewals as it has no need to validate the basket. IPNs have to validate against the basket. I suppose it could be rewritten at some point to take the original basket and create a new one from it by clearing the id before storing, which would effectively do what you're wanting, but that's not likely to happen anytime soon as it's a pretty serious change.

Have added a feature ticket to review rewriting the behavior to see if creating a new basket per renewal would be more ideal.

#6647