Killing the checkout or: How I learned to stop worrying and love Payment Request
summary
Demo shows Payment Request API already implemented in major browsers and reduces form friction while 69% checkout abandonment and 14 fields average quantify the problem. The API returns payment details but does not process payments; integration still needs backend charging. The Payment Handler API is demonstrated as a installable payment web app using a payment-manifest service worker and postMessage resolver flow, with a working Chrome demo today — Payment Handler support limited to Chrome currently.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:22About Me
- 1:09Brief History
- 3:50W3C's solution in 2000
- 5:19State of the checkout today
- 8:15What is PaymentRequest?
- 9:26Initializing
- 9:36Details
- 10:31Options
- 11:15What is method data?
- 13:17Code Overview
- 14:03Showing the Sheet
- 16:43Browser's Payment Methods
- 17:24International Payment Methods
- 18:15Payment Handler demo
- 19:25Implementing a Payment Web App
- 20:47Payment method entry point
- 21:40Registering the app
- 22:19Payment Request Method Data
- 24:20Two-Way Communication
- 24:32Payment Method App
- 26:50Resolving payment method
- 27:42What is Payment Handler API?
- 28:25Summary
- 28:51Caveats
- 29:49Paradigm shift
- 30:42Join the discussion
related talks
28mWeb Payments
45mHow Web Payments will make paying for things more accessible on the web
18mUnified checkout experience using Web Payment API
23mWeb Payment APIs
48mStandard Web Payment APIs
46mMake checkout great again
33mBuy my mixtape: the Payment Request API in action
22mReducing the friction of online payments