A recurring fee is created for each failed attempt with authorize.net cim

WOW. subscribing.

Have you tested this on the current non-dev release? I'd like to, but not exactly sure how to simulate a failed payment.

Is this still an issues?

Recurring fees are created on hook_order('submit', ...) so unless there is some code invoking that hook in other places I'm not sure how this would be happening.

So if this were happening to you, you could debug by checking the order log? I just want to be careful, before launching my site with uc_recurring.

I've noticed something similar happening to our live site, the fee is being added when adding a comment to orders that failed. The checkmark for 'Process the 1 recurring fees associated with products on this order.' has NOT been checked.

I'm having this issue too, and am trying to get to the bottom of it. One more screenshot for the bunch: https://skitch.com/stompeers/rw42c/skitched-20110315-121253

Is this still an issue?

I apologize for marking this as active but there has been no fix for this issue and I can confirm that it exists. When you make a comment on an order it charges them for the order again. It doesn't create a new recurring fee but it acts as if you selected the "process recurring fee" option.

I noticed this happening while I was canceling orders. Glad I realized what was actually happening because I was kind of going insane for a bit.

So you are saying that when you add a comment to an order in the administrative interface, the recurring fee gets run again? Is this only if Auth.net fails (as in the OP), or also when it can successfully process the card?

This concerns me, since I have this module's 2.x branch running in production currently. Any further guidance on how I could reproduce this problem? Perhaps I can test it on the test site and avoid incurring charges for a live transaction.

It sounds like there are multiple issue:
* The first issue is that multiple recurring fees are setup
* The second issue is that multiple orders are created on renewals

It also sounds like this is specific to Auth.net CIM, I am not seeing this on a live site using a different gateway.

I am using uc_cim. I have not been able to pin down exactly when it happens but I was doing some checking on orders the other day and commenting, etc. The result was about 5 different orders that were double charged. Today was not fun... several customers e-mailing asking why we charged them multiple times even though I voided the transactions immediately. :(

chrisshattuck & FaberfoX, are you able to nail down exactly when this is happening?

Using Auth CIM. subscribing

Recurring fees are created on hook_order('submit', ...) so unless there is some code invoking that hook in other places I'm not sure how this would be happening.

hook_order('submit', ...) will fire every time a customer submits the checkout review form, whether the initial payment was successful or not. Any code that is being executed when $op = 'submit' cannot assume that the initial payment was successful. See hook_order for more details.

The uc_recurring_order_order function needs to check the status of the initial payment transaction before trying to add a recurring fee, so that it does not add the recurring fee if the initial payment was declined. I took a quick look at uc_recurring_order_order and I see no such check, so I believe that is why people are reporting that recurring fees are being added for declined transactions (eg. comment #5).

I am using Auth.net CIM with Ubercart 2.x-dev and Recurring 2.x-dev, and the declined orders seem to work allright. Here's what my original order looks like. I will be working on a test site soon and will try to reproduce some other people's problems.

04/20/2011
9:14:07 AM 59 Authorization only
ACCEPTED: This transaction has been approved.
Amount: $99
AVS response: Y - Address (Street) and five digit ZIP match
CVV match: M - Match
04/20/2011
9:14:07 AM 59 Recurring fee 42 added to order.
04/20/2011
9:14:10 AM - Order created through website.
04/23/2011
2:39:10 PM 1 New recurring fee processed, new order is 194.
05/05/2011
1:00:37 AM - New recurring fee processed, new order is 212.
05/05/2011
1:00:39 AM - Error: Recurring fee 42 for product failed.
05/05/2011
1:00:39 AM - New recurring fee failed on order 212.
05/08/2011
1:00:16 AM - New recurring fee processed, new order is 221.
05/08/2011
1:00:19 AM - Error: Recurring fee 42 for product failed.
05/08/2011
1:00:19 AM - New recurring fee failed on order 221

It will create new orders until the fee expires which seems correct. Also related, if you are using CIM and Anonymous checkout you must manually patch UC Recurring, otherwise Ubercart will always use the same CIM profile.

I have marked #1152252: UC Recurring Bills 4 Extra Payments as a duplicate of this issue.

Regards

Christian Larsen

Hi all,

we may be having the same issue with the 6.x-2.0-alpha6.

Is the recommendation to switch to the 6.x-2.x-dev version? I'm always leery about using "dev", but I guess it is better than alpha ;-)

Any idea on when the dev will come out of dev?

Just FYI. This doesn't appear to be an issue on the 7.x branch as I just ran some tests.

I take that back. Some local testing is showing replicated orders.

BTW, duplicate of #1073704: New order created for each payment retry attempt - should use last failed payment attempt order?

as rickmanelius said,
this is a dupe of #1073704