Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50)

@cyberphone An Android app is able to query other locally installed apps that are registered to handle "https://bobpay.xyz" and invoke them via intents. Sorry for the confusion. I am hoping that this works in 4 steps:

1. BobPay app registers to handle "https://bobpay.xyz" via an [intent handler](http://developer.android.com/training/app-links/index.html#intent-handler).
2. ShoppingWebsite.com creates a PaymentRequest with one of the supported payment methods being "https://bobpay.xyz".
3. Chrome queries the [PackageManager](http://developer.android.com/reference/android/content/pm/PackageManager.html#queryIntentActivities(android.content.Intent, int)) for locally installed apps that can handle "https://bobpay.xyz"  and finds the BobPay app.
4. Chrome launches the BobPay app via the intent mechanism, passing to BobPay the payment information.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/50#issuecomment-201175807