question

agnesdrent avatar image
agnesdrent asked David Marginian edited

Cloud Pay Display Huge delay on to connect and get device ready - Cloud Semi integration

We are a partner (Ocuco) that is completing a semi-integration between the Flex device and our POS through our middleware solution called Hub. We are using Cloud Pay but we notice a 5-6 second delay in transactions compared to non-integrated.

We have quite a good wifi /network connection but we notice a big delay on connecting to the Device.

Cloud Pay display is running on the flex device. We notice that on connect it takes between 2-4 seconds to get "device-ready". It takes an extra 1-2 sec to see the payment request on the flex device. We are quite worried that we will end-up with a 10 sec delay at the customer site.

We already have a POS and we want to create the integration via our middleware called Hub.

We cannot keep the connection open. So we use the following schema.

1632923194465.png

1632923075212.png

Is the delay to get device ready withing average? Can we improve it in some way?

We need the answer this week because we have to decide whether we can start development on Monday based on your answer. Thanks in advance for your help.

Remote Pay Cloud
1632923075212.png (35.4 KiB)
1632923194465.png (30.4 KiB)
10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
David Marginian avatar image
David Marginian answered David Marginian edited

I just ran a few tests on sandbox with a Flex using our starter example (https://github.com/clover/remote-pay-cloud-examples/tree/master/remote-pay-cloud-starter) and I am consistently getting onDeviceReady within a few hundred milli-seconds when CPD is running. When CPD is not running the same takes several seconds (which is expected).

It seems you have some other architecture in the way, so it is hard to say what is going on. Honestly, I would not recommend what you are doing. Going through your middle-ware is much more difficult to manage (than a direct/consistent websocket connection from the POS) and may cause issues unless your implementation is solid. Hopefully you have a good reason for doing this.


10 |2000 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community