#calebr
1 messages ยท Page 1 of 1 (latest)
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.
- calebr, 23 minutes ago, 6 messages
Apologies, I had just realized that
We found conflicting info and I was trying to look further and the server got busy. Picking that back up
Thanks
Hi there ๐ jumping in as I've been helping look into this.
What I've been struggling with most is finding a good way to test this to see exactly how the onboarding flow will behave. Any chance you're asking about this because you're starting to see your Connected Accounts with contents inside of future_requirements?
Oh, gotcha, you might actually be able to check this easier than I can then ๐
They're being asked to eventually provide an SSN for one of their officers. We'd like to both prevent them from having a disruption in payouts once the new requirements are live, and also avoid needing to have PII like an SSN go through anyone or any system we control.
If you create a new test mode Connected Account, are future_requirements being populated there too?
I don't think so, but let me check
Ah, I think I see the requirement you're talking about, where the requirement shifts from last-4 of SSN to full SSN over a certain threshold.
Hm, the only thing I can think of to try to force hosted onboarding to collect that, since it seems like more of a threshold requirement, is to set collect to eventually_due when creating the Account Link:
https://stripe.com/docs/api/account_links/create#create_account_link-collect
But looking at the contents of requirements and future_requirements on the account, I'm nervous that it won't.
We're using the embedded onboarding component, so I don't think the account link option applies?
Ah, didn't realize that, let me take another look with that context.
Sorry, I think that was back in the first thread that got closed
Hm, nothing is jumping out at me for that integration path so far, and I'm unsure whether that means it collects eventually due by default, or if it doesn't support that yet.
Okay, it does look like future_requirements is populated with the same ID number requirement for new test accounts, and the onboarding flow doesn't seem to register it as something that can be requested.
Gotcha, can you share the new test account ID so I can follow along?
And you did try to create an Account Session and render the onboarding component for them, but didn't see the full SSN being asked for when doing that? (only the last4)
acct_1OUXbH2jqh9kmkCJ
Yes
Yup, I see the requirement there in the hash where I was expecting.
Alright, so my suspicion is that the embedded component currenlty doesn't support collecting eventually due requirements, so now I have a better idea of what I'm looking for on my end to see if that's correct and being looked at.
Thanks. We'd like to be able to prevent payout interruptions for our clients by preemptively asking for this info, as I'm sure this isn't the only account that we'll need this for
Trying to check in on that now, but if I'm not able to get a prompt response the discussion may need to move into a support ticket.
Okay, thanks
Sorry for the delay, and thank you for your patience. I was able to confirm that the embedded onboarding component currently does not support collecting eventually due requirements, but that is something that is actively being worked on and our team hopes to have that feature available soon.
Okay, thanks. Is there a way to be notified when this becomes available?
Sorry, not that I'm aware of.
I think you will need to look for it instead, and would recommend doing so towards the end of the month.
Thanks