#peter_40675
lyric tartanBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- peter_40675, 5 days ago, 16 messages
- peter_40675, 5 days ago, 11 messages
tranquil walrus
Is there a question?
hazy lodge
Yes why this is coming because when i create bank account threwout apis, its showing restricated in stripe dashboard
tranquil walrus
Then I suspect that we require verification information for those bank accounts, which you can provide via the API or an Account Link. Your integration should be handling this
tranquil walrus
Then you'll need to listen for account.updated events and check for when the requirements hash changes: https://stripe.com/docs/connect/handling-api-verification#determine-if-verification-is-needed
tranquil walrus
That's information you'd collect from your user in a live integration. There's probably test data here you can use: https://stripe.com/docs/connect/testing
hazy lodge
If @worthy crow is here then please ping here, he will understand
tranquil walrus
They're not available I'm afraid
In any case, they'd jsut share the same information I've provided
hazy lodge
i mentioned my code as screenshoat when i create account it should be restricated then what is that field name
tranquil walrus
If/when you update the details of a connected account (i.e. attach an external account) that can trigger additional verification requirements, which is likely the case here (hence they've transitioned to restricted). You need to collect that verification info from your user and provide it to Stripe
tranquil walrus
I don't understand what you're asking me. But what I described above is explained here: https://stripe.com/docs/connect/handling-api-verification#determine-if-verification-is-needed
Ultimately you're using custom accounts which have a higher integration effort than standard or express. You need to account for that
hazy lodge
what i say Legal name and TIN is required
Then what verible can i pass to stripe, i haven't seen in your doc
tranquil walrus
https://stripe.com/docs/connect/testing#test-personal-id-numbers should work for TIN
hazy lodge
just a min
individual: {
address: {
state: 'North Carolina',
city: 'Durham',
postal_code: '27703',
line1: '1224'
},
dob: { day: '25', month: '08', year: '1990' },
email: 'dsdas@eee.rrr',
first_name: 'sdsadAA',
last_name: 'ddAA',
phone: '7404630034',
ssn_last_4: '0000',
id_number: '128280000',
verification: { additional_document: [Object], document: [Object] }
I pass this already but not working
as id_number
id_number: '128280000',
tranquil walrus
What's 'not working'? Are you listening for account.updated events? Can you share the evt_xxx of the most recent one for the account you're working with?
tranquil walrus
There will still be account.updated events. You need to be listening to those
hazy lodge
check log
we will account.create
not update
req_Nrky29RLsoV2xG - please check logs
tranquil walrus
I'm not disputing that you're using the Account create endpoint
hazy lodge
stripe.accounts.create(accountObject,function(errx,account){.
id_number: '128280000', - i pass
tranquil walrus
But there will be account.updated webhook events fired that contain information regarding requirements due for the account and why it's in a restricted state
hazy lodge
then now what should i do
tranquil walrus
tranquil walrus
Then you'll need to listen for `account.updated` events and check for when the `...
I've told you a handful of times already
hazy lodge
NO EVENTS
tranquil walrus
That's because I guess you're looking at the events tab of your platform account. The account.updated events fire on the connected account
You need to set up a Connect webhook: https://stripe.com/docs/connect/webhooks
hazy lodge
fIRST lEAVE iT
Its Any changes last month in US CONEECT ACCounts?
see pic
Since last month restriction
worthy crow
Its Any changes last month in US CONEECT ACCounts?
overall we're a bit more strict now about accepting "nonsense" data and require things like the statement descriptor to match the business name
overall though, this is test mode, so you must use the values we provide at https://stripe.com/docs/connect/testing#identity-verification in order for accounts to actually get verified in test mode. If you have some specific account ID acct_xxx with a problem I could attempt to look at it and say what it needs/is missing etc.
hazy lodge
Thanks but i pass this ->
individual: {
address: {
state: 'North Carolina',
city: 'Durham',
postal_code: '27703',
line1: '1224'
},
dob: { day: '25', month: '08', year: '1990' },
email: 'fdsf@eee.rrr',
first_name: 'fsdfAsdfdf',
last_name: 'fsfsdAdsfsdf',
phone: '3312762635',
ssn_last_4: '0000',
id_number: '000000000',
verification: { additional_document: [Object], document: [Object] }
},
tos_acceptance: { date: 1699360449, ip: '10.0.2.16' },
capabilities: {
card_payments: { requested: true },
transfers: { requested: true }
},
external_account: {
object: 'bank_account',
country: 'US',
currency: 'usd',
bank_name: 'STRIPE TEST BANK',
account_holder_name: 'Jane Aysten',
account_number: '000123456789',
routing_number: '110000000'
}
}
Still restricated
worthy crow
what's the account ID of that account that was created using that code and is restricited?
hazy lodge
first one
worthy crow
what is the account ID acct_xxx.
hazy lodge
acct_1O9oA3C1LzoBDIVb
worthy crow
line1: '1224'
note that is incorrect, you need to use the stringaddress_full_matchas mentioned in the testing docs I linked above.
dob: { day: '25', month: '08', year: '1990' },
same with that, it must be 1/1/1901
lyric tartanBOT
hazy lodge
but i think that's not issue right?
worthy crow
acct_1O9oA3C1LzoBDIVb
if you check the requirements hash in the API you can see that the following fields are required and have not been provided in your code:
company.name
company.tax_id
the requirements are documented on https://stripe.com/docs/connect/required-verification-information#US+US+custom+full+individual+card_payments,transfers:~:text=external_account-,COMPANY,-Company name
I'd suggest taking the time to read through all the docs in detail slowly and use the API to build your confidence in understanding the state of the accounts and how to know what information is needed. You're integrating Custom Connect which is the most complicated product Stripe has and it will take a lot of dev work to understand and build.
hazy lodge
we have to lunch our app on tommorow
and facing this issue, now what can we do for this new requirment....
worthy crow
Your timeline might be imossible to meet then, sorry, you don't seem to be ready to go live with this.
worthy crow
and facing this issue, now what can we do for this new requirment....
provide the information that is required and the API is clearly asking you for(company name and tax ID at least).
hazy lodge
okay then where can i get this tax_id
worthy crow
You ask the user for it.
You are choosing to integrate Custom Connect via the API so you must already have a UI where you ask your users for personal information and your company has people who are familiar with business and identity information collection. If that's not the case, I wouldn't use Custom Connect via the API, you can use one of our hosted onboarding surfaces such as Express.
Either way I'm sorry but it seems impossible to launch tomorrow really so you likely want to take a step back and work with your company overall.
hope that helps!
hazy lodge
what is tax_id for testing purpose?
worthy crow
what is tax_id for testing purpose?
@hazy lodge hopefully your next steps are clear! can we close this thread for now?
hazy lodge
yes thanks a lot