PaymentRequest IPC connection error

[willhowlett]

Describe the bug
We use adyen-web 5.55.1

Since around 5pm on Monday 22nd April we’ve had the following error on our payments page on a subset of Android browsers

Renderer process could not establish or lost IPC connection to the PaymentRequest service in the browser process

This seems to only be affecting the following or very similar, i.e. SamsungBrowser) useragent

Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/24.0 Chrome/117.0.0.0 Mobile Safari/537.36

I’m not aware of the PaymentRequest API being used in adyen-web (have searched the codebase), but is this in use by your components (v5) in some form and do you know what might be causing this error?

I have raised an Adyen support ticket but they suggested posting here

Many thanks

[longyulongyu]

Hi @willhowlett thanks for reporting.

In adyen-web, we are not using the PaymentRequest api, but it could be that some express payments such as Google Pay or Apple Pay uses it, and not all browsers support it.

If you support the express payments, could you disable them for the mentioned user agent and check if the issue persists?

If you don't support the express payments, we'd like to know how you integrate with adyen-web sdk, are you using WebView or something similar? Which payment method(s) caused the issue or the whole adyen-web was not rendering?

[sponglord]

@willhowlett - any update on this issue? Did you try the above advise?

[willhowlett]

Apologies, I overlooked this

The errors are happening on our main checkout page where we do not have any express payments enabled

We are on 5.55.1 of adyen-web, rendered directly in our app (no webview or anything)

As far as I can tell it is not stopping any payment methods from rendering. I was able to see from our logs that I had unknowingly had the error happen during my session when testing for the issue in browserstack, but there was no errors for me in the frontend when this happened. Based on that it seems like there is no direct customer impact, it would just be good to understand why the error is happening if possible.

Many thanks

[longyulongyu]

@willhowlett thanks to get back to us.
Do you know which device and os version you were using in the browserstack in order to reproduce this issue?
Most likely it's not caused by our sdk, but we would like to know which payment method(s) may cause it.

[willhowlett]

I believe it was

Galaxy S20
Android 10.0
Samsung Browser