One of our customers was charged 10 times via Authorize but in Magento there is only 1 order, 1 invoice, and 1 transaction. So she was charged 9 additional times. All but three of them have different invoice numbers. The other three share the same number and none of these numbers can be found under the admin panel. What scenario could even cause something like this to happen?

  • Check the sever access log, see if there is any weird activity corresponding to that transaction. Also what are you using to process the transactions?
    – SR_Magento
    Jan 26, 2015 at 22:05
  • I am using magento's default credit card processing, which I believe utilizes Authorize.net.
    – SHNTRY
    Jan 28, 2015 at 20:29
  • Did you find it out meanwhile? Feb 24, 2015 at 18:26
  • Might want to audit any third-party extensions. It would be trivial for a malicious extension to drop it's own version of core Authorize.net files into your store. This isn't very likely, but not out of the realm of possibility.
    – pspahn
    Apr 14, 2015 at 15:57
  • Authorize.net should have a setting in their merchant control panel that will catch and prevent duplicate authorizations. Most card processors automatically do this. Aug 17, 2015 at 20:00

3 Answers 3


I have this kind of issue with Paypal when the user tries to click the submit button multiple times as the button did not faded immediately.Check the authorize.net log in var/log and system.log if there is not error.


Please try checking the Authorize.net log file in var/log folder. It will tell you the number of times a payment request has made by your customer.

If there is only one entry for that particular transaction, then there is nothing wrong the transaction. You might wanna contact Authorize.net to sort out this issue.

Just a quick question though, have all those transactions been approved? Have you matched the transaction number in your magento admin panel as well?


Have you kept your magento installation updated or at least security patched?

There are a number of known vulnerabilities some of which could potentially hijack your customer's checkout info and repurpose it into their own merchant account.

As this is a Magento forum, I'm guessing your know these things, but posting them anyway for folks who may just be getting here.



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.