topic Re: API response change (not the JSON change) in Integration and Testing

API response change (not the JSON change)

willief — Fri, 05 Aug 2016 16:11:51 GMT

I am not the dev working on this but am researching for a client of ours (I'm a reseller). They've been using auth.net for 10+ years, same coding and no changes made. On Aug 2 around 3PM CST they started receiving back a different response than they used to receive. Originally they would receive back a delimited string that had 70 fields. Tuesday afternoon an extra field was thrown in at the end which "broke" their system.

IT fixed the coding on their end to accomodate, but then they started receiving some responses back that added in an extra field somewhere in the middle as well, for a total of 72 fields. Tech support said no changes were made but something had to have changed. They've again updated their logic to accomodate since they mostly get back responses w/ 71 fields but sometimes 72 fields but are concerned that the responses will continue to change.

Has anyone else run into this in the last few days? I know this is all fairly vague but what could cause extra fields to be sent back to them? Thank you in advance.

Re: API response change (not the JSON change)

Lilith — Fri, 05 Aug 2016 17:42:36 GMT

The new field at the end is expected -- we are in the process of rolling out a replacement for the MD5 Hash in transaction responses. More details will be forthcoming.

The new field they're saying they see in the middle, however, is not.

Is it possible to get examples of the transaction responses? And are they seeing any value at all in the new field?

Re: API response change (not the JSON change)

willief — Fri, 05 Aug 2016 18:19:02 GMT

Hello. Here is a Word doc they made showing the fields in the string (it is not the exact verbage of the response they get, just a list of the fields that he made). I don't have the exact message that comes back but I can try to gather. All of the new fields are currently blank when they come back.

Original Response:

1
|1
|1
|This transaction has been approved.
|07898A
|Y
|1274424396
|
|ma rvbk w/pretest tausha
|39.95
|CC
|auth_capture
|7889869
|FirstName
|LastName
|
|123 Wayne Ave
|Stony Point
|NewYork
|10980
|USA
|5554294077
|
|Email
|
|
|
|
|
|
|
|
|
|
|
|
|
|F9C9243F3E55ADB348A635BF9031B612
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|780731
|175

Response that has the 72 fields in it:

1
|1
|1
|This transaction has been approved.
|H26536
|Y
|20098616085
|
|Completing CE courses Online  1 Online Practice Test – Insurance
|36.45
|CC
|auth_capture
|8282884
|First
|Last
|
|1234 Flagstone Ave
|Riverside
|California
|92503
|United States
|5552950121
|
|Email
|
|
|
|
|
|
|
|
|
|
|
|
|
|F5FA041899AC812E5BE477B3A175311D
|M
|
|
|
|
|
|
|
|
|
|
|
|XXXX0771
|MasterCard
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|1559501
|601062
|

The response w/ just 71 lines that they get most of the time is the same as the 72 above except one of the fields between #38 and #68 are not there.

Re: API response change (not the JSON change)

Lilith — Thu, 11 Aug 2016 16:53:36 GMT

Thanks. For now, please have your parser disregard the 72nd position. As I mentioned, that will be used for a new transaction response hash, for which we'll provide documentation in the near future.