Hi all...I'm about to have to setup a payment gateway for my fathers store. He has chosen to go with the opencart's Authorize.Net(AIM) gateway. He has finished setting up the account with them and has a Login ID, and a Transaction Key.
I have a few questions before I attempt to go further.
1. MD5 Hash: What do I put here?
2. Transaction Server: Do I leave this on Live?
3. Transaction Mode: Do I leave this on Live?
4. Transaction Method: I would think I need to change this to Capture?
5. Order Status: I would think I need to change this to Complete?
My other question is, do I need to purchase a SSL certificate to go along with the Authorize.Net(AIM) gateway.
I looked online for a tutorial on this and could find nothing. Any help would be great!
Thanks everyone.
I have a few questions before I attempt to go further.
1. MD5 Hash: What do I put here?
2. Transaction Server: Do I leave this on Live?
3. Transaction Mode: Do I leave this on Live?
4. Transaction Method: I would think I need to change this to Capture?
5. Order Status: I would think I need to change this to Complete?
My other question is, do I need to purchase a SSL certificate to go along with the Authorize.Net(AIM) gateway.
I looked online for a tutorial on this and could find nothing. Any help would be great!
Thanks everyone.
1. It is optional, only if you have it set in your actual authorize.net account settings
2. Yes
3. Yes
4. Capture
5. Complete or whatever status you want the order to be in when payment is successful
Yes you need SSL for any payment gateway that is hosted and collects card data directly on your site
Q
2. Yes
3. Yes
4. Capture
5. Complete or whatever status you want the order to be in when payment is successful
Yes you need SSL for any payment gateway that is hosted and collects card data directly on your site
Q
Thanks for the fast response Q. Do you suggest buying the certificate though the web host provider or through Authorize.Net? The costs are just about the same.Qphoria wrote:
Yes you need SSL for any payment gateway that is hosted and collects card data directly on your site
Q
I recently purchased the Q add-on for Opencart but its generating an error - ERROR: (TESTMODE) The merchant login ID or password is invalid or the account is inactive. I am using the Authorize.net Sandbox to generate the API Login Id and Transaction Key on OPen Cart v.1.4.9.4.
I could use some help to understand what needs to be modified in order to get this to work properly. Thank you.
I could use some help to understand what needs to be modified in order to get this to work properly. Thank you.
Hi, guys,
I am getting a consistent "This transaction cannot be accepted." error when I try to check out using the Authorize.net payment module. I purchased the Q product for authorize.net and it also did not work, so I went back to the original module to see if I can't get it to work again. Here is what I have done to troubleshoot:
I have enabled SSL on my host and in my OpenCart. I checked my Authorize.net account against my OpenCart, and my API Login ID, Transaction Key and MD5 hash match between authorize.net and OpenCart. I checked my host against my OpenCart timezones, and my OpenCart is set to Central/Daylight Savings Time and my host is located in Texas, so this is correctly configured as well. I have set up an OpenCart GeoZone to USA, with a Description of USA, and a Zone of All Zones.
I tested with Authorize.net on the phone, and they tell me my tests are not even hitting their server, so the problem is on my end. Next steps, please?
Thanks,
EdS
I am getting a consistent "This transaction cannot be accepted." error when I try to check out using the Authorize.net payment module. I purchased the Q product for authorize.net and it also did not work, so I went back to the original module to see if I can't get it to work again. Here is what I have done to troubleshoot:
I have enabled SSL on my host and in my OpenCart. I checked my Authorize.net account against my OpenCart, and my API Login ID, Transaction Key and MD5 hash match between authorize.net and OpenCart. I checked my host against my OpenCart timezones, and my OpenCart is set to Central/Daylight Savings Time and my host is located in Texas, so this is correctly configured as well. I have set up an OpenCart GeoZone to USA, with a Description of USA, and a Zone of All Zones.
I tested with Authorize.net on the phone, and they tell me my tests are not even hitting their server, so the problem is on my end. Next steps, please?
Thanks,
EdS
Hey guys/gals,
I just got off the phone with authorize.net- we got it to work. If you have an existing authorize.net API login ID and Transaction Key, you MUST create a new transaction key if you are migrating your shopping cart to a new server.
Would it have value for me to document what I have learned about troubleshooting and making authorize.net (AIM) work and posting it somewhere on the community forum?
Thanks,
EdS
I just got off the phone with authorize.net- we got it to work. If you have an existing authorize.net API login ID and Transaction Key, you MUST create a new transaction key if you are migrating your shopping cart to a new server.
Would it have value for me to document what I have learned about troubleshooting and making authorize.net (AIM) work and posting it somewhere on the community forum?
Thanks,
EdS
Thought I would add a more accurate solution here for the error, "(TESTMODE) The merchant login ID or password is invalid or the account is inactive." when using Authorize.net AIM gateway.
Assuming you have all the right details entered not all accounts have privileges to the test url so you have to use the normal secure subdomain and set the parameter for a test request to true.
A quick and dirty fix is
In file catalog/controller/payment/authorizenet_aim.php
find:
change to:
Assuming you have all the right details entered not all accounts have privileges to the test url so you have to use the normal secure subdomain and set the parameter for a test request to true.
A quick and dirty fix is
In file catalog/controller/payment/authorizenet_aim.php
find:
Code: Select all
$url = 'https://test.authorize.net/gateway/transact.dll';
Code: Select all
$url = 'https://secure.authorize.net/gateway/transact.dll';
You also have to sign up for a separate account on the sandbox server which is completely separate from your regular account.
https://www.lotnllc.com is your one stop shop for all your computer needs!
We are using Authorize.Net on OpenCart Version 1.5.1.3.
Registered customers are receiving a "Transaction Invalid" error when trying to submit their payment info. Unregistered users are able to submit their payment without error. We have entered a new Login ID and Transaction Key for the module, without resolve to this issue. Please advise.
Registered customers are receiving a "Transaction Invalid" error when trying to submit their payment info. Unregistered users are able to submit their payment without error. We have entered a new Login ID and Transaction Key for the module, without resolve to this issue. Please advise.
GoDaddy... $25Smokinoakum wrote:Thanks for the fast response Q. Do you suggest buying the certificate though the web host provider or through Authorize.Net? The costs are just about the same.Qphoria wrote:
Yes you need SSL for any payment gateway that is hosted and collects card data directly on your site
Q
The "test" server is for developer accounts only. Not for live accounts in test mode.cmohunter wrote:I recently purchased the Q add-on for Opencart but its generating an error - ERROR: (TESTMODE) The merchant login ID or password is invalid or the account is inactive. I am using the Authorize.net Sandbox to generate the API Login Id and Transaction Key on OPen Cart v.1.4.9.4.
I could use some help to understand what needs to be modified in order to get this to work properly. Thank you.
Using a phrase will work, but that isn't the REAL problem.
The root of the problem is this:
1.) Grab a hash from any site like http://www.adamek.biz/md5-generator.php , an MD5 hash is always 32 characters
2.) Enter the hash into Authorize.net's md5 hash and compare that to the hash you created. You'll notice that on Authorize.net's MD5 hash the field length is limited to 20 characters but the md5 hash field in opencart is not. This is the causing invalid hash collisions.
Solution: Create your hash from a password or for example i_love_lucy.
i_love_lucy will hash into bcd91b9012a23f973cd8baca7eeeb5de but only 20 of those 32 characters will be allowed into the authorize.net md5 hash field.
So in conclusion the hash that needs to be put into opencart auth.net aim is bcd91b9012a23f973cd8
Do not comment out the hash checking code as this will more than likely compromise your shops security.
Ultimately, the true fix for the authorize.net aim module would be to limit the md5 hash field to 20 characters so that it matches the hash entered in to authorize.net
I figured this out while pooping and thinking. I win.
Opencart 1.5.6.4
The root of the problem is this:
1.) Grab a hash from any site like http://www.adamek.biz/md5-generator.php , an MD5 hash is always 32 characters
2.) Enter the hash into Authorize.net's md5 hash and compare that to the hash you created. You'll notice that on Authorize.net's MD5 hash the field length is limited to 20 characters but the md5 hash field in opencart is not. This is the causing invalid hash collisions.
Solution: Create your hash from a password or for example i_love_lucy.
i_love_lucy will hash into bcd91b9012a23f973cd8baca7eeeb5de but only 20 of those 32 characters will be allowed into the authorize.net md5 hash field.
So in conclusion the hash that needs to be put into opencart auth.net aim is bcd91b9012a23f973cd8
Do not comment out the hash checking code as this will more than likely compromise your shops security.
Ultimately, the true fix for the authorize.net aim module would be to limit the md5 hash field to 20 characters so that it matches the hash entered in to authorize.net
I figured this out while pooping and thinking. I win.
Opencart 1.5.6.4
ok so looking at that error here:FAISALBTT wrote:Anyone knows how to solve this errors? "Country must be a valid three-character value if specified"
https://wordpress.org/support/topic/error-664
It seems that if Authorize.net uses "EVOSnap" as the processor, they require a 3-letter country instead of the normal full country name. So you have 2 options
1. Ask Auth.net to change you to another processor
2. Change the opencart code as follows:
a. EDIT: catalog/controller/payment/authorizenet_aim.php
b. FIND (TWICE):
Code: Select all
$order_info['payment_country']
Code: Select all
$order_info['payment_iso_code_3']
Code: Select all
$order_info['shipping_country']
Code: Select all
$order_info['shipping_iso_code_3']
I already have authorize.net AIM on my OpenCart store 3.0.2.0 and it works fine. I want to add authorize.net as a payment gateway for a new Ecwid/Facebook store I am opening. The Ecwid interface requires me to enter a Signature Key and authorize.net in turns requires me to generate a new Signature key to be able to do that. Generating a new key will disable any old keys. That means, if OpenCart requires a Signature Key, the gateway will no longer function on my OpenCart store. I cannot find a Signature Key field in my Authorize.net AIM edit page on the dashboard. Does this mean that OpenCart doesn't require a Signature key and that I'm safe in generating a new one?
I asked for advice from authorize.net tech support and they told me the following:
20:46:56 UTC Brandon : There are 3 main possibilities:
1. Your existing store doesn't use it, so it will ignore it when changed, so the change will have no effect
2. Your existing store doesn't use it, so when it's received the store will not know how to handle it, producing errors
3. Your existing store uses it, so the change will cause errors until the store is updated with the new Key.
20:47:04 UTC Willis Domingo : In other words, if I generate a new Signature key, then the old one will be disabled and processing will not work? Is that right? So I need to have the developer of my existing store on hand and ready to reconfigure before I add authorize.net to the new Facebook store. Is that right?
20:47:40 UTC Brandon : Generating a new Signature Key will disable the previous Signature Key, yes.
20:46:56 UTC Brandon : There are 3 main possibilities:
1. Your existing store doesn't use it, so it will ignore it when changed, so the change will have no effect
2. Your existing store doesn't use it, so when it's received the store will not know how to handle it, producing errors
3. Your existing store uses it, so the change will cause errors until the store is updated with the new Key.
20:47:04 UTC Willis Domingo : In other words, if I generate a new Signature key, then the old one will be disabled and processing will not work? Is that right? So I need to have the developer of my existing store on hand and ready to reconfigure before I add authorize.net to the new Facebook store. Is that right?
20:47:40 UTC Brandon : Generating a new Signature Key will disable the previous Signature Key, yes.
Who is online
Users browsing this forum: No registered users and 95 guests