[SOLVED]Payments issue AIM authorize.net

Code: Select all

However these configuration files has no effect in the FastCGI environment you currently have. So I went ahead and adjusted system wide PHP config to create environment that appears to be required by your shopping cart and, it looks like, what it really needs is to have magic_quotes_gpc option turned Off. Once this was done session files started to contain more content which appears to be correct at this point of time.

I have also traced PHP engine that serves your script and confirmed that connection to auth.net is being established and is not rejected or anything to that extend. After that I started to play with the code and found that "(TESTMODE) The merchant login ID or password is invalid or the account is inactive" message is returned by this line in the store/catalog/controller/payment/authorizenet_aim.php file:

*************
if ($response_data[1] == '1') {
...
} else {
$json['error'] = $response_data['4'];
}
....
*************

and here is the complete printout of the array returned by auth.net in the "item number: value" format:
************
1: 3
2: 2
3: 13
4: (TESTMODE) The merchant login ID or password is invalid or the account is inactive.
5: 000000
6: P
7: 0
8: 
9: 
10: 506.65
11: 
12: auth_capture
13: 
14: 
15: 
16: 
17: 
18: 
19: 
20: 
21: 
22: 
23: 
24: 
25: 
26: 
27: 
28: 
29: 
30: 
31: 
32: 
33: 
34: 
35: 
36: 
37: 
38: 3C377FE676969738B0D9105310BF71BA
39: 
40: 
41: 
42: 
43: 
44: 
45: 
46: 
47: 
48:
49: 
50: 
51: 
52: 
53: 
54: 
55: 
56: 
57: 
58: 
59: 
60: 
61: 
62: 
63: 
64: 
65: 
66: 
67: 
68: 
************

out of everything listed above these two lines would be the most important ones:


3: 13
4: (TESTMODE) The merchant login ID or password is invalid or the account is inactive.


This error code (13) along with the error message matches with this auth.net's KB article: https://support.authorize.net/authkb/index?page=content&id=A415&pmv=print&impressions=false - according to the article you have to specifically request test account to play with their test servers and looks like either test account was not requested or wasn't provisioned to their test servers so they're rejecting your test authorization attempts.