Jump to content

jwaskovich

Member
  • Posts

    4
  • Joined

  • Last visited

jwaskovich's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I am using a production account for authorize.net that is NOT in test mode. This is used by several other pages our company has to process credit cards and works fine. I will try the delimiter change and let you know. I am also trying a fresh clean install of CC6 on a new domain to see if it is the upgrade from 4 to 6 problem or authorize.net. Stay tuned... UPDATE: that change for making the delimiter yes and type as | (pipe) didn't do anything. I will update this response when I finish my testing on a fresh install. UPDATE 2: I tried on a new clean install and this did not work again. I will see what I can change on my authorize.net side to make this work. I have a suspicion that I need to upgrade the authorize.net version from 3.0 to 3.1 and explicitly enable the delimiter.
  2. are you running 3.1 or 3.0 in authorize.net? The only differences i have found are the card code settings are validated on 3.1 vs. 3.0
  3. I did, yes. However, I do not see those exact field names in our merchant area. I am posting a screenshot of the settings I see for where i think I need to change them. Keep in mind that the values listed there in the screenshot are what we had before and it was working in CC4. I tried changing the default separator to a | (pipe) and ran it again right with no success. We have 2 other parts to our company that heavily use this same merchant account so I can not go changing a lot of settings without potentially breaking those. We have hundreds of transactions run successfully through our own AIM implementation using this same merchant account which makes this puzzling. Does it matter if we are using 3.0 and not the latest 3.1 available to us? If I put it into test mode I do get that same screenshot you posted. The problem is when it is in "live" mode. Let me try again and post screenshot of that response. I have attached the test mode screenshot to this response as well.
  4. I am having a major issue here with using the Authorize.net plugin. I recently upgraded our install from a CC4 to the latest CC6 install. I followed the instructions listed on the web site for the upgrade and everything went off without a hitch. I then proceeded to reinstall any new plugins that we used in version 4 (All in One shipping and Authorize.net). Again, both installed just fine and I thought I was good to go. I configured authorize.net with the proper information (API key and Tran Key) and chose for the plugin to authorize and capture the transaction. I also chose AIM as the method of processing so that the customer stayed on the page. We have an SSL on this site as well in case the plugin requires it. The problem comes in when I try to run through some testing of the Authorize.net payment. When you enter in your shipping and billing information along with the credit card details and click 'Make Payment' the page will simply post and then basically reload itself. There isn't a response code/reason given at the top if it failed or even submitted for that matter. This process simply looks like it reposted to itself just like you were there for the first time. If anyone can help and is interested then I can set you up with a dummy order and you can put in a dummy credit card number and see. the typical visa one 4111.... is the one I use. I have even tried with a real credit card and got the same result; the page simply just didn't post to authorize.net. I would be happy at this point with getting a response back stating an bad credit card number, or anything that states it went to Authorize.net In regards to troubleshooting, I have looked over at Authorize.net to see if the transaction even attempted to post. Nothing in regards to even an attempted transaction has been recorded on Authorize.net's merchant area. I made sure that all of the read/receipts variations were listed under my account to allow this post to happen. I made sure that all the settings were exactly what we had before in CC4. I had the authorize.net plugin before on this older version of CC and it worked no problem with AIM support. I am sure I am leaving something out on my troubleshooting but I have tried several solutions to no avail. I have tried uninstalling the plugin and reinstalling it. I tried going down to version 1.1.0 instead of the 1.1.1 and had no success. I also have tried clearing my site cache in the maintenance section and that didn't do anything. If anyone has any input that would be greatly appreciated. I can answer any followup questions one might have as well on this. I apologize if I left something out of this post.
×
×
  • Create New...