Soap request does not parse our XML request

[shelly.barnett]

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.

[support]

Hello,

Thank you for contacting our support forum and we look forward to being able to assist you. Also, we genuinely appreciate you providing additional examples to help us determine what may be going on. We're reviewing your request and are reviewing the examples that you have provided. Our team will provide you with an update via this post once we've uncovered additional details.

Regards,

The Plum Voice Support Team

[support]

Hi Shelly,
Our engineers are looking into this as a potential bug. Thank you for bringing this to our attention. We will address this in the normal course of our bug fix schedule.

Regards,
The Plum Voice Support Team

[shelly.barnett]

Hi Shelly,
Our engineers are looking into this as a potential bug. Thank you for bringing this to our attention. We will address this in the normal course of our bug fix schedule.

Regards,
The Plum Voice Support Team

Since I'm a new user and under some deadlines, I want to understand if you are treating this as a bug or enhancement request. Also what is Plum's bug fix or enhancement schedule for something like this.

Best

[support]

Hi Shelly,
Our engineers are looking into this as a potential bug. Thank you for bringing this to our attention. We will address this in the normal course of our bug fix schedule.

Regards,
The Plum Voice Support Team

Since I'm a new user and under some deadlines, I want to understand if you are treating this as a bug or enhancement request. Also what is Plum's bug fix or enhancement schedule for something like this.

Best

Hey Shelly,

We are working on this issue still for you and at this time we're treating it as a bug. When our Devs work on the soap request from the back end everything works as indicated but the issue seems to be a bit more complex in terms of syntax. We're still digging into this issue and should have an update shortly.