Reply
Highlighted
Member
Posts: 3
Registered: ‎04-25-2012
Accepted Solution

AIM Error 66 Debugging - "The transaction did not meet gateway security guidelines"

[ Edited ]

I've been searching around, and have been unable to find a listing of possible causes for response error 66 "The transaction did not meet gateway security guidelines" when using the AIM method (with https of course).

 

I am porting the code over from another domain, I have set the x_test_request attribute, and  have used the test transaction code 4222222222222, a valid address, city and state etc.

 

here is the posting array from the posting file

                                $AuthNet_Values                = array
                                (
                                    "x_login"                => $AuthNet_LoginID,
                                    "x_version"                => "3.1",
                                    "x_delim_char"            => "|",
                                    "x_delim_data"            => "TRUE",
                                    "x_url"                    => "FALSE",
                                    "x_type"                => "AUTH_CAPTURE",
                                    "x_method"                => "CC",
                                     "x_tran_key"            => $AuthNet_TranKey,
                                     "x_relay_response"        => "FALSE",
                                    "x_card_num"            => $_POST['Card_Number'],
                                    "x_exp_date"            => $_POST['Card_Exp_M'].$_POST['Card_Exp_Y'],
                                    "x_description"            => "Yada Yada",
                                    "x_amount"                => sprintf("%01.2f",($_POST['Amount'] == 'Other' ? $_POST['Amount_Other'] : $_POST['Amount'])),
                                    "x_first_name"            => $_POST['First_Name'],
                                    "x_last_name"            => $_POST['Last_Name'],
                                    "x_address"                => $_POST['Address'],
                                    "x_city"                => $_POST['City'],
                                    "x_state"                => $_POST['State'],
                                    "x_zip"                    => $_POST['Zip'],
                                    "x_country"                => 'US',
                                    "x_phone"                => $_POST['Phone'],
                                    "x_email"                => $_POST['Email'],
                                    "x_recurring_billing"    => $recurring,
                                    "x_test_request" => "TRUE" // test line
                                );

 

What are some things I could check into, to get back specific details of what needs fixed?

 


Accepted Solutions
Solution
Accepted by topic author jmhead
‎08-21-2015 01:58 AM
Member
Posts: 3
Registered: ‎04-25-2012

Re: AIM Error 66 Debugging - "The transaction did not meet gateway security guidelines"

[ Edited ]

Well it looks like the problem for me was the test transaction code 4222222222222, which since it was from here http://developer.authorize.net/guides/AIM/Test_Transactions/Test_Credit_Card_Numbers.htm , it should have worked in theory.

 

I tried CC# to 4111111111111111 and it processed.

 

Then I ran a real credit card number through and it processed fine with response "(TESTMODE) This transaction has been approved.", and the conformation email with ************* TEST MODE ************* at the head.

 

It seems it might be best to test with all the actual id's and trasactions keys in place, but add the x_test_request = TRUE line.

View solution in original post


All Replies
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: AIM Error 66 Debugging - "The transaction did not meet gateway security guidelines"

Can you echo the request before sending it to test.authorize.net?

Member
Posts: 3
Registered: ‎04-25-2012

Re: AIM Error 66 Debugging - "The transaction did not meet gateway security guidelines"

[ Edited ]

Here is a dump of some data and the response back:
Looks like the error may be 25, which is even more vague "(TESTMODE) An error occurred during processing. Please try again."

 

