I have set up recurring payments for a client's site, using AIM, all modules are most recent versions. Some customers have their payment set to automatically recur every month. It has been correctly billing them for the new month, but sometimes authorize.net is charging 2 or more times for the same payment, much to the distress of some of our customers. Looking at out transaction log at authnet, I do see the multiple billings; they claim they are following our requests, but I don't see why the second charge was made.

As an example, I see an order in our orders log with a recurring charge that was made on 10/29 at 04:13PM, which is correct. But if I go to authnet, I see both this charge, and a second one with the same customer name and amount, at 10:25PM. Authnet says it is something we are doing, but I don't see anything in our order logs indicating the additional payment was made. Is there somewhere I should be looking for this on our server? Would it help to try the dev version of the recurring module?

The site owner says authnet is offering a service to do recurring payments, but he is not signed up for that, but suspects the problem may be on their end.

Is there a way to get more information on when we are sending payment requests to authnet? Have others experienced this problem (I didn't see anything in the issue queue)?

Comments

boon4376’s picture

boon4376 CreditAttribution: boon4376 commented

I have not experienced this issue, but honestly, this recurring module is buggy as hell and I am abandoning it. It has not been updated in over a year.

WooCommerce has a recurring feature which I have found to work much better and so I've had to switch to Wordpress and WooCommerce.

It's unfortunate because this uc_recurring module is close to being so excellent, I'm not sure why development and maintenance all of the sudden stopped. I even contacted the owner and offered payment to fix some of the errors and heard nothing back.