Guest Posted June 1, 2003 Posted June 1, 2003 Response Reason code comes back with 103, Fingerprint, transaction key or password is required for this transaction. Using Ian's Loaded 5 Authorize.net, Wells Fargo SecureSource version 3.1 SIM method Transactions in test mode in osC and Authorizenet Used Sluggis echo and SIM 99 routine to troubleshoot, all fields transmitting ok. Any ideas why Authorize.net doesn't recognize fingerprint/transaction? Have I provided enough info to enable anyone to give an opinion?
Guest Posted June 1, 2003 Posted June 1, 2003 have you spoken to a rep at authnet and have them watch or perform a sample transaction to see if they can spot what the problem is? usually the support people at authnet are very good at doing this 8)
Guest Posted June 1, 2003 Posted June 1, 2003 Didn't know that was a possibility. (Did spend quite a bit of time on phone with AN. The guy I got was very unfriendly, unhelpful, and condescending...claimed problem is with shopping cart.)
Guest Posted June 1, 2003 Posted June 1, 2003 it is entirely possible that the problem is in the payment mod, but whenever i have not been able to debug something from my end, i have called them and they have setup a user account and done a transaction and watched the process and 9 out of 10 times they have caught something going on that shouldnt
Guest Posted June 2, 2003 Posted June 2, 2003 Since authorize.net support was closed, I did some further tinkering. Now have error 99 (server-generated fingerprint does not match merchant supplied fingerprint in x_FP_Hash field), which I think is probably closer to the real problem. I hardcoded actual login ID and transaction keys into the TABLE CONFIGURATION fields towards the end of catalog/includes/modules/payment/authorizenet.php, and ftp'd that file to the server. (I had also added the code snippet somebody posted that would help show the reply reason codes...very useful, by the way.) Then in the Admin panel I updated login ID and transaction key to match the hardcoded values. Then submitted an order in shopping cart, which failed with error 99. A look at database with phpmyadmin shows downlevel login ID and transaction keys. In other words, Admin panel didn't seem to update the database. Could having different values in the database vs. the hardcoded values in the /authorizenet.php module be the problem? Why didn't Admin panel update the database?
Guest Posted June 2, 2003 Posted June 2, 2003 i would have to install the mod to take a look and see how it is writing info to the db but at least you are narrowing down the search the hard coded values should over ride the db stored values unless it is still reading values from the db
Guest Posted June 2, 2003 Posted June 2, 2003 Are you aware of any other modules where login ID and especially Transaction Key actually appear written in the code?
Guest Posted June 2, 2003 Posted June 2, 2003 no i am not i know the authnet mod that i did has multi files and one contains the account info, but since it is using the adc connect method there is no transaction key/finger print required
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.