All,
I am attempting to get the included AIM module to work.
1.) Or is that simply impossible and I have to go to the "new" AIM module.
I have all the settings in osCOmmerce admin correct, except for one thread that said to set the admin settings for
2.) Transaction server and transaction mode to "live". That does not seem right to me. Any input?
3.) Also, have changed
switch (MODULE_PAYMENT_AUTHORIZENET_CC_AIM_TRANSACTION_SERVER) {
case 'Live':
$gateway_url = 'https://secure.authorize.net/gateway/transact.dll';
break;
default:
$gateway_url = 'https://test.authorize.net/gateway/transact.dll';
break;
}
in authorizenet_cc_aim.php
so that both are "test.authorize.net" and have also tried setting both to "secure.authorize.net"
any input on that one?
Authorize.net says it should be test.authorize.net while in test mode but again another thread said change over to "secure.authorize.net"
4.) Lunarpages gave me 3 paths for the cURL path and said.....
"The pathway you use would depend upon the path that the gateway processor software requires. Please refer to their documentation for further clarification on this issue."
OK, except the only thing on A.net about cURL is in reference to using their module with a hosting company that uses proxy servers. Lunarpages does not use proxy servers.
Lunarpages says the cURL is compiled in PHP.
5.) I have not entered a MD5 Hash number because it is optional, plus the script apparently in authorizenet_cc_aim.php apparently generates one.
At this point the advice on all the different settings makes for so many computations my head is swimming. Lunarpages has been responsive, authorize.net has not been.
This thread http://forums.oscommerce.com/index.php?showtopic=293398 has been very helpful, bit I am looking for any insight before I dive into the array of suggestions.
Any advice specific or general would be appreciated.
Cordially,
Hank
http://forums.oscommerce.com/index.php?showtopic=293398
Latest News: (loading..)
osCommerce default AIM Module
Started by hwkd, Sep 10 2008, 15:47
4 replies to this topic
#1
Posted 10 September 2008, 15:47
#2
Posted 11 September 2008, 17:52
hwkd, on Sep 10 2008, 11:47 AM, said:
All,
I am attempting to get the included AIM module to work.
1.) Or is that simply impossible and I have to go to the "new" AIM module.
I have all the settings in osCOmmerce admin correct, except for one thread that said to set the admin settings for
2.) Transaction server and transaction mode to "live". That does not seem right to me. Any input?
3.) Also, have changed
switch (MODULE_PAYMENT_AUTHORIZENET_CC_AIM_TRANSACTION_SERVER) {
case 'Live':
$gateway_url = 'https://secure.authorize.net/gateway/transact.dll';
break;
default:
$gateway_url = 'https://test.authorize.net/gateway/transact.dll';
break;
}
in authorizenet_cc_aim.php
so that both are "test.authorize.net" and have also tried setting both to "secure.authorize.net"
any input on that one?
Authorize.net says it should be test.authorize.net while in test mode but again another thread said change over to "secure.authorize.net"
4.) Lunarpages gave me 3 paths for the cURL path and said.....
"The pathway you use would depend upon the path that the gateway processor software requires. Please refer to their documentation for further clarification on this issue."
OK, except the only thing on A.net about cURL is in reference to using their module with a hosting company that uses proxy servers. Lunarpages does not use proxy servers.
Lunarpages says the cURL is compiled in PHP.
5.) I have not entered a MD5 Hash number because it is optional, plus the script apparently in authorizenet_cc_aim.php apparently generates one.
At this point the advice on all the different settings makes for so many computations my head is swimming. Lunarpages has been responsive, authorize.net has not been.
This thread http://forums.oscommerce.com/index.php?showtopic=293398 has been very helpful, bit I am looking for any insight before I dive into the array of suggestions.
Any advice specific or general would be appreciated.
Cordially,
Hank
http://forums.oscommerce.com/index.php?showtopic=293398
I am attempting to get the included AIM module to work.
1.) Or is that simply impossible and I have to go to the "new" AIM module.
I have all the settings in osCOmmerce admin correct, except for one thread that said to set the admin settings for
2.) Transaction server and transaction mode to "live". That does not seem right to me. Any input?
3.) Also, have changed
switch (MODULE_PAYMENT_AUTHORIZENET_CC_AIM_TRANSACTION_SERVER) {
case 'Live':
$gateway_url = 'https://secure.authorize.net/gateway/transact.dll';
break;
default:
$gateway_url = 'https://test.authorize.net/gateway/transact.dll';
break;
}
in authorizenet_cc_aim.php
so that both are "test.authorize.net" and have also tried setting both to "secure.authorize.net"
any input on that one?
Authorize.net says it should be test.authorize.net while in test mode but again another thread said change over to "secure.authorize.net"
4.) Lunarpages gave me 3 paths for the cURL path and said.....
"The pathway you use would depend upon the path that the gateway processor software requires. Please refer to their documentation for further clarification on this issue."
OK, except the only thing on A.net about cURL is in reference to using their module with a hosting company that uses proxy servers. Lunarpages does not use proxy servers.
Lunarpages says the cURL is compiled in PHP.
5.) I have not entered a MD5 Hash number because it is optional, plus the script apparently in authorizenet_cc_aim.php apparently generates one.
At this point the advice on all the different settings makes for so many computations my head is swimming. Lunarpages has been responsive, authorize.net has not been.
This thread http://forums.oscommerce.com/index.php?showtopic=293398 has been very helpful, bit I am looking for any insight before I dive into the array of suggestions.
Any advice specific or general would be appreciated.
Cordially,
Hank
http://forums.oscommerce.com/index.php?showtopic=293398
Using
osCommerce Online Merchant v2.2 RC2a
#3
Posted 12 September 2008, 15:12
This worked for per Joshua M in this forum:
So I found that even though you are testing, you need to make the "Authorize.net Credit Card AIM" Live. Turns out that in the default settings for osc's authorizenet, "Test" means that you are submitting requests to https://test.authorize.net/gateway/transact.dll. This is the wrong gateway to send it to unless your API login starts with "cpdev" or "cnpdev". The server will return error 13 message (basically wrong username or password). The correct test server if your API login doesn't start with "cpdev" or "cnpdev" is the same as the live server: https://secure.authorize.net/gateway/transact.dll
For testing, you need to make sure that Authorize.net is in test mode.
To do this, log in to Administration.
In the left navigation click on Modules then Payment
In the center list, click on Authorize.net Credit Card AIM
On the right, you will see the settings. Set them as follows:
--------------------------------------------------------------------------------------------------------------------------------------------
Enable Authorize.net Credit Card AIM
Do you want to accept Authorize.net Credit Card AIM payments?
True *
False
Login ID xxxxxxxxxx
The login ID used for the Authorize.net service
Transaction Key xxxxxxxxxxx
Transaction key used for encrypting data
MD5 Hash xxxxxxxxxxxxxxxxxxxxxxx (same as in authorize.net settings)
The MD5 hash value to verify transactions with
Transaction Server
Perform transactions on the live or test server. The test server should only be used by developers with Authorize.net test accounts.
Live *
Test
Transaction Mode
Transaction mode used for processing orders
Live *
Test
Transaction Method
The processing method to use for each transaction.
Authorization
Capture *
Payment Zone (personal configuration)
If a zone is selected, only enable this payment method for that zone.
Set Order Status (personal configuration)
Set the status of orders made with this payment module to this value
Sort order of display. **Not necessary**(0=first in the list 99=last in the list)
Sort order of display. Lowest is displayed first.
cURL Program Location
The location to the cURL program application.
So I found that even though you are testing, you need to make the "Authorize.net Credit Card AIM" Live. Turns out that in the default settings for osc's authorizenet, "Test" means that you are submitting requests to https://test.authorize.net/gateway/transact.dll. This is the wrong gateway to send it to unless your API login starts with "cpdev" or "cnpdev". The server will return error 13 message (basically wrong username or password). The correct test server if your API login doesn't start with "cpdev" or "cnpdev" is the same as the live server: https://secure.authorize.net/gateway/transact.dll
For testing, you need to make sure that Authorize.net is in test mode.
To do this, log in to Administration.
In the left navigation click on Modules then Payment
In the center list, click on Authorize.net Credit Card AIM
On the right, you will see the settings. Set them as follows:
--------------------------------------------------------------------------------------------------------------------------------------------
Enable Authorize.net Credit Card AIM
Do you want to accept Authorize.net Credit Card AIM payments?
True *
False
Login ID xxxxxxxxxx
The login ID used for the Authorize.net service
Transaction Key xxxxxxxxxxx
Transaction key used for encrypting data
MD5 Hash xxxxxxxxxxxxxxxxxxxxxxx (same as in authorize.net settings)
The MD5 hash value to verify transactions with
Transaction Server
Perform transactions on the live or test server. The test server should only be used by developers with Authorize.net test accounts.
Live *
Test
Transaction Mode
Transaction mode used for processing orders
Live *
Test
Transaction Method
The processing method to use for each transaction.
Authorization
Capture *
Payment Zone (personal configuration)
If a zone is selected, only enable this payment method for that zone.
Set Order Status (personal configuration)
Set the status of orders made with this payment module to this value
Sort order of display. **Not necessary**(0=first in the list 99=last in the list)
Sort order of display. Lowest is displayed first.
cURL Program Location
The location to the cURL program application.
#4
Posted 19 September 2008, 00:14
I've spent the last five hours or so trying to get authorizenet_cc_aim working. I'm getting cranky and probably need to take a nap before I start ranting and offend someone. 
Is there any decisive answer to how/if to get it working? I'd dearly love to discover one when I wake up...
TIA for any insights!
Is there any decisive answer to how/if to get it working? I'd dearly love to discover one when I wake up...
TIA for any insights!
hwkd, on Sep 12 2008, 08:12 AM, said:
This worked for per Joshua M in this forum:
[snip]
[snip]
#5
Posted 19 September 2008, 09:51
Appears to be resolved and closed [I can only hope]. I'm going to go smash my head in with a rock now... 
Resolution: http://forums.oscommerce.com/index.php?act...amp;pid=1309060
Resolution: http://forums.oscommerce.com/index.php?act...amp;pid=1309060
adrenalynn, on Sep 18 2008, 05:14 PM, said:
I've spent the last five hours or so trying to get authorizenet_cc_aim working. I'm getting cranky and probably need to take a nap before I start ranting and offend someone. 
Is there any decisive answer to how/if to get it working? I'd dearly love to discover one when I wake up...
TIA for any insights!
Is there any decisive answer to how/if to get it working? I'd dearly love to discover one when I wake up...
TIA for any insights!














