#Sharik

1 messages ยท Page 1 of 1 (latest)

neon ledgeBOT
proper nimbus
tawny lotus
#

req_mjZcHs09IKZlm7

#

Thank you Jack

proper nimbus
#

OK. So this is a Connect request that you made on a connected account. The customer object is created in platform, not connected account, and that's why the API complained about customer not found.

tawny lotus
#

I see. While creating a customer I need to have this ['stripe_account' => <connect stripe account id generated at step 1>] in RequestOpts. in order for this to be fixed. Correct?

proper nimbus
#

Yes you are right.

tawny lotus
#

ah It went through but ran into another one ๐Ÿ˜”

#

Card Payment and Transfers I gave these two capabilities to platform and now it says this in test account.

#

Says I need to provide more details to stripe to allow those abilities in test account. Is that necessary for test account?

proper nimbus
tawny lotus
#

I see. I read through docs and it says all custom connect account service agreement needs to have consent accepted through API.

I used Standard before custom but I was getting this error You cannot create Standard connected accounts with capabilities via API
I assume both issues are related.

proper nimbus
#

Which do do you follow along? can you share with me the link?

tawny lotus
#

I was reading through errors and landed on error pointing to this doc

proper nimbus
tawny lotus
#

Yes

#

using that code I indicated an acceptance

#

giving another shot to it

#

still getting this Your account cannot currently make charges. To find out why charge creation is currently disabled, look at the requirements.disabled_reason property on this account (/v1/accounts/acct_1NFVYlFjA0E1W0Sq).

proper nimbus