#vgontier_google-pay-unavailable

1 messages · Page 1 of 1 (latest)

brave troutBOT
#

👋 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/1486725422514442280

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

surreal bluff
#

Hello, can you share more about your integration? For example, are you using CheckoutSessions or Elements? Are you following a specific guide? What device and browser are you using? And are you logged into a Google account with a card in it's wallet?

unkempt jay
#

Hello, sorry if its in french, but you can see that on my browser session two cards are availables and one has google pay enabled

#

we're using only elements

#

I'm on Windows with Chrome latest build

surreal bluff
#

Thanks for confirming. Are you using the Payment Element, Express Checkout Element, both, or something else?

unkempt jay
#

We’re not using the Payment Element or the Express Checkout Element. I think we’re using Stripe’s legacy Payment Request Button flow: stripe.paymentRequest(...) with PaymentRequestButtonElement

surreal bluff
#

I see. What payment method type are you seeing instead of Google Pay?

unkempt jay
#

Stripe returns Link as available instead of Google Pay. We don’t explicitly render Link in our UI, but canMakePayment() returns link: true and googlePay: false, so the Google Pay button is not shown.

#
canMakePaymentResult : {
    "applePay": false,
    "googlePay": false,
    "link": true
}
#

in the wallet-config call I can see that google pay is available too :

google_pay_available: {payment_request_button: true}
surreal bluff
#

You can try logging out of your Link account to confirm the Google Pay flow works.

unkempt jay
#

how to log out from link lol ?

#

but that's highly possible that it is the main problem

surreal bluff
#

Are you using test or live mode?

unkempt jay
#

test mode

surreal bluff
#

If you click the button to pay with Link, it should open a modal with three dots in the top right and clicking that has a option to log out 🙂

unkempt jay
#

That makes sense, but in our current implementation we don’t actually render the Link button when Stripe reports Link. We detect link: true in canMakePayment(), log it, and don’t display the payment request button, so we can’t access the Link modal logout option from our page

#

Isn't there a way to log out anywhere else ?

#

is it bind to a specific domain ?

#

when trying on a fresh chrome profile I still have
{ "applePay": false, "googlePay": false, "link": true }

I dont understand how this work

surreal bluff
#

In production, you can log in/out with link.com but since you're in test mode you have to use an integration path. If you don't want to change your code to temporarily render the button with Link, the easiest option is probably to create a PaymentLink and log out there like this: https://docs.stripe.com/payment-links/create

#

It is strange that it's choosing Link in a new Chrome profile though since you shouldn't be authenticated... Just double checking, you registered your domain for Google Pay and are using HTTPS, right?

unkempt jay
#

Yeah using ngrok to test in local and my ngrok https link has been registered in test mode for Stripe

surreal bluff
#

Okay, can you try logging out of Link like I described above? If that doesn't work, we'll keep digging.

unkempt jay
#

Sure, lemme do it and get back to you asap

surreal bluff
#

Thanks!

unkempt jay
#

I'm not even login apparently lol

#

I cleared the cookies too but still having the same issue

surreal bluff
unkempt jay
#

after desactivating Link, canMakePaymentResult return just null

surreal bluff
unkempt jay
#

this ?

{
  applePay: false
  googlePay: false
}
surreal bluff
#

Sorry, what are you asking?

unkempt jay
#

Oh mb I understood what you meant, lemme double check

#

Yeah I've checked everything and my browser seems well configurated

surreal bluff
#

What country are you located in?

unkempt jay
#

France 🥖🥸

surreal bluff
#

Haha awesome! Okay, let's troubleshoot why you aren't seeing Google Pay in the demo. Once it shows there, it should also show in your integration.

The wallet must have at least one card.

Log out of Link. If you see Pay with Link in the demo, your Link account takes priority over Google Pay.
Can you confirm clicking Link prompts you to sign in?

You must use a compatible Apple Pay device and Google Pay device.
Do you meet these requirements? https://developers.google.com/pay/issuers/overview/supported-devices#compatibility_requirements

You must use a supported version of a supported browser for the wallet you’re testing.

Allow applicable browsers to access your wallet.
Chrome: Settings > Autofill and passwords > Payment methods > Allow sites to check if you have payment methods saved
Have you done this?

Don’t use a Chrome incognito window.
Can you confirm this?

Confirm you’re operating from a supported Apple Pay region and Google Pay region.

unkempt jay
#

For link yes I confirm

#

for chrome yes the switch is enabled to allow sites to check if you have payment methods saved

#

and yes Im not in incognito

surreal bluff
#

Hmm this is strange 🤔 let me do some more digging.

unkempt jay
#

Yeah I asked a co worker to test the same page as me, and he can see the stripe google pay button, so its definitely a browser problem

#

but some clients are complaining, cause they're in the same issue as me, so I need to find the exact answer that could block this button from showing

#

my coworker has this configuration returned :

{
"applePay": false,
"googlePay": true,
"link": true
}

surreal bluff
#

Interesting! And your coworker is using the same device/browser in the same location?

unkempt jay
#

same location and browser yes

surreal bluff
#

Can you confirm this setting is enabled?

unkempt jay
#

yes I confirm

surreal bluff
#

I'm sorry, that's about everything I can think of 🙁 At least we've ruled out that it's not your Stripe integration and your coworker is able to test. Customers shouldn't have issues so long their setup matches the things we checked. If you want to keep debugging your setup, I'd recommend reaching out to Google.

brave troutBOT
unkempt jay
#

umm okay, is there a way to know how stripe handle this verification too ?

#

how do they know that there is an available google pay card ?

clever holly
#

Hi 👋

I'm taking over as my colleague needs to go soon but it's going to take me a while to catch up.

unkempt jay
#

Hey, no problem !

clever holly
#

umm okay, is there a way to know how stripe handle this verification too ?

STripe doesn't do the verification, Google does. We send a request to Google and they tell us if the browser session is valid for Google Pay

unkempt jay
#

Okay I'll see with Google then

#

thanks for the help !

clever holly
#

Sure thing! Happy to shed what 💡 we can