New comments for feature: Link rel=facilitated-payment to support push payments

1 view
Skip to first unread message

Chromestatus

unread,
Feb 24, 2025, 8:58:23 PM2/24/25
to paymen...@chromium.org
Chrome Platform Status
 Comment posted on feature entry:
Link rel=facilitated-payment to support push payments
A comment was added to this feature:
Your next steps:

You are receiving this email because:

  • You are a devrel contact for this feature.

Unsubscribe

Chromestatus

unread,
Feb 24, 2025, 9:02:31 PM2/24/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
1) No. 2) No. 3) No.
Your next steps:

Chromestatus

unread,
Feb 24, 2025, 9:11:23 PM2/24/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
1) Yes. My feature met the minimum automated test coverage and health requirements. 2) We have unit tests coverage for the feature. Below are examples: http://shortn/_mJgckCOQvr http://shortn/_qU3iw0qX3f http://shortn/_K8F3f2x40n http://shortn/_Ig3oOXUfP0 http://shortn/_HbN1jQydkI http://shortn/_J9vHPi9wSC http://shortn/_lVnaWTr95z http://shortn/_8f87oV0AcI Also, this feature was tested by QA at https://launch.corp.google.com/launch/4320162/approver/14626 3) No. All feature related test cases are automated. 4) Actually this feature is being tested by QA, so not sure if I need complete the survey again here. https://launch.corp.google.com/launch/4320162/approver/14626
Your next steps:

Chromestatus

unread,
Feb 25, 2025, 12:43:02 PM2/25/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
unhuihe@, Thanks for filing the survey. As per launch bug, QA testing is inprogress. I will change the test staus to "Review started". Note: we will appprove once QA team completes the testing (https://launch.corp.google.com/launch/4320162/approver/14626)
Your next steps:

Chromestatus

unread,
Feb 25, 2025, 12:44:19 PM2/25/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
junhuihe@, Thanks for filing the survey. As per launch bug, QA testing is inprogress. I will change the test staus to "Review started". Note: we will appprove once QA team completes the testing (https://launch.corp.google.com/launch/4320162/approver/14626)
Your next steps:

Chromestatus

unread,
Feb 26, 2025, 2:41:48 AM2/26/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Could you please expand on (2)?
Your next steps:

Chromestatus

unread,
Feb 26, 2025, 1:48:33 PM2/26/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Sorry for providing the wrong info. For (2), we didn't encounter anything unexpected. So it should be `Yes`.
Your next steps:

Chromestatus

unread,
Feb 26, 2025, 1:58:42 PM2/26/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
(1) I don't know. Enterprise reviewers, please help me decide. The relevant information is: This change will help facilitated push payment flow, where user will get a prompt in the checkout page where a payment link is embedded. But it won't affect any existing Autofill flow. (2) I don't know. Enterprise reviewers, please help me decide. The relevant information is: https://launch.corp.google.com/launch/4320162 (3) This feature does interact with the below policy: https://chromeenterprise.google/policies/#AutofillCreditCardEnabled If the policy is disabled this feature won't work. (4) This launch will help facilitate push payment flow for users. When a supported payment link is embedded in the PSP's checkout page, Chrome will prompt a FOP selector. And user can complete the payment flow in Chrome without switching apps.
Your next steps:

Chromestatus

unread,
Feb 26, 2025, 2:56:46 PM2/26/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Enterprise review: approved in go/launch/4320162
Your next steps:

Chromestatus

unread,
Feb 26, 2025, 5:36:37 PM2/26/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
sadapala@, thanks so much! I think it's already approved in the launchcal now.
Your next steps:

Chromestatus

unread,
Feb 26, 2025, 5:39:27 PM2/26/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
https://launch.corp.google.com/launch/4320162/approver/14626 - Android team completed the testing. Changing the status to "Approved"
Your next steps:

Chromestatus

unread,
Feb 28, 2025, 8:49:21 AM2/28/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Does the user need to have done anything besides visiting a page with the link rel=facilitated-payment before the payment client is notified? This seems like it would allow the payment client to track the user even if they do not end up using the payment client to complete a transaction.
Your next steps:

Chromestatus

unread,
Mar 3, 2025, 6:31:13 PM3/3/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Thanks for bringing the concern! Actually this feature requires users' registration. In case of Google Pay, this happens when the user links their Wallet into Google Pay. Even a FOP selector is shown, if the user didn't select a wallet at all, the payment client actually shouldn't know it. And in the platform UI, we have the checkbox for user to agree terms and conditions. Also, the user can turn off `pay with eWallet` option in the settings page so they can choose to opt out of this feature, by which we convey the control on users' data to users.
Your next steps:

Chromestatus

unread,
Mar 10, 2025, 2:28:11 PM3/10/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Sounds to me like you are saying that until user confirms, the payment client is not notified about anything. Is that correct? If that is the case, how is the payment selector rendered? Also, what you are saying contradicts the explainer here https://github.com/WICG/paymentlink/blob/main/README.md#possible-payment-sequence-using-facilitated-payment-link, step 4. It does not appear like the user has interacted at all with the site containing the link before the payment client is notified? I'm a bit unfamiliar with payments APIs but it seems this is allowing payment client tracking of users? The fact that I eg accept to use some wallet in my phone does not imply I accept to it being allowed to track every site I visit. Are there mitigations for this?
Your next steps:

Chromestatus

unread,
Mar 11, 2025, 7:05:54 PM3/11/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
> Sounds to me like you are saying that until user confirms, the payment client is not notified about anything. Is that correct? Yes this is correct. In our use case, Chrome syncs ewallets account users have (and that's why they're available at settings page). And when a payment link is detected, Chrome will render the fop selector without any interaction with the payment client (google payment platform here). > Also, what you are saying contradicts the explainer here. Thanks for pointing it out! The explainer is a very generic proposal. But since we can utilize chrome sync on Chrome, payment client won't be involved until user confirms as I mentioned above. Please let me know if it addresses your concern or not.
Your next steps:

Chromestatus

unread,
Mar 18, 2025, 10:43:44 AM3/18/25
to paymen...@chromium.org
Chrome Platform Status
A comment was added to this feature:
Sorry, for some reason your comments did not show up on my inbox (possibly because you attempted to change reviewer). LGTM given that this feature does not expose anything to the payment clients unless the user specifically engages with the browser-crafted UI. By the way the launch bug you linked does not seem to be the same as this. Do you have a launch bug? This is needed due to the new UX.
Your next steps:
Reply all
Reply to author
Forward
0 new messages