ian_paymentintent-statementdescriptor

[split radish]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253371554998521856

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

[signal oxide]

Hm if the statement descriptor looks good on the get account call, I'm not sure why the old descriptor would be used. I recommend reaching out to the support team so they can look into it: https://support.stripe.com/contact

[vague flume]

very odd because even in the dashboard for the payment intent, the correct statement descriptor is showing

i wonder if the bank has a lag time?

[signal oxide]

Yeah not sure. That's why I recommend asking the support team

If you share an example payment intent I can check what statement descriptor we sent to the network

But sometimes the banks do weird things, and the statement descriptor we send isn't what they used

[signal oxide]

so this could be possible

[vague flume]

pi_3PT66KFNVbYFceRM1lNkwD6S

[signal oxide]

What statement descriptor are you expecting

[vague flume]

T&T ASSOC.

[signal oxide]

yeah that's what we passed

so likely a bank thing

that we don't have much insight into

[compact obsidian]

ian_paymentintent-statementdescriptor