chee-hong_docs

[dawn bane]

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

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

[rancid vine]

Hi River

I want to understand more about the statement_descriptor

There is still quite a number of my stripe acccounts are make use of statement_descriptor when create paymentintent for card charges and not getting 400 error

Is the validation is going to rollout by phase?

[sour zephyr]

I'm not too sure about the timeline of the enforcement. However, you should ensure that your integration updates statement_descriptor to statement_descriptor_suffix as soon as possible to avoid the validation failure. If you wish to find out the enforcement timeline, I'd recommend checking with the Support https://support.stripe.com/contact

[rancid vine]

The tricky part is that statement_descriptor are somehow in used for non-card charges

So we have to maintain a logic like if (paymentType===card) {set statement_descriptor_suffix } else{ set statement_descriptor} , which it obviously can be handled out of box within stripe

[rancid vine]

I already sent out the question to https://support.stripe.com/contact

[sour zephyr]

Great! I'd recommend also following up with the Support about handling the statement_descriptor for the non-card charges as well

[rancid vine]

All right. I have forward exact the same question to Support.

Thanks