#hritik9607_api
hollow inletBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1216626316346921020
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
coral cliffBOT
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.
- hritik9607_api, 2 days ago, 26 messages
amber yarrow
I think if you try to onboard a new Custom account to your account in Test mode, you would see these changes
raven hazel
for the already registered user ? how i will check them
i mean for old registered user
amber yarrow
You can call Retrieve Account API to see if their account returns any requirements or future_requirements
raven hazel
Alright, that sounds good. However, in test mode, I only have access to one US connected test account, which is '000123456789.' I'm wondering if there's a way to simulate the 'future_requirement' error for this particular test account so I can validate my various test cases. Do you know if such a simulation is possible?
amber yarrow
that doesn't look like an account id to me. An Account Id is acct_xxx
But you can try calling Retrieve Account API on its Id and see how it looks like
raven hazel
Here is the Stripe account ID: acct_1Ot294QOnCaTQdvu. I have just onboarded this test account using the old flow. However, upon checking the account via the retrieval API, I did not find any pending 'future_requirement' cases. Therefore, I need such pending cases in order to test my new changes aligned with Stripe's updates.
amber yarrow
Hmm could you elaborate what is old flow and what is new flow here?
raven hazel
let linkObj = {
account: opts.account_id,
failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
type: 'custom_account_verification',
collect: "eventually_due",
};
let linkResult = await stripe_obj.accountLinks.create(linkObj);
i have used this object for creating the onboarding hosted page link which is used by the user to create a custom connect account
so above is the old flow because collect: "eventually_due", is used in the old api version
but now below the new request according to the new flow
let linkObj = {
account: opts.account_id,
failure_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/error.html?domain_name=" + opts.domain_name,
success_url: "https://" + opts.web_domain_name + "/payment/stripe-connect/success.html?domain_name=" + opts.domain_name,
type: 'custom_account_verification',
collection_options: {
fields: "eventually_due",
future_requirements: "include"
}
};
let linkResult = await stripe_obj.accountLinks.create(linkObj);
where
collection_options: {
fields: "eventually_due",
future_requirements: "include"
}
is used to create the onboarding hosted page
amber yarrow
Did you change it because of API version or according to any guide?
raven hazel
i have changed it according to some stripes guide
amber yarrow
Yeah could you elaborate a bit more there?
which guide?
Sorry I am trying to make sure we are on the same page
amber yarrow
Ahh alright, that's parameter on newer API version. But I don't think it's related to this 2023-2024 changes, does it?
raven hazel
I think this doc is to meet the Verification requirements changing for US connected accounts, stripe provided us this doc to handle the the changes
we are using apiVersion: '2019-12-03' and stripe hosted onboarding so do we need to to changes for new onboarding or not
although i know we need to do changes for old existing register customer
amber yarrow
Oh if you are using 2019 version then yes please do update, but the new changes mentioned in the first Doc is kind of a different things
They are new changes from 2024 in compare to 2023
raven hazel
we can not update the api version now we will plane it for future
so i want to know do we need to make any changes for new onboarded flow i mean in the request body
amber yarrow
No the code looks good.
Looks, there are 2 things
- You need to update your code to upgrade from API version 2019 to a more recent version, say 2024. That requires updating code as the Doc provides
- You need to test the new changes for Custom Connected Account in 2023-2024 changes. This is a different thing, and it will just send you some more information need to collected in
future_requirements
amber yarrow
If you call Retrieve Account API on that old register Connected Account, do you notice any new future_requirements?
raven hazel
yes i notice it as empty
amber yarrow
Okie can you onboard a new Test Account in Test mode to see if there are those new requirements?
raven hazel
acct_1Ot3ZJPNkmI6NVxS i have created this account but i didn't get any future_requirement error
just created
i also tried this as mention in the https://docs.stripe.com/connect/custom/handle-verification-updates doc but i didn't get the error
@amber yarrow