Here's the use case:
- The POS initiate a payment on Clover over the semi-integration
- The POS is unexpectedly down before it has enough time to finish the transaction (it's down because of many possible reasons: power lost, OS frozen, POS closed/killed - especially when the POS is running in a browser, network connect between it and the clover is lost/interrupted....)
- When POS comes back, employees start a new payment or re-initiate the previous failed payment: it will fail because it has no idea about the current state of Clover.
If the Connector has some method for the POS to basically tell the Clover 'hey, forget anything you have been told / get out anything you're doing' every time before it tells the POS to initiate a payment (or when the POS try to establish connection to the Clover), then it will make the integration more resilient, and fool proof for checkout employees.
The Clover often is exclusively designated for its corresponding POS in this integration, so there shouldn't any other thing for the POS to interfere with by calling this proposed method.
