AnsweredAssumed Answered

cnpAPI service not returning content-type in specific cases

Question asked by munshad on Aug 27, 2018

Hi, 

 

We are currently using the pre-live URL for cnpAPI services - authorize, credit and capture. 

URL :  https://payments.vantivprelive.com/vap/communicator/online


We are using Jersey Rest Client to invoke the service and when we request a certain content-type like application/xml, we get the response back with that content-type as expected which is good. 

 

But when the service returns errors like the below ones, the content-type is not sent back, which is causing issues for us as the client assuming the content-type to be application/octect-stream. 

 

 

<cnpOnlineResponse version="12.5"
xmlns="http://www.vantivcnp.com/schema" response="1" message="System Error - Call Vantiv"/>

 

or

 

<cnpOnlineResponse version="1.0" xmlns="http://www.vantivcnp.com/schema" response="3" message="Invalid credentials. Contact eCommerceSupport@vantiv.com."></cnpOnlineResponse>

 

  1. Can the pre-live service always return content-type? 
  2. Will the behavior be similar in production? Or will  production service always return content-type?


Thank you. 

Outcomes