updated feature: Link rel=facilitated-payment to support push payments

1 view
Skip to first unread message

Chromestatus

unread,
Feb 14, 2025, 6:51:43 PM2/14/25
to paymen...@chromium.org
Chrome Platform Status
 Updated feature entry:
Link rel=facilitated-payment to support push payments
Updates made by junh...@google.com:
  • active_stage_id:
    Old: 5167060035829760
    New: 5200576215777280

  • adoption_plan:
    Old: None
    New: Working with Payment Service Providers and merchants directly.

  • anticipated_spec_changes:
    Old: None
    New: The discussion in an explainer issue[1] proposed to shift the identification of standardized payment methods from the custom scheme to the type attribute, and to use HTTPS URLs for proprietary methods. This may result in eventual changes in link's href formatting, but there're no immediate plans to change it as of now. [1]https://github.com/WICG/paymentlink/issues/3

  • non_oss_deps:
    Old: None
    New: The majority of the code for this feature is in Chromium. However, Chromium does not have any code for providing wallets which would be triggered by this feature. It's up to an embedder to provide these wallets, e.g. in Google Chrome we will do this via Chrome Sync.

  • webview_risks:
    Old: None
    New: Not supported in WebView

Your next steps:

You are receiving this email because:

  • You are a devrel contact for this feature.

Unsubscribe

Chromestatus

unread,
Feb 14, 2025, 7:01:49 PM2/14/25
to paymen...@chromium.org
Chrome Platform Status
Updates made by junh...@google.com:
  • dt_milestone_android_start:
    Old: None
    New: 134

  • interop_compat_risks:
    Old: None
    New: The main risk is It fails to become an interoperable part of the web platform if other browsers do not implement it. If we eventually remove this feature entirely, it won’t break sites, as merchants/Payment Service Providers can still rely on the unfacilitated flow. *Mozilla*: No signal in https://github.com/mozilla/standards-positions/issues/1112 *WebKit*: No signal in https://github.com/WebKit/standards-positions/issues/428, but there’s an open issue in https://github.com/WICG/paymentlink/issues/3 about the use of custom schemes. *Web developers*: Presented at Web Payment Work Group [[minutes](https://www.w3.org/2025/01/30-wpwg-minutes.html#a59a), [slides](https://www.w3.org/2025/Talks/google-paymentlink-20250130.pdf)] and received positive feedback: **gkok**: “if this being applicable to UPI, it seems like an interesting approach. I'd like to explore this more” Received positive signals from ShopeePay at https://github.com/WICG/proposals/issues/150: *“ShopeePay is interested in supporting this proposal as it could offer a more seamless online payment experience.”*

Your next steps:

Chromestatus

unread,
Feb 14, 2025, 7:03:23 PM2/14/25
to paymen...@chromium.org
Chrome Platform Status
Updates made by junh...@google.com:
Your next steps:

Chromestatus

unread,
Feb 14, 2025, 7:04:51 PM2/14/25
to paymen...@chromium.org
Chrome Platform Status
Updates made by junh...@google.com:
  • shipped_android_milestone:
    Old: None
    New: 135

Your next steps:
Reply all
Reply to author
Forward
0 new messages