Renewals creating incorrect expiration date
10 years 3 months ago #239280
by LukeDouglas
Replied by LukeDouglas on topic Renewals creating incorrect expiration date
Kyle,
As I only have access to the cPanel and have not made any changes to the database, we can eliminate that as a potential problem. We have checked with the two individuals who have access and neither one of them have modified a subscription record.
Here is a subscription for Pamela Farmer who signed up on 12/03/2013. She paid on that date yet it renewed the subscription on 12/31/2013 whereas we would expect it to renew on 01/03/2014.
Also, in looking at Pamela's current / past subscriptions from their record, it shows the Monthly Plan with 1 month Active, expiring on 2014-09-03.
And it shows the recurrings used as 9 and the same expiration date 2014-09-03 here.
Here is the Monthly subscription plan pricing tab screenshot:
As far as I can see, it is setup correctly.
I would expect that if they had subscribed on 2013-12-03 that on 2014-01-03, they would have been charged by Authorize.net, the payment to be recorded on their payments record on CBSubs, and their recurrings to be incremented 'one' time from '0' to '1' for the 1st time and that the expiration date would have been extended to 2013-02-03. This did not happen.
This problem has my client real jittery right now as they are fast losing faith in the stability of the CBSubs application. Somewhere the system is generating multiple recurrings and extending the expiration date further out than it is suppose to be extended.
We need help in resolving this issue quickly.
As I only have access to the cPanel and have not made any changes to the database, we can eliminate that as a potential problem. We have checked with the two individuals who have access and neither one of them have modified a subscription record.
Here is a subscription for Pamela Farmer who signed up on 12/03/2013. She paid on that date yet it renewed the subscription on 12/31/2013 whereas we would expect it to renew on 01/03/2014.
Also, in looking at Pamela's current / past subscriptions from their record, it shows the Monthly Plan with 1 month Active, expiring on 2014-09-03.
And it shows the recurrings used as 9 and the same expiration date 2014-09-03 here.
Here is the Monthly subscription plan pricing tab screenshot:
As far as I can see, it is setup correctly.
I would expect that if they had subscribed on 2013-12-03 that on 2014-01-03, they would have been charged by Authorize.net, the payment to be recorded on their payments record on CBSubs, and their recurrings to be incremented 'one' time from '0' to '1' for the 1st time and that the expiration date would have been extended to 2013-02-03. This did not happen.
This problem has my client real jittery right now as they are fast losing faith in the stability of the CBSubs application. Somewhere the system is generating multiple recurrings and extending the expiration date further out than it is suppose to be extended.
We need help in resolving this issue quickly.
Please Log in to join the conversation.
krileon
10 years 3 months ago #239349
by LukeDouglas
Replied by LukeDouglas on topic Renewals creating incorrect expiration date
Kyle,
I've double-checked the Authorize.net gateway settings and compared to the settings on Authorize.net. The API login id matches, the transaction key matches with the original settings, the MD5 Hash 'should' match as I recopied it over to Authorize.net, the Silent Post URL matches and the CBSubs settings is 'set at Authorize.net'.
As far as 'auto recurring with notifications', you are correct as they are 'Autorecurring without notifications'. As I previously had the Silent Post URL settings NOT set as 'set at Authorize.net', is this the reason why these are listed as 'auto recurring without notifications'? I checked the Plans / Pricing and the Auto-renewals with auto-recurring payments was set to 'Yes: subscribe user to automatic recurring payments'. There were no options for setting it for 'with notifications' or 'without notifications'. Is there a place for this or is it determined by the settings for the Silent Post URL?
I've double-checked the Authorize.net gateway settings and compared to the settings on Authorize.net. The API login id matches, the transaction key matches with the original settings, the MD5 Hash 'should' match as I recopied it over to Authorize.net, the Silent Post URL matches and the CBSubs settings is 'set at Authorize.net'.
As far as 'auto recurring with notifications', you are correct as they are 'Autorecurring without notifications'. As I previously had the Silent Post URL settings NOT set as 'set at Authorize.net', is this the reason why these are listed as 'auto recurring without notifications'? I checked the Plans / Pricing and the Auto-renewals with auto-recurring payments was set to 'Yes: subscribe user to automatic recurring payments'. There were no options for setting it for 'with notifications' or 'without notifications'. Is there a place for this or is it determined by the settings for the Silent Post URL?
Please Log in to join the conversation.
Moderators: beat, nant, krileon
Time to create page: 0.234 seconds
