cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

API Response Codes

According to the API PDF (http://www.authorize.net/support/AIM_guide.pdf) there are 45 return fields.

 

Using the url: https://test.authorize.net/gateway/transact.dll

 

If i send

 

x_delim_data=true&x_relay_response=false&x_card_num=4111111111111111&x_exp_date=1015&x_amount=1.00

 

I get about 22 fields returned

 

 

But if i send

 

x_solution_ID=A1000006&x_currency_code=USD&x_delim_data=TRUE&x_relay_response=FALSE&x_type=AUTH_CAPTURE&x_method=CC&x_invoice_num=20140221213924_1393043964&x_amount=70.44&cardType=American+Express&x_exp_date=0120&x_card_code=002&x_card_num=370000000000002&x_address=SM+Road&x_zip=46208

 

I get about 65 fields returned

 

 

I'm trying to write a handler but It's hard to understand what the extra fields are since it seems like it's 20 that aren't in the API document.

 

1 ACCEPTED SOLUTION

Accepted Solutions

The current AIM NVP guide indicates there will be 68 fields returned (assuming you're using V3.1), however those above 55 are not yet defined.

 

http://www.authorize.net/support/AIM_guide.pdf

 

Richard

View solution in original post

12 REPLIES 12

Should be 39

 

1,1,1,This transaction has been
approved.,tt9ieF,Y,2149207083,,,1.00,CC,auth_
capture,,,,,,,,,,,,,,,,,,,,,,,,,,DE9F3FAD313D32144FA7EDF4B27CCE02,,2
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,merchant defined field 1,merchant
defined field 2

 

see the merchant defined field 1,merchant defined field 2.

If you pass in anything that is not authorize.net defined. it will echo back in the response.

 

RaynorC1emen7
Expert

According to the API document there are 45 response fields if you count them, though the fields numbers start to jump after 40 to 51 (i believe this to be a typo in the guide).  Even if it was 39 or even the 45, how come i only get 22 when i do a simple transaction? Shouldn't it always give me at least all the responses?

According to the API document there are 45 response fields if you count them, though the fields numbers start to jump after 40 to 51 (i believe this to be a typo in the guide).

Look like it wasn't updated. They added parital authorization later and start with index 51.

 

Even if it was 39 or even the 45, how come i only get 22 when i do a simple transaction? Shouldn't it always give me at least all the responses?

Can you post the response?

https://test.authorize.net/gateway/transact.dll?x_login=XXXX&x_tran_key=XXXX&x_solution_ID=A1000006&...

 

Returns 68 fields:

 

2,2,27,The transaction has been declined because of an AVS mismatch. The address provided does not match billing address of cardholder.,EPWCAR,S,2222622386,20140221213924_13930,,70.44,CC,auth_capture,,,,,SM Road,,,46208,,,,,,,,,,,,,,,,,,D7CE051D308E8EE97E0AEE4B38FC6513,P,2,,,,,,,,,,,XXXX0002,American Express,,,,,,,,,,,,,,,,

 

Actually, I was mistaken, it always returns 68 fields it seems.  But what are the other fields?

 

https://test.authorize.net/gateway/transact.dll?x_login=XXXX&x_tran_key=XXXX&x_delim_data=true&x_rel...

1,1,1,This transaction has been approved.,DGJBYP,Y,2222622403,,,1.00,CC,auth_capture,,,,,,,,,,,,,,,,,,,,,,,,,,1585DE6C62AA6A5DC7376C87C20AA570,P,2,,,,,,,,,,,XXXX1111,Visa,,,,,,,,,,,,,,,,

I was right, i found the call that gave me only 22 fields

 

https://test.authorize.net/gateway/transact.dll?x_login=XXXX&x_tran_key=XXXX&x_delim_data=true&x_rel...

 

1.0,1,1,This transaction has been approved.,B5VX7F,Y,,2222622893,A2A250609199CA31380186AE2437F0A8,,,,,,,,,,,,XXXX1111,Visa

That the response from Card Present, it different then Card NOT Present

 

http://www.authorize.net/support/CP_guide.pdf

23 and up are for split authorization only

What field determines if a card is present or not?

Also, i still don't understand where the extra fields are from in the Card Not present

If you examine the latest AIM XML guide or the API Reference, you'll notice that createTransactionRequest supports both Card Present (Track Data) and Card Not Present (Card Number or encrypted data) in the same API.  It also supports transactions submitted encrypted card data or a CIM profile.