Upcoming changes to payment response validation [Android Native Apps Only]

[Sahel Sharifymoghaddam]

If you don’t make android native payment apps, you can stop reading now.

TL;DR: Chrome validates “methodName” and “details” fields in a payment response with RESULT_OK result.

Summary

If the activity result of a payment response received from the invoked payment app is set to RESULT_OK, then Chrome 84 and later will check for non-empty “methodName” and “details” in its extras. If the validation fails Chrome will return a rejected promise from request.show() with one of the following developer facing error messages:

'Payment app returned invalid response. Missing field "details".' 'Payment app returned invalid response. Missing field "methodName".'

Chrome 84 is currently available in Canary and Dev. It is expected to start rolling out to the Stable channel around the 14th of July.

Background

Prior to M84 Chrome would resolve the request.show() promise as long as the activity result of the payment response received from the invoked android app was RESULT_OK without validating “methodName” and/or “details” in the response’s extras bundle. The validation change landed in M84 aligns with Chrome validation for payment responses received from web based payment handlers.

Please reply to this email with any questions/concerns and we will get your issues resolved.

Cheers,

Sahel