I have a monthly recurring subscription product set up on our production site. We launched this last month and got several subscription orders. Now, the renewals are starting to process, and I'm seeing some behavior I can't explain. In the Drupal site, all looks fine. A new order for the renewal for $30 is created, processed and paid. But on the authorize.net site, 2 transactions for $30 are charged to the customer. The first one is correct, with the correct invoice number corresponding to the renewal order. The second $30 transaction charged to the customer is sent to auth.net a few hours later, but the invoice number is wrong - it matches some other order number for a different customer for a different amount.

I don't see anywhere in the recurring fees configuration or the log messages where this 2nd transaction is being triggered and sent to auth.net. This is happening to a lot of our customers, and they are unhappy! Please help!

Comments

michellezeedru created an issue.

bchaffer’s picture

bchaffer CreditAttribution: bchaffer commented

My best guess is that you have a development or staging copy of the site running outside of production (with a snapshot of production data), and that site is creating recurring orders on cron. I would bet that if you chase down that copy of your site, you'll find invoice numbers that match your extra transactions in Authorize.