This article has been ported to Troubleshooting Authorize.net errors

"This transaction has been approved." "1"

Error Message : "This transaction has been approved." "1" usually this error is returned by Authorize.net

when the settings in your Authorize.net account are setup incorrectly or if that account is used with another

shopping cart which requires different response settings.

In any case, the account account should be set to default Authorize.net settings in order to fix this issue.

This means that you will need to log in into Authorize.net console and go to Settings -> Direct response.

Once you're there you'll need to put the 'Field Encapsulation Character' back to empty(blank) option from the dropdown.

You practically need to choose the blank option where you have double quotes.

I receive a error when i try to process payments using Authorize.net payment gateways

ERROR: An error occurred while processing credit card "This transaction has been approved." "1" Please go back

(javascript:history.back(1);) and correct this.

"This transaction cannot be accepted. 103"

"The error message is "This transaction cannot be accepted 103" - and this is passed to BC by the gateway (Authorize.net).

Looking further at the reasons for the error, it seems there is some form of error with the Authorize.net credentials -

Link "A valid fingerprint Transaction Key, or password is required for this transaction." We suggest contacting Authorize.net to

ascertain why the payment gateway account credentials are throwing the error.

"This transaction has been declined 205"

From the authorize.net site and according to their documentation, the error you are getting "This transactionhas been declined 205" is actually related to in incorrect merchant number. "The value submitted in the merchant number field is invalid." Please refer to the below link and search for "205"

http://www.authorize.net/support/merchant/Transaction_Response/Respons e_Reason_Codes_and_Response_Reason_Text.htm

Token was null or empty. E00044

This error is usually thrown by a recurring gateway, like Authorize.net  and for some reason the token is missing against the initial (master order). The usual cause for the token missing is because, in case of Authorize.net, the CIM is not enabled.

The CIM stands for Customer Information Manager and it must be enabled on Authorize.net accounts in order to process recurring payments. It's an additional service from this gateway which is not enabled by default.

The merchant login ID or password is invalid or the account is inactive. 13

Please note the error “The merchant login ID or password is invalid or the account is inactive” is being returned from Authorize.net and it seems to have to do with the account being active. It may be worthwhile to check that your username and password are correct with authorize.net, and that your authorize.net account is indeed active.