#Akshay-connect

1 messages · Page 1 of 1 (latest)

cursive aurora
#

Hello! Give me a few minutes to take a look

brittle mantle
#

Thanks! For context, it did work with a test Stripe Connect account, and only failed for a live account

cursive aurora
#

This looks like a limitation on our end (I see someone else has flagged it internally) - our Google Pay integration doesn't correctly handle a livemode connected account with test API keys. The current suggested workaround is to also connect the account in test mode

brittle mantle
#

The same account can be connected in both test and live mode?

cursive aurora
#

Just to check though - is there a specific reason you're testing this out?

brittle mantle
#

Apple Pay only works with live Stripe Connect accounts

#

I have the integration working with Google Pay, now I just want to verify that Apple Pay is also working

#

Also I'm not sure what the client application is

cursive aurora
#

I also want to ask - are you testing this out on Android? I don't believe there's a way you can get Apple Pay to work on an Android phone...

brittle mantle
#

No I would test on my iPhone on safari

cursive aurora
#

I'm surprised you hit that specific error on your iPhone w/ safari - that's an error I'd only expect as part of the Google Pay flow

brittle mantle
#

No I got that error on GPay

#

I was just wondering what caused it

#

Now I know it's exclusive to Gpay though

#

I should have clarified, we want both Gpay and ApplePay to work

#

I test GPay on my desktop chrome, and test ApplePay on my iPhone safari

#

with the test mode stripe connect account, only Gpay works. when switching to live, now Gpay is failing and I'm hoping ApplePay works too

#

But I need to set up the domain association file, which is a separate challenge because of something configured in our domain name

#

But I do want to use your solution of connecting the live/test stripe accounts simultaneously, as I'd like to use a live account for a POC that both GPay and Apple Pay work

cursive aurora
#

Ah, that makes more sense! Let me re-summarize then:

  • If it's important for you to have a single connect account that works with both Google Pay and Apple Pay then yes, you'd need to connect it in both live and test mode using Oauth
  • It's safe for you to ignore the Google Pay error - it's something that will only happen for Live mode connect accounts w/ your test mode API keys. Your live users should never see this error.
brittle mantle
#

Ok good to know, is there a way to do it without Oauth? The link you sent me requires going through a separate connect process?

cursive aurora
#

To my knowledge, the only way to do this would be through oauth

brittle mantle
#

Ok the guide isn't making a lot of sense to me for this use case - I already have a live connect account, so how would I use that existing account ID and enable it for test mode as well?

cursive aurora
#

can you be specific about what part of the guide doesn't make sense?

brittle mantle
#

This guide is about creating a new connect account?

#

Maybe I'm misunderstanding, but I don't see where I enable test mode for an existing live account

#

Also, when I go to my Connect dashboard, I see the payment intents whether or not the Test mode toggle is on/off

fervent lion
#

Hello @brittle mantle I will take over from here

#

The link my colleague provided would be the way for you to go. In Step2 you will connect your existing Live account, instead of creating one

fervent lion
#

Hello, when you are back feel free to open a new thread