54 replies to this topic

[squarede]

netstep, on Nov 8 2007, 02:45 AM, said:

Sounds like the info your passing to Anet isn't verifying in the Anet system.
Authorize.net > Login > Account > Settings > Response/Receipt URLs
http://YOURSITE/checkout_process.php [Default Receipt URL]
In your site this may look like:
http://www.squaredealfarm.org/osCommerce/c...out_process.php
You'll also need to enter the transaction key from Anet into your osC payment module.

...looks like you may be in over your head a bit at http://www.squaredealfarm.org/osCommerce/c...stall/index.php
Geeks like to make it sound like installing osC is a piece a cake...and it is for geeks....but if you're a beginner it can be trying to take a drink from a fire hose. Believe me when I say I can feel your pain. I was a beginner about 7 years ago, and many of the super geeks in osC community help me realize I've still got a great deal to learn. If you're about to go crazy, you may want to considering hiring a member of this talented community to help you get your site up an running.

OFF TOPIC...in addition to your osC install you need some help getting you images optimized, etc.
Example: http://squaredealfarm.org/images/threestacktwo.JPG is 1.2mb can be optimized to 19k and cut the loading time for that image by 98%.
Get optimized image here - right click - save-as
A free program like http://www.fookes.com/ezthumbs/ can really help get your images resized and speed up your page loading time.

Sam, Thanks for the response -I am in WAY over my head. However, we have been using OS commerce for a couple of years with good luck. What you are seeing right now is a little skewed as just upgraded to the latest version of OS and my set up got pretty messed up.
We are forging forward and will try to make this work since we are in no position to be paying a site developer right now.
Thanks for the tip about optimizing -that's a new one on me.
Anyway, I'm back to the point where I can try to get the Authorize.net SIM add-on to work. I'm sure I'll have more questions.
Do you like maple syrup?
Ray

[Dragonkeeper]

I have two problems that I could use some help on. I have read many of the threads on problems encountered but haven't seen
these exact problems. So, in hope that someone knows how to fix these, I'd be most appreciative for the info. I am currently still
in Test mode and all apears to be working with these exceptions.

Problem #1 - This really does not appear to affect anything but when I go to the Checkout Confirmation page, in the new box that
appears (yellow background) the text reads "...you will be returned to DOMAIN" where do I make the change so that DOMAIN
actually spells out the name of my website?

Problem #2 - The appears to also be some sort of configuration problem but I cannot locate the source. After I am brought to the
AUTHORIZE.NET page when I enter my CC information and click the Submit buttom, I am faced with an error screen that tells me

"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."

I received the email and it tells me

"Your script timed out while we were trying to post transaction results to
it.
Transaction ID: 0
Transaction Result: This transaction has been approved.

The following message was displayed to the customer:

------------------------------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."

Where did I mess up? Or, is this standard for Test Mode? Many thanks for your reply.

[netstep]

Quote

Problem #1 - This really does not appear to affect anything but when I go to the Checkout Confirmation page, in the new box that appears (yellow background) the text reads "...you will be returned to DOMAIN" where do I make the change so that DOMAIN actually spells out the name of my website?

I apologize. The constant "DOMAIN" is not standard in osC. The simplest way to fix this is to add the constant to your includes/config.php file.

define('HTTP_COOKIE_DOMAIN', 'www.Example.com');
define('DOMAIN','www.Example.com');
You may also use define('DOMAIN',HTTP_COOKIE_DOMAIN);

Quote

Problem #2 - The appears to also be some sort of configuration problem but I cannot locate the source. After I am brought to the AUTHORIZE.NET page when I enter my CC information and click the Submit buttom, I am faced with an error screen that tells me

"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."

I received the email and it tells me

"Your script timed out while we were trying to post transaction results to it.
Transaction ID: 0
Transaction Result: This transaction has been approved.
The following message was displayed to the customer:
------------------------------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."
Where did I mess up? Or, is this standard for Test Mode? Many thanks for your reply.

Errrr....not sure about this one. I never messed around much with using the module in test mode. I went straight to the production mode and put a $1 test product in my catalog. Then I made actual purchases with my CC then canceled them. If you do this a bunch you're CC company may flag your card and you'll have to let them know this was intentional. May help to do different amounts..$1, $2, $3, etc. As long as you can log into your authorize.net terminal and cancel them before they post.
I wish I could be more help, but it's challenging when I can't duplicate the error.

[Dragonkeeper]

Thanks for reply. One more question, if you don't mind. In Section 3 of your documentation, you spell out some definitions to add to a configuration file. Forgive my naivete but is this required and, if it is, to which file do I add this information. I am not too clear on this part.
Gary

[netstep]

You are referring to constants that may be added to the includes/config.php file (optional).

3. CUSTOMIZE PAYMENT FORM (See screen shot)
***NOTE: Any references to files (images/CSS) must be on an SSL server or it will cause the Internet Explorere "non-secure items" warning.
***Example: You might want to dress up your form by linking it to your site style sheet....but EVERY time someone goes to your form it will pop-up a warning window...unless your stylesheet is on an SSL server.
***Even if it's on an SSL server, the visitor may get a phishing warning because the reference is to a site other then the site they are on (authorize.net).
You may add some customization to the payment form by editing the form settings in your Authorize.net control panel.
OR
You can define values that will be sent to the form.
I prefer this method because the header/footer settings in the merchant control panel are limited to 255 characters.
It doesn't take much formatting to suck this up.
CSS
I put all my CSS in the tag too so no external style references.
Some of the values are specific to the Payment form (view code on form to see other elements you can format.
Example: #x_exp_date,#x_card_code,#x_card_num{background: #FFFF66;} makes the background for the required fields yellow.

Add the definitions below to your configuration file.

//EVERYTHING REFERENCED BY CSS OR IMAGES MUST BE HOSTED ON SSL TO PREVENT IE "Secure/non-secure" error
define('AUTHORIZENET_PAYFORM_HTML_HEADER','
	<style type="text/css">
	body {font-family:Tahoma,Verdana,Arial;font-size:12px;background: #4C71AB;}
	.name{font-size:30px;font-weight:bold;}
	.title{font-size:18px;font-weight:bold;color:#666666;}
	.HeaderFooter1{font-family:Tahoma,Verdana,Arial;font-size:12px;}
	.Page{background: #ffffff;}
	#x_exp_date,#x_card_code,#x_card_num{background: #FFFF66;}
	</style>
	<span class="name">Company or Site Name</span><br>
	<span class="title">Secure Payment System</span>
	');
define('AUTHORIZENET_PAYFORM_HTML_FOOTER','I suggest displaying your street address here in the footer<br />Phone: 555-555-5555 | Fax: 555-555-5555');
define('AUTHORIZENET_PAYFORM_LOGO',''); //MUST BE ON SSL SERVER

These values are optional.
The code in the payment module looks like this.
Note the "if(defined...."

		//+HEADFOOT - PAYMENT FORM HEADER & FOOTER - Not limited to 255 characters like the Authorize.net payment form settings. You can include styles, etc. However, be careful not to link to images on NON-SSL sites.
//define these variables in your configuration file: AUTHORIZENET_PAYFORM_HTML_HEADER, AUTHORIZENET_PAYFORM_HTML_FOOTER, AUTHORIZENET_PAYFORM_LOGO

		if(defined('AUTHORIZENET_PAYFORM_HTML_HEADER')){
			$payform_header_html = AUTHORIZENET_PAYFORM_HTML_HEADER;
		}else{
			$payform_header_html = '';
		}
		if(defined('AUTHORIZENET_PAYFORM_HTML_FOOTER')){
			$payform_footer_html = AUTHORIZENET_PAYFORM_HTML_FOOTER;
		}else{
			$payform_footer_html = '';
		}
		if(defined('AUTHORIZENET_PAYFORM_LOGO')){
			$payform_logo = AUTHORIZENET_PAYFORM_LOGO; //MUST BE ON SSL SERVER & LISTED IN YOUR AUTHORIZED URLS.
		}else{
			$payform_logo = '';
		}
		//-HEADFOOT

[Dragonkeeper]

Hi, Sam. Thanks for the help. I have change the DOMAIN constant and that fixed the first problem but the second problem remains. After I click the Submit button on the ANet payment form and wait a few seconds, I am presented with

""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."

I received the email and it tells me

"Your script timed out while we were trying to post transaction results to it.
Transaction ID: 0
Transaction Result: This transaction has been approved.
The following message was displayed to the customer:
------------------------------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."

So, I contacted ANet and Tech Support gave me a list of things to check.

"When Authorize.net is responding back to a script on your server,
our system waits 10 seconds for a response. If we do not get a response in 10 seconds,
our server will time out and display an error page. The first thing that you will need
to look for is the order that your script executes. It is very important that something
is printed to the screen before any other process is started. If your script prints to
the screen first, we will recognize that you are receiving the information. The most
effective method would be to PRINT the headers, and a line of text such
as "Processing, please wait."

To resolve this issue:

-Check that your script permissions are correct and that it can accept a HTTPS POST.

-Check that the script is not completing other functions before writing to the screen,
such as writing to a database or sending emails.

- Please check to see if there are different processes that are used in your script for
approvals, declines, or errors. Be sure to check each process to be sure that each process
will write to the screen before any other functions.

- Check if your script is using redirects immediately upon receipt of the response from our
servers. Redirects are discouraged because they can potentially interfere with the process.

***On occasion, timeouts will occur that are outside of the control of your script or our
servers. Typical reasons for these timeouts are Internet traffic, your server is overloaded
or malfunctioning, or Internet routing issues. Depending upon your server location and what
route is used to send data, it is possible that you may occasionally receive the message you
are seeing. "

I have no idea as to what to look for in my setups or configurations to solve this. If you (or anyone else for that matter)
could point me in the direction of what I might look for to fix this, I would be most grateful. Thanks.
Gary

[netstep]

Dragonkeeper, on Dec 11 2007, 05:52 PM, said:

"Your script timed out while we were trying to post transaction results to it.
Transaction ID: 0
Transaction Result: This transaction has been approved.

1. Is the Anet-SIM module set to "test" or "production" mode?

2. Is the transaction appearing in the Authorize.net system.
Connect > transact > fail on return to osC
OR
Connect > fail

3. What is your "Default receipt URL" in
Authorize.net > Account > Settings > Response/Receipt URLs
Should be like: http://www.example.com/checkout_process.php (or https:// for secure + make sure w/w-out www matches your config too)

[Dragonkeeper]

netstep, on Dec 11 2007, 02:05 PM, said:

1. Is the Anet-SIM module set to "test" or "production" mode?

I am in Test mode right now.

Quote

2. Is the transaction appearing in the Authorize.net system.
Connect > transact > fail on return to osC
OR
Connect > fail

Since I am in test mode, the transactions do not appear. But I do get message that everything was processed properly. Should I try it in production mode? Where can I cancel the transaction after it is done since I don't actually want it to go through to my card?

Quote

3. What is your "Default receipt URL" in
Authorize.net > Account > Settings > Response/Receipt URLs
Should be like: http://www.example.com/checkout_process.php (or https:// for secure + make sure w/w-out www matches your config too)

It is http://www.mywebsite.com/oscommerce-2.2ms2...out_process.php

Which CONFIG file do I need to check this with?
Thanks.
Gary

[Dragonkeeper]

As an "oh, by the way" I am getting the error message while at the https://secure.authorize.net/gateway/transact.dll page if that helps at all.

[Dragonkeeper]

I have now tried it in LIVE mode and got the same response. The transaction went through (and I have voided it). I am at a loss as to what's wrong. Could it have anything to do with my site being on a SSL server and my putting only http://.... in the Receipt/URL?

Edited by Dragonkeeper, 11 December 2007, 20:30.

[netstep]

Dragonkeeper, on Dec 11 2007, 08:27 PM, said:

Could it have anything to do with my site being on a SSL server and my putting only http://.... in the Receipt/URL?

A bit confusing but posted earlier in #47

Quote

3. What is your "Default receipt URL" in
Authorize.net > Account > Settings > Response/Receipt URLs
Should be like: http://www.example.com/checkout_process.php (or https:// for secure + make sure w/w-out www matches your config too)

That's the next factor to consider.
If your site is set to SSL, then the script may be trying to redirect the Anet call to the SSL page...which is not authorized.
From Anet's response: we discourage redirects.... because it might break the script.
You were not intentionally redirecting the that would be the result of sending Anet to an HTTP: page on HTTPS: site.

Why did you bury your osC install so far down in your web site?
Icky url path... http://www.mywebsite.com/oscommerce-2.2ms2...out_process.php
It's not relevant to this discussion because Anet doesn't care, but have you considered moving it to:
http://www.mywebsite.com/catalog/checkout_process.php

[Dragonkeeper]

netstep, on Dec 11 2007, 03:49 PM, said:

A bit confusing but posted earlier in #47

Quote

That's the next factor to consider.
If your site is set to SSL, then the script may be trying to redirect the Anet call to the SSL page...which is not authorized.
From Anet's response: we discourage redirects.... because it might break the script.
You were not intentionally redirecting the that would be the result of sending Anet to an HTTP: page on HTTPS: site.

Is there a way I can fix this?

Quote

http://www.mywebsite.com/oscommerce-2.2ms2...out_process.php[/url]
It's not relevant to this discussion because Anet doesn't care, but have you considered moving it to:
http://www.mywebsite.com/catalog/checkout_process.php

Actually, I didn't. I had a web designer do this and since we were both neophytes when it came to installing OSC that's the way it was set up.
Everything works fine otherwise.

[netstep]

Dragonkeeper, on Dec 11 2007, 09:50 PM, said:

Is there a way I can fix this?

Yes. Easy. But this if off topic. Please PM me for help.

[netstep]

If you've been reading this forum in anticipation of the end of Dragonkeeper's issue. We traced the transaction all the way through but still have an unanswered question.
In the checkout process, the events occurring at the end include sending order confirmations and clearing the cart just before redirecting to the checkout success page. Dragonkeeper's transaction made it all the way through all the steps except for the final redirect to the success page before timing out.
His communication with Anet included.

Quote

On occasion, timeouts will occur that are outside of the control of your script or our servers. Typical reasons for these timeouts are Internet traffic, your server is overloaded or malfunctioning, or Internet routing issues. Depending upon your server location and what route is used to send data, it is possible that you may occasionally receive the message you are seeing.

As I understand it Dragaonkeeper's server is located in AU and Anet's server is in New Jersey US...about as far away as you can get. I know light travels fast, but I suppose if you through in a little packet routing and network congestion and you can get a time-out problem (a theory).

Drangonkeeper was able to install the AIM module and all transactions worked perfectly.
No worries.

[maxemus]

I guess no one has a fix for this.