Suggestion: more robust error code / message handling about authnetjson HOT 2 CLOSED

I don't see this as being valuable. There won't be any values contained in those fields that will be unique or otherwise useful. Once you see you the response code (2 is a standard decline, 3 means a voice authorization is required, and 4 means the card needs to be picked up) you know what the status is and can react accordingly. The text in those fields won't be user friendly or unique and you should be creating your own user-friendly messaging in those situations.

from authnetjson.

This was for logging, nothing user-facing. At the moment, I forget the situation that brought this up, though, so it wasn't super important or something I couldn't work around. :)

from authnetjson.