beltranc | Stripe Developers | Page 1

sturdy cryptBOT Jul 31, 2023, 7:34 PM

#

uncut shuttle Jul 31, 2023, 7:35 PM

#

I was told by dev support here that this is a Google Pay issue not a Stripe issue. So I contacted Google Pay support and they told me the following:

Please make sure you are using correct gatewayMerchantId provided by your payment gateway. (This is performed by Stripe)
Make sure you are using correct merchantId xxx provided by Google Pay. (This is performed by Stripe as the provided component does not use a merchantId)
If your app is pointed to the Google Pay API production environment, the Google Pay API returns ERROR_CODE_MERCHANT_ACCOUNT_ERROR (405) if the signing key fingerprint used to sign the Android app does not match the release key fingerprint registered with Google Play. For more information please follow this document. (This is performed by Stripe as it abstracts the call to Google Pay)
Make sure that your APK is signed with the release key, not with the debug key you used in the test environment. The debug key will not work in the production environment. (I can confirm I have done this)
To enable Google Pay in your app, you need to add the following Google Pay API meta-data element to the<application> element of your project's AndroidManifest.xml file. (I can confirm I have done this)

cold sandal Jul 31, 2023, 7:37 PM

#

Hello 👋
As far as I know, once you've followed google's instructions then the only thing required from Stripe's side is switching to using your live mode API keys and setting testEnv: false
https://stripe.com/docs/google-pay?platform=react-native#going-live-react-native

uncut shuttle Jul 31, 2023, 7:39 PM

#

Yeah i have done that

#

Google said everything looks fine on their end

#

however for the type of error i am getting i cannot debug it or check any logs since that error is passed between Google Pay and the gateway provider (Stripe)

cold sandal Jul 31, 2023, 8:01 PM

#

sorry for the delay, can you confirm if the same code works in test mode?

uncut shuttle Jul 31, 2023, 8:07 PM

#

yes, it works in test mode with no issues

cold sandal Jul 31, 2023, 8:10 PM

#

Gotcha. In that case, I'd recommend tripple checking all the going live steps.
As I mentioned earlier, from Stripe's end the only expected change is in the testEnv and using live API keys.

Aside from that, everything else takes place in google's console. That's not something we'd have an visiblity into either

uncut shuttle Jul 31, 2023, 8:12 PM

#

I have checked many times and everything looks identical, is there a way that Stripe can check the logs for the info being passed to Google and viceversa?

cold sandal Jul 31, 2023, 8:15 PM

#

Can you share an example PaymentIntent where you are seeing this error?

uncut shuttle Jul 31, 2023, 8:19 PM

#

It's not an issue with the payment intent and there are no logs with it

#

it's a frontend Stripe component issue

#

or the integration between Stripe and Google Pay but it does not reach the payment intent

cold sandal Jul 31, 2023, 8:30 PM

#

Yeah I don't think we'd have logs for that specifically. We haven't heard of any other reports similar to this.

In the past, it almost always has been some configuration issue in the Google console or with the signing of the release APK

uncut shuttle Jul 31, 2023, 8:36 PM

#

By Google console you mean as if the integration was not approved on Google's side?

cold sandal Jul 31, 2023, 8:38 PM

#

Right, or if the production access was misconfigured somehow

uncut shuttle Jul 31, 2023, 8:39 PM

#

But Google confirmed everything is configured properly and approved on their end. The app signing is default and generated by EAS too

cold sandal Jul 31, 2023, 8:42 PM

#

I see. I'd recommend writing in via our support team and provide as much as information as you can
https://support.stripe.com/?contact=true

This would allow us to dig deeper and pull in product team if necessary

uncut shuttle Jul 31, 2023, 8:43 PM

#

Ok, I will try that, thanks

#beltranc