Although we checked all the configuration multiple times, and seems like all the configuration is set according to Authorize.net guidelines, the payment processing fails, giving the following error code:

Credit card payment declined: Authorize.net AIM AuthorizeNet Error: Response Code: 3 Response Subcode: 2 Response Reason Code: 13 Response Reason Text: The merchant login ID or password is invalid or the account is inactive.

Our account is set to active (https://snag.gy/h7OLTw.jpg) and the merchant ID and password is ok, so we suppose this problem could come from the module side.

Any idea?

Comments

michael.farkas created an issue. See original summary.

m.stenta’s picture

m.stenta
he/him
Primary language English
commented
Priority: Major » Normal

Just to be sure... you're not using your Authorize.net login username and password, right? You should be using the "login id" and "transaction key" that you generated within Authorize.net. Those must be set up as a separate step.

Otherwise, I would suggest regenerating the id and key. Authorize.net provides a way to do this. Someone reported a similar issue in the past, and they said that regenerating their id and key solved it for them. It wasn't an issue with the module.

Give that a try and let us know if it worked.

michael.farkas’s picture

michael.farkas commented

No, we didn't use our Authorize.net login username and password: just like you said, we are using the API Login ID and Transaction Key generated within Authorize.net (https://snag.gy/0artoz.jpg). The transaction key was regenerated a couple of times, but didn't solve our problem. If Authorize.net can regenerate the ID as well (I didn't see an option for this), we will give a try.

We have tried the API without the drupal integration and the test payment was sent to the Authorize.net live account (not to the developer account). Unfortunately the payment from durpal is not going through neither to live or developer account.

I will ask the Authorize.net if is possible to regenerate the API login ID.

michael.farkas’s picture

michael.farkas commented

We managed to make a transaction by choosing Authorize.net as a Default gateway, but the transaction is not working with Authorize.net API (uc_authnet) gateway - https://snag.gy/baTzhQ.jpg

What can be the problem?

m.stenta’s picture

m.stenta
he/him
Primary language English
commented

Do you have sandbox mode turned off? That setting is at /admin/settings/authnet

There is also a checkbox there to turn on debug mode, which will post the full Authorize.net API response to watchdog. That might provide some clues.

m.stenta’s picture

m.stenta
he/him
Primary language English
commented
Status: Active » Closed (cannot reproduce)

Assuming this was resolved... ?