Hi there,
We are now integration with Vantiv through triPOS service and we are using the similar code as the suggestion from the doc here (triPOS Direct - How to Generate a Request ).
We met some cases that the request is timeout on client side when waiting for the response from triPOS services (and I assume the default timeout for the httpClient is 100s), however, the finally transaction is successful on Vantiv side. This could cause the issue in our App that not mark the spec payment with correct status. We can increase the timeout setting for this, however, this should not be a perfect solution on my perspective. So I am wondering if there is any suggestion from Vantiv for such cases?
HttpResponseMessage respMessage = null;
using (var httpClient = new HttpClient())
{
var message = new HttpRequestMessage(HttpMethod.Post, new Uri(url));
this.CreateRequestHeaders(message, postBody, contentType, developerKey, developerSecret);
Task response = httpClient.SendAsync(message);
response.Wait();
respMessage = response.Result;
}
Thanks,
Going to need a little more information about the environment, for example:
- Is the triPOS service located at the host running, and is your request using the right TCP port?
- Firewall, A/V or web filter (i.e. websense, zscaler, etc.) blocking the request?
- Can you run Fiddler or Wireshark during your request to see if it's going to the right location and/or if there's any type of response that's getting "swallowed"?
FWIW, when I'm performing a request, I give the HTTP client 5 minutes to timeout; reason-being, since the request is actually waiting for user input from the PIN pad, you'll want to give them enough time to get their credit card out, put it in the device, fat-finger their PIN a couple of times, respond to the prompts, sign the device, etc. etc. etc...