Difference between revisions of "Web Payments"
From MgmtWiki
m (→Context) |
(→Full Title or Meme) |
||
| Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
| − | [[Web Payments]] as implemented by the W3C and browser manufacturers. | + | [[Web Payments]] as implemented by the W3C and browser manufacturers as opposed to [[Open Banking]] as implemented by the banks. |
| + | |||
==Context== | ==Context== | ||
* Payment Request API was originally focused on streamlining checkout ie. extracting money from the user was fast as possible. Security of user assets was not a goal. | * Payment Request API was originally focused on streamlining checkout ie. extracting money from the user was fast as possible. Security of user assets was not a goal. | ||
Revision as of 12:46, 29 October 2020
Full Title or Meme
Web Payments as implemented by the W3C and browser manufacturers as opposed to Open Banking as implemented by the banks.
Context
- Payment Request API was originally focused on streamlining checkout ie. extracting money from the user was fast as possible. Security of user assets was not a goal.
- in late 2020 the focus switched to methods that are of "High Value to the industry", namely low friction user authentication. Security of user assets is still not a goal.
- Open Banking mean which has focused on Secure Customer Authentication, again focusing on the needs of the Financial Sector not on the consumer.
- Solving the "NASCAR Problem" of two many options was rejected by brands that wanted to be in the consumers face and merchants that wanted to control the order of brands on their site.
References
[[Category: Finance] [[Category: Standard]
