#jason_checkout-statementdescriptor
1 messages ยท Page 1 of 1 (latest)
๐ 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/1212798217029296230
๐ 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!
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- jason_payment-statementdescriptor, 16 hours ago, 13 messages
Can you share the payment intent id?
Sure! pi_3OpCMsIqONfMPfff2TPTIZsQ
Hm I see some unique behavior enabled on your account
Could potentially be causing this
Can you try creating a new checkout session and only pass in the suffix (not in addition to statement_descriptor)?
jason_checkout-statementdescriptor
@rocky sonnet what's your ask? You seem to have passed the same exact value in both parameters so I don't really follow
I thought that's what you told me to do. Hahah!
sure but you are trying to debug, so pass statement_descriptor: 'FULL DESCRIPTOR' and statement_descriptor_suffix: 'THIS IS A SUFFIX' and then see which one is used
I guess what's confusing me is that I'm just trying to adjust our compatibility for this change: https://support.stripe.com/questions/use-of-the-statement-descriptor-parameter-on-paymentintents-for-card-charges
When explicitly creating Payment Intent with the card payment_method_types, it's clear what to do, But in this case it's less clear since it's part of a Checkout Session.
We had customers saying that credit card fields were failing. I put together a hot fix, based on the change in this article, and it's fixing the issue. I haven't heard anything from customers about Checkout Sessions not working; I'm just trying to be proactive about this.
But perhaps it simply doesn't apply in that scenario.
yeah sorry this is a bit meta
You're asking what to do and that's what I explained yesterday: pass both
I just tried the thing I told you to try, I passed 'payment_intent_data' => [ 'statement_descriptor' => 'FULL DESCRIPTOR', 'statement_descriptor_suffix' => 'THIS IS A SUFFIX', ],
and my card payment has calculated_statement_descriptor: "CONCERT TI* THIS IS A ",
CONCERT TI* is my "prfix" as I was playing with this for another developer last week.
And THIS IS A is the truncated statement_descriptor_suffix I passed in my code
so as a developer of a plugin my recommendation is that you always pass both so that it's configured to use the right one for cards and can pull from the other one for non card payments.
I appreciate you layouing that out. So we'd pass the same value as both, right? So in some cases it will look redudandt, but in other cases (cards) it will use only the suffix?
I wouldn't pass the same value personally since statement_descriptor is the full descriptor and statement_descriptor_suffix is appended to whatever the prefix is as configured in that account.
So if you are say Uber you would pass something like
'payment_intent_data' => [
'statement_descriptor' => 'UBER NYC RIDE AIRPORT',
'statement_descriptor_suffix' => 'NYC RIDE AIRPORT',
],```
For a card payments they would see `UBER* NYC RIDE AIRPORT` because that suffix is appended to the default prefix
Ah, I see what you mean. Ok, I'll play around with it and figure out what makes the most sense for our application. ๐
Appreciate you taking the time to help me better wrap my head around this!
Sure thing! This is really easy once you get it, but it's so obscure otherwise. I helped design a lot of this in our API so I know it inside out
Oh nice! Out of curiosity, where does the descriptor come from for cards such that only a suffix should be used?
Is it the name of the Stripe account?
It's pulled from https://docs.stripe.com/api/accounts/object#account_object-settings-payments in the API.