Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447)

> Nothing prevents a payment app from communicating with other parties. That is neither required nor forbidden by this API

What I said (or meant at least), is that the API (particularly when used with native Apps), requires OOB calls for anything outside of the core API.  Putting it another way: The API fits card-emulating Apps like Android Pay but may turn out to be less useful for more advanced schemes, designed from scratch (including Saturn).

-- 
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/447#issuecomment-283971839

Received on Friday, 3 March 2017 14:49:16 UTC