#kerrygotten

1 messages · Page 1 of 1 (latest)

manic troutBOT
cerulean echo
#

Hi 👋

spare bronze
#

hi

cerulean echo
#

Have you checked the requirements property on the Account object?

#

That is where you can see the rest of the information required to onboard the account.

spare bronze
#

Thanks, this is what's on the requirements property:

requirements: {
alternatives: [],
current_deadline: null,
currently_due: [ 'external_account', 'tos_acceptance.date', 'tos_acceptance.ip' ],
disabled_reason: 'requirements.past_due',
errors: [],
eventually_due: [ 'external_account', 'tos_acceptance.date', 'tos_acceptance.ip' ],
past_due: [ 'external_account', 'tos_acceptance.date', 'tos_acceptance.ip' ],
pending_verification: []
},

#

Is there somewhere I can read about this, it's not in the docs I was following

#

Since there is content in the requirements property, does that mean I need to fill in all of those somehow?

#

Is it supposed to be the case even though I'm trying to use the express onboarding flow?

#

Would the express flow not provide for the user submitting this information?

#

To clarify, I'm trying to test a seller account for the a marketplace.

cerulean echo
#

Connect is a big topic. There is a whole Navigation section in our docs dedicated to it

spare bronze
#

Thanks!

#

The tutorial page I was using didn't mention anything about capabilities haha

cerulean echo
#

Yeah, we could do a better job of tying it all together. There are A LOT of moving parts here

spare bronze
#

thanks, but great job on the live support, really appreciate it