We are in the process of moving from using ACTION_SECURE_PAY and ACTION_CLOVER_PAY to the PaymentsConnector (it seems to offer a lot of benefits and remove a bunch of logic we previously needed in our code).
Unfortunately, upon testing it looks like the PaymentConnector is launching the payment flow on the primary device when in a tethered scenario.
Is this expected behaviour? I am struggling to find documentation stating that, and also what code/logic we need to put in place to handle it?
Thanks
Lee