Other than the "id" field on each transaction type and the orderId field are there any other fields that will be passed back on a transaction response with the values that were passed?
I'm thinking perhaps of custom fields that can be passed.
Thanks.
Jim,
The spec includes an optional element called merchantData available on several transaction types, that has 3 child elements (affiliate, campaign and merchantGroupingId) that can be used to support the scenario you outline above. Section 4.238 of the latest version of the spec provides additional information. Thanks.
Regards,
Joe
Jim,
The spec includes an optional element called merchantData available on several transaction types, that has 3 child elements (affiliate, campaign and merchantGroupingId) that can be used to support the scenario you outline above. Section 4.238 of the latest version of the spec provides additional information. Thanks.
Regards,
Joe