Free subscribed charged

Kyle,

I believe I know the answer to this but I wanted to confirm. If a subscriber has their account upgraded to a free subscription, then management will have to log into Authorize.net to terminate the recurring charge. Is this correct?

Here is where their monthly subscription was upgraded to an annual subscription (they won a contest). However, look at the original monthly subscription recurrings used which is 6 and the expiration date of 2013-12-19! This is a date which is 'less' than what I would expect it would be which is 2014-01-03! This is the same problem as in my other posts so let's don't get into that aspect on this ticket.



Here is where they had originally paid.



However, they were charged on 2014-01-03.



So there is no functionality within CBSubs that will 'terminate' a recurring charge on Authorize.net on an account that has either been terminated or upgraded. Is this correct?

So there is no functionality within CBSubs that will 'terminate' a recurring charge on Authorize.net on an account that has either been terminated or upgraded. Is this correct?

There is, that's how the cancellations work. It should be running the cancellation API call before the upgrade completes so the previous subscription can cancel its recurring profile. This assumes "Authorize.net name (API login id):", "Authorize.net transaction key:", and "Authorize.net MD5 Hash:" have all been properly configured so the API call can be made. If this isn't working then it's a bug that'll need to be fixed in next release.

Also both of those subscriptions say not auto recurring. So they are single payments. The only way for it to recurring by 6 is if the user manually renewed it 6 times, which is possible because you allow renewal in advance by 1 year based off your other topic regarding this.

Kyle,

The Authorize.net Gateway looked like it was configured properly but I noticed that the 'Silent Post URL above is" setting was incorrect as the link had 'http://...' whereas the Authorize.net was 'https://...'. I have changed the Authorized.net to 'http://...'. Also the setting was set to not configured so I now have it set to 'set at Authorize.net' on our side.

Could this be the reason that the recurring charge on the Authorize.net was not cancelled when the upgrade was performed on our end?


As I've PM'd the login credentials for another post, could you also look at this?

Could this be the reason that the recurring charge on the Authorize.net was not cancelled when the upgrade was performed on our end?

Yes, it sounds like your gateway is not configured correctly as the hash is not validating. Meaning the API call is failing. Please review your CBSubs documentation carefully and configure Authorize.net exactly as instructed.

Kyle,

I confirmed the MD5 Hash is correct.

Now as far as recurrings, I have set the annual and monthly plans for Renewable in advance by = 'Only after expiration' and set the grace period to 1 day. Hopefully, this will ensure that no one can do multiple renewals which could potentially create multiple 'recurrings' and an 'expiration date' way far into the future.