#DominicB - Payment Request Button
hasty isle
đź‘‹ let's chat here
Is your team using direct or destination charges? https://stripe.com/docs/connect/charges#types
haughty thicket
Hey! Direct charges
hasty isle
On your front end, are you using the stripeAccount option to specify the connected account? https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-using-with-connect
haughty thicket
Yes! We use the pk_test apikey from the platform account and the accountId from the connected account when initializing stripe on the frontend
hasty isle
Got it. Do you receive this error with just one connected account or any of the connected accounts?
haughty thicket
We only have one account connected for testing purposes at the moment
hasty isle
Could you share the Platform and Connected Account IDs?
haughty thicket
Platform: acct_1KnOpQEL4e65GS5o
Connected: acct_1JysR3LiY5F9tBM7
hasty hamlet
Hi there đź‘‹ taking over for roadrunner
Give me a minute or two to get caught up
haughty thicket
Sure, no problem!
hasty hamlet
So, this is an error that you get specifically from Google Pay, as far as I can tell. The issue is: the connected account is connected in livemode to your platform. Usually that allows you to also make test mode API requests on their behalf, but it doesn’t work with Google Pay, for a technical reason — it will only work with Google Pay in live mode(using livemode API keys).
The resolution is:
if you’re just testing, you'll have to create a test mode Standard account instead(either with the API, or using your “development” ca_xxxx client ID for OAuth) and then use that account for testing, instead of this live mode one. You can establish a test mode connection to this existing livemode account by running the OAuth process(https://stripe.com/docs/connect/oauth-standard-accounts) again, using using your “development” ca_xxxx client ID.
haughty thicket
In our "fix attempt #2" (from my initial message), this is what we did as far as I can tell:
Went to the platform account dashboard, to the Connect tab. Then switched to test mode and clicked on +Create button to get the OAuth link.
When I compare the link provided by the dashboard UI, it uses the test mode ca_XXX client id and as the same format as the one described in the doc link you sent.
Is there a better way to do this? Is it possible we are in some kind of bugged state after connecting/disconnecting the same account (see Initial setup, Fix attemp #1 and #2).
hasty hamlet
It has to be created as a test-mode only account from the start, so you cannot disconnect and reconnect as far as I can tell
haughty thicket
I think that is the part that confuses me from all I've read so far. What is a test-mode only account, how can we tell if it is test-mode only from the dashboard and how do you create one?