#TheUchi-Connect

1 messages · Page 1 of 1 (latest)

half yew
#

Hi there,
1/ you mostly just want to rely on the requirements hash to know if someone has outstanding onboarding requirements.
2/ Can you provide an example? These shouldn't be different.

velvet ridge
#

Sure thing, give me a few mins, stepped out for a bit

#

Ok, I am back in my office, let me prepare some screenshots so you can see

half yew
#

Better than screenshots would be IDs that I can actually look at

velvet ridge
#

Connect account IDs?

half yew
#

Yep that would work

#

And where exactly you see the difference in banks versus external_accounts

velvet ridge
#

Ok, I will send the ID with the screenshot

half yew
#

Likely this is just your own code changing the names. Since we don't have a connectAcc object

velvet ridge
#

This is from the connect account with the ID acct_1LYF4K2SFFeszVcM. This is also from the production one.

#

This is from the connect account with the ID acct_1LRqPiPoZt2kJN1S. This is also from the testing one.

#

You can see that one gives me the bank info as external_accounts, and the other as bank_accounts

half yew
#

Yeah see how your object in the second one is called connectAcc?

#

We don't have a bank_accounts property on our account object

velvet ridge
#

The connectAcc is just an object I named, since I am also getting some other data from the API endpoint I created. The data inside of it is using the same exact Stripe API endpoint, tho

#

So I am not sure why is it different on both

#

Both builds(my local one and production one) are using the same version of Stripe NPM

#

There are some other objects that have different name, but same data

#

So this is a problem for development, since then I cannot really move this to production without changing the names

#

For reference, the specific API I am using is stripe.accounts.retrieve(stripe_account_id)

half yew
#

Okay

#

So

#

Your testing is using a very old API version

#

You are using 2015-04-07

#

So that is why

#

Where we changed to external_account in 2015-10-01

#

In livemode you are on 2020-08-27

velvet ridge
#

Hmmm but I should be using the same on both, since both use the same codebase

#

I will have to take a look then

half yew
#

Yeah you'll need to check that and see if you are versioning your requests in livemode.

#

Your default is indeed set to 2015-04-07

velvet ridge
#

Where can I check what version am I using?

half yew
#

For the request or for your default?

velvet ridge
#

For the default

#

So that I can make sure that the default is the latest one

half yew
#

That said be very careful upgrading

velvet ridge
#

Oh wow, I always thought that the npm package would hold that info to use the latest API

#

Thank you so much, that was it!