cancel
Showing results for 
Search instead for 
Did you mean: 

Issue trying to get merchantDefinedData to work with SOAP transactionProcessor call

Hello!

I am using postman and trying to use a SOAP call https://ics2wstesta.ic3.com:443/commerce/1.x/transactionProcessor  version 1.130 and i am trying to set the merchantDefinedData/field1 field using the below XML Request ...but i get back a  fault. If i take out the section for the merchantDefinedData data the nit works ok. I was wondering if anyone had any suggestions ?

Request....

<soapenv:Body>
<urn:requestMessage xmlns:urn="urn:schemas-cybersource-com:transaction-data-1.130">
<urn:merchantID>mid</urn:merchantID>
<urn:merchantReferenceCode>test_refund</urn:merchantReferenceCode>


<urn:merchantDefinedData>
<urn:field1>field1 data</urn:field1>
</urn:merchantDefinedData>


<urn:purchaseTotals>
<urn:currency>USD</urn:currency>
<urn:grandTotalAmount>1.01</urn:grandTotalAmount>
</urn:purchaseTotals>

<urn:ccCreditService run="true">
<urn:captureRequestID>00000000000000</urn:captureRequestID>
<urn:refundReason>test-refund</urn:refundReason>
</urn:ccCreditService>
</urn:requestMessage>
</soapenv:Body>

 

Fault message 

<soap:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:c="urn:schemas-cybersource-com:transaction-data-1.0">
<faultcode>soap:Client</faultcode>
<faultstring>XML parse error.</faultstring>
</soap:Fault>

 

Thanks for any help!!!!

dgalen13
New Member
1 ACCEPTED SOLUTION

Accepted Solutions

well i believe i solved my own issue ... the order of the xml request seems to matter ... so the below seemed to work...

<soapenv:Body>
<urn:requestMessage xmlns:urn="urn:schemas-cybersource-com:transaction-data-1.130">
<urn:merchantID>mid</urn:merchantID>
<urn:merchantReferenceCode>test_refund</urn:merchantReferenceCode>

<urn:purchaseTotals>
<urn:currency>USD</urn:currency>
<urn:grandTotalAmount>1.01</urn:grandTotalAmount>
</urn:purchaseTotals>

<urn:merchantDefinedData>
<urn:field1>field1 data</urn:field1>
</urn:merchantDefinedData>


<urn:ccCreditService run="true">
<urn:captureRequestID>00000000000000</urn:captureRequestID>
<urn:refundReason>test-refund</urn:refundReason>
</urn:ccCreditService>
</urn:requestMessage>
</soapenv:Body>

View solution in original post

dgalen13
New Member
1 REPLY 1

well i believe i solved my own issue ... the order of the xml request seems to matter ... so the below seemed to work...

<soapenv:Body>
<urn:requestMessage xmlns:urn="urn:schemas-cybersource-com:transaction-data-1.130">
<urn:merchantID>mid</urn:merchantID>
<urn:merchantReferenceCode>test_refund</urn:merchantReferenceCode>

<urn:purchaseTotals>
<urn:currency>USD</urn:currency>
<urn:grandTotalAmount>1.01</urn:grandTotalAmount>
</urn:purchaseTotals>

<urn:merchantDefinedData>
<urn:field1>field1 data</urn:field1>
</urn:merchantDefinedData>


<urn:ccCreditService run="true">
<urn:captureRequestID>00000000000000</urn:captureRequestID>
<urn:refundReason>test-refund</urn:refundReason>
</urn:ccCreditService>
</urn:requestMessage>
</soapenv:Body>

dgalen13
New Member