bumbzor-statementdescriptor-changes | Stripe Developers | Page 1

rapid forumBOT Feb 12, 2024, 5:51 PM

#

fiery skiff Feb 12, 2024, 5:52 PM

#

Hi 👋

This was a change in the API from back in 2019
https://stripe.com/docs/upgrades#2019-02-19

rapid kayak Feb 12, 2024, 5:58 PM

#

is it possible that this customer is using the latest API in Stripe, even though we set our own API version in the integration and he is affected by this change?

#

but the API requests would normally use the API version that we set in the api calls.

#

that changelog is not what caused this error for the user. The returned error message linked to here https://support.stripe.com/questions/use-of-the-statement-descriptor-parameter-on-paymentintents-for-card-charges

fiery skiff Feb 12, 2024, 5:59 PM

#

You can specify the API version directly

rapid kayak Feb 12, 2024, 5:59 PM

#

from that page: As of 02/01/2024, Stripe no longer supports the statement_descriptor parameter on the PaymentIntent API for PaymentIntents in which one of the supported payment_method_types is card.

fiery skiff Feb 12, 2024, 5:59 PM

#

Ah, yes, for Payment Intents

rapid kayak Feb 12, 2024, 6:02 PM

#

is this in the API changelog somwehre where we can read more about it?

fiery skiff Feb 12, 2024, 6:08 PM

#

No I don't think so. This isn't a new field or parameter but a requirement for processing payments on card networks

rapid kayak Feb 12, 2024, 6:10 PM

#

right but it feels that a change like this could impact many live stores.

fiery skiff Feb 12, 2024, 6:12 PM

#

I can understand that. It should be widely shared. The Support article appears to be the best public documentation we have presently.

rapid forumBOT Feb 12, 2024, 6:17 PM

#

graceful flame Feb 12, 2024, 6:23 PM

#

@rapid kayak when we made the change it only applied to brand new Stripe accounts, not existing ones

#

bumbzor-statementdescriptor-changes

rapid kayak Feb 12, 2024, 6:24 PM

#

So the change from that article As of 02/01/2024, Stripe no longer supports the statement_descriptor parameter on the PaymentIntent API for PaymentIntents in which one of the supported payment_method_types is card. applies only to new accounts?

#

accounts after 2/1/2024?

graceful flame Feb 12, 2024, 6:25 PM

#

For now yes. We do plan to require this for everyone but we'd tell those accounts about the change before making it

rapid kayak Feb 12, 2024, 6:27 PM

#

so basically on Payment Intents the statement_descrpiptor is not allowed? This is a change that we were not aware of and we need to know if it's something we need to push an update for our customers ( WordPress integration)

graceful flame Feb 12, 2024, 6:38 PM

#

@rapid kayak it's allowed, the docs my colleague linked you to explain this clearly. But for card payments we require that you use statement_descriptor_suffix

rapid kayak Feb 12, 2024, 6:39 PM

#

is this change not when in Test mode? I tried to see if I can replicate the error in test mode but I can't get the error.

#

I tried a few Card payments and that should have triggered it?

graceful flame Feb 12, 2024, 6:40 PM

#

Are you testing on your own Stripe account created before that date though?

rapid kayak Feb 12, 2024, 6:41 PM

#

ah yes that's true.

#

do I need an entire new stripe.com account or just to add an Account under my existing one?

#

pi_3Oj4USG2lcdV7TvN0dnMMm7x

graceful flame Feb 12, 2024, 6:46 PM

#

you seem to be using Connect here. So what would matter is the time the Connect platform was created. Not each connected account. Otherwise we'd break every platform

rapid kayak Feb 12, 2024, 6:53 PM

#

I will relay this to our team and I think we will talk more with our Stripe contact to get more details. Thanks for the info tho!

graceful flame Feb 12, 2024, 6:54 PM

#

sure thing!

rapid kayak Feb 12, 2024, 6:57 PM

#

quick one. in order to try and replicate it we should try with an account and use API keys instead of the Connect method?

#

I know the Platform account is older.

#

are you saying that this change will NOT apply to us if our integration uses Connect? Our customers can't add their API keys manually.

#

but then this would not make sense as this customer uses the Connect feature using Payment Elements so it should NOT apply to him, yet he got the error as he is the first that brought this up.

#

I can get you details of this customer that brought the issue to us shortly

graceful flame Feb 12, 2024, 7:01 PM

#

bumbzor: are you saying that this change will NOT apply to us if our integration uses Connect? Our customers can't add their API keys manually.
yes that's what I am saying

I can get you details of this customer that brought the issue to us shortly
yes that would help

rapid kayak Feb 12, 2024, 7:03 PM

#

so you say it does NOT apply to us since we use Connect BUT then this user is using Connect and got the issue so this is conflicting with what you just confirmed

graceful flame Feb 12, 2024, 7:04 PM

#

hey this is a public server, everyone can see, read and log everything you say. Please do not share PII like this

#

As the developer, you should be able to find the exact request id req_123 for the failed request for example

rapid kayak Feb 12, 2024, 7:05 PM

#

we are trying to see if we can find that via the Connect Platform

graceful flame Feb 12, 2024, 7:06 PM

#

Ask them for it or for a PaymentIntent id or similar, they must have something

rapid kayak Feb 12, 2024, 7:07 PM

#

we are checking.

#

Our team just told me they are in contact with our point of contact at Stripe so will handle it there. Thanks for the assistance!

#bumbzor-statementdescriptor-changes