Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66)


> An alternative to Dave's proposal is to also register the payment instruments inside a payment app (or at least an id that the payment app can recognize).

How would this registration work? How, specifically, is it different from what I proposed?

In my proposal, my intent was to communicate that the payment instruments would be registered inside the payment app. I left open how the browser becomes aware of this information, however -- with a suggestion that it could be as simple as tracking payment responses, but we could also have an API call or send message or something. Shane recommended a query or declarative mechanism but that may have authentication issues.

How do you recommend the browser become aware?

Perhaps we mean different things when we say "registered inside the payment app"?

Reply to this email directly or view it on GitHub:

Received on Wednesday, 24 February 2016 20:20:19 UTC