#mike-j_api

1 messages ¡ Page 1 of 1 (latest)

latent saffronBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1237351276518309980

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

twilit joltBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

eager tinsel
#

Can you share the pi_xxx ID?

stuck bough
#

Let me find it...

#

pi_3PDkhYQtREZRfjbv0JCbKniy

eager tinsel
#

Generally this is on eof two things:

  • In Connect scenarios you're missing the stripeAccount header in Stripe.js
  • API key account mismatch
stuck bough
#

Ok, I'll double check those things. I'm a little confused that the process works in certain scenarios and as far as I'm aware, the api leys shouldn't be changing between them, but stranger things have happened. Thanks

eager tinsel
#

From the initial req_xxx you shared you're initialising Stripe.js with the pk_xxx of the connected account. You need to use the publishable key of the platform

#

And then pass stripeAccount: 'acct_connectedaccount'

stuck bough
#

Ahh, I think I see where it's happening. Thanks!