Feature proposal #6647
closed
Auto recurring payments do not generate new baskets
100%
Description
When an auto recurring payment comes through it simply renews the existing basket and creates a payment for it. For manual renewals a new basket is created each time. Since basket and invoice are one in the same for CBSubs this causes a problem for invoicing. When a user views their invoices from their subscription tab they only have 1 invoice even if they've auto renewed a dozen times. Again, not an issue for manual renewals.
Auto recurring payments should use the original basket as a reference for validation. It could then clear the id and store a new basket for each renewal.
Updated by krileon almost 7 years ago
- Status changed from New to Assigned
- Assignee set to beat
- Priority changed from Normal to Urgent
Updated by krileon almost 7 years ago
This could probably be done in updatePaymentStatus of cbpaidPayHandler which would universally apply to all gateways otherwise my initial assessment is this would have to be changed on a per gateway basis. So ideally the first payment would just pay the original basket. If it's a renewal it'd generate a new basket and pay it instead of modifying the original basket. Since updatePaymentStatus has all of that information AND is always called after the original basket is verified it should be the safest place to do it.
Updated by
Updated by krileon over 5 years ago
- Project changed from 2 to CB Paid Subscriptions
Updated by krileon over 5 years ago
- Target version changed from CbSubs 4.5.0 to 4.6.0
Updated by krileon over 5 years ago
- Status changed from Assigned to Rejected
- Target version deleted (
4.6.0) - % Done changed from 0 to 100
Closed in favor of #7435