Standard Web Payment APIs
summary
Claims that adopting the web Payment Request API cuts mobile form pain and lowers checkout abandonment, with a live demo using new PaymentRequest(), a web component + Java wrapper served from Jetty, and browser-provided UI that prefills cards but still requires CVC still required. Supported gateways include Google Pay/Android Pay and Apple Pay integration, while Stripe/PayPal must add support. Limitations: no unified multi-factor flow, no pre-validation of card with issuer, limited UI customization, and HTTPS is mandatory. Progressive Web App and autocomplete attributes are used to minimize typing.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 10:34Progressive web apps overview
- 13:47Payment form challenges
- 17:28Payment Request API demo
- 25:43Live demo walkthrough
- 37:17Current challenges
- 44:35Q&A session
related talks
23mWeb Payment APIs
37mWeb Payment APIs
28mWeb Payments
45mHow Web Payments will make paying for things more accessible on the web
18mUnified checkout experience using Web Payment API
34mKilling the checkout or: How I learned to stop worrying and love Payment Request
59mPayments
22mReducing the friction of online payments
