How to Change Your Stripe Statement Descriptor
The short answer: in the Stripe Dashboard, open Settings, go to Business settings, and click Public details. Change the statement descriptor or the shortened descriptor there. It must be 5 to 22 characters, use Latin characters, and reflect the name your customers know you by.
Key points
- The descriptor is the name on your customer's card statement.
- A customer who does not recognize it may dispute the payment.
- Stripe sets the rules for what it can contain. The customer's bank decides how it is shown.
- Subscriptions take their descriptor from the invoice or the product, not from the payment.
Where is the setting?
Stripe's support article gives the path: "From the Settings page of the Dashboard, scroll down to Business Settings and click Public Details. From there, you can modify your statement descriptor or shortened descriptor."
Two fields matter:
- Statement descriptor: the full, fixed name.
- Shortened descriptor: a prefix used when part of the name changes per payment.
What are the rules?
Stripe's documentation lists them. A descriptor:
- "Contains only Latin characters."
- "Contains between 5 and 22 characters, inclusive."
- "Contains at least one letter (if using a prefix and a suffix, both require at least one letter)."
- Does not contain the angle brackets, the backslash, the single or double quotation mark, or the asterisk.
- "Reflects your Doing Business As (DBA) name."
- "Contains more than a single common term or common website URL."
How do prefixes and suffixes work?
They let one account show different text per payment. Stripe: "A static prefix, also called a shortened descriptor in the Dashboard, must contain between 2 and 10 characters, inclusive. The remaining characters are reserved for the dynamic suffix."
"The suffix is concatenated with the prefix, the * symbol, and a space to form the complete statement descriptor that your customer sees." Stripe's example: the prefix RUNCLUB and the suffix OCT MARATHON appear as RUNCLUB* OCT MARATHON. "The 22-character limit applies to the complete descriptor", and "dynamic suffixes are supported only for card payments."
If you set a descriptor but no prefix, Stripe uses the descriptor as the prefix for card payments, and "if it's longer than 10 characters, we truncate it".
What about subscriptions?
They work differently. "Because Stripe creates subscription charges automatically, you can't set the statement_descriptor or statement_descriptor_suffix on the associated PaymentIntent." Instead, set the descriptor on the invoice or on the product. Stripe applies them in that order: the invoice first, then the product, then your account's default.
Why does this matter for chargebacks?
Because an unrecognized charge is a reason to call the bank. Stripe puts it plainly: "If your customer can't recognize one of your payments, they might dispute it."
Stripe has a dispute category for it, Unrecognized: "The customer doesn't recognize the payment appearing on their card statement. This is effectively indistinguishable from the Fraudulent reason." Its advice for preventing it: "Make sure your statement descriptor is easily recognizable to your customers and reflects the URL or business name they would associate with their purchase".
Does my name match everywhere the customer sees it?
This is a fictional example. A company registered as Northfield Digital LLC sells a meal-planning app called Platewise. A customer subscribes in March and is renewed in April. Follow the name:
| Where the customer sees a name | What it says |
|---|---|
| The payment page | Platewise |
| The receipt email | Receipt from Northfield Digital |
| The renewal reminder | Your Platewise plan renews on 4 April |
| The card statement | NORTHFIELD DIGITAL |
The customer bought Platewise. A month later the statement shows a company they have never heard of. Nothing is wrong with the charge, and it still looks like one to dispute.
The fix is to choose the name the customer knows and use it in all four places: a descriptor such as PLATEWISE, a receipt from Platewise, and a reminder that says what the statement line will read.
Run the same check on your own business. Make a test purchase, then read your payment page, receipt, renewal email and statement side by side.
What can a descriptor not fix?
- The bank's display. "Most banks display this information consistently, but some might display it incorrectly or not at all." "The card issuer still controls how the descriptor appears on the statement."
- Other kinds of dispute. A clear name does not help when the customer says the order never arrived or that they cancelled.
- A forgotten renewal. A reminder before the charge does more for that than the statement line after it.
Where does ChargePilot fit?
ChargePilot does not set your descriptor; that stays in your Stripe settings. It is for the disputes that arrive anyway. On Stripe, ChargePilot builds the response from your own records, with a person on our team reviewing it, and its Policy health check reads your policies against the disputes you actually get. There is no monthly fee to fight disputes: you pay 15% of what we recover, only when we win. Every price is on one page, and our guide to reason codes explains the label on a dispute.
Questions and answers
Where do I change my statement descriptor in Stripe?
Stripe's support article says: from the Settings page of the Dashboard, scroll down to Business Settings and click Public Details. From there, you can modify your statement descriptor or shortened descriptor.
How long can a Stripe statement descriptor be?
Between 5 and 22 characters, inclusive, according to Stripe's documentation. The shortened descriptor, used as a prefix, must contain between 2 and 10 characters, and the 22-character limit applies to the complete descriptor.
Can I show a different descriptor for each product?
For card payments, yes, with a dynamic suffix. Stripe joins your prefix, an asterisk, a space and the suffix. Stripe's own example is the prefix RUNCLUB and the suffix OCT MARATHON, which the customer sees as RUNCLUB* OCT MARATHON.
Why does my descriptor look different on a customer's statement?
Because the customer's bank decides how to show it. Stripe says most banks display this information consistently, but some might display it incorrectly or not at all, and that the card issuer still controls how the descriptor appears on the statement.
Does a clear descriptor prevent chargebacks?
It removes one cause. Stripe says that if your customer can't recognize one of your payments, they might dispute it, and that clear and accurate statement descriptors can reduce chargebacks and disputes. It does nothing for disputes about delivery, quality or cancellations.
On ChargePilot: ChargePilot on Stripe
By Samuel Bengisu, ChargePilot. Last reviewed November 12, 2026.
Protect your revenue → Get Started
Have your disputes handled — no work on your end wherever ChargePilot submits, a person reviewing every response before it is submitted.
Get Started FreeRelated Posts
How to Fight a Chargeback for Services Rendered
No tracking number? Fight a services chargeback with your agreement, your delivery record and client messages. What card networks ask for, and the time you get.
6 min readCan a Customer Charge Back a Deposit?
Yes, even after signing your terms. What a signed deposit agreement changes, what card networks ask to see, and how to take a deposit that holds up.
5 min read