.n0tnull

[sage wyvern]

Hi 👋 can you elaborate on that a bit? Like are you trying to accept Google Pay for your own account, in which case you don't need to provide an account ID? Or is this part of a Connect flow?

[covert fox]

I have multiple account_id (one per country) and I don't see how to create the payment method on a specific account when using GooglePayPaymentMethodLauncher

When adding a credit card with validation using the PaymentLauncher, we can pass the account_id as parameter

[sage wyvern]

You use your API keys to indicate which account you want to be making requests to, you'll swap the secret and publishable keys being used in your flow to change the account you're using.

[covert fox]

I don't have access to other keys. Only the main one. So it seems to be an issue

Do you have any other solution ?

Maybe calling again PaymentConfiguration.init just before making the call ? 🤔

[sage wyvern]

Are you using Connect? Otherwise you can't (and shouldn't) be able to take action on an account you don't have the keys for, that's the point of those keys.

[covert fox]

I don't know what is Connect. I'm using the Android SDK

[sage wyvern]

Connect is our solution for building scenarios where multiple parties are involved:
https://stripe.com/connect
You should look into using it if you want to build a flow where you have a Platform that is taking action on behalf of other entities (such as vendors or suppliers).

[covert fox]

We are not a marketplace or PaaS. We have an account id per country

[sage wyvern]

Then I would expect you to have access to your API keys for each of your accounts. If you don't you may want to work with your team(s) to get access to those keys, or link all of your accounts together using Connect as though you were a marketplace.

[covert fox]

Then I don't understand why you have differences between credit card API and Google Pay API

And even the Android SDK has lower capability than the iOS one

So, for you, there is no other solution than using an API key per country?