#casey-Custom-Connect
1 messages Β· Page 1 of 1 (latest)
I think I found answer to "2"
Stripe::Payout.create takes currency as an argument
@wary iris but still need help with "1"
Please let me refer to the documents and come back to you π
(I think our friend at Support would be the best to assist)
@wary iris thanks
@snow path the stripe docs state that it's not required but it gets required in testing environment...
so I wasn't sure what to expect in production
I think it's not a problem between Test mode vs Live mode, but honestly I am not certain. I would suggest to reach out to our friend at Support and they would be the best to assist you with requirements and spec
:question: Have a non-technical question, account issue, or need one-on-one support?
We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact
hmm I see.. then are you assuming that the required verification documentation is not correct?
I think there could be other reason
but I'm using exact "successful" values in testing docs too..
Canadian individual doesn't even have to provide any id number
so I'm not sure why it would trigger additional verification every single time
Just double check, I see requirement on name/dob/address. Have you provided address?
no for "transfers"
it doesn't show "address"
and they are also not in "requirements" π
I only have one choice π€
CA custom connect account only accepts "recipient" agreement
maybe the account you're using doesn't have cross-border payouts enabled?
A service agreement establishes the relationship between Stripe and the platform's users.
Yeah could be. Sorry I don't have a direct answer for you now. Maybe just contact our Support would be faster as they might have the knowledge already
:question: Have a non-technical question, account issue, or need one-on-one support?
We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact
Is that Live Support? Let them open an email conversation and further support will come
yes
hmm I see. I will ask them to start the email conversation if I don't get any help π
if it's asking for a document it probably means we can't verify the account from the other info. If it's test mode make sure you use 1/1/1901 as the date of birth so the programatic verification works.
interesting. What's the acct_xxx ID of this account?
acct_1Js20vQdT83WUHhR
the additional verification gets triggered on every single account I create without identity document π
well it's not required, the account is fully active right now. The docs are the minumum requirements to activate the account, I think the document requirement in eventually_due is just that it will eventually be needed if the account passes a certain threshold of payouts as that hits compliance triggers.
But if you're doing a testing for a custom connected account, you can disregard uploading an ID since it is for live accounts.
this is their quote
@burnt plank we've been collecting all eventually_due requirements from users ahead of time so they don't ever get "disabled" period and can provide whatever necessary with some bandwith
fair enough, that's an option you are free to do! I agree the docs should be clearer
do you think we should ignore eventually_due and only focuses on currently_due?
but I'm not sure if it will be the case for
looking at it I think that verification is required at $500,000 of volume. Should really be in the docs
every single Canadian Individual
haha finally
yeah I wanted some clarification like that
thanks for finding that information
where did you get it?
it's up to you, you can ask for the minimum to reduce onboarding friction, and progressively ask for the rest when it's needed, or ask for absolutely everything now
in an internal tool
but does that mean in production, identity_document will also show up on eventually_due?
yep test mode is the same as live
aha.... makes sense
but it won't move to currently_due until they hit $500,000
which would be a rare case in our scenario
time to make some adjustment....
can you just let me know where you found that $500k information so I can make a note of it?
@burnt plank βοΈ
it's an internal tool
as I said ideally it would be in the docs, similar to what we have for some other country/capability combinations like here
I see.. hmm what would be the best way to download a transcript of this thread? just screenshot-ing?
but basically this is all relating to https://stripe.com/docs/connect/testing-verification#testing-thresholds
Other times theyβre triggered by a processing or time component. For example, more information might be required after 1,500 USD in charges or 30 days after an account is created (whichever comes first). To find out what information is required and by when, you can check the requirements[eventually_due] array and the requirements[current_deadline] timestamp.
ideally we'd document the exact triggers but as far as I know they can change as it's all to do with regulatory and compliance reasons, so from your perspective as Custom Connect platform you're intended to treat it generically and just ask for the information when we send you webhhoks about things being currently_due
but in this Canadian Individual case, it's for $500k and not 30 days after account creation or $1500, right?
yes, those are just examples above
thanks! that makes much more sense
in that specific account I looked at the regulatory requirement was $500k of volume
it's not really in the API(though should be documented ideally) as this is something we try to abstract(and heavily push to use Express or Standard accounts so we can handle this for you). I wouldn't take my figure above as a hard rule, it's just to explain this specific case, that is the regulatory requirement for that type of account you create today (and it's the same in live and test mode) , it might change, but basically stuff in eventually_due means it might be needed when certain thresholds are hit in the lifetime of the account
yeah I totally get what you mean, your explanation was through
I wasn't going to screenshot it as a hard rule
but more for the context and reference,
so I can explain this and decide whether we would like to take the same stance toward this as other eventually_due
with our team
or just make it more lenient since $500k is pretty hard to reach π
@burnt plank thanks again