How Web Payments will make paying for things more accessible on the web
summary
Web browsers expose a concrete API — the Payment Request API — that replaces repetitive HTML forms with a standardized payment sheet (demoed as a working payment sheet in Firefox Nightly and in Chrome), returns a JSON payment response, and keeps CVV out of browser storage. Merchants declare methods (basic-card, Apple Pay), totals, shipping options and modifiers; the sheet supports localization, keyboard access, event-driven shipping/validation updates, a retry loop for failed payments, and an emerging payment handlers mechanism for native or web wallets.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:02#id 24
- 1:24Marcos Caceres Mozilla
- 1:56Buying and selling stuff
- 2:46Filling out forms
- 30:52Check for data errors
- 36:38The Future
related talks
28mWeb Payments
23mWeb Payment APIs
48mStandard Web Payment APIs
34mKilling the checkout or: How I learned to stop worrying and love Payment Request
18mUnified checkout experience using Web Payment API
37mWeb Payment APIs
06mLightning Talk: Payment Request API in a React Higher-Order Component
33mBuy my mixtape: the Payment Request API in action
