Re: [w3ctag/design-reviews] Secure Payment Confirmation (#544)

@ianbjacobs I fully agree with this.  However, my [essentially only] concern are the things happening *before* SPC finally is invoked.  This part is at least as important as SPC since it is necessary in order to build a system.  It also has huge impacts on the UX.

Since this part is (by design) _undefined_, Google will most likely find it quite challenging writing developer information of the kind they have done for other Web APIs.  The only workable solution AFAICT, is referring to the proprietary checkout APIs provided  by Stripe, Adyen, Wordline, etc.

It is obvious that Stripe & Co need this flexibility in order to lock-in merchants into their respective worlds. What is not equally clear is if this properly serves the market consisting of a gazillion of _consumers_, _merchants_, _payment intermediaries_, and _banks_.

It is a pity that none of the other browser vendors have expressed a single word on the WPWG mailing list regarding their support of this project.
@wseltzer @sideshowbarker  

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/544#issuecomment-902427691