question

ACTION_CLOVER_PAY should be used when you want the merchant to give the customer a choice of any supported tender type (check, cash, credit/debit, manual card entry, other). A merchant facing screen will appear allowing the merchant to select the tender type. Note that this also works with multi-device tethering setups, meaning that if you launch ACTION_CLOVER_PAY on a merchant-facing Clover Station which is USB tethered to a customer-facing Clover Mini, then the customer-facing Mini will prompt for a card-present payment.

ACTION_SECURE_PAY should be used when you want to jump directly to a card payment (it supports manual card entry), this will exclude cash, check and some other merchant-facing only tender types. This method does not support multi-device tethering setups. This means the above tethering example does not apply, the card-present payment will always be launched on the merchant-facing device and tethering will be ignored.

There is also the PaymentConnector#sale method which operates similarly to ACTION_SECURE_PAY in that it only supports customer-facing tenders and excludes cash, checks, etc but this method is aware of multi-device tethering setups.

During development we came across an issue recently where the paymentconnector.sale() request is creating an extra PayActivity Receipt Screen on the Clover Station Solo. This extra screen does not appear on any of the other Clover devices we test with (Flex, Mini, Duo.)

This is leading to another issue when the merchant also has "Automatically print customer receipt after each order". If this option is turned on, the extra screen is also causing extra receipts to print. Do you know how we would avoid this issue? Is there a different way we could go about using the paymentConnector or SaleRequest?