Re: [webpayments] What is the appropriate conversational pattern for the API? (#55)

My concern is that if we don't define (at least eventually) as much of this flow as separate low-level APIs then we'll be prescribing far too much.

As the checkout detail interdependencies increase, so will the management complexity increase ... leading merchants to want to design and control their own checkout flows. This is further reason to ensure that we layer this stuff -- create low-level APIs that people can assemble in JS libraries. I do think there's room for a simple high-level checkout API for the "80%" case, but we should be clear that it is composed of lower-level APIs (or can eventually be, where the first one is the API that just handles getting a payment request message to a payment app which will return a payment acknowledgement).

Reply to this email directly or view it on GitHub:

Received on Friday, 12 February 2016 21:34:29 UTC