--- Sent values --- 
string(471) "x_login=[login]&x_version=3.1&x_delim_char=%7C&x_delim_data=TRUE&x_url=FALSE&x_type=AUTH_CAPTURE&x_method=CC&x_tran_key=[TransKeyNum]&x_relay_response=FALSE&x_card_num=4222222222222&x_exp_date=032014&x_description=Yada+Yada&x_amount=25.00&x_first_name=test&x_last_name=test&x_address=6965+Regent+st&x_city=Indianapolis&x_state=Indiana&x_zip=46225&x_country=US&x_phone=555-555-5555&x_email=sdfg%40sdfgdr.com&x_recurring_billing=NO&x_test_request=TRUE&"
---------------------------
--- Form Values ---
array(22) { ["Type"]=> string(8) "One-Time" ["Amount"]=> string(5) "25.00" ["Amount_Other"]=> string(0) "" ["Event_Name"]=> string(0) "" ["Card_Number"]=> string(13) "4222222222222" ["Card_Exp_M"]=> string(2) "03" ["Card_Exp_Y"]=> string(4) "2014" ["Prefix"]=> string(3) "Mr." ["First_Name"]=> string(4) "test" ["Last_Name"]=> string(4) "test" ["Address"]=> string(12) "6965 Regent st" ["Address_2"]=> string(0) "" ["City"]=> string(12) "Indianapolis" ["State"]=> string(7) "Indiana" ["Zip"]=> string(5) "46225" ["Phone"]=> string(12) "555-555-5555" ["Email"]=> string(15) "sdfg@sdfgdr.com" ["Employer"]=> string(4) "test" ["Occupation"]=> string(4) "test" ["Industry"]=> string(11) "Agriculture" ["Disclaimer"]=> string(1) "1" ["Refund"]=> string(1) "1" }
---------------------------
--- Response Array ---
array(69) { [0]=> string(1) "3" [1]=> string(1) "3" [2]=> string(2) "25" [3]=> string(66) "(TESTMODE) An error occurred during processing. Please try again." [4]=> string(6) "000000" [5]=> string(1) "P" [6]=> string(1) "0" [7]=> string(0) "" [8]=> string(25) "Yada Yada" [9]=> string(5) "25.00" [10]=> string(2) "CC" [11]=> string(12) "auth_capture" [12]=> string(0) "" [13]=> string(4) "test" [14]=> string(4) "test" [15]=> string(0) "" [16]=> string(12) "6965 Regent st" [17]=> string(12) "Indianapolis" [18]=> string(7) "Indiana" [19]=> string(5) "46225" [20]=> string(2) "US" [21]=> string(12) "555-555-5555" [22]=> string(0) "" [23]=> string(15) "sdfg@sdfgdr.com" [24]=> string(0) "" [25]=> string(0) "" [26]=> string(0) "" [27]=> string(0) "" [28]=> string(0) "" [29]=> string(0) "" [30]=> string(0) "" [31]=> string(0) "" [32]=> string(0) "" [33]=> string(0) "" [34]=> string(0) "" [35]=> string(0) "" [36]=> string(0) "" [37]=> string(32) "[String of Characters]" [38]=> string(0) "" [39]=> string(0) "" [40]=> string(0) "" [41]=> string(0) "" [42]=> string(0) "" [43]=> string(0) "" [44]=> string(0) "" [45]=> string(0) "" [46]=> string(0) "" [47]=> string(0) "" [48]=> string(0) "" [49]=> string(0) "" [50]=> string(8) "XXXX2222" [51]=> string(0) "" [52]=> string(0) "" [53]=> string(0) "" [54]=> string(0) "" [55]=> string(0) "" [56]=> string(0) "" [57]=> string(0) "" [58]=> string(0) "" [59]=> string(0) "" [60]=> string(0) "" [61]=> string(0) "" [62]=> string(0) "" [63]=> string(0) "" [64]=> string(0) "" [65]=> string(0) "" [66]=> string(0) "" [67]=> string(0) "" [68]=> string(5) "FALSE" }
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: AIM Error 66 Debugging - "The transaction did not meet gateway security guidelines"

[ Edited ]

Not sure why, but when I use my test account loginID and transactionKey, I also getting error 25 "(TESTMODE) An error occurred during processing. Please try again." with your sent values. 

But if I remove the x_test_request=TRUE or change it to x_test_request=FALSE, it ran thru ok.

 

Or change the CC# to 4111111111111111 and keep the x_test_request=TRUE, it ran thru ok also.

Solution
Accepted by topic author jmhead
‎08-21-2015 01:58 AM
Member
Posts: 3
Registered: ‎04-25-2012

Re: AIM Error 66 Debugging - "The transaction did not meet gateway security guidelines"

[ Edited ]

Well it looks like the problem for me was the test transaction code 4222222222222, which since it was from here http://developer.authorize.net/guides/AIM/Test_Transactions/Test_Credit_Card_Numbers.htm , it should have worked in theory.

 

I tried CC# to 4111111111111111 and it processed.

 

Then I ran a real credit card number through and it processed fine with response "(TESTMODE) This transaction has been approved.", and the conformation email with ************* TEST MODE ************* at the head.

 

It seems it might be best to test with all the actual id's and trasactions keys in place, but add the x_test_request = TRUE line.