Certain push payment flows can cause high friction for users (e.g. display of a QR code that the user needs to scan with an eWallet app). Browsers may have the ability to more easily facilitate these payment flows (e.g. if the user has a wallet installed on their device that supports the underlying payment method for the displayed QR, or has a browser extension for the supported eWallet). This is a proposal for <link rel="payment"> that browsers can read to better assist users with payments.
Introduction
Certain push payment flows can cause high friction for users (e.g. display of a QR code that the user needs to scan with an eWallet app). Browsers may have the ability to more easily facilitate these payment flows (e.g. if the user has a wallet installed on their device that supports the underlying payment method for the displayed QR, or has a browser extension for the supported eWallet). This is a proposal for
<link rel="payment">that browsers can read to better assist users with payments.Read the complete Explainer.
Feedback
Please provide all feedback below.
I welcome feedback in this thread.
cc @rsolomakhin @aneeshali @stephenmcgruer