We recently changed one of our sites over to using this module and the uc_authnet module for accepting payments. During dev and testing we used the sandbox and CIM test mode and every transaction went through as expected. Now that we've moved to production and switch our API credentials to the live server credentials and turned of sandbox and text modes it won't accept any valid credit card. We also turned of CIM since we do not allow user accounts on this site (long story) but regardless of whether that is enabled or not we still get the following errors when trying to place an order to the live Auth.net server:

Authorize.net AIM AuthorizeNet Error: Response Code: 3 Response Subcode: 1 Response Reason Code: 103 Response Reason Text: This transaction cannot be accepted.

Payment failed for order 4026: Credit card payment declined: Authorize.net AIM AuthorizeNet Error: Response Code: 3 Response Subcode: 1 Response Reason Code: 103 Response Reason Text: This transaction cannot be accepted.

Looking up the error code got me this page: https://support.authorize.net/authkb/index?page=content&id=A852

I'm not sure how useful that info is though.

Any ideas what's happening?

Comments

merzikain created an issue. See original summary.

m.stenta’s picture

Project: Authorize.net API » Ubercart Authorize.net Payment Gateway
Version: 7.x-1.0-beta2 » 7.x-2.x-dev

According to the link you posted:

This error is generated when your Authorize.Net account is in Password-Required Mode and you are not sending a valid Transaction Key or hash fingerprint with your transaction request.

Check to be sure that your login id and transaction keys are correct. Try copying and pasting them directly from Authorize.net to be sure. They should be in /admin/settings/authnet

Also make sure you are not ALSO using the Authorize.net payment gateway that comes with Ubercart. It may be confusing which config is for which module - so make sure you are using the right one. Disabling the one that comes with Ubercart is the easiest way to be sure.

Moving this to the UC Authnet module because that's where the code is that sends AIM requests, so if something needs to be changed chances are it's in that module.

merzikain’s picture

I forgot to update this yesterday.

I don't know how or why but Auth.net stopped accepting our transaction key. When I generated a new one and updated the site to use it it started working again. I'm working with them to find out what happened to the old one.

Thanks!

m.stenta’s picture

Status: Active » Closed (works as designed)

Great! Glad to hear it's all working!