#BKGRV-PaymentSheet-Google-Pay
humble dock
Thanks! I can't imagine the process would be to do a string comparison on the resulting PaymentOption's label to know that it's "Google Pay" and then use the GooglePayPaymentMethodLauncher. Our iOS app has no problems launching apple pay when tapped from the payment sheet without any hackiness
tribal monolith
Okay sorry, not the most familiar with this so checked with a colleague. First, this is on iOS, right?
Wait no sorry
It is called PaymentSheet.FlowController on Android too
humble dock
hah yeah native android app that's giving us problems.
tribal monolith
Yeah okay
What does the PaymentOption object actually return as?
We are under the impression that the Google Pay dialog would still launch here, so a bit surprised.
humble dock
just a stripe PaymentOption object, com.stripe.android.paymentsheet.model.PaymentOption. Which is just label and drawable - both of which are returning correctly... but skipping the Google Pay dialog presentation
tribal monolith
Interesting
humble dock
I kind of figured the pay dialog would launch as well since I can't find any examples of people presenting it manually after the payment sheet callback. I'm not familiar with our backend but I'm not leaning towards that being the problem since our website is using google pay successfully, and everything works fine if using one of Stripe's google pay launchers in android. We just changed directions from a standalone google pay button and would like it to be in the payment sheet now.
dapper socket
Hello! I'm taking over and catching up...
Can you share the code you're using to create the GooglePayConfiguration object and the code you're using to create the PaymentSheet's configuration?
humble dock
Sure flowController.configureWithSetupIntent( setupIntentClientSecret = clientSecret, configuration = PaymentSheet.Configuration( merchantDisplayName = "Grove", primaryButtonColor = AppCompatResources.getColorStateList( fragment.requireContext(), R.color.bg_button_cta ), googlePay = PaymentSheet.GooglePayConfiguration( PaymentSheet.GooglePayConfiguration.Environment.Test, "US", "USD" ) ) ) { isReady, error -> if (isReady) flowController.presentPaymentOptions() else error?.let { errorCallback?.invoke(error) } }
dapper socket
Hm...
Seems like that should work. And you've got android:name="com.google.android.gms.wallet.api.enabled" in your manifest?
humble dock
Yep - added that when we were going with the google pay button approach (which still works through the GooglePaymentMethodLauncher - shows me my demo cards and what not)
deft spade
👋 Hey! Multiple people on my team looked but we're unfortunately not super familiar with this and it doesn't seem like something we can debug in real time right now
I'm sorry to do this but could you write in with all the information you can share (exact Android + stripe-android versions, screenshots that you see on the custom Google Pay integration versus what's on our version, etc.) and then someone on my team can dig deeper async and see what could cause this?
You can contact us via https://support.stripe.com/contact/email
LMK once you have, I'll find the "ticket" and then we can find someone with more expertise to dig into wht could be causing this