https://community.developer.cybersource.com/t5/News-and-Announcements/x-response-subcode-removed/m-p/3913#M33 <P>Recently we removed&nbsp; x_response_subcode from our SIM, Relay and Silent Post responses. The data returned in&nbsp; x_response_subcode was for internal tracking only. I apologize if this caused any issues with your integration.</P> <P><BR />As a best practice, we recommend that when you parse responses for SIM, Relay Response and Silent Post, that you parse the data for name/value pairs rather than parsing for the order that the fields are usually returned in. We do not document the field order for these integration methods and it is subject to change without notice. Parsing our response by field name will prevent errors in your integration should this occur.<BR /><BR /></P> <P>Thanks,</P> <P>&nbsp;</P> <P>Michelle</P> <P>Developer Community Manager</P> Wed, 07 Jul 2010 22:47:57 GMT Michelle 2010-07-07T22:47:57Z https://community.developer.cybersource.com/t5/News-and-Announcements/x-response-subcode-removed/m-p/3913#M33 <P>Recently we removed&nbsp; x_response_subcode from our SIM, Relay and Silent Post responses. The data returned in&nbsp; x_response_subcode was for internal tracking only. I apologize if this caused any issues with your integration.</P> <P><BR />As a best practice, we recommend that when you parse responses for SIM, Relay Response and Silent Post, that you parse the data for name/value pairs rather than parsing for the order that the fields are usually returned in. We do not document the field order for these integration methods and it is subject to change without notice. Parsing our response by field name will prevent errors in your integration should this occur.<BR /><BR /></P> <P>Thanks,</P> <P>&nbsp;</P> <P>Michelle</P> <P>Developer Community Manager</P> Wed, 07 Jul 2010 22:47:57 GMT https://community.developer.cybersource.com/t5/News-and-Announcements/x-response-subcode-removed/m-p/3913#M33 Michelle 2010-07-07T22:47:57Z