Currently, AuthNet returns an error if the order of JSON object elements is not exactly as written in the API documentation. Since the JSON spec allows for object elements to be in any order, standard serialization tools on various development platforms don't construct JSON strings as AuthNet prescribes.
Removing the order restriction would greatly simplify the work requried to integrate with the Authorize.Net API.
Thanks!