Guest Posted September 20, 2008 Share Posted September 20, 2008 I was in the same place. I was logging the exchange and the Auth.net was giving a "transaction approved" response but OSC was failing it. When I gave it a bad number/date/etc. I was getting a "good" failure message instead of a generic failure. But on an approved transaction, OSC was giving the generic fail response. Near as I can tell, OSC was cranky that the message didn't contain the correct hash. The module decided it was fake because the signature hash was invalid - if that makes sense. It's worth looking into. If you put logging code in, look at the returned hash from Auth.net and compare it to what you have stored in the module configuration... Good luck! Just as an FYI - I didn't have to change any code on the stock module (with a fairly stock cart). , [Comma] delimited, " [double-quote] encapsulated - as/per the modules code. I haven't turned on AVS and CVC fraud check yet - probably tomorrow. We have about 800 more products to get into the catalog, and I still need to do some SEO work before we introduce it to Google and start the ad campaign. :blink: That's GREAT news for you! I would definitely get drunk if I was you. I'm still not getting mine to work. If I get a general error all the time, except when I put in a wrong CC number (where I get a CC declined error instead), I must be getting past the MD5 portion of the problem right? Meaning that this probably won't fix my problem? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.