#mkoenke_account-requirements
sullen cedarBOT
đ Welcome to your new thread!
âąď¸ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
đ 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/1212770072607854642
đ Have more to share? You can add more detail below, including code, screenshots, videos, etc.
â˛ď¸ 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. Thank you for your patience!
weary orioleBOT
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.
- mkoenke_unexpected, 20 hours ago, 24 messages
dusk bobcat
Hello
wintry kernel
hello!
dusk bobcat
So there is fallback logic for what Statment Descriptor is used if you don't set one. The first fallback, is the business_profile.url
wintry kernel
ahh ok that makes sense, but what happens if that url is too long? I can see that it was truncated on the dashboard - what is the logic arounf that
around*
dusk bobcat
Yep, it gets truncated as you noted.
I believe it is 14 characters max
The recommendation really is to set a Statement Descriptor on the Connected Account
So that you control this SD
wintry kernel
Is there a way to have this show as a field when we are using the stripe onboarding tool? Previously we hardcoded the prefix to 'OTT' and now with the new requirements we can not do that. When we process a payment intent, we send a suffix statement_descriptor_suffix - but this is only a part of the statement descriptor. We need to be able to generate the whole thing, but without sending the prefix when we create the account, I have not been able to figure out another way to allow our sellers set the prefix so its within the requirements
dusk bobcat
Hmmm I don't think we collect this via onboarding, no. Let me double check on the best way to handle this.
wintry kernel
ok great thanks so much
dusk bobcat
Ooc are you using collect: eventually_due in your Account Link creation?
wintry kernel
Right now we have collect: 'currently_due' and we are updating to use collection_options: { fields: 'eventually_due' },
when we use 'eventually_due' we can not set the prefix to 'OTT' bc it errors out, but when we remove that from the account creation, theres no way to set it in the stripe onboarding tool so it remains null
dusk bobcat
Thanks for clarifying
wintry kernel
sure thing
weary orioleBOT
wintry kernel
Our preference would be to let stripe generate the prefix, because we know it will pass the new requirements... but we would rather not have to internally generate the prefix by using the same logic that stripe uses... if that logic should change with stripe, what we display in our terms of service will not be correct. However, it doesnt seem like there is a straightforward way to get the prefix that stripe will generate and use when it is not set on the account, so maybe thats the only way. Alternatively, we could allow the person using the stripe onboarding tool to set it, if there is a way to get that input field in that interface.
dusk bobcat
Yeah from what we are seeing so far, I believe we should be setting it for you with the new restrictions. But trying to confirm that still
@dark crystal is going to take over here and will confirm on the above one way or another
dark crystal
Will get back to you when I know more
wintry kernel
sounds good thank you!
dark crystal
Hi so looks like this is an api version thing. To have us auto generate the prefix from business_profile.name, you'll need to use api version 2023-10-16 or higher. Looks like you created that test account with 2019-12-03: https://dashboard.stripe.com/test/logs/req_yPcV2HSyD7hQzO
Would passing business_profile.name in the account creation step work for you? Looks like you do collect some info prior to account creation
wintry kernel
We do collect some infomation prior, but we do not necessarily need to use the name, but we could I suppose. We would need to use the different API version? The one we are using now would use the business_profile.url? Is there no way to get the stripe generated prefix from stripe?
dark crystal
No the newer version takes business_profile.url. On the older api version you're using, we take the first available out of these to generate the static component of the descriptor:
acct.statement_descriptor_prefix
acct.statement_descriptor
acct.business_name
acct.entity.legal_rep.name
hmmm thats strange because currently for this payment intent pi_2OpAa7UmS57H7yUM0NzKs8mn the prefix looks like it was generated from the url, and you are saying we are on the old version?
dark crystal
Correct. It may be that url is the next choice after the above
Doesn't look like they're filled out on the account
wintry kernel
hmm ok, is there any way to retrieve whatever stripe generates for the prefix when it is null on the account?
dark crystal
I recommend setting one of the above fields really so you know what the generated value is
Otherwise, no
wintry kernel
ok, that makes sense - we can just set the value for statement_descriptor_prefix but how do we know what value will be acceptable with the new requirements?
I know there is restrictions on it and not sure how to ensure avoiding the invalid_statement_descriptor_prefix_mismatch error
dark crystal
Oh I wasn't aware of these restrictions
Where did you hear about them?
I think setting acct.business_name would avoid that (if you want to continue using the old api version)
Assuming you want it based off the business name
wintry kernel
It just says "The statement descriptor prefix must be similar to the full statement descriptor." but we don't know how to ensure this - which is why we could just let stripe generate it, but if we do, we need to be able to access it somehow
dark crystal
Yeah makes sense. Would setting acct.business_name work for you?
wintry kernel
we could, but If we are going to set it internally, I would think setting statement_descriptor_prefix with whatever value we can in order to assure it is similar enough to the full statement descriptor would be better? I guess if we are going to set business_name to be used as a fallback with a value we know will pass the requirements, why would we not just want to set statement_descriptor_prefix directly with a value we know will pass the requirements? The problem is knowing what that value should be so its similar enough to not error
dark crystal
Yeah I'm not familiar enough with these new restrictions to say
I recommend talking to our support team on that
They should be able to guide on proper values there better than I
wintry kernel
ok, I can ask them, thanks!
weary orioleBOT
honest otter
mkoenke_account-requirements
wintry kernel
hello