Soap request does not parse our XML request
Posted: Fri Oct 25, 2019 2:40 pm
I have trying for a few days to get our request XML to work with both your Soap Tester and call flow. I will not return a response which included the data I placed into the XML. We current use this request with another vendors product and it work in our production environment. We have a situation that requires us to use the current software if possible to avoid another audit. I will show you below examples of what I get from the Soap Tester as well as another tester that works fine.
Hope you can help us resolve this.
WSDL
https://ivr.paystationdeploy.com/IVRDat ... singlewsdl
Request XML used in Parameters
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://ivr.paystation.com">
<SOAP-ENV:Body>
<ns1:FirstRequest>
<ns1:IVRProfileId>3</ns1:IVRProfileId>
<ns1:CustomerPhone>2061234567</ns1:CustomerPhone>
<ns1:SecurityResponse>0000</ns1:SecurityResponse>
</ns1:FirstRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Raw Request as shown by Plum Soap Tester
it seems no affect on Request at all
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://ivr.paystation.com">
<SOAP-ENV:Body>
<ns1:FirstRequest/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The tester does seem to have sent the request since the response has some information created by our software indicationg that the IVRProfileID is invalid. It also appears on our log file at server as received and responded.
Using a different Soap Tester
Results are as expected
WSDL
https://wsdlbrowser.com/soapclient?wsdl ... rstRequest
XML Request
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://ivr.paystation.com">
<SOAP-ENV:Body>
<ns1:FirstRequest>
<ns1:IVRProfileId>3</ns1:IVRProfileId>
<ns1:CustomerPhone>2061234567</ns1:CustomerPhone>
<ns1:SecurityResponse>0000</ns1:SecurityResponse>
</ns1:FirstRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Result
Result:
<s:Envelope
xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<FirstRequestResponse
xmlns="https://ivr.paystation.com">
<CustomerResponse
xmlns:a="http://schemas.datacontract.org/2004/07/IVRData"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<a:Customer>
<a:ACHAccount i:nil="true"/>
<a:ACHRouting i:nil="true"/>
<a:AMEX_Accepted i:nil="true"/>
<a:AddressIdentifier i:nil="true"/>
<a:BooleanIdentifier i:nil="true"/>
<a:CardCVV i:nil="true"/>
<a:CardExp i:nil="true"/>
<a:CardNumber i:nil="true"/>
<a:CustomerAddress i:nil="true"/>
<a:CustomerCity i:nil="true"/>
<a:CustomerIdentifier1 i:nil="true"/>
<a:CustomerName i:nil="true"/>
<a:CustomerPhone>2061234567</a:CustomerPhone>
<a:CustomerState i:nil="true"/>
<a:CustomerZip i:nil="true"/>
<a:Discover_Accepted i:nil="true"/>
<a:DueDate i:nil="true"/>
<a:Error i:nil="true"/>
<a:FailureMessage i:nil="true"/>
<a:FeeAmount i:nil="true"/>
<a:IVRClientName>Retail Lockbox Technology Group</a:IVRClientName>
<a:IVRProfileId>3</a:IVRProfileId>
<a:Identifier1Name>Account Number</a:Identifier1Name>
<a:Mastercard_Accepted i:nil="true"/>
<a:OtherInfo i:nil="true"/>
<a:PaymentType i:nil="true"/>
<a:PaymentTypeACH i:nil="true"/>
<a:PaymentTypeCARD i:nil="true"/>
<a:PrincipalAmount i:nil="true"/>
<a:ProcessSuccessful>false</a:ProcessSuccessful>
<a:SecurityPassed>True</a:SecurityPassed>
<a:SecurityResponse i:nil="true"/>
<a:TotalAmount i:nil="true"/>
<a:TransactionId i:nil="true"/>
<a:TransactionSuccessful i:nil="true"/>
<a:TransactionToken i:nil="true"/>
<a:UploadSuccessful i:nil="true"/>
<a:UseAddressIdentifier>false</a:UseAddressIdentifier>
<a:UseBooleanIdentifier>false</a:UseBooleanIdentifier>
<a:Visa_Accepted i:nil="true"/>
</a:Customer>
</CustomerResponse>
</FirstRequestResponse>
</s:Body>
</s:Envelope>
Result of this call (1st of 6 or 7) is correct. We don't know if there is anything we can do on Plum Side, or is this a problem that can't be fixed without software changes to our platform.
Hope you can help us resolve this.
WSDL
https://ivr.paystationdeploy.com/IVRDat ... singlewsdl
Request XML used in Parameters
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://ivr.paystation.com">
<SOAP-ENV:Body>
<ns1:FirstRequest>
<ns1:IVRProfileId>3</ns1:IVRProfileId>
<ns1:CustomerPhone>2061234567</ns1:CustomerPhone>
<ns1:SecurityResponse>0000</ns1:SecurityResponse>
</ns1:FirstRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Raw Request as shown by Plum Soap Tester
it seems no affect on Request at all
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://ivr.paystation.com">
<SOAP-ENV:Body>
<ns1:FirstRequest/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The tester does seem to have sent the request since the response has some information created by our software indicationg that the IVRProfileID is invalid. It also appears on our log file at server as received and responded.
Using a different Soap Tester
Results are as expected
WSDL
https://wsdlbrowser.com/soapclient?wsdl ... rstRequest
XML Request
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://ivr.paystation.com">
<SOAP-ENV:Body>
<ns1:FirstRequest>
<ns1:IVRProfileId>3</ns1:IVRProfileId>
<ns1:CustomerPhone>2061234567</ns1:CustomerPhone>
<ns1:SecurityResponse>0000</ns1:SecurityResponse>
</ns1:FirstRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Result
Result:
<s:Envelope
xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<FirstRequestResponse
xmlns="https://ivr.paystation.com">
<CustomerResponse
xmlns:a="http://schemas.datacontract.org/2004/07/IVRData"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<a:Customer>
<a:ACHAccount i:nil="true"/>
<a:ACHRouting i:nil="true"/>
<a:AMEX_Accepted i:nil="true"/>
<a:AddressIdentifier i:nil="true"/>
<a:BooleanIdentifier i:nil="true"/>
<a:CardCVV i:nil="true"/>
<a:CardExp i:nil="true"/>
<a:CardNumber i:nil="true"/>
<a:CustomerAddress i:nil="true"/>
<a:CustomerCity i:nil="true"/>
<a:CustomerIdentifier1 i:nil="true"/>
<a:CustomerName i:nil="true"/>
<a:CustomerPhone>2061234567</a:CustomerPhone>
<a:CustomerState i:nil="true"/>
<a:CustomerZip i:nil="true"/>
<a:Discover_Accepted i:nil="true"/>
<a:DueDate i:nil="true"/>
<a:Error i:nil="true"/>
<a:FailureMessage i:nil="true"/>
<a:FeeAmount i:nil="true"/>
<a:IVRClientName>Retail Lockbox Technology Group</a:IVRClientName>
<a:IVRProfileId>3</a:IVRProfileId>
<a:Identifier1Name>Account Number</a:Identifier1Name>
<a:Mastercard_Accepted i:nil="true"/>
<a:OtherInfo i:nil="true"/>
<a:PaymentType i:nil="true"/>
<a:PaymentTypeACH i:nil="true"/>
<a:PaymentTypeCARD i:nil="true"/>
<a:PrincipalAmount i:nil="true"/>
<a:ProcessSuccessful>false</a:ProcessSuccessful>
<a:SecurityPassed>True</a:SecurityPassed>
<a:SecurityResponse i:nil="true"/>
<a:TotalAmount i:nil="true"/>
<a:TransactionId i:nil="true"/>
<a:TransactionSuccessful i:nil="true"/>
<a:TransactionToken i:nil="true"/>
<a:UploadSuccessful i:nil="true"/>
<a:UseAddressIdentifier>false</a:UseAddressIdentifier>
<a:UseBooleanIdentifier>false</a:UseBooleanIdentifier>
<a:Visa_Accepted i:nil="true"/>
</a:Customer>
</CustomerResponse>
</FirstRequestResponse>
</s:Body>
</s:Envelope>
Result of this call (1st of 6 or 7) is correct. We don't know if there is anything we can do on Plum Side, or is this a problem that can't be fixed without software changes to our platform.