Hey Guys,
We have around 15 Clover devices in our store, and we have a semi integration that uses the Javascript SDK for communication over the secure network pay display. When we go to refund a charge, we have to call a function from the JS SDK and pass in the associated transaction. If we refund a charge from the same register / machine that the charge was created from, the refund happens very quickly, within a second or two. If, however, we process the refund from a different register / Clover device pairing, it takes sometimes upwards of three to four minutes to complete. I've placed timers in my code right before the call to connector.refundPayment, and inside of the callback function, and can verify that all of the time being consumed during our card present refund process is indeed being consumed waiting on the Clover device to respond. This happens consistently and is reproducible in our environment. Any ideas why we would have slow performance on refunds when they're issued from another Clover device?
