v135 · dom

Link rel=facilitated-payment to support push payments

Adds support for <link rel="facilitated-payment" href="..."> as a hint that the browser should notify registered payment clients about a pending push payment.

concepts

  1. rel=facilitated-payment

    The raw markup — emit a <link> and probe the browser for relList support.

  2. UPI / Pix push-payment flow

    The three-actor scenario from the Chrome blog: merchant emits the link, browser routes to a registered payment-handling PWA, app shows its own sheet.

  3. UPI handshake walkthrough

    A three-lane swimlane diagram for a UPI push payment. Each step lights up: merchant emits the link, Chrome recognises it, the wallet opens, the user confirms, the bank settles. End-to-end view with no Payment Request modal.

  4. Payment Scheme Explorer

    Compare UPI, PIX, FedNow, PromptPay, PayID, and Open Banking side by side. Fill in each scheme's fields and see the generated <link rel="facilitated-payment"> element, plus a support matrix for browser wallets.

why it shipped

This feature lets the browser assist users in push-based payment flows by facilitating the transfer of payment information between the payment provider (on the payee side) and the payment client (on the payer side). The feature lays the foundation for payment integrators in streamlining push-based payment flows, towards a consistent and low-friction user experience. Explainer: https://github.com/WICG/paymentlink/blob/main/README.md

references