#mtanzi_code

1 messages ¡ Page 1 of 1 (latest)

rocky kelpBOT
#

👋 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/1316449248983781407

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

leaden lava
#

Hi, I suspect the keys being used might be in play. Let me look around

gleaming ibex
#

Hi @leaden lava , thanks for looking!

#

for all the other calls to Stripe that we make using the ruby wrapper we pass the stripe_account and the resource is dispatched to the correct account

#

this is the only API I had some issue with

leaden lava
gleaming ibex
#

I looked at that issue but it's not quite the same, we use the OAuth link to open the widget and the problem is on the callback when we try to generate the token

#

can it be related on how the accounts were generated?

#

the SO "solution" says that they were using the client ID using a different account key, but we are passing the connected account to the call so we should be using the platform key

leaden lava
#

Yeah. You said it's just happening on one account only?

#

Can you share the account id with me?

gleaming ibex
#

it happens on the connected accounts.. it works for the platform account

#

Can you share the account id with me? sure

#

shall I share it here or in a DM?

leaden lava
#

Ytou can share it here, it's just act acct_ id. If you're not comfortable sharing that informaiton here you would need to write in to support.

gleaming ibex
#

here is the account where I encountered the issue: acct_1NTZO0DVCWpjew1S

#

I have a customer in this account and this customer is trying to onboard to get his connected account

leaden lava
#

You're attempting to add a connected account on acct_1NTZO0DVCWpjew1S account?

gleaming ibex
#

correct

leaden lava
#

Yeah, I was able to confirm that error happens when you're using the secret key of the wrong platform account when you initialize the Stripe library to call \OAuth::token.

gleaming ibex
#

so, for this API I cannot pass the id of the connected account to perform the call?

#

any reason why this behave differently from the other API calls that we have?

leaden lava
#

I'm unsure, you would need to debug this on your end

gleaming ibex
#

is there a suggested approach for this type of configuration?

#

would it work if I pass the key associated to the connected account?

leaden lava
#

You would need to pass the key associated with the Platform account that is creating the connected account. In this case, since you're creating the connected account on acct_1NTZO0DVCWpjew1S, you would need to use the key from that account

gleaming ibex
#

that account is a connected account itself... would that create problem or it will be just the platform for the new one

leaden lava
#

They would need to enable the connect setting on that account but they would be the Platform account for their connected account.

#

I'm unsure what issues you're referring to

gleaming ibex
#

not a particular issue was just trying to understand if there might be some other problem I might run into

#

ok... let me try with setting the key explicitelly

#

thanks again for the help!