#mkoenke_unexpected

1 messages ¡ Page 1 of 1 (latest)

honest coyoteBOT
#

👋 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/1212455694318575687

📝 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!

atomic roverBOT
stone furnace
#

Hello! What's the error you're seeing?

obsidian fable
#

invalid_statement_descriptor_prefix_mismatch

#

We have never seen this before. Previously when creating the account link and redirecting them to the stripe interface, we have always set the statement_descriptor_prefix to 'OTT' when we create the account, and then when we create the account link, we were using collect: 'currently_due' - now we want to update to collection_options: { fields: 'eventually_due' } with the expectation that one of our sellers could redirect to the stripe interface and update the requirements that stripe needs. When I started testing this for newly created accounts, I ran into the invalid_statement_descriptor_prefix_mismatch error and the new account never fully verifies unless corrected from the stripe dashboard, we are unable to correct from the stripe onboarding tool interface

stone furnace
#

This is part of the new onboarding requirements and is expected. Let me find the docs, hang on...

obsidian fable
#

The statement descriptor issue is part of the new requirements, so this behavior is expected? Which means we can no longer hard code the prefix. That makes sense. So when I tried creating an account without hardcoding the prefix, everything worked fine, but then there is no prefix set at all, and it doesn't give a field for the seller to set it themselves, is that a problem?

stone furnace
#

If there's no prefix set by you I believe we generate one.

obsidian fable
#

For the accounts that already exist, if we update to use 'eventually_due' will the stripe onboarding tool have the inputs for them to provide the information they need to update?

#

This was the account I created without the prefix and it looks like its not set acct_1Ooq3cRs8e0wKir0

stone furnace
#

I believe so. Have you tried that in test mode?

obsidian fable
#

I have not been able to because I am not sure how to trigger needing to update the requirements

stone furnace
#

No, I mean have you tried to create an Account Link that gathers the eventually due requirements in test mode?

obsidian fable
#

yes

stone furnace
#

Of note from that page:

How we prefill statement descriptors and statement descriptor prefixes. If a statement descriptor isn't provided, the prefill logic has changed to use either the business profile name, the business URL, or the legal entity name of the connected account.

#

That page also has the new error codes, including the invalid_statement_descriptor_business_mismatch one you're running into.

obsidian fable
#

ok gotcha, that makes sense - and for existing accounts where the link was created with the old param, and then we update to the new param when we redirect them to the onboarding tool, will they be able to fix whatever is required and not provided?

stone furnace
#

They should be able to, yes.

obsidian fable
#

Also, if we want to obtain the prefix that is set for an account, we can just retrieve the account and get it from the Stripe::Account.settings?

stone furnace
#

Yes.

obsidian fable
#

ok great thanks so much

stone furnace
#

Happy to help!