After some testing this problem appears only after about revision 313 or so of the development code. The alpha 7b release works fine, but most subsequent ones don't. Unfortunately I also need the rate quote module for shipping and that fails to work on the alpha7b and only works on the versions that authorize.net does not work - so it will be a little while before I can try out the software.

To be expected for alpha software, I'm just concerned that there seems to be important functions breaking with seemingly unrelated bug fixes....

Chad, not sure what's causing the problems for you. I've heard folks mention trouble with this module in the past, but it's actually based off the e-commerce version. I've set it up on the Livetest right now and it works both from checkout and the order administration page.

Are you using the AIM login for your account and not your site login?

What version of PHP are you on?

Also, at the very least, you can install the dev version and then overwrite the authorizenet.module, but I don't think that module has changed any since mid-July.

I just re-installed everything with the latest dev version as of 09/06/07 and I still have the same problem with authorize.net. I have everything setup correctly and the same login and key work in e-commerce. I'm testing this on a lampp machine with php 5.2.1

I'll try going back to the alpha7b version with the latest dev build and let you know what happens... thanks for the help!

Chad, I'll look into this to see if I notice anything funny. The code did come straight from the e-commerce module for sending the payment, but if you can compare the versions you have and report any major differences in the URLs, cURL functions, or anything that'd be cool.

I'll look through the code some more as time permits. I can say that I'm fairly convinced that it's not even trying to talk to authorize. In fact, I tried submitting a transaction with my computer off the network and I got the exact same error in exactly the same split second timing as I do when it's on the net.

I tried using the older authorize.net module to no avail - although if I install the whole alpha7b package it works fine. One thing I noticed is the change in recent versions from the folder uc_payment to just payment. Could there be some code that is looking for the module in a different location?

Hi Folks - I am now in the same boat in terms of getting the "We were unable to process your credit card payment. Please verify your card details and try again. If the problem persists, contact us to complete your order" message from Authorize.net

Have you made any progress Chad?

Update (that was quick!)

I got the error to go away by turning the module on production mode, but leaving Authorize.net in test mode so it wouldn't charge me. However, it didn't seem to pass the information along to Authorize.net properly because the transaction didn't show up in my account.

Any ideas?

Ryan, could you clarify this question for me:

"Are you using the AIM login for your account and not your site login?"

I was using my API Login ID and my Transaction Key as the info in Ubercart. Should I be using the login I use for the Authorize.net site login?

Well, I'm having the same issue now. Ugh... I'm not sure how to even begin to debug why. Any tips?

Brenda et al,

I got it working by turning it the Ubercart module on for production mode, and leaving Authorize.net in Test Mode. The tests don't show up, but they are emailed to the admin email in the Authorize.net settings so you can see that they went through.

And to clarify, you should indeed be using API Login ID and my Transaction Key for the info in the Ubercart settings.

Hope this helps.

Dan

My client was giving me the wrong API Login ID. It works now.

hi there,

after quite awhile of debugging this exact problem, we discovered through talking to authorize.net tech support that the issue was in where the test orders were being submitted to. the following code simply changes the url used to POST orders to when the module is in test mode:

Awesome! This has been around for a while. Fixed and committed your patch. I think that deserves a happy little Bob the Builder badge.

Just an FYI for anyone else working with the authorize.net module who stumbles on this thread as I did, sometimes the old value is correct. My test URL is https://test.authorize.net/gateway/transact.dll. The new one does not work for me. This may be because I am using a test account, rather than the test mode of a real account. After switching back, everything works fine.

Interesting... you're right, that's why it would work for me and not other folks. I suppose I could've just specified you need to have an actual test account to test it, not a live account with a test mode. Probably won't do anything about it now, but it would be great to have a setting so both work.

Attached is a simple diff which changes the transaction mode options to (Production, Test - Live Account, Test Account) and sets the urls accordingly to accommodate these 3 types of Authorize.net transactions.

Many thanks.

Finally got to submitting cYu's patch. I imagine we'll hear from someone else if this doesn't finally solve the issue.

hey when i do the transaction it gives back this information in $authorize in uc_authorize module in this function uc_authorizenet_charge($order_id, $amount, $data)

1,1,1,(TESTMODE) This transaction has been approved.,000000,P,0,24,Innovative Applications in Water Reuse and Desalination: Case Studies 2 x1,20.00,CC,auth_capture,2,altaf,samnani,,samnani,mumbai,FL,234424434,US,123456,,altafsamnani ............ user details...

here 1 means transactin charged through credit card and it even displays thank you message and order successfull submitted message.... but but but user tries to see the details order from my account it shows pending

so what i did is in uc_authorizenet.module in d above

function uc_authorizenet.charge
-
-

else {
$message = t('Credit card charged: !amount', array('!amount' => uc_currency_format($amount)));
$result = array(
'success' => TRUE,
'comment' => t('Credit card payment processed successfully. Approval code: !code', array('!code' => $x_approval_code)),
'message' => t('Credit card payment processed successfully. Approval code: !code', array('!code' => $x_approval_code)),
'uid' => $user->uid,
);

+ db_query("UPDATE {uc_orders} SET order_status = 'completed' WHERE order_id =".$order_id);
}

added +
now it displays order complete everthing is fine but is it proper way to do it ryan can u tell me ? any help would be appreciated
thanx in advance
-altaf

is their a handbook or suggested reading material for curl support? becuase i just ran into a minor error and would like to look into it further.

my error was:
AFTER ADJUSTING CART SETTINGS FOR PANES.

AFTER ENABLEING PAYPAL EXPRESS CHECKOUT:

The configuration options have been saved.
PayPal Express Checkout requires curl for PHP. Please talk to your system administrator to get this.

perhaps im just not looking at things correctly or have no education reguarding what curl is or its function is. but i would like to know if theirs a major outline for the use and functionality of this entity.

whare can i find a basic overview that explains this in laymans terms, and then, a more detailed outline of how to harness the functionality of this "curl" thing.

i would like to maintain and stay on top of my education surrounding the ubercart module and gain a proper understanding of the use, functionality, and execution of its existance.

thanks,
kasperjames