Web Payment APIs
summary
Claim: implementing the standard Web Payment APIs increases conversions and makes the user click pay more often by surfacing a native platform flow. Concrete tools and constraints are shown: the Payment Request API, support for basic-card and third‑party methods, and a Polymer web‑components demo that collects shipping, updates totals on shippingaddresschange, simulates a server round trip to a payment gateway, and completes the UI. Support is roughly half of browsers today and the demo works end‑to‑end with server validation simulated.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:36Why is this important
- 2:39Mobile checkout forms
- 5:37Payment request API
- 8:16Payment request constructor
- 13:02Payment request response
- 15:02Data binding
- 16:02Payment request
- 17:02Payment request UI
- 18:02Error dialog
- 19:02Request payment
- 21:02Accepting network cars
related talks
37mWeb Payment APIs
48mStandard Web Payment APIs
45mHow Web Payments will make paying for things more accessible on the web
28mWeb Payments
18mUnified checkout experience using Web Payment API
34mKilling the checkout or: How I learned to stop worrying and love Payment Request
16mSign-in and Payments without Forms
22mReducing the friction of online payments
