m0uka_api

[barren seal]

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

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

[brittle rivet]

Hello! This is not possible. For card charges, you'll want to set statement_descriptor_suffix. Our API reference explains the difference in more detail: https://docs.stripe.com/api/payment_intents/object#payment_intent_object-statement_descriptor

[mellow edge]

so if payment_method_types includes card, and the statement_descriptor field is set, an error will be thrown? even if a statement_descriptor_suffix is defined?

[brittle rivet]

Digging deeper, I might have been wrong about this! It's possible that if you set both, Stripe will choose the right one depending on if it's a card charge or not. Can you try this? I can as well once I respond to another thread.

I see there is also a statement description prefix that might be helpful to you: https://docs.stripe.com/get-started/account/statement-descriptors#static

I was able to create a PaymentIntent with both statement_descriptor and statement_descriptor_suffix then successfully confirm it with a card - let me know if you have issues with this!

[mellow edge]

thanks! i tested this out as well and works fine

another question - would you happen to know if the description field on the payment intent gets displayed somewhere on the customer's payment method?

[formal thorn]

Hi taking over here. Give me a bit to catch up on context