It is critical for your integrated POS to complete the payment flow on the Clover device while the customer is present. Usually this is handled when the POS receives a charge response. However, the POS must consider and code for other situations. Some examples include:
- Incomplete payment—The customer leaves before completing the payment flow on the Clover device. Example: The merchant requires a signature, but the customer fails to provide one.
- Poor connectivity—An unreliable connection can cause message loss between the POS and Clover device. Example: The POS is set to handle duplicate payment challenges, but the POS does not receive the challenge message. In this situation, the Clover device is waiting for verification of the duplicate challenge 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 about 2 months ago