Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

authorize.net settings


droyalty

Recommended Posts

Hello all! I've scoured the forums here and at oscDox.com for a concise answer...

I've also gone to authorize.net for the answers, but they didn't have the expertise...

 

In a nutshell...I'm using osCommerce 2.2 MS2 at www.joshua19.com. Currently I'm

using PayPal IPN and would like to offer authorize.net as a payment option. Using

the out-of-the-box authorize.net module, what are the proper settings (at authorize.net)

for:

 

- Response/Receipt URLs

- Silent Post URL

- Receipt Page

- Relay Response

- Direct Response

 

Wouldn't any osC 2.2 MS2 site using authorize.net need these set?

 

I know there are other a.net contributions available, but (I think) regardless of

the implementation, the same settings will need to be dealt with.

 

Any and all advice/help is appreciated!

 

Dennis

Link to comment
Share on other sites

First the original default module is out of date.

 

You need to install the new Authorize.net module, available here.

 

http://www.oscommerce.com/community/contri...h,Authorize.net

 

(**PLEASE BE SURE TO BACK UP YOUR SHOP BEFORE ADDING NEW MODULES**)

 

If you have never installed a new module, the instruction are pretty much

straight forward...if you need help, let me know.

 

Not adding the new updated module is where most people fail, but after that

it's usually in the settings themselves.

 

First thing you need to do is have a very competent web host that knows what

they are doing.

 

First, they need to have the latest version of cURL installed on your

server.

 

http://curl.haxx.se/

 

Once, you have positively established that cURL is installed and set up

properly, then you need to set up Authorize.net as well as the new module

properly.

 

In your Authorize.net setting you should have the following setup courtesy

of petercwik.

 

"OK Guys here's the deal. (Just got it working last week)

 

You don't need a Receipt page, so delete that entry in Authorize.net

 

The Response page (at authorize.net) should be

https://www.yoursite.com/catalog/checkout_process.php

 

In the Direct Response (at authorize.net), click the YES radio button to say

that you want delimited response, you can leave the default delimiter of a

comma.

 

That is it."

 

----------------------------------------------------------------------------

------

 

Here are the osCommerce settings in the admin CP

 

Authorize.net Consolidated v1.7 by Austin519

 

Enable Authorize.net Module

True

 

Login Username

example_admin

 

Login Transaction Key

example_transactionkey324jewsr8u

 

cURL Setup

Compiled

 

cURL Path

/usr/bin/curl

 

Transaction Mode

Production

 

Transaction Method

Credit Card

 

Processing Mode

Authorize And Capture

 

Sort Order Of Display

0

 

Customer Notifications

True

 

Accepted Credit Cards

 

 

After weeks of getting close...our final problem was this

 

1) Go to authorizenet_direct.php. Go to line 149, which reads: $url =

"<https://secure.authorize.net/gateway/transact.dll>"; Remove the brackets.

It should now read: $url =

"https://secure.authorize.net/gateway/transact.dll"; ...the 1.7 version of

this code has a lot of the previous issues associated with this section of

code cleaned up, so you shouldn't have to do more than this.

 

Adding the new module, correcting the setting in Authorize.net &

osCommerce and making the above change corrected all our problems...I hope

this helps

 

Sincerely

 

The Finman - Administrator of RonaldReagan.com

Link to comment
Share on other sites

First the original default module is out of date.

 

You need to install the new Authorize.net module, available here.

 

http://www.oscommerce.com/community/contri...h,Authorize.net

 

(**PLEASE BE SURE TO BACK UP YOUR SHOP BEFORE ADDING NEW MODULES**)

 

If you have never installed a new module, the instruction are pretty much

straight forward...if you need help, let me know.

 

Not adding the new updated module is where most people fail, but after that

it's usually in the settings themselves.

 

First thing you need to do is have a very competent web host that knows what

they are doing.

 

First, they need to have the latest version of cURL installed on your

