Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)

Hi @torgo ,

Happy new year and thanks for your feedback!

**To answer your question about the relationship between this proposal and web payment**
This proposal aims to improve the user experience of push payments on the web. While it doesn't introduce a new payment mechanism itself, it provides a way for browsers to passively detect push payment options on a page and offer users a potentially better experience through digital wallets or payment extensions. Compared to the existing web payment APIs like Payment Request, which is a defined as a primary mechanism, this proposal is to potentially help a user agent accelerate a payment which will be presented to the user via other means (e.g. QR code).

**Regarding the venue for this proposal**
We believe HTML is the appropriate venue for standardization because:
- Link relations: All browser-understood link relations are defined in the HTML specification. This proposal introduces a new link relation (rel="facilitated-payment"), making HTML the natural fit.
- Hint mechanism: This proposal acts as an acceleration hint, providing an optional, additional way to convey payment information already present on the page. It doesn't define a new payment mechanism, thus avoiding the complexities of other payment APIs and their standardization processes.

We're open to discussing this further and exploring alternative venues if necessary. However, we believe that standardizing this feature within the HTML specification offers the most straightforward and consistent approach.

**Note**
We're working on prior art consideration work for this proposal and we've decided to rename the `payment` keyword in the `rel` attribute to `facilitated-payment`. This is based on the conflict of [microformat's rel='payment' proposal](https://microformats.org/wiki/rel-payment), and the existing defined `payment` keyword in [IANA registry](https://www.iana.org/assignments/link-relations/link-relations.xhtml). We'll modify this request issue very soon with the latest alignment.

Thanks,
Junhui

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1015#issuecomment-2585001612
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1015/2585001612@github.com>