mark_bacs-displayname

[astral harbor]

👋 Welcome to your new thread!

⏲️ 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.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 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/1401939059059855400

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[lucid cypress]

We have seen this doc as well https://docs.stripe.com/payments/payment-methods/bacs-debit#custom-branding, which seems to indicate that if we don't want custom branding we should either not specify display_name or specify it explicitly to be "Stripe" before requesting the bacs_debit_payments capability. I tried setting settings.bacs_debit_payments.display_name both before and after requesting the capability on my test mode account and got the Stripe::InvalidRequestError: You cannot update the Bacs Direct Debit Display Name error both times.

[dense sentinel]

Hi there 👋 can you share the ID of the failed Account update request? I'd like to take a closer look at the error returned, to see if you're blocked from updating this because it's an Express Connected Account so they should set it themselves, or something else.

[lucid cypress]

Here's a failed request Id: req_sXCj2tUr6Nbo0K

It is an express connected account afaik.

[dense sentinel]

Thank you, taking a look!

Hm, it doesn't look like this failed because we'd rather an Account Link be used here, so I need to do a bit more digging to see if I can spot why this error was thrown.

[lucid cypress]

Thank you!

[dense sentinel]

Unfortunately, what I'm finding is a bit mixed. I'm finding discussions that we intentionally block you from updating this via the API after the capability has been requested (in which case I wonder why you were told to by an agent, and why our docs say you can, update this setting in this way).

I hate to say this, but at this point I'd suggest going back to discuss this further with the support contacts you were working with. I'm not sure if they expected to give you adjusted access to help clean this up. The other key thing here, is that you're trying to undo this over pricing concerns, which my team doesn't have experience dealing with and in general aren't super familiar with all the fees that get assessed. So I'd like you to keep working with the teams that are familiar with those fees, both when they're charged and whether/how to refund those if possible.

[lucid cypress]

Thanks for the response! So I should have our product manager reach back out with questions. Namely: are we expected to have adjusted access to be able to clean up our display_names?

Also, do you think trying this in live vs test mode could possibly produce different results?

[dense sentinel]

Possibly, but I'd expect that to be a pretty low possibility

But yeah, I'd double check with support the right way to clean this up.

I just don't want to risk making a suggestion that seems to work, just to find out later that it inadvertently made the fees worse.

[lucid cypress]

I appreciate your help! We'll reach back out to support.

[lucid cypress]

@serene hinge 👋 Any thoughts other than reaching back out to customer support?

[hardy sage]

mark_bacs-displayname

@lucid cypress It's sadly a hard requirement right now. That name is used during onboarding with BACS where we generate something called the SUN for you and it can't be changed/
I think we're working on making it easier to fix this though but reaching out to our support team is the best approach