992 replies to this topic

[ramel_l2]

There has been an error processing your credit card
Please try again and if problems persist, please try another payment method.

Im getting the above error when I go to check out. When I log into my a.net account the orders are the but have general error next to them. if I put in a credit card with only 8 digits I get the same error. Anybody know what the issue could be?

[Kris.Ong]

Arghhhh! Can somebody help me? The transactions are posting in Authorize.net. They are submitted and a day later they clear. Unfortunately, the OSCommerce template does not acknowledge credit card payment and I show nothing in the OSC Admin Panel of a confirmed order. I get the following error: "Your credit card could not be authorized for this reason. Please correct any information and try again or contact us for further assistance." I tried the fix from 10/14/08.

Checkout shipping page passes fine.
Checkout payment page passes fine.
Checkout confirmation pages does not pass and produces the above error.

I feel like its an issue with the cookies.

I do have shared ssl and believe I have configured it appropriately (https://secure.bluehost.com/~fantasu6). I do have cURL in PHP, I do have an account with Authorize.net, Direct response is delimited response "no", Default Field Separator "comma", Field Encapsulation Char "blank". Transaction Key must be working properly since transactions are posting. Transaction version is 3.1. Site is not in the "catalog" directory but in the main root. Padlocks/ ssl seem to be appearing in the right places (i.e. login page, checkout, and credit card pages, etc.). Nothing in Receipt / Relay URLs.

URL is: https://secure.bluehost.com/~fantasu6/checkout_payment.php
Domain Name: www.fantastictoyfigures.com

Configure files are:

define('HTTP_SERVER', 'http://www.fantastictoyfigures.com'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://secure.bluehost.com/~fantasu6'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'www.fantastictoyfigures.com');
define('HTTPS_COOKIE_DOMAIN', 'www.fantastictoyfigures.com');
define('HTTP_COOKIE_PATH', '/~fantasu6/');
define('HTTPS_COOKIE_PATH', 'secure.bluehost.com/~fantasu6');
define('DIR_WS_HTTP_CATALOG', '/~fantasu6/../');
define('DIR_WS_HTTPS_CATALOG', '/');


Do you know why I'm not reaching the checkout success page? I keep getting sent back to the checkout payment page with the above error? I hope it's just a simple cookies configuration problem. Please help, I've almost ripped out all my hair.

Thanks,
Kris

[baddog]

Kris.Ong, on Nov 6 2008, 06:15 AM, said:

... Nothing in Receipt / Relay URLs.

Try setting Receipt / Relay URLs to https://'secure.bluehost.com/~fantasu6'/enter_correct_path/checkout_process.php

[Kris.Ong]

nope =( and it seems like confirming takes a long time to process.

[IcedDante]

I noticed that this contribution was originally created because AIM was not available in the suite of Authorize.net payment modules. However, it seems that now AIM is available as a standard feature with OSCommerce so I was wondering what benefits this module offers for AIM integration over the OOTB version. I am asking because I have been unable to get credit card processing to work using the default module and I am not sure why. I was wondering if this contribution offers different functionality or fixes known issues that may help us resolve the problem.

Randeep

[baddog]

IcedDante, on Nov 9 2008, 02:52 AM, said:

I noticed that this contribution was originally created because AIM was not available in the suite of Authorize.net payment modules. However, it seems that now AIM is available as a standard feature with OSCommerce so I was wondering what benefits this module offers for AIM integration over the OOTB version. I am asking because I have been unable to get credit card processing to work using the default module and I am not sure why. I was wondering if this contribution offers different functionality or fixes known issues that may help us resolve the problem.

Randeep

I never took the time to try to figure out how to fix the stock module (which did not work for me) simply because I installed this module and it worked. It would be nice if the developers would address this issue.

[rs2k]

IcedDante, on Nov 9 2008, 12:52 AM, said:

I noticed that this contribution was originally created because AIM was not available in the suite of Authorize.net payment modules. However, it seems that now AIM is available as a standard feature with OSCommerce so I was wondering what benefits this module offers for AIM integration over the OOTB version. I am asking because I have been unable to get credit card processing to work using the default module and I am not sure why. I was wondering if this contribution offers different functionality or fixes known issues that may help us resolve the problem.

Randeep

I could not get the stock module to work either. This module offers CCV2. I don't know if the stock module offers that or not.

Edited by rs2k, 09 November 2008, 15:16.

[Kris.Ong]

spencermjax, on Sep 21 2008, 06:35 PM, said:

Well...Well...Well...I actuall tried something that I should have tried first. The field "CURL Proxy URL" in the admin was automaticlly filled in when installed. I just edleted the contents of that fiels and BOOM! It's working!!!!!!!

Thank you to everyone who got involved in constantly making this module better. And thank you Rhea for starting it all. The module works and I'm on my way.

[cjpopp]

I just found that my web host wil not enable CURL

Any ideas on what to do now? All my client needs is to be able to capture and authorize with Authorize.net

Thanks,
Chris

[IcedDante]

Honestly... get a new host.

curl is a requirement for using this module, although I do believe it has a configuration set up for using a proxy CURL. But I do think you would be better off using a host that supports OSCommerce and basic ecommerce necessities like curl.

cjpopp, on Nov 12 2008, 03:37 PM, said:

I just found that my web host wil not enable CURL

Any ideas on what to do now? All my client needs is to be able to capture and authorize with Authorize.net

Thanks,
Chris

[IcedDante]

baddog, on Nov 9 2008, 04:37 AM, said:

I never took the time to try to figure out how to fix the stock module (which did not work for me) simply because I installed this module and it worked. It would be nice if the developers would address this issue.

I had the same experience baddog. I think it is ridiculous that authorize.net, which I believe is a pretty common service, does not work OOTB, but I am very grateful to the people who provided this module which works fantastically. This really needs to be merged into the core since the OOTB errors delayed our launch date significantly.

And yes, the stock module doesn't support CVV2 and this one does. All the more reason to merge.

Good job guys and thanks for the info!

[IcedDante]

Has anyone else had a problem using the CVV Help link? I always get a 404 Error and I think the problem is related to a slash that prepends the Help link. It's located in the languages/english/modules/payment/authorizenet_aim.php file and I don't think a javascript link really belongs here. I posted a release that eliminates this extra slash but I think there is a better way.

Any ideas?

[mrbones]

I have been using this module for a year with no trouble. But now I get the same error even with the latest update. How do we fix this?

ramel_l2, on Nov 3 2008, 05:28 PM, said:

There has been an error processing your credit card
Please try again and if problems persist, please try another payment method.

Im getting the above error when I go to check out. When I log into my a.net account the orders are the but have general error next to them. if I put in a credit card with only 8 digits I get the same error. Anybody know what the issue could be?

Edited by mrbones, 21 November 2008, 15:40.

[mrbones]

Is there any Authorize.net AIM module that works? I downloaded and tried another one and it didn't work either?

Anybody?

mrbones, on Nov 21 2008, 10:31 AM, said:

I have been using this module for a year with no trouble. But now I get the same error even with the latest update. How do we fix this?

[baddog]

mrbones, on Nov 21 2008, 10:31 AM, said:

I have been using this module for a year with no trouble. But now I get the same error even with the latest update. How do we fix this?

If it was working and suddenly stopped working, you need to figure out what changed in order to figure out why it stopped working and how to fix it. Did your host change something? Did you change something?

[mrbones]

You are right, someone changed a setting without my knowledge. So when I was troubleshooting this and saw a fix for the error I was getting I thought it was the module. So I spent time trying to fix what wasn't broke. I reinstalled the module and followed the instructions and when it was in test mode it gave me an error that my logon was incorrect. I then found out the transaction key was invalid and generated a new one. Then viola, it works!

Pretty frustrating when someone within the office messes with your settings and doesn't tell anybody and then asks you to fix it. Anyway, it works now and thanks for the great module.

-mrb

[support@dir]

spencermjax, on Sep 21 2008, 09:35 PM, said:

Well...Well...Well...I actuall tried something that I should have tried first. The field "CURL Proxy URL" in the admin was automaticlly filled in when installed. I just edleted the contents of that fiels and BOOM! It's working!!!!!!!

where is the field "CURL Proxy URL" in the admin. is it in the file manager or in the admin control panel?

[support@dir]

ok i am so close to getting my account to work. i installed the new module and read every little tread changing everything,BUT i have my cart talking to a.net becuase i get a email showing that the transaction has gone through.BUT within oscommerce i get this


Your credit card could not be authorized for this reason. Please correct any information and try again or contact us for further assistance.

and it goes back to the payment infomation screen. PLEASE HELP ME

i am so close an just need a push into the right direction

[NimaP]

i'm getting redirected to my login page when confirming. i have 2 other sites that use the module just fine. this is the only RC2 site though. is there something i have to change?

[dtchaos]

Hello, I have a working shop http://hegemshop.com For the most part it works. However if the user enters a bad credit card number or goes back after getting to checkout_confirmation.php They are give the following message:

Quote

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card. This transaction has been approved. It is advisable for you to contact the merchant to verify that you will receive the product or service.

On some occasions in the past Authorize would receive the payment, but OScommerce would not record it. The help desk at Authorize told me this was a server time out issue, however the company that hosts our site says that my Authorize AIM add on is not properly configured, omitting the critical information as to HOW it is improperly configured. However I did get them to say it has something to do with SSL and cookies. They mentioned forcing cookie use (which if turned on in OSC causes the page to go to cookie_usage.php in stead of checkout_confirmation.php even if the browser has cookies enabled). I have very little knowledge of CURL stuff so I'm at a loss as to how to find out where things are going wrong.

My configure.php reads as follows:

// define our webserver variables
// FS = Filesystem (physical)
// WS = Webserver (virtual)
  define('HTTP_SERVER', 'http://thegemshop.com'); // eg, http://localhost or - https://localhost should not be NULL for productive servers // changed for AIM (dtk)
  define('HTTP_CATALOG_SERVER', 'http://thegemshop.com');// changed for AIM (dtk)
  define('HTTPS_CATALOG_SERVER', 'https://thegemshop.com');// changed for AIM (dtk)
  define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module
  define('HTTP_COOKIE_DOMAIN', 'thegemshop.com');// added for aim 12/08/2008(dtk)
  define('HTTPS_COOKIE_DOMAIN', 'thegemshop.com');// added for aim 12/08/2008(dtk)
  define('HTTP_COOKIE_PATH', '/catalog/');// added for aim 12/08/2008(dtk)
  define('HTTPS_COOKIE_PATH', '/catalog/');// added for aim 12/08/2008(dtk)
  define('DIR_WS_HTTP_CATALOG', '/catalog/');// added for aim 12/08/2008(dtk)
  define('DIR_WS_HTTPS_CATALOG', '/catalog/'); // added for aim 12/08/2008(dtk)
  define('DIR_FS_DOCUMENT_ROOT', $DOCUMENT_ROOT); // where your pages are located on the server. if $DOCUMENT_ROOT doesnt suit you, replace with your local path. (eg, /usr/local/apache/htdocs)
  define('DIR_WS_ADMIN', '/admin/');
  define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN);
  define('DIR_WS_CATALOG', '/catalog/');
  define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG);
  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
  define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');
  define('DIR_WS_INCLUDES', 'includes/');
  define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');
  define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
  define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
  define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
  define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
  define('DIR_WS_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');

// define our database connection
  define('DB_SERVER', '');
  define('DB_SERVER_USERNAME', 'mysql');
  define('DB_SERVER_PASSWORD', '');
  define('DB_DATABASE', 'osCommerce');
  define('USE_PCONNECT', 'false');
  define('STORE_SESSIONS', '');
?>

And the CURL section of authorizenet_aim.php is as follows:

$ch = curl_init();

	  curl_setopt($ch, CURLOPT_URL,$url);

	  curl_setopt($ch, CURLOPT_VERBOSE, 0);
	  
	  curl_setopt($ch, CURLOPT_CAINFO, 'd:\home\thegemsh\ca-bundle.crt'); // blank response fix

	  curl_setopt($ch, CURLOPT_POST, 1);

	  curl_setopt($ch, CURLOPT_POSTFIELDS, $data);

	  curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);

	if(MODULE_PAYMENT_AUTHORIZENET_AIM_CURL_PROXY != 'none') {
		  curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
		  curl_setopt ($ch, CURLOPT_PROXY,MODULE_PAYMENT_AUTHORIZENET_AIM_CURL_PROXY);
	}
	  $authorize = curl_exec($ch);

	  curl_close ($ch);

	  $response = split('\,', $authorize);

	  // Parse the response code and text for custom error display
	  $response_code = explode(',', $response[0]);
	  $response_text = explode(',', $response[3]);
	  $x_response_code = $response_code[0];
	  $x_response_text = $response_text[0];
	  // If the response code is not 1 (approved) then redirect back to the payment page with the appropriate error message
	  if ($x_response_code != '1') {//try changing this to <> instead of != 
		  tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, 'error_message=' . $response[0] . ' - ' . urlencode(MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_DECLINED_MESSAGE), 'SSL', true, false));
		//tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, 'error_message=' . $x_response_text . ' - ' . urlencode(MODULE_PAYMENT_AUTHORIZENET_AIM_TEXT_DECLINED_MESSAGE), 'SSL', true, false));
	  }

If you notice something missing or you have any idea what may be causing the problem, or how I might be able to track it, please let me know.

Thanks.