#jason_payment-statementdescriptor
fluid mossBOT
👋 Welcome to your new thread!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
🔗 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/1212536816486453289
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
⏲️ 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. Thank you for your patience!
sage sentinel
wind wadi
Hi, I recommend that you test this on your end. I'm also testing this on my end to confirm.
serene hound
@dusky prairie can you clarify what your exact queston is? You just linked to a support article
jason_payment-statementdescriptor
dusky prairie
When making an API call for a Checkout Session and using the payment_intent_data.statement_descriptor, does that need to be changed to use the statement_descriptor_suffix as well based on that article? The payment_intent_data.capture_method in our case is set to "automatic" — not "card".
I'm currently working on a patch for our PaymentIntent code to correctly use the "suffix" alternative.
serene hound
capture_method is completely unrelated/irrelevant
And yes we recommend setting statement_descriptor_suffix for card payments in that case so pass both if you do card and non card payments
dusky prairie
Ah, so it's fine to pass both in this case? It won't result in a 400 error code as the article says?
serene hound
correct passing both should work fine