next »

[stanman1]

I am trying to type the Authorize.Net Transaction Key into the payment module configuration of VirtueMart and it won't "take." The Current Transaction Key shows "(empty!)" and when I type my valid Joomla password into the field that asks for it the "Show/Change the Password/Transaction Key" form just reloads.

I know I am using the correct password and the form seems to be malfunctioning.

Can anybody help me?

[integris1]

Did you find the issue? I have the same problem with setting up eCheck
I was able to set up Credit Card properly however.
Joomla 1.1.59 VM 1.1.5

[Stonedfury]

I cant get the credit card to work either. Joomla 1.5.20 and VM 1.1.5

[integris1]

Searching the forums there seems to be quite a few people having a similar issue. Auth.net CC and echeck seems like a pretty basic feature to have an issue with.. I'm rather disappointed with this as I'm loosing a client over it.

[Stonedfury]

I have actually gotten this solved. It's pretty easy.

The password is your JOOMLA password.. I swear I messed that up a few times.

#1 Make sure you have an merchant account with Authorize.net

#2 Authorize.net API Login ID  (not your login name for the website)
This is your Authorize.Net API Login ID

Authorize.net Transaction Key    ---------     Ive done this a few times. It is fairly easy and again they will walk you through this. Give them a call. makes it easier than searching.

#3 Test runs dont work. For those that they do.. LUCKY.. Just set it up to go live.

#4 Don't turn on more than ONE credit card for authorize.net. You can set them up with different price groups. Shopper, Wholesale, Distributor, etc., but then turn them off. Do not enable them. The one that is enabled will use the groups from the others. (NO idea why it works like that)

#4 Make sure your host (should have mentioned sooner) has socks 443 open. As it is the default. Technically you can change this but eh. easier to comply. Most cpanel if not all are already set. cURL is not required per authorize.net.

Keep in mind. You can NOT have multiple credit card (authorize.net) processors enabled. Read above.

Hit me up if that doesnt help. Took a while but in the end it was plbcam (problem lies between chair and monitor)

[chasedoggy]

OK - I'm still having the same issue. I updated to 1.1.5 with hopes that this would be solved but no go. I'm using Pivotal payment gateway and I've done what is necessary to connect with them instead of directly to Authorize - but that isn't the issue.

The issue is that when I type my JOOMLA! password or any other password on the "Show/Change the Password/Transaction Key" page it just loops back to the enter your password page.

Virtuemart -> please give me a sql statement or something that I can use to enter my Transaction Key. Is there a hotfix or a hack that I can do to fix this?

Thanks -

[BanquetTables.pro]

Stonedfury is correct

chasedoggy, sounds like you are not entering the right password for the superadmin

[chasedoggy]

Thank you for the quick response. I really appreciate it.

I've tried this with the SuperUser and it's not doing me any good. Could it be something else? I definitely am using the Super User. I have multiple Super User accounts but I am using the original super user account that was created when Joomla! was installed.

Does anyone know another way to upload the transaction key? Can I put it directly in the db?

[BanquetTables.pro]

I dont know of a way. I am pretty sure its encoded

[chasedoggy]

Thanks - I will update this post when I figure it out.

[chasedoggy]

You guys were right. I modified the code to allow for email address as username and that created a situation where I was not able to update my transaction key. I used the following sql and everything went back to normal. This wasn't a bug in Virtuemart as I suspected, it was my fault.

update `jos_users` set `username` = `email`

Thanks for all your help!

[idgafra]

I couldn't get it to work in FireFox so I switched to Safari and it worked.

[nflmerch]

I couldn't get it to work in FireFox so I switched to Safari and it worked.

Same here, I couldn't get it to work in IE, but it works great in google Chrome