AnsweredAssumed Answered

triPOS timeout issues

Question asked by maikzhang on Oct 15, 2018
Latest reply on Oct 25, 2018 by jwmarin

Like • Show 1 Like1
Comment • 3

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,

frank Oct 25, 2018 7:34 AM

Correct Answer

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...

// use a client with a 5 minute timeout setting. This will (**should**) give enough time for the response 
// to come back in the cases where cardholders forget to remove their cards from the PIN pad (even with all
// the damn beeping and flashing telling them to remove it).
using (var httpClient = new HttpClient() { Timeout = TimeSpan.FromMinutes(5) })
{
    using (HttpRequestMessage message = new HttpRequestMessage(new HttpMethod(method), triposUri))
    {
        // call method to set the triPOS request headers (not shown for brevity)
        CreateTriPOSRequestHeaders(message, messageBody, "application/json", DateTime.UtcNow.ToLocalTime(), isInTestMode);
        message.Content = new StringContent(messageBody, Encoding.UTF8, messageContentType);

        Task<HttpResponseMessage> response = httpClient.SendAsync(message);

        response.Wait(httpClient.Timeout);
        responseMessage = response.Result;
    }
}

See the reply in context

No one else had this question

Outcomes

maikzhang Oct 18, 2018 7:30 AM

Is there any update or suggestion on this?

Actions

frank Oct 25, 2018 7:34 AM

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"?

// use a client with a 5 minute timeout setting. This will (**should**) give enough time for the response 
// to come back in the cases where cardholders forget to remove their cards from the PIN pad (even with all
// the damn beeping and flashing telling them to remove it).
using (var httpClient = new HttpClient() { Timeout = TimeSpan.FromMinutes(5) })
{
    using (HttpRequestMessage message = new HttpRequestMessage(new HttpMethod(method), triposUri))
    {
        // call method to set the triPOS request headers (not shown for brevity)
        CreateTriPOSRequestHeaders(message, messageBody, "application/json", DateTime.UtcNow.ToLocalTime(), isInTestMode);
        message.Content = new StringContent(messageBody, Encoding.UTF8, messageContentType);

        Task<HttpResponseMessage> response = httpClient.SendAsync(message);

        response.Wait(httpClient.Timeout);
        responseMessage = response.Result;
    }
}

1 person found this helpful

Actions

jwmarin Oct 25, 2018 8:05 PM

I have the same issue, integrating triPOS with restaurant point-of-sale software. Using triPOS 5.15 and a Verifone VX 805, the device timeout occurs before users can finish entering card data. Note that it doesn't matter if I use a timeout value greater than 60 seconds with the HttpClient request. The device still has a timeout and the request returns after 60 seconds.

According to our contact at Worldpay, the device software has fixed timeout value that cannot be changed via configuration.

This is a significant issue for our customers, and consequently, for us.

Actions

triPOS timeout issues

Outcomes

Related Content

Recommended Content