Adoption2019

Elements in a strategy to increase adoption of Payment Request and payment handlers. Questions? Email Ian Jacobs.

Increase Browser Interoperability

• Create a superior user experience that is interoperable and takes into account merchant feedback (e.g., card-on-file integration, eliminating the sheet, minimal UX, delegation of data requests to payment handlers)
• Investigate secure modal dialog as a way to gain more browser traction of Payment Handler API

Engage Merchants

• Create resources for merchants to explain clearly how to use these APIs to create superior checkout experiences. Note: these might be output from a hackathon.
• Continue to work closely with MAG and in other fora like Merchant Risk Council (MRC)
• Share relevant adoption data (e.g., from Stripe, Google) - ideally demonstrating reduced drop-out, or improved conversion
• Start Business Group within W3C dedicated to merchant use cases and requirements?

Encourage Payment Handler Development

• Document benefits of payment handlers (Justin Toupin and Ian Jacobs to work on this)
• Continue to engage with priority payment service providers around requirements, obstacles.
• What sort of incentive program might we put in place (e.g., a grant) to spur payment handler development? For instance we might organize a formal study that involves comparing a payment handler solution to a traditional solution and evaluate the results.
• Hackathon

Improve the User Experience

• Continue to work with browser vendors on UX improvements (e.g., delegate data requsts to handlers? eliminate the sheet? minimal UX? instrument-level display? default payment handlers?)