#mad-dog_api

1 messages ยท Page 1 of 1 (latest)

misty crestBOT
#

๐Ÿ‘‹ 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/1374073480101761125

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

obtuse estuary
#

The account ID you shared is a sandbox Connect Account

zinc lynx
#

req_CAVijHdOSSzizR

#

we wanted to use express connect account for onboarding

obtuse estuary
#

The account you are trying to create an account link for belongs to acct_1P0ncoBlS0X1H1vO. The account attempting to generate the account link is acct_1ROroYQpERdYUCGO. They have to be the same account

misty crestBOT
zinc lynx
#

it's weird

#

when calling the api, do i pass the acct id?

obtuse estuary
#

Both account creation and account link creation should happen on your platform accout

#

You do not need to provide the Stripe Account header

zinc lynx
#

on the backend, it only uses the stripe secrect key

#

how do solve this issue?

#

is the stripe secret key mismatch with account?

#

hey hum i need your help!

quaint nest
#

Hey there, I'm in another thread will get to you shortly.

zinc lynx
#

still waiting..

quaint nest
#

Hi there, you'll need to use the API keys associated with the Platform account that acct_1RP7GIPmJ7zAmr2A is connected to. In this case, the Platform account is acct_1P0ncoBlS0X1H1vO as my colleague pointed out.

zinc lynx
#

where i check the account id and api key?

#

i dont see any of the account is associate with acct_1RP7GIPmJ7zAmr2A

#

for this to work, do i need a live account? or sandbox account is good enough for testing onboarding

#

i need help, is any other member available to help?

quaint nest
#

You can test onboarding with the sandbox or in test mode.

#

The account you should be looking for the API keys for is acct_1P0ncoBlS0X1H1vO

zinc lynx
#

this is all my account

#

there's no matching

#

i just created a Tesing account for connect, and test,

#

changing the secret api key, still not working

quaint nest
#

Please provide the request ID

zinc lynx
#

req_5D1CttgS1wgUzI

#

i updated the secret api key for this account as well

misty crestBOT
zinc lynx
#

anyone can help?

waxen beacon
#

๐Ÿ‘‹ hey there

#

I'm stepping in as eze needs to step away

zinc lynx
#

hi, please help me with this!

waxen beacon
#

I'm taking a look, but please be patient. We work with multiple folks at once here.

zinc lynx
#

i spent so much time on this

waxen beacon
#

Okay based on the request ID you shared above it looks like you are mixing up API keys and accounts.

zinc lynx
#

yea, i think so too

#

how about this, let me close up all the account, and just keep one for clearity

#

guild me how to delete these account

waxen beacon
#

The other option instead of closing your accounts is to check your API key that you are using in your integration against your Dashboard

#

And then ensure you are using the same API key across your integration and run a new end-to-end test.

zinc lynx
#

ok right now, i just have this only account

#

what is next thing i should do ?

waxen beacon
#

Check your integration an ensure you are using the API key from that remaining account

zinc lynx
#

can i share screenshot with you?

#

with api keys on, its ok, i will rotate later, but i need this to be figured

waxen beacon
#

No need to do that

#

Can you tell me where you are confused at this point?

zinc lynx
#

it just doesnt work

#

i go to remaining account, check the api key

#

change my backend

waxen beacon
#

You are going to need to be more specific for me to help. What doesnt' work? Is there an error? Did you test again? Do you have a new request ID you can share?

zinc lynx
#

req_oUO3S7JlypHrIG

#

this is the reqeust id

waxen beacon
#

Okay so same issue. So next step is to go create a new Connected Account using the API Key of the remaining account you are using.

zinc lynx
#

here ?

waxen beacon
#

No, I'd suggest doing this via the API like you are going to do when you onboard a user.

#

I assume you are building an onboarding process here for your users?

zinc lynx
#

yea right

waxen beacon
#

You would follow those steps.

#

If you have specific questions then I'm happy to help, but we can't write your code for you.

zinc lynx
#

im not asking you to write code

#

right now, new user cannot onboard...

#

due to account and secret key not working properly right?

waxen beacon
#

We already determined why it is not working -- due to the mismatch, yes. So now you need to run a new end-to-end test using the singular key. So that this all occurs on the same account.

zinc lynx
#

so everyone has to do this step for testing stripe connect?

waxen beacon
#

Yes, you have to create a test account first. You don't have to use real details when you onboard it though.

zinc lynx
#

for the test account? is it not done on stripe dashboard?

misty crestBOT
waxen beacon
#

If you want to do it via the Dashboard then you go to your Connected accounts section: https://dashboard.stripe.com/test/connect/accounts and use the Create button. But if you are building an integration here why would you not do it via the API to test your integration end-to-end?

zinc lynx
#

I'm building an integration.

I want to create a testing account on stripe dashboard, using that api key for integration

for future new user onboarding, it would use the api key for onboard to connected with the testing account

#

is this wrong?

waxen beacon
#

You already have a platform test account. Now you want to create Express Connected Accounts using your platform API key.

zinc lynx
#

please check this account

#

acct_1RQZFlBQXtng9QlH

#

is this express connected?

waxen beacon
#

Yeah

zinc lynx
#

ok, now i have this connected account

#

the api key for new onboard should work as expected right?

waxen beacon
#

I'd assume so, if you used the platform account corresponding with the correct API Key

zinc lynx
#

after the I have the connected account created with the api key

#

what if user previously onboard with stripe

waxen beacon
#

You are going to need to be more specific.

zinc lynx
#

let say, this user(lol@gamil.com) onboard with stripe on platform 1

#

then he come to platform 2, and do stripe onboarding

waxen beacon
#

This can only be done with Standard Accounts though.

#

With Express Accounts they are isolated to each platform.

#

So a user could have multiple Express Accounts with different platforms.

#

They can use the same email for that.

zinc lynx
#

please check this account

#

acct_1Q6uIAPecxcaVGCh

#

is this standard?

waxen beacon
#

You need to be able to figure this out yourself. Load it in your platform Dashboard and it will tell you on that page what type of account it is

zinc lynx
#

acct_1Q6uIAPecxcaVGCh (lol@gamil.com) is linked to another platform via stripe.

#

if this (lol@gamil.com) come to our platform, can he connect with us with express connect?

#

the answer is yes right

waxen beacon
#

Yes they would create a new Express Account to connect to your platform

zinc lynx
#

Thanks, the issue is resolved, it is the issue with our database user account id and stripe platform account mismatch...