#device_api

1 messages ¡ Page 1 of 1 (latest)

primal whaleBOT
#

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

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

winged light
#

Hi, let me help you with this.

#

Where do you expect to see these fields filled out exactly?

south kettle
#

on the external account entityt

#

both of them are null

#

even though it can be inferred that it's a 'company' for account_holder_type

#

or maybe is this due to the fact that it's a default stripe test bank account?

winged light
#

The main question, is it preventing you from making payouts in Live mode? If not, I wouldn't worry about it.
Yes, most likely it's due to the fact that it's Test mode.

south kettle
#

No, it is not preventing us to make payouts in live mode. However, there is also no way for a connected account during the completion of the kyc process to select the values for those 2 fields.

#

do you know exactly how those values are prefilled and on what they depend?

winged light
south kettle
#

There is a way to update it, but I thought that this should be included in the kyc process.

#

That's what I was asking about

winged light
#

During the Live mode onboarding, Stripe with request all the necessary details for making successful payouts. I think it will be pre-filled from the account information, if not requested directly.

south kettle
#

so that means, that the values of those fields depend on the type of bank account that is provided, right?

winged light
#

I am not sure what you mean.
I suggest to take a step back for a moment. What are you actually trying to achieve, on high level?

south kettle
#

so, after completing the kyc process, we redirect the connected account to a page where the bank accounts are displayed. There we display the account_holder_name and account_holder_type alongside other fields. Since the values for those fields is null for the stripe test account (and probably other accounts in test mode), then we have an undefined there. So what we want to achieve is either be able to infer those values for the external bank accounts through the kyc process or we need to setup another step to update those values in stripe so that they are not null.

winged light
#

Got it. I am fairly positive this won't be a problem in Live mode. Stripe will either request those to be filled out, pull from the bank, or infer from the other info provided during onboarding.

south kettle
#

ok, but I'm also interested in the flow for the testmode. Can we influence those values in any way in test mode through the demo kyc process?

winged light
#

How are you currently selecting a test bank account?

south kettle
winged light
#

It's possible that for SEPA DD, you don't need the account holder information actually.

#

My best recommendation, is to make your own system more flexible and hide the empty fields. As I said, Stripe will ensure all the necessary information is collected.

south kettle
#

Thanks. I'm going to first validate that on the live environment it works as expected and then I'll let you know if I have further questions. Thanks Ivan :))

winged light
#

Happy to help.

south kettle
#

Do you need any new developers at stripe? :)))

winged light