#wally648_api
alpine quailBOT
đź‘‹ 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/1212046311076134983
đź“ť 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!
potent bronzeBOT
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.
- wally-statement-descriptor, 16 hours ago, 10 messages
dense flame
Hi đź‘‹ looking at the response to that request, it looks like settings.payment.statement_descriptor, the value you made the request to unset, is set to null and is unset. Are you seeing something different?
obtuse plover
Yeah it is set to null. I was wondering if we can get it to use the logic for this.
If you update an account’s business_profile.name, business_profile.url, or the name of the company or individual and the existing statement descriptor is based on lower precedence data, Stripe automatically resets the statement descriptor to match the higher precedence value. For example, if the statement descriptor is automatically set based on the URL, then you set or update business_profile.name, Stripe resets the statement descriptor to match the business profile name. If the statement descriptor is automatically set based on business_profile.name, and you set or update the name of the company or individual, the statement descriptor doesn’t reset because business_profile.name has higher precedence. The precedence order is business_profile.name, business_profile.url, then the name of the company or individual.
Any update to an account’s full statement descriptor causes Stripe to automatically set the statement descriptor prefix to a shortened version of the updated statement descriptor, even if the previous prefix is manually set.```this thread i linked roadrunner_stripe seemed to believe it should work that way.
dense flame
Looking at our description for that behavior here:
https://docs.stripe.com/upgrades#2023-10-16
I'm getting the impression that is only expected to happen if one of the other values that we pull from is also provided in the request.
The statement descriptor is only set automatically when one of the above fields is provided as a parameter, so existing accounts will not be impacted unless a dependent field is updated. Similarly, settings.card_payments.statement_descriptor_prefix will be defaulted to a shortened version of the settings.payments.statement_descriptor.
Can you try including one of the additional parameters in your update request?
obtuse plover
Yeah I had that hunch too. Let me get a coupld live mode id's.
Here's one with only the 2 statementd descriptor fields req_IZUjKTbTLHT5vg
And here is one changing the business_profile name. req_ESWP8YvWsjSUA6
dense flame
Hm, well that doesn't look like what we say it should, let me poke around a bit.
obtuse plover
Yeah, something is up. Thanks for looking at it!
dense flame
I see that we're setting it on Account creation as described in my testing, let me find an older account and specifically try to test updating that.
obtuse plover
Yeah the account creation works great! This is a pretty old account, I wonder if a newer account works fine too
dense flame
Alright, after some testing, I have an idea of what is going on, but I'm not quite sure whether it's expected. What I think is going on, is that we are respecting your input indicating that you want to set the statement_descriptor to null rather than ignoring your input and setting the statement descriptor automatically.
In my testing, I'm seeing that if I omit the code to unset the existing statement descriptor, that those values automatically update as we describe.
Can you try that and see if you're seeing the same?
obtuse plover
Interesting. That does seem to work! Do you think I would need to unset the statment descriptor first? Or should only change the profile name for example update it always?
dense flame
Ah, actually, I do think that's expected behavior now that I've reread the first part of that description:
In the Accounts API, if no settings.payments.statement_descriptor is supplied, the statement descriptor is automatically set to the first supplied parameter of (in priority order):
I think that's why the automatic behavior isn't kicking in when usetting the value.
I believe (but would recommend testing to double check) that you can skip unsetting the statement descriptor if you want to let us automatically update it based on other information provided.
obtuse plover
Just with my brief testing it seems that I need to "unset" the statement descriptor and then update the business_profile name. Which adds an extra api call, but should work just fine for this đź‘Ť
dense flame
Oh, I see, it looks like if you explicitly set the statement descriptor, then you have to unset it for our automatic logic to kick in. I think the Account I tested with initially had never had it's statement descriptor explicitly set.