seems like multiple people are having the same issue.
seems like multiple people are having the same issue.
I emailed authorize.net support
Has anyone heard anything yet?
This sucks!
Haven't heard anything yet, I emailed authorize.net as well to see if they know anything... .
Here is the contact info for Authorize:
877-447-3938
Oh, and just a side note, I just did a test purchase with paypal and everything works fine. Just authorize.net is not working, so it has to be a problem on their end. Please when anyone has updates, let me know,, I will be calling tomorrow right when they open to ask
Have you tried to do an order via PayPal?
If that works fine then try to reinstall the Authorize.net module (take note of your configurations before uninstalling and reinstalling)
Looks like an Authorize.net problem.
Will be interesting to hear what Authorize.net says when you contact them.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Why was this thread moved to the upgrade forum? Doesn't it belong in payment module or general?
I'm running 1.3.8. Is everyone else having this problem using 1.3.8?
Last edited by mm8303; 30 Jun 2010 at 08:49 AM.
To anybody that is wondering what is going on, this issue seems to have been caused by Authorize.net changing their API without any warning or explanations.
In their silent POSTback, they are now passing the x_amount parameter as 19.9500 (for example) but still using 19.95 as the amount for the x_MD5_Hash parameter.
I'm not sure what they'll do about it tomorrow, but an immediate fix would require stripping out the last two 0's from x_amount when calculating the MD5 hash so that the computed md5 hash matches the x_MD5_Hash passed.
I just had to cancel a bunch of transactions from folk who had tried to put their orders through. This "little issue" is making me lose money!
Is there some kind of fix I can do on my zencart end to cope with the changes made by Authorize.net?
Sharni
Bookmarks