#William1 - Connect

1 messages · Page 1 of 1 (latest)

thick estuary
#

Hi 👋
Thanks for the callout about Support chat. We'll take a look at that.

#

As for the statement descriptor. We do not currently have an exposed validator service for that. The best bet is to simply try to adhere to the guidelines and gracefully recover from failures.

wet ice
#

Would you be able to publish some sort of guidance? Apparently it includes U.S. States - but that is completely random so it could be any assortment of words? What if the state is just part of the DBA name?

thick estuary
#

but that is completely random
I think the process for creating/naming a state is pretty deliberate and not likely to randomly occur.

#

But language does evolve and certain terms do become more common in usage.

wet ice
#

But are Country names not allowed either? What about city names?

thick estuary
#

But if someone is doing business as Minnesota then they'd better be part of the stat government

wet ice
#

Yes

#

So I have government groups on my platform

#

for instance the "New York Police"

#

If they had that as their statement descriptor would it fail?

thick estuary
#

Does it clearly spell out what kind of transaction this is? These rules are put in place because they reduce the number of disputed charges

#

If it was just "New York" then yes, but the name "New York Police" is more specific

wet ice
#

This happened when creating a new account with AccountService

#

When setting AccountSettingsOptions

#

Which has a AccountSettingsPaymentsOptions.StatementDescriptor

thick estuary
wet ice
#

Right

thick estuary
#

But unfortunately none of that gets us any closer to ensuring only valid statement descriptors are used,

#

The best advice is to 1) use the guidelines we provide and 2) DBAs should be specific to a business in their naming

wet ice
#

The problem is that people set their "Statement Descriptor" in our platform and then we later pass it in to whatever else they create (e.g. Accounts, Charges, etc.) - so it is sort of awkward to throw an exception.

The advice you guys have is vague though - and it's not clear about how far it goes. For instance, if a user is a representative of a State, then they should be able to use that state in their Statement Descriptor. Is there some way that we could escalate this conversation to get some more concrete guidance?

thick estuary
#

To escalate the request you will need to write in to Support: https://support.stripe.com/contact/email

I think I will also suggest internally that we see if we can expose a statement descriptor validation endpoint so your form could ping it when the user fills out that field.

#

Because I agree, if the statement descriptor is going to fail, you want to know as soon as the user has provided it to allow them to take corrective action

wet ice
#

Thank you very much!

thick estuary
#

Okay feature request made. If you write in to Support they will have more information about the validation requirements and be able to offer more advice.

wet ice
#

Thank you very much!