question

Just a follow up, we had this happen again today on the same register, really not sure what's causing this or how to clear it out. Please do let me know if you guys have any insight here, this is really messing up our flow.

Hi, can you please help me with sample payment ids? where this issue was encountered?
Also since when are you using this setup? Has this issue been since day 1 or started occurring only lately? Would you be able to share a video of this issue flow? I would like to have a look at the issue itself when it occurs?
Also if you have a look here - https://docs.clover.com/docs/payment-response-reference

payment.transactionSettings.disableDuplicateCheck

^ If true, the device did not check whether the current payment may be a duplicate of an existing payment.
What I guess is that the clover device is thinking the new payment is a duplicate of an already existing payment and this needs to be handled.

Please check in this topic of semi-integration which talks about duplicate check -
https://docs.clover.com/docs/using-per-transaction-settings#duplicate-checking

Let me know if that helped.

This is a very good guess and I would imagine worth testing. We do sometimes frequently have order with similar totals, and I could imagine them getting flagged as duplicates.

We used the remote pay cloud javascript integration for our environment, and it looks like the "setDisableDuplicateCheck" method was never fully implemented here when I look on the github. Still, it looks like I can just set the boolean value through saleRequest.disableDuplicateCheck = true, which I imagine should be good.

Can you verify if this is the proper way to handle this, and also if there are any other downfalls or gotchas we should be aware of with using disabling duplicate checking? (outside, of course, of possible duplicates)

Also, it's tough to get a video because it isn't always reproducable, and I also can't get transaction IDs, because we can never actually get the transactions to go through. It's as if the Clover device won't allow us to even start the transaction because it returns the "existing_payment" code and never actually starts into the payment flow. Hoping this is because of the duplicates though, so if we can just verify the proper way to disable those in the JS environment (regarding using a direct boolean assignment as opposed to a getter / setter method), then I can test that out and see if it clears up the issue!

Just following back up here to see if this is indeed the proper way to disable duplicate checking with the JS SDK. Can you guys please let me know? Thanks.

Two weeks later and still no reply from Clover's team at all, very disappointing. We ended up having to trial and error in our production environment to answer our own question. For anyone in the future that finds this, the answer was indeed duplicate checking, and my method of disabling it above did turn out to be correct it would appear.