#chris-oliver_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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/1220800532617236620
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
Can you share the request where you create the Checkout Session?
Or the Session ID?
cs_live_b1i3myPchMcMYL3C1EerxOw5NDfU3fbzhaj5GGj6WtG8jWGa36a1jaQfxM
Interesting
"payment_method_types": [
"card"
,
"cashapp"
,
],
Yes but card should also allow GooglePay
but automatic_payment_methods: true was sent
Would that have come from stripe-ruby?
No, it wasn't specified in the request body
oh yeah, but that's teh default now
But the User Agent in the creation request https://dashboard.stripe.com/logs/req_9XNDhbPdyNUNDa suggests this is a 3rd party modification of stripe-ruby
yeah, it's a Ruby gem I maintain called Pay (I'm part of the developer experts thingy)
I'm surprised Google Pay shows up in the Checkout UI if it's not allowed in production?
Can you share a screenshot of the UI you are seeing? The GooglePay modal?
And also trying to determine why Google Pay isn't in the payment methods list when it's enabled on our account?
Yeah
Google Pay, at least on the web, is just a wraapper around card payment methods
It wouldn't show up as a separate PM type in the list
Okay that's pretty weird. And this recording is using the checkout session you provided to me?
Yes
I haven't changed anything, but every checkout session I create is the same
We've had this enabled for quite some time and this is the first time I've heard about it, so possibly we have previous customers on Google Pay, but I'd have to confirm that.
Okay this is pretty weird. I'm reaching out to some colleagues to help me look into this
Thanks @wraith crystal ๐
I thought it was pretty strange too
I didn't try disabling/re-enabling Google Pay in the payment method settings yet, but I can if you think that'd help. Although if it does fix it, won't help you find the root of the issue I guess.
Can you share a URL where this occurs?
https://gorails.com/subscriptions/new?plan=plan_RdELmMYr2NjOmfyJkZ1bx6lq (you'll have to register to get there)
Thanks. We're checking further
Appreciate it!
Would you be able to roll your publishable key and use the new one in your integration without too much difficulty/risk? https://docs.stripe.com/keys#rolling-keys
We have a hunch this is an issue with the publishable key you're using being in an old format.
Okay, I can do that
Is this one from 2018 that uses pk_live_ prefix new enough?
the old one from 2011 only is pk_
yeah the newer one with pk_live should do the trick
Awesome!
Thanks for the confirmation
The team is working on handling those older keys
But recommend you use that newer one
Perfect, thank you so much!