Working with Authorize.net

[aapk]

Has anyone out there worked with Authorize.net to process credit cards transactions and if so, how do you configure it on Miva? I have tried configuring it and it doesn't work and Authorize.net says its a Miva issue.

Any help would be soo appreciated.
Thanks.

[DesignExtend-MSI]

What is the problem you're having. Did you plug your info into the module's admin?

If it's an error during checkout, it may be that the host hasn't provided your site with the proper Commerce Library, so you should check with your host on that issue.

If it's something else, please advise.

[dotCOM_host]

aapk,

Are you getting any error messages during checkout, and of so - can you copy and paste an example so we can see what the problem might be? If you are not getting any server-side errors, did you look through the documentation or help screens to make sure you have all your settings entered correctly? You may want to check with your host as well, if they offer MIVA Merchant support, to get this set up quickly for you.

If you do get an error during checkout - let us know what it is, there are several simple misconfigurations that are very easy to fix if we know what sort of problem you are running into...

[aapk]

This is the error message I am receiving ...(after using their test mastercard number)
Unable to authorize payment: Error connecting to 'https://secure.authorize.net/gateway/transact.dll': Error establishing SSL connection: certificate verify failed

In the module on Miva (under Authorize.net on payment module) I have verified the Authorize URL in their documention. My id and password are set.Charge method set for Oline, Test mode checked and payment methods set for MC and Visa (what we signed up for).

Now, I am used to using Paradata .. so easy, get transcation ID, enter it in the module and good to go. And no where is there a place to put a transaction key under the module for Authorize.net.

So, not sure what I am missing here in the set up.

Again, thank you for any help you can give me ... answers so far have helped.

[Vic - WolfPaw Computers]

What version of the AuthorizeNet payment module are you using?

What version of the AuthorizeNet Commerce Library does your host have installed?

What version of the Miva Engine are you on?

Its possible there is either a mismatch between the commerce library and the engine - or an incorrect version of OpenSSL and or SSL configuration.

[DesignExtend-MSI]

Its possible there is either a mismatch between the commerce library and the engine - or an incorrect version of OpenSSL and or SSL configuration.

In any of these cases, this is something that should be addressed by your host.

[aapk]

What version of the AuthorizeNet payment module are you using? I am embarrsed to say, I don't know, any links I have to their stuff doesn't give me indication of version.

What version of the AuthorizeNet Commerce Library does your host have installed? Not sure either .. their email support says it's a miva problem (which I don't believe).

What version of the Miva Engine are you on? that I can answer - version 4.

Its possible there is either a mismatch between the commerce library and the engine - or an incorrect version of OpenSSL and or SSL configuration. no clue.

[Vic - WolfPaw Computers]

What version of the AuthorizeNet payment module are you using? I am embarrsed to say, I don't know, any links I have to their stuff doesn't give me indication of version.


In your Miva Merchant admin, click on the drop down for Modules. Find the AuthorizeNet Payment module and click on it. The version number will be on the right.

What version of the AuthorizeNet Commerce Library does your host have installed? Not sure either .. their email support says it's a miva problem (which I don't believe).


You would likely have to ask your host on this one.

What version of the Miva Engine are you on? that I can answer - version 4.


When you first login to your admin, the upper left corner of the right pane will show you the Miva Merchant version and Miva Engine version. The engine version is what I was asking about. There are several minor versions that make a big difference, for instance, 4.07 is a lot different than 4.1400.

Its possible there is either a mismatch between the commerce library and the engine - or an incorrect version of OpenSSL and or SSL configuration. no clue.

As Pamela said, this would be something handled by your host.

AuthorizeNet Support is right - sort of. Its not a MIVA problem per se, but definately a host cofiguration issue in most cases.

[aapk]

You guys are the best!!!!!!

The Authorize.net version is 3.0

Miva version 4.13

Hummm ok .. my hosting firm is NetNation .. got Miva through them .. so you are saying I need to contect Netnation?

Again thanks for your help .. hate feeling this lost!

[aapk]

PS .. sorry You guys and gals are the best!

[Vic - WolfPaw Computers]

You guys are the best!!!!!!

The Authorize.net version is 3.0

Miva version 4.13

Hummm ok .. my hosting firm is NetNation .. got Miva through them .. so you are saying I need to contect Netnation?

Again thanks for your help .. hate feeling this lost!

Thats the AuthNet version, not the module version. Its likely 4.13. This should be updated though...should be using Authnet 3.1, Module version 4.131.

You may have to contact Miva support as I no longer see that patch available.

Keep in mind also, version 4.13 and earlier are no longer supported by MIVA.

I'd strongly recommend you upgrade for 4.24.

[Jimmy Cooper]

Unable to authorize payment: Error connecting to 'https://secure.authorize.net/gateway/transact.dll': Error establishing SSL connection: certificate verify failed

Whenever you see that "certificate verify failed" error, it means that the 'certs' directory for MIVA Empresa is not configured correctly. That's the only thing that will bring that specific message up during checkout.

So, what you will want to tell your Web host is that they need to check the MIVA Empresa configuration file on the server and make sure that they have specified the 'certs' directory correctly.

To go a step further, you could refer them to this installation guide: http://smallbusiness.miva.com/support/docs/empresa/v4_INSTALL_UNIX-HTML/InstallVM_UNIX.html. While this is for v4 of MIVA Empresa (you're running under v3), the configuration of the 'certs' directory is the same.

[ILoveHostasaurus]

Whenever you see that "certificate verify failed" error, it means that the 'certs' directory for MIVA Empresa is not configured correctly. That's the only thing that will bring that specific message up during checkout.

So, what you will want to tell your Web host is that they need to check the MIVA Empresa configuration file on the server and make sure that they have specified the 'certs' directory correctly.


That is not always the case. I've found that error occurs with some newer certificates that use intermediate CA certificates that Miva has not included in the certs distribution. For example, Empresa cannot make remote https connections to sites using new Comodo certificates signed by AddTrust for this reason. I've sent in the appropriate certifcate that needs to be added to the distribution.

[Vic - WolfPaw Computers]

We've seen this as well. Often with Comodo and Starfield (GoDaddy) certs.

[Jimmy Cooper]

Thanks for the info, David and Vic. I'll make sure Development has a note about that.