server.

 

http://curl.haxx.se/

 

Once, you have positively established that cURL is installed and set up

properly, then you need to set up Authorize.net as well as the new module

properly.

 

In your Authorize.net setting you should have the following setup courtesy

of petercwik.

 

"OK Guys here's the deal. (Just got it working last week)

 

You don't need a Receipt page, so delete that entry in Authorize.net

 

The Response page (at authorize.net) should be

https://www.yoursite.com/catalog/checkout_process.php

 

In the Direct Response (at authorize.net), click the YES radio button to say

that you want delimited response, you can leave the default delimiter of a

comma.

 

That is it."

 

----------------------------------------------------------------------------

------

 

Here are the osCommerce settings in the admin CP

 

      Authorize.net Consolidated v1.7 by Austin519

 

      Enable Authorize.net Module

      True

 

      Login Username

      example_admin

 

      Login Transaction Key

      example_transactionkey324jewsr8u

 

      cURL Setup

      Compiled

 

      cURL Path

      /usr/bin/curl

 

      Transaction Mode

      Production

 

      Transaction Method

      Credit Card

 

      Processing Mode

      Authorize And Capture

 

      Sort Order Of Display

      0

 

      Customer Notifications

      True

 

      Accepted Credit Cards

      After weeks of getting close...our final problem was this

 

      1) Go to authorizenet_direct.php. Go to line 149, which reads: $url =

"<https://secure.authorize.net/gateway/transact.dll>"; Remove the brackets.

It should now read: $url =

"https://secure.authorize.net/gateway/transact.dll"; ...the 1.7 version of

this code has a lot of the previous issues associated with this section of

code cleaned up, so you shouldn't have to do more than this.

 

      Adding the new module, correcting the setting in Authorize.net &

osCommerce and making the above change corrected all our problems...I hope

this helps

 

      Sincerely

 

      The Finman - Administrator of RonaldReagan.com

 

 

Hello. New here and don't mean to hijack the thread, but I am having some similar problems as well.

 

I have followed all the advise above. When trying to test this using an authorize.net test card # VISA 4007000000027, I get the following returned to me in red at the top of the page:

 

There was an error processing your credit card ():

 

Then I tried it with the other CC test numbers with the same result.

 

No code or anything. Nothing at authorize.net indicates it was even communicating with them either. I can't tell if it's talking to them or not.

 

Can anyone offer up any ideas? This isn't my first time setting up something with Authorize.net (did a Modernbill setup) but it is my first OSCommerce site.

 

Any help is greatly appreciated!

Link to comment
Share on other sites

Fin! It worked beautifully! Thanks to you and Austin!!

 

David, I don't know why it's not working for you. I just followed Fin's and Austin's

instruction and install directions and it works great!

 

I *did* have an old version of cURL on my system, but that went in easily. I'm

running a linux server, purring along at my feet... don't know if u're using M$oft

of a *nix variant.

 

You might want to kick this out to another thread either here or at www.oscdox.com

and see what that might bring you.

 

Good Luck! Fin - u the man!!

Link to comment
Share on other sites

On this topic of authorize.net, we have been receiving a great deal of GENERAL TRANSACTION errors. Is there 1) an OSC fix for this or 2) a way to capture credit card details to rebill? This is what Authorize.net claims is happening:

 

"The response we got back on that transaction was: (52) The transaction was successfully authorized but the client could not be notified. This transaction will not be settled. The transaction was authorized but the client could not be notified; it will not be settled.

 

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

 

Thanks for any help possible, as these are coming through to osc as actual sales - we have shipped many orders based on this false positive.

 

Thanks again everyone! ;)

Link to comment
Share on other sites

how do you have your settings at authorizenet? are you using receipt/return url's? if u r using the latest version of anet, do not use receipt/return url's.

also could be a server issue, with your host having a slow connection

Link to comment
Share on other sites

We were using receipt/return url's.. AND using current version of anet. Server uptime of 100% (ev1 servers) last 4 months so that is ruled out. pehaps it was receipt/return urls?

 

Thought osc would not get fed data without them>

 

The settings should be like this??

 

Response/Receipt URLs Help

The Payment Gateway verifies the URL specified in the post string against the URLs in this list. If the URL provided does not match one of the values on this list, the transaction will be rejected. If no URL is provided, the Default URL value will be used.

 

URL Add URL

(Click Edit to define a default URL value.) Default Receipt URL Edit

(Click Edit to define a default URL value.) Default Relay Response URL Edit

Edited by ThanksEveryone
Link to comment
Share on other sites

  • 2 months later...
Just like drylinehosting. I had installed everything by following your comment. But when I click the confirm bottom it shows "There was an error processing your credit card ():". Can anybody help me? :'(

This may be it a bit late, but I have figured out why we were getting the empty error message "()".

 

Basically, the message is put in an array in two different lines of code (they're redundant). The end result is that the only thing that gets preserved is the actual error code that the module works off of to determine that the purchase did not go through.

 

Now, for the fix:

 

In the before_process() function of /includes/modules/payment/authorizenet.php, find these lines:

// Change made by using ADC Direct Connection
 $response_vars = explode(',', $response[0]);

 

Comment out the second line like so:

// Change made by using ADC Direct Connection
//	$response_vars = explode(',', $response[0]);

 

The reason for this:

The $response variable is created as an array from the text of the returned string for curl_exec() in authorizenet_direct.php.

 

The line that splits it into an array is this:

$response = split(",", $authorize);

 

It worked for me, and I have a hunch that it will work for those of you having a problem. I am a bit confused as to why this bug doesn't show up for all users, but I think it is safe to say that the fix that I just posted should work on all installations.

 

If someone wants to go ahead and update that one line of code and add it into the Contributions page, it would be appreciated.

 

Let me know if this fixed your problem (if you hadn't figured it out/given up already).

Link to comment
Share on other sites

Oh, and add this line after the one you commented out:

 

$response_vars = $response;

 

So the entire thing looks something like this:

   // Change made by using ADC Direct Connection
//	$response_vars = explode(',', $response[0]);

 $response_vars = $response;

 $x_response_code = $response_vars[0];
 $x_response_subcode = $response_vars[1];
 $x_response_reason_code = $response_vars[2];
 $x_response_reason_text = $response_vars[3];

Link to comment
Share on other sites

I am new at this but I do have some store background.

 

I why in the admin of osCommerce under the modules/authorized.net

 

I do not see the options for "cURL Setup" and "cURL Path" and "Processing Mode"

Link to comment
Share on other sites

How do you go about updating to the latest version of the Authorize.net contribution? I havent been able to figure out how to update it correctly.

 

On a linux server (don't know what it looks like on a Micro$oft

machine) and assuming you don't have a heavily modified osCommerce

system:

 

- make a copy of your catalog directory (or just the affected files)

cd (to the directory containing your catalog directory)

cp -R catalog catalog_backup

 

- copy the catalog directory from the contribution overtop your

working catalog (that's why you made a copy, in case something

goes awry)

 

cp (where ever you downloaded and unzipped the contribution)

-R catalog .

 

example; cp -R /usr/local/downloads/auth.net_dir/catalog .

 

- if there's anything else that wasn't copied ... any files at the top level of

the contribution, just copy them into your catalog directory.

 

- if this messes something up, just copy the saved catalog over the modified

catalog, or rename catalog_backup to catalog (same thing different method).

 

Note: my version of cURL was out of date, so I had to install the latest. Please

see the response from Finman near the top of this thread for a thorough

explanation. As mentioned elsewhere in this thread, I simply followed Finman's

directions exactly and all went perfectly.

 

Good luck! Dennis

Link to comment
Share on other sites

  • 6 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...