Privacy changes to IS_READY_TO_PAY intent

[Rouslan Solomakhin]

Hello,

To align with the goals of the Privacy Sandbox, Chrome will be removing the following fields from the IS_READY_TO_PAY Android intent, similar to the upcoming changes to the "canmakepayment" service worker event:

• origin
  
• topOrigin
• topLevelOrigin
• paymentRequestOrigin
• iframeOrigin
  
• certificateChain
• topLevelCertificateChain
• methodNames
• methodData
• data
  
• dataMap

This change can be tested by setting the chrome://flags/#identity-in-can-make-payment to the "Disabled" value in Chrome Canary.

If your app needs these fields, please reach out to let us know about your use cases.

The PAY intent is not affected by this change.

Cheers,

Rouslan

[Rouslan Solomakhin]

Hello,

The flag name has been changed in Chrome 108 (currently in Canary) from chrome://flags/#identity-in-can-make-payment to:

  chrome://flags/#clear-identity-in-can-make-payment

The feature may now be tested by setting this flag to "Enabled".

Cheers,

Rouslan

[Rouslan Solomakhin]

Hello,

The privacy improvements for IS_READY_TO_PAY are now enabled by default in Chrome 111 (currently in Canary). Please test your payment apps to ensure that they continue to work correctly.

Cheers,

Rouslan

(A temporary flag chrome://flags/#add-identity-in-can-make-payment can be used to re-enable passing the fields in IS_READY_TO_PAY.)