#morteza_api
1 messages ¡ Page 1 of 1 (latest)
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.
- morteza_api, 22 hours ago, 23 messages
- morteza_issuing-web, 1 day ago, 40 messages
- morteza_api, 2 days ago, 34 messages
- morteza_api, 2 days ago, 33 messages
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260576598109720727
đ Have more to share? Add details, code, screenshots, videos, etc. below.
I jsut deleted your message since it included your secret key
now I recommend to roll your secret key in your dashboard since this is a public forum.
how long should I wait for them to be activated
you mean when the connected account will be activated?
once all the required information will be provided
once the connected account has went though onboarding, and Stripe collected all the requirement information.
the account
was created 4 hours ago
by the way when I run card_isuing requests I get an object , how can I get what information should I provide for stripe based on that object ?
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [
"settings.card_issuing.tos_acceptance.date",
"settings.card_issuing.tos_acceptance.ip"
],
"disabled_reason": null,
"errors": [],
"eventually_due": [
"settings.card_issuing.tos_acceptance.date",
"settings.card_issuing.tos_acceptance.ip"
],
"past_due": [
"settings.card_issuing.tos_acceptance.date",
"settings.card_issuing.tos_acceptance.ip"
],
"pending_verification": []
}
this is what I get inside that object
and other data
but it says we must first accept the terms of service through the API
â
Hello
Are you using hosted onboarding? If so, you can create an account link and share it with the connected account. That way they can complete the onboarding and submit required information..
Depending on the type of the connected account, they can often also use their dashboard to submit the data.
What type of accounts are you creating?
custom
In that case, you can build the forms/ui that the connected account can use to accept TOS and then you'd call Update account API to update the specific requirements that are past due in the object
See: https://docs.stripe.com/connect/api-onboarding#determine-information-to-collect
can I call update account and give for that fields the values ??
Yes
so if I update the following fields it's work
"past_due": [
"settings.card_issuing.tos_acceptance.date",
"settings.card_issuing.tos_acceptance.ip"
],
??
Try it out
and for ip I should add my ip ?
No, that should be the connected account's IP.
"tos_acceptance": {
"date": 1720607842,
"ip": "213.123.132.118",
"user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36"
},
I set this one which was already on the object
is that correct?
I guess when the account is created this's on the object to complete TOS , right ?
usually this should be done by the user to whom we create connected account right ?
so we should develop a UI and let them do that
Correct. This is upto you on how you'd build this in your flow.. With API based onboarding, your platform is responsible to collect all the required information in order for the connected account to complete onboarding.