We several clients with Minis tethered to Stations. Our app responds to both merchant and customer tenders. When a sale is put through and the customer facing Mini displays payment options, some clients are accidentally hitting our tender when they wish to pay with a standard contactless debit or credit card. That's our first bit of feedback, that potentially the positioning of the tenders should change somehow if you get the same feedback from elsewhere.
The main question though is that when our app is launched it is apparently not given the clover.intent.action.CUSTOMER_TENDER intent action. It's working fine on the sandbox devices, but for production merchants it's either not given an action at all, or it's given the MERCHANT_TENDER action. I've tried every flow I can think of to launch the app via the secure payments activity on a Mini but cannot repro what they are seeing.
Have you guys ever seen anything like this?
Here is the manifest entry for the merchant and customer tender. I have a theory that enclosing both intent filters in the same activity is problematic on production but it's a shot in the dark :)
<activity android:name=".activities.MainActivity" android:configChanges="keyboard|keyboardHidden" android:exported="true" android:windowSoftInputMode="adjustPan"> <meta-data android:name="clover.intent.meta.CUSTOMER_TENDER_IMAGE" android:resource="@mipmap/mini_tender" /> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> <category android:name="android.intent.category.DEFAULT" /> <action android:name="clover.intent.action.MERCHANT_TENDER" /> <action android:name="clover.intent.action.CUSTOMER_TENDER" /> </intent-filter> </activity>