#master-yoda_api

1 messages · Page 1 of 1 (latest)

woven stormBOT
#

đź‘‹ 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/1303172882544988221

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

vestal dove
#

Let me know if you need more details 🙂 I appreciate any help you can provide!

limber otter
#

hello! if you reach out to Stripe Support - https://support.stripe.com/contact, they'll be able to advise you on that! I don't really have much context about the statement descriptor change that you're referring to unfortunately

vestal dove
#

I don't know if this can help, but we received this email today:

Hello,    
  
Starting 30 November 2024, statement descriptors for card payments made via the PaymentIntents and Checkout Sessions APIs will be required to include the statement descriptor prefix that you’ve set in your Stripe account settings. This prefix must clearly indicate your business name or DBA.    
  
What this means for you    
  
To accommodate this change, we’ve added the statement_descriptor_suffix parameter. After 30 November 2024, you’ll need to use statement_descriptor_suffix on card payments to define any characters that you’d like to appear alongside the prefix to form your dynamic statement descriptor.    
  
It will not be possible to add a dynamic statement descriptor to a card payment using the statement_descriptor parameter. As an alternative, you can omit the parameter entirely so that only the static prefix will be used.    
 
Note that this change will only affect card payments made via the PaymentIntents and Checkout Sessions APIs when using a dynamic statement descriptor. If your integration does not set the statement_descriptor parameter at the time of payment, there’s no action required of you.    
 
See our docs for more guidance on using statement descriptors.    

If you have any questions, please visit our support site. We’re here to help.    
 
— The Stripe team
limber otter
#

based off this line

 If your integration does not set the statement_descriptor parameter at the time of payment, there’s no action required of you.    

it looks like you don't have to do anything since you mentioned you are not using this parameter