Thank you for the prompt and informative response, Trevor; it was articulate and concise.
While we're on the subject (I hate to start another topic for this), is there any reason of which you're aware that the <extraOptions>...</extraOptions> data would be parsed incorrectly on the Authorize.Net side?
I'm submitting the following (via the createCustomerProfileTransactionRequest method)
<extraOptions><![CDATA[x_delim_data=TRUE&x_delim_char=|&x_customer_ip=127.0.0.1]]></extraOptions>
and in the Transaction Detail view of the sandbox site (CIM -> Customer Profile -> View History -> Transaction Detail), the customer IP line looks like this:
Customer IP: 127.0.0.1]]>
It appears that the closing CDATA tag is being appended. In fact, it seems that whichever parameters are included first and last in the list are affected in this way.
To explain further, in the "Merchant Email Receipt" that is generated as a result of the API request, I find the following (using the same <extraOptions> data that is pasted above):
========== MERCHANT DEFINED =========
%3c!%5bCDATA%5bx_delim_data : TRUE
In this instance, it appears that the opening CDATA tag is being prepended (and URL-encoded).
Any thoughts as to why this is happening? Am I doing something wrong on my end?
Thanks in advance.