Still occurring. And unlike before, I've also now seen it on MacOS Safari User Agents Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/27.0.1 Safari/605.1.15

(Sorry, to be clear, this is using the PaymentRequest API, not the Apple Javascript one)

Definitely looking specific to Google apps on iPad. Another instance: Mozilla/5.0 (iPad; CPU OS 17_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) GSA/343.0.695551749 Mobile/15E148 Safari/604.1

I saw "Safari" and didn't look further on the User Agents, but these appear to be iOS Chrome and the iOS Google app. But testing with both of those myself, they do not behave this way normally or by default.

Noting this behavior persists. I have cards added to the wallet, but the demo site does not present Apple Pay. What is going on?

Where is the code that actually logs "sessionError"? Sounds like your onvalidatemerchant completes without error and your onpaymentauthorized never starts, so what catches and logs that error? (No, I don't know anything about Braintree, and not a whole lot about Apple Pay. I've just implemented it once myself and have hit some cases where I haven't been able to get help either. So I'm empathetic to others struggling and trying to help out any way I can.)

And your error handler isn't triggered either? And nothing else in the browser console? (You might want to reformat your post to make the code easier to follow)

Sadly, I don't have any suggestions for you, but I wanted to commiserate that both: We've seen some similar, unexplained failures The level of support here has been disappointing

In our experience, many of the AMEX sandbox accounts don't work. Or work sometimes, or for some devices/users, but not for others.

Our payment provider requires different certificates in their production and non-production environments. Which does require two Apple Merchant IDs. (We added a ".test" suffix to our non-production one.) I can't speak for how other providers would answer this.

For completeness/posterity, also added to StackOverflow: The annoyingly tiny answer was that the first argument to the PaymentRequest constructor is supposed to be an array. const request = new PaymentRequest([ applePayMethod ], paymentDetails); (Or, make the variable an array from the start. The two examples I'd seen used different approaches, I missed the array brackets.)

(Administrator says using a gmail account instead worked fine.)