Can't set up authorize.net AIM

[williamc]

I've been trying to set up authorize.net AIM in shopsite without success.

The only things that shopsite requires are the web api id (which I've verified correct with authorize.net) and a transaction key. The key also checks out using authorize.net test page (I get a 1-1-1) and also see 1-1-1 tacked onto the generic shopsite error message.

// shopsite error message //

Payment Processing Error
Your order was not processed

There was a problem processing your credit card information.
Please verify that the following were entered correctly:

Zip Code
Card Number
Expiration Date

If you repeatedly see this message, complete your order by contacting the merchant directly.

// END //

Has anybody else had this problem? The test order does NOT show up in orders in shopsite manager, but an order email is sent to the store mailbox. Other test orders behave normally.

[Jim]

To see more details on the Checkout screen error message you an enable the "Display Error Details" check box on the Commerce Setup > Payment > authorize.net Configuration screen.

[williamc]

To see more details on the Checkout screen error message you an enable the "Display Error Details" check box on the Commerce Setup > Payment > authorize.net Configuration screen.

Thanks, Jim, but that's where the message I posted came from. In addition, to what I posted it, there is also some info from authorize.net. Here is a cut and paste from a test order I just ran.

*** *** ***
Payment Processing Error
Your order was not processed

There was a problem processing your credit card information.
Please verify that the following were entered correctly:

Zip Code
Card Number
Expiration Date

If you repeatedly see this message, complete your order by contacting the merchant directly.Detailed error message:
Response Code: -1-
Response Subcode: -1-
Reason Code: -1-
Reason: -(TESTMODE) This transaction has been approved.-

[Jim]

It looks like you have your authorize.net account set to test mode not live to a live server.
There isn't a setting in ShopSite to change to the test mode so it must be on the Authorize.net side that this is set.
You can see the url that ShopSite uses on the configuration screen in the backoffice of your store.

Check on the Authorize.net site control panel and see if there is an option to switch to the live server.

[williamc]

Jim,

Yes we do have authorize.net in test mode (with authorize.net) at the moment, but that does not mean we're hitting the test server. It's a special mode of the actual server so that you don't generate actual charges and get billed for tests.

In shopsite, we're still set to...

Host: secure.authorize.net
Port: 443
Authorize Script: /gateway/transact.dll

[williamc]

I should add, that I did have the owner take authorize.net out of test mode for a trial order and we got the same result. I should test that again, though. LATER: did test it again. The only effect of taking it out of test mode is that test cc#s fail as response code 34 - invalid card number. Valid cc#s fail as described above. Shopsite 11.2 is treating 1-1-1 as if it were a bad response when set up with AIM.

[williamc]

Jim,

I see that you addressed a similar problem in...

http://support.shopsite.com/forums/viewtopic.php?t=7640

and I see that my response from authorize.net looks like the following inside shopsite

Code: Select all

Response Code: -1-
Response Subcode: -1-
Reason Code: -1-
Reason: -(TESTMODE) This transaction has been approved.-

not...

Code: Select all

Response Code: 1
Response Subcode: 1
Reason Code: 1
Reason: -(TESTMODE) This transaction has been approved.-

I wonder if that's the source of the problem...

[Jim]

The source of the problem is that, as the error message returned from Authorize.net indicates, your Authorize.net account is still set to TESTMODE. You must change that on your authorize.net account control panel.

[williamc]

For anyone else researching the problem, the issue did turn out to be the field delimiter being set to a dash. When the owner went into authorize net and reset that to an empty string the problem went away.

You find this on the Authorize.net account Settings > Transaction Format Settings > Direct Response . The options should be either No or Yes but with the Default Field Separator set to comma and the Field Encapsulation Character set to nothing.

Testmode is a mode of the authorize.net production server which prevents you from getting charged for test transactions (it also does not create pending charges on real credit cards and allows test credit card numbers to be used).

Not to be confused with the sandbox/developer server... Test mode was not the source of the problem with shopsite. It was happening either way.