#kgeark_error
brisk oarBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1432406530057179196
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
merry turret
Hello 👋
The canMakePayment() function checks with the PaymentRequest API to determine whether or not Goole/Apple Pay payment methods are available
lucid snow
We are seeing in instances where the GPAY button does not even show as an option - this happens for some diners but not all
We continue to receive diner and partner complaints that the Google Pay button intermittently fails to display even when:
The diner’s device/browser supports Google Pay.
The diner has a valid card saved to their Google Pay wallet.
Stripe is correctly configured as the processor.
merry turret
Right, if the result returned from canMakePayment() includes {googlePay: false} this indicates that google pay is not supported and we do not show it
lucid snow
If all of the following are true:
The diner’s device/browser supports Google Pay.
The diner has a valid card saved to their Google Pay wallet.
Stripe is correctly configured as the processor.
What would cause googlePay to return as False?
It tends to be for certain sessions and not all
merry turret
Some browser privacy settings or extensions might block it
Here is a useful test page you can use to check the browser session: https://4242.io/test/payment-request-button/
In the Output section, the results for canMakePayment are printed out
You can see something similar for the Exrpess Checkout Element here; https://4242.io/test/express-checkout-element/
lucid snow
@lucid vigil for vis
The current stripe library we are using:
"@stripe/react-stripe-js": "^2.1.0",
"@stripe/stripe-js": "^1.52.1",
What is the latest stable SDK version we should look into upgrading too?
merry turret
What is the latest stable SDK version we should look into upgrading too?
Why are you looking to upgrade? I would need much more context about your goals to make any recommendation.
Up until now, the question has been about the visibility of Google Pay
lucid snow
Since we are on an older version could the issue be cause by being behind on our versions?
merry turret
No
That would not impact the values returned by the PaymentRequest API. That API is a browser standard, not something controlled by Stripe
lucid snow
Got it - thank you for that
merry turret
There are a lot of different parts, especially for digital wallets! It can be hard to keep them all straight
Can you clarify exactly what Stripe products you are using? Payment Request Button, Payment Elmement, Express Checkout Element?
lucid vigil
We are currently using Payment Request Button
Im apart of the same team dealing with the above issue
merry turret
Got it. Do you have a front-end I could view?
lucid vigil
The actual UI or code snippets?
merry turret
The actual UI. digital wallet availability is often a result of the specific device/browser configuration. Unless it's never available, the problem isn't your code.
I tested my browser with the https://4242.io/test/payment-request-button/ site and I can see {googlePay: true} being returned consistently
lucid vigil
You can view the digital wallets UI here by adding an item to your cart and proceeding to the checkout page https://www.twoeggsrestaurant.com/store/14889/Two Eggs Restaurant Stockbridge
merry turret
Thanks, testing
I am seeing Google Pay as available
This suggests the issues where your customers/testers are not able to see Google Pay is due to the browser/session
It's important to note that having a Card saved to a browser is not the same as having a card saved to Google and being signed in to a Google Account in the browser.
lucid vigil
Yes, we thought this as well but an internal user with a valid card in their Google wallet was not seeing the Gpay button unless they throttled their browser network.
There was another instance where a user was seeing the GPay button, but after restarting their laptop and re-testing, the GPay button was missing for a few hours and without any changes started to reappear again.
Any insights to this behavior?
merry turret
an internal user with a valid card in their Google wallet
Are they signed in to their Google account in the Chrome browser though.
lucid vigil
For the internal user testing, yes. For the other instance I can't say, for sure at the moment
merry turret
With respect to the throttling, I can assure you my connection is very fast and I do see Google Pay consistently rendered.
It sounds like there could be some extensions possibly blocking the resolution of the requests to google. If you review the network requests when you load the checkout page, you can see the requests to pay.js. This is loading the Google Pay functionality directly from Google.
lucid vigil
We will continue investigating the root cause. Thank you for your help @lucid snow Feel free to ask anymore questions you may have.
merry turret
Yeah, the more I tinker and think, the more I suggest watching the request to Google for pay.js. If you can identify some blocking behaviors that would help suggest what is wrong here.
lucid snow
Adding in @frozen tree to this thread as she is our FE dev manager
merry turret
We close threads due to inactivity but you can always refer back to this thread for reference later