topic CIM live transaction error E00027/ response 205 in Integration and Testing

CIM live transaction error E00027/ response 205

mps_sudipta — Tue, 20 Sep 2011 06:27:45 GMT

below is the response I normally recieve:

AuthorizeNetCIM_Response Object
(
    [xml] => SimpleXMLElement Object
        (
            [messages] => SimpleXMLElement Object
                (
                    [resultCode] => Error
                    [message] => SimpleXMLElement Object
                        (
                            [code] => E00027
                            [text] => This transaction has been declined
                        )

                )

            [directResponse] => 2,2,205,This transaction has been declined,,P,3867877920,1316217600,,1.00,CC,auth_capture,1,Corbin,Grimes,,4646 Sunridge Terrace Dr.,Castle Rock,CO,80109,USA,3034892014,,corbingrimes@gmail.com,Corbin,Grimes,,4646 Sunridge Terrace Dr.,Castle Rock,CO,80109,USA,,,,,,1064D4065A28F988F65CD8EC3D377CEB,,,,,,,,,,,,,XXXX5975,MasterCard,,,,,,,,,,,,,,,,,23334812
        )

    [response] => ï»¿ErrorE00027This transaction has been declined2,2,205,This transaction has been declined,,P,3867877920,1316217600,,1.00,CC,auth_capture,1,Corbin,Grimes,,4646 Sunridge Terrace Dr.,Castle Rock,CO,80109,USA,3034892014,,corbingrimes@gmail.com,Corbin,Grimes,,4646 Sunridge Terrace Dr.,Castle Rock,CO,80109,USA,,,,,,1064D4065A28F988F65CD8EC3D377CEB,,,,,,,,,,,,,XXXX5975,MasterCard,,,,,,,,,,,,,,,,,23334812
    [xpath_xml] => SimpleXMLElement Object
        (
            [messages] => SimpleXMLElement Object
                (
                    [resultCode] => Error
                    [message] => SimpleXMLElement Object
                        (
                            [code] => E00027
                            [text] => This transaction has been declined
                        )

                )

            [directResponse] => 2,2,205,This transaction has been declined,,P,3867877920,1316217600,,1.00,CC,auth_capture,1,Corbin,Grimes,,4646 Sunridge Terrace Dr.,Castle Rock,CO,80109,USA,3034892014,,corbingrimes@gmail.com,Corbin,Grimes,,4646 Sunridge Terrace Dr.,Castle Rock,CO,80109,USA,,,,,,1064D4065A28F988F65CD8EC3D377CEB,,,,,,,,,,,,,XXXX5975,MasterCard,,,,,,,,,,,,,,,,,23334812
        )

)

The thing worked fine while the account was in test mode, but in live I am having this problem, any ideas?

below is how I connect to auth.net api, for my tests, do I need to change anything for live mode?

require_once("../anet_php_sdk/AuthorizeNet.php");
define("AUTHORIZENET_API_LOGIN_ID", "7y3xxxxxxx");
define("AUTHORIZENET_TRANSACTION_KEY", "7Dxxxxxxxxxx");
define("AUTHORIZENET_SANDBOX", false);

Re: CIM live transaction error E00027/ response 205

TJPride — Tue, 20 Sep 2011 17:14:03 GMT

Has to be one of these two things. Not sure about the second one, I may or may not be reading the output incorrectly.

API Error Code: E00027
Error Code Text: The test transaction was unsuccessful.

Response Reason Code: 205

Response Reason Text: This transaction has been declined.

Other Suggestions: This error code applies only to merchants on FDC Omaha. The value submitted in the merchant number field is invalid.

You have sandbox set to false, but maybe your production account is set to test mode? Certain things don't work in test mode.

Re: CIM live transaction error E00027/ response 205

mps_sudipta — Wed, 21 Sep 2011 07:33:47 GMT

Actually I am sure it is NOT in test mode cause, while in test mode, the code worked fine, the problem started after briniging it out of test mode, to live. Any suggestions on how to proceed with debugging?

Re: CIM live transaction error E00027/ response 205

TJPride — Wed, 21 Sep 2011 09:22:00 GMT

Are you putting in test credit card numbers?

Re: CIM live transaction error E00027/ response 205

mps_sudipta — Wed, 21 Sep 2011 09:44:18 GMT

Nope, actual details and card which is used for real transactions elsewhere

Re: CIM live transaction error E00027/ response 205

Trevor — Thu, 22 Sep 2011 21:47:04 GMT

An error 205 refers to the merchant account number that Authorize.Net uses to connect to the processing network, it generally does not represent any problem with your integration. To correct the issue, the merchant will need to contact Authorize.Net support and make sure that the account is set up with the correct merchant account details.