#josh-unger_unexpected

1 messages · Page 1 of 1 (latest)

vale surgeBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

urban cedar
#

Hi there,
can you give me a bit more context what the issue is, what you are seeing compared what you are expecting to see?
Do you have by chance a web accessible link, where I can take look at this directly?

#

And the code snippet for the Express Checkout Element?

placid coyote
#

Hello

# 
          ...(applePayConfig && { applePay: applePayConfig }),
          billingAddressRequired: true,
          layout: {
            overflow: 'never'
          },
          paymentMethods: {
            applePay: 'always', // Always show Apple Pay so it appears on Chrome and uses the QR code,
            link: 'never' // Hugh is testing,
          }
        };```
#

Sorry no web accessible link.

urban cedar
#

Do you have the entire codfe snippet for the express checkout component? And does the console show any logs or errors?

placid coyote
#

expressCheckoutElement = elements.create('expressCheckout', expressCheckoutOptions);

urban cedar
#

Sorry for all those questions but debugging frontend issues are always a bit more complicated since we don't have much visibility into what is going on in your integration.

placid coyote
#

This is Chrome.

#

googlePay: 'always' does force the button to be available.

#

I'd like to know why Stripe didn't render it with debug logging.

#

I'm guessing Stripe is thinking something is wrong so if we can get the logging that would be helpful.

urban cedar
#

I just copy and pasted your settings into my integration to test it, and I can see all Payment Methods, so no overflow.

placid coyote
#

Of course! 🙂

#

Google Pay has additional configurations that determine when Stripe can show it. By default, Google Pay shows when the customer is using a supported platform and when we determine it's advantageous for your conversion. This is the auto behavior.

#

I'd like to find the logging for this logic?

#

"we determine it's advantageous for your conversion" <--- how do we see this?

urban cedar
#

is this from our docs? do you have a link?

placid coyote
#

Yeah

urban cedar
#

Ok got it. There is no user facing logging, if the googlePay is set to auto . Stripe checks internally if the PaymentMethod can be displayed or not.

But let me take a step back. I am a bit confused right now as to what you are seing when you look at your ECE. Do you see GooglePay as a payment method? And do you have the overflow arrow/button to expand, or can you see all payment methods?

#

Do you have a screenshot?

urban cedar
#

The more code I have, the easier it is for me to understand what is going and investigate

placid coyote
#

Can we get an answer to "we determine it's advantageous for your conversion"?

#

What the Stripe SDK is doing?

urban cedar
#

Let me check if I have some more information about this

#

What that means is, that we display Google Pay as Payment Method only, when the customer already has a card saved in their Google Wallet

#

We have this doc pointing this out and providing guidance on rendering issues for ECE (and other Elements)

placid coyote
#

Yeah that page shows Google Pay

#

Shoot I gotta run to a meeting.

#

What can we do next on this to determine why Stripe hid it?

#

In our testing we clicked on Apple Pay several times, so I was starting to wonder if Stripe now only shows Apple thinking it has better advantage for conversion.

urban cedar
#

That doesn't matter, I can see applepay and googlepay in my chrome browser.

placid coyote
#

Yeah I'm surprised you don't have debugging to determine why Stripe hid the button.

urban cedar
#

Do you have your account ID?