LIVE, now I am DEAD (sigh)
This is a discussion on Authorize.net Error within the Authorize.net forums, part of the Payment Modules category; LIVE, now I am DEAD (sigh)...
LIVE, now I am DEAD (sigh)
John and BH...
OK, I installed SSL and still nothing..
BH, what return strings? I forgot to mention...that that link you gave here on the threads...did nothing..
I have tried everything under the sun..
Authorize.net PAYMENT MODULE PROBLEMS - osCommerce Community Support Forums
Help?
PS...John, I have not tried your files again..
It has to be in FORM SETTINGS and response strings...some say leave it blank...some say fill it in.
It now takes money in Authnet in 2.0.4 as I backed out all but 2 check boxes in Authnet Form settings ...
But will not give me a "order" in the danged cart.
Thanks again...and getting closer?
RESOLVED !!
Autherize.net is working/processing but reads error! - osCommerce Community Support Forums
Man, so many different people on OSC had so many different problems..
Frigging MD5 HASH just removed..as you can't remove it from AuthNet side..
His above post...I did not do anything as far as setting FALSE for sessions.
Thanks to all for all help.. I am for sure going to get this into the WIKI so no one has to go thru this.
First, I need to get back to the coupon deal now.
Sorry all. I didn't mean to disappear, but I have not been able to get on oscmax.com for about 2 weeks. At first I thought the site was down, but now I'm not sure as I got it tonite through a proxy server. Were there any problems with the forum here? Did the site go down? It still seems buggy.
Anyway, I got AIM to work by changing settings in my Authorize merchant control panel. If you do not have all the settings right it won't work. It will get through but stop your cart from finishing the checkout process.
Go to Account > Virtual Terminal Settings.
Make sure the Field Name boxes are all checked in the View/Edit column, so that every option that is configured for osCMax's checkout is included. I have them all checked as it can't hurt anything and ensures it will work.
Under Business Settings, I set the Transaction Cut Off Time to 11:59 pm as well to allow orders late at nite. You may not want this, but I do on my site.
Under Security Settings, make sure Card Code Verification is turned on as it is included in osCMax.
Set the Daily Velocity high enough to allow transactions to process. I initially thought this was # of transactions daily per credit card, but it is for # of transactions from all cards per day. Very Important distinction as it will stop your checkout from finishing!
Apparently, if you're using MD5 Hash you just enter a word in there and not an encrypted password. I did that as well and it is working fine.
Do all these things and everything should work fine for you.
Thx for the reply !!....lol... That was not the issue for me...
Trick is to Xnay the MD5 hash for sure...just leave it blank...and works fine.
Thing is, once one is recorded the first time in AuthNet...you can not REMOVE it...so therefore, I was under the impression the cart needed it.
No, I have not noticed any site errors or downtime on the forums.
And in my end of VTS...All is working with these NOT CHECKED>
Currency
Recurring Billing Transaction
Card Code
Also, I have shipping blank...as I will be using a DL item. (I hope)
Jim
The MD5 is for the SIM module and isn't needed for the AIM because AIM connects using CURL SSL so it's already encrypted. Authorize.net has an online help manual that states that so I was a little puzzled why it is in the AIM module other than it's easier and faster to make them that way.
FYI, there is a 2nd version of the AIM module available on the main OSC contribution that has one line added to it so you can add this yourself.
Around 382 find this
add this after itPHP Code:curl_setopt($curl, CURLOPT_HEADER, 0);
PHP Code:curl_setopt($curl, CURLOPT_SSLVERSION, 3);
John
John and all...thx again for your help....
I am not going to touch a thing now in that...lol...just awaiting now to get get the issue with the Coupons resolved in the 2.0.x series.
Bug is reported, workaround given? Not sure if it is applicable to the series as it's RC3
Really should not have to attempt it, (I feel) as being the 'released' version...and any fixes...now going into a 2.1? Which is beta...
One feels that the simple fix in 2.0.4 and a simple re-zip of the package would eliminate things.
Thanks again to all...and if Authnet had a way to remove the MD5 entry...instead of just a CHANGE (it does not allow blank) after initial input..this would have been resolved a week ago+
Jim
all sounds good but is there a setting to accept the changes of an existing order and existing price before it is captured by authorize.net? or does everyone who use AIM have to run a 2nd order (reorder everything) all over again for the smallest changes on an existing order?
BH, I am a little confused as to what you are asking?
Are you speaking along the lines of once your customer places the order...that should they come back in and change it?
The only thing I can think of...would be to SET to "authorize only" and then you have to manually run it...and I guess along the lines of "wait and see" until they are done? (the customer)
Bookmarks