#ayeeemon-connect-descriptor

1 messages · Page 1 of 1 (latest)

tropic geyserBOT
bleak pasture
#

So when you retrieve this account, you don't see any requirements or future requirements. Just to be clear, is this something you want to test and need help getting the account in a specific state or do you see the invalid statement descriptor error somewhere for this account?

tropic geyserBOT
#

ayeeemon-connect-descriptor

thorny imp
#

This is something i am trying to test, and needed the account to get to. We do an API based onboarding flow, and want to inform the user if the statement descriptor doesnt match business name or related fields you guys check for.

#

So they can properly update it an not get their payout restricted in the future

bleak pasture
#

Got it

#

What have you tried so far? Are you able to trigger a requirement if you update details about the company or business profile so they don't match the descriptor you use?

thorny imp
#

So I was able to create a account, that has the future requirement error: acct_1Of8TJGaIEyOiDNf

#

but i am not understanding why it appears in this account but not the other

#

both account are almost the same

#

they both has statement descriptor that doesnt match business name

#

so not sure why the error is appearing in one and not another

#

also not sure if you are able to see the details of the each account, but i can send them in you need

bleak pasture
#

I'm looking at the account creation requests for both accounts and the response for both includes the invalid_statement_descriptor_business_mismatch error code

thorny imp
#

hmmm, i dont see it when i make the call to GET the account for acct_1Of7uqGhWd4gf43o

bleak pasture
#

can you show me the same for the other account?

thorny imp
bleak pasture
#

Still digging into this

bleak pasture
#

I'm trying to find where that requirement falls off. If you look at the account.updated event on account acct_1Of7uqGhWd4gf43o ~4 seconds after account creation, the settings.payments.statement_descriptor requirement is still there

#

This is the event I'm referring to: evt_1Of7uuGhWd4gf43oc8DUfLqO

tropic geyserBOT
thorny imp
#

Ahh so we create the connected account, we initially create it using an API call, and then we generate an onboarding link, where the user will complete the rest of of onboarding.

#

in the api call this is where we allow them to set up doing business as name, currency, country, and statement descriptor prefix, and the rest is collected using the onboarding form