Fwd: Chrome 138 will omit deprecated payment intent parameters

[Rouslan Solomakhin]

Cross-posting from paymen...@chromium.org.

---------- Forwarded message ---------
From: Rouslan Solomakhin <rou...@chromium.org>
Date: Wed, May 21, 2025 at 1:13 PM
Subject: Chrome 138 will omit deprecated payment intent parameters
To: paymen...@chromium.org

Hi everyone,

Starting with Chrome version 138, the payment intents will omit the following parameters, which have been deprecated since 2022:

certificateChain
data
dataMap
details
id
iframeOrigin
methodName
origin

Please ensure that your Android payment app does not rely on the deprecated parameters.

Only the following parameters will remain in payment intents starting with Chrome 138:

• certificate
• merchantName
• methodData
• methodNames
• modifiers
• paymentRequestId
• paymentRequestOrigin
• topLevelCertificateChain
• topLevelOrigin
• total
• paymentOptions
• requestPayerName
• requestPayerPhone
• requestPayerEmail
• requestShipping
• shippingType
• shippingOptions
• packageName

Chrome 138 is currently in the Canary channel and is planned to go to stable on June 18, 2025.

It's possible to test this change in Chrome by enabling the chrome://flags/#enable-web-payments-experimental-features flag.

WebView implementation of payment intents already omits the deprecated parameters. If your payment app works in WebView, then there are no further follow up actions needed on your part.

Please let us know if you have any questions or concerns about this change.

Sincerely,

Rouslan

Chrome Payments

[Rouslan Solomakhin]

Chrome 138 has been released to the Beta channel.

If an Android payment app relies on any of the parameters in the IS_READY_TO_PAY and PAY intents, that app should be tested to verify that it continues to work in Chrome Beta.

The early release of Chrome 138 to Stable channel is expected to begin on June 18, 2025.