pucman,
from my little experience with Android intents, the only way I could get them to work was basically trial and error configuring the intent or intents, you can have more than one.
The reason a scanner is needed is to trigger the DataWedge intent and play with different intent configurations until your app either loads or is at least is shown as an option to open the payload in the list of apps presented in the dialog box. If the DataWedge app has a simulated trigger to send an intent then that would be all you need to proceed. I haven’t downloaded the app yet, so not sure where to find this feature.
I have looked through some of the DataWedge documentation trying to find the mimeType of the payload. It could be MSR or possibly NFC, I really don’t know.
You may need a permission like this also,
<uses-permission android:name=“android.permission.NFC” />
If you had a scanner in hand, you may also be able to see the intent pass into the logcat?
I got lost reading the documentation, but it looked like you may be able to load your app into a profile in the DataWedge app as a recipient of the output, but I didn’t spend enough time to fully understand it. I was focusing mainly on associating an app with an intent and mimeType.
Nail
Nail