It is critical for your integrated POS to complete the payment flow on the Clover device while the customer is present. Under normal circumstances this is handled when the POS receives a charge response. However, the POS must consider and code for other situations. Some examples include the following:
- Incomplete payment - The customer leaves before completing the payment flow on the Clover device. For example, the merchant requires a signature, but the customer fails to provide one.
- Poor connectivity - An unreliable connection could cause message loss between the POS and Clover device. For example, the POS is set to handle duplicate payment challenges, but a challenge message is not received by the POS. In this situation, the Clover device is waiting for the duplicate challenge to be verified and for the merchant to accept or reject the payment. If the customer is allowed to leave, the payment is still active on the device, and the merchant is unable to proceed with the next transaction. The merchant may then close the payment application on the Clover device, or the POS may call resetDevice; either action can void the payment, but the merchant cannot reprocess the payment because the customer has left.
- POS issues - The POS crashes or the user shuts down the POS in the middle of a payment
Updated 10 months ago