What a Stripe statement descriptor is and why it matters for disputes
A Stripe statement descriptor is the text a cardholder sees on their bank statement next to your charge. When it does not match the name they know you by, they ask a simple question: what is this charge? Too often, the next step is a dispute. Stripe's documentation says clear and accurate statement descriptors can reduce chargebacks and disputes. The card networks and issuing banks set rules about what has to appear so a customer can read the statement and know who charged them.
So treat the descriptor as a chargeback prevention tool first. A brand name on a statement is nice to have. A descriptor the customer recognizes can reduce disputes.
The two parts: static prefix and dynamic suffix
A descriptor can have two parts. The static prefix is set on your Stripe account. Stripe's guide says a static statement descriptor appears on all customer statements. It is the constant part, usually your business name.
The dynamic suffix is set per charge. Stripe's guide says a dynamic statement descriptor suffix is joined with the prefix, a star symbol, and a space to form the full descriptor. If your prefix is "ACME" and your suffix is "HEATER", the cardholder sees "ACME* HEATER". The suffix lets you add order or product detail without changing your account settings.
Stripe's requirements for a valid descriptor
Stripe enforces formatting rules on the complete descriptor. The whole descriptor has to use Latin characters only. It has to reflect the business's Doing Business As name, the one customers know. And a lone common word or bare website address is not enough on its own. A bare word like "COFFEE" or a lone URL will not pass. The DBA rule exists because the customer should be able to connect the charge to a real business they gave their card to.
Setting a dynamic suffix on a one-off card charge
For a single card charge, you add the suffix when you create the PaymentIntent. Stripe's guide says you specify the statement descriptor suffix in the PaymentIntent's statement_descriptor_suffix parameter. Pass the product or order reference there, and Stripe combines it with your account prefix at charge time.
Why subscriptions are different
You cannot set the descriptor on a subscription's PaymentIntent. Stripe's documentation says you cannot set the statement descriptor or its suffix on a PaymentIntent for subscription charges because Stripe creates them automatically. Trying to pass the suffix there will not work.
Instead, Stripe's guide says you update a subscription's statement descriptor by updating the Invoice or by specifying it when you create or update a Product. Set the descriptor on the product when the product name itself is what the customer should recognize. Update the invoice when a charge covers something specific to that billing cycle.
Multi-item subscriptions and which descriptor wins
A subscription can carry several items. Stripe's guide says a Subscription with multiple items uses the first item in its items.data array that has a custom statement descriptor. If the first item has none, Stripe looks at the next one. Plan your item order so the most recognizable product comes first, since that is the name the customer will see.
Kanji and kana descriptors for Japanese accounts
Japanese accounts get extra options. Stripe's guide says you can change your account's static kanji and kana statement descriptors and shortened descriptors in the Dashboard. You can also set dynamic suffixes in kanji and kana on PaymentIntents and CheckoutSessions for card charges.
Truncation and calculated_statement_descriptor
Descriptors have a maximum length. Stripe's guide says descriptors exceeding the maximum length are truncated. That means the end of your text can be cut off, so front-load the important part. Put your business name first and the order detail after it.
To see what the customer actually sees, check the API response. Stripe's guide says it computes the full descriptor cardholders see by concatenating the shortened prefix and separators, like the statement_descriptor_suffix. The result appears as calculated_statement_descriptor. One catch: Stripe's guide says the calculated_statement_descriptor in API responses is always the Latin statement descriptor, even for accounts with kanji and kana set.
Limitations: dynamic suffixes are card-only
Dynamic suffixes do not work everywhere. Stripe's documentation says only card payments can carry a dynamic suffix. Other payment methods do not take a dynamic suffix. If most of your volume is not card based, your static prefix has to carry the recognition on its own.
How a clear descriptor connects to lower chargebacks
Confused customers file disputes. Stripe's documentation says providing clear and easy to understand statement descriptors is important to reduce confusion and chargebacks. So match the descriptor to the name on your receipts, your checkout page, and the email you send after purchase. Test it with a real charge before you rely on it.
Sources
What a Stripe statement descriptor is, how the static prefix and dynamic suffix combine, and how to set them for one-off charges and subscriptions.