Renewal Rules Directory ↓

Statement descriptor examples that stop chargebacks

As of

Switch within Billing descriptors

What a statement descriptor looks like on a bank statement

A statement descriptor is the line your customer sees next to your charge on their card statement. When it says something odd, they call their bank and dispute. When it names your business, they remember the purchase. Here is a before-and-after pair.

Bad:

SQ *FIRSTCLASS

Good:

TOMS HARDWARE

The bad line hides the business behind a processor code and a vague word. The good line is the name the customer knows. Here is another pair for an online seller.

Bad:

PMT 4419

Good:


MAPLE YOGA STUDIO

The customer paid for a yoga class, not for a payment code. Every example below follows that same idea: name the business the way the customer knows it.

The rules every descriptor example must follow

Stripe's documentation lists rules for a complete statement descriptor. Stripe's rules say the whole descriptor has to use Latin characters only. The descriptor has to match the DBA name, the one the business actually trades under. It also needs more than one common word or a plain web address on its own.

In practice, that means:

  • Use the name on your storefront or website header, not a legal entity name like "TTG Holdings LLC".
  • Avoid single common words. "COFFEE" alone tells a customer nothing. "RED ROOSTER COFFEE" does.
  • Skip bare URLs. "redrooster.com" reads like spam on a statement line.
  • Keep it short. Descriptors exceeding the maximum length get truncated, and a truncated name can look like a stranger's charge.

If you sell in Japan, you can set static kanji and kana descriptors in the Stripe Dashboard. Dynamic suffixes in kanji and kana are also an option for card payments. For everything else, Latin characters are the rule.

Statement descriptor examples for subscriptions

Subscriptions need a descriptor that stays stable, because the customer sees it every month. Stripe's documentation says you cannot set the descriptor or its suffix on a PaymentIntent for subscription charges, because Stripe creates them automatically. To override a subscription's default, update the Invoice or specify the descriptor when you create or update a Product.

Say you run "Harbor Fit" and sell three plans. Set the product-level descriptors like this:

HARBOR FIT BASIC
HARBOR FIT PLUS
HARBOR FIT PRO

The customer sees the same brand each month, plus the plan they chose. A subscription with multiple items uses the first item in its items.data array that has a custom descriptor. So put the descriptor on the first product in the list.

Dynamic statement descriptor examples: prefix, star, and suffix

A static descriptor appears on all customer statements. A dynamic suffix lets you add detail per charge, like the product name. Stripe's guide says the full descriptor joins the prefix, a star symbol, and a space. You set the suffix in the PaymentIntent's statement_descriptor_suffix parameter.

Example: your account prefix is "HARBOR FIT" and you sell a one-off workshop.

HARBOR FIT* DEC 12 WORKSHOP

The API response also returns calculated_statement_descriptor, which is always the Latin statement descriptor. Use it to check your work before customers do.

One limit: dynamic suffixes are supported only for card payments. And per the subscription rule above, you cannot use them on subscription PaymentIntents.

How to set your descriptor in Stripe

Two places, two jobs:

  1. Static descriptor. Set it on your Stripe account. A static statement descriptor appears on all customer statements.
  2. Dynamic suffix. Pass statement_descriptor_suffix on the PaymentIntent for card charges that need product detail.

For subscriptions, set the descriptor on the Product or the Invoice, not the PaymentIntent. For more on suffixes, see statement descriptor suffixes, and for the full Stripe setup, see the Stripe statement descriptor guide.

Why a clear descriptor prevents chargebacks

Stripe's documentation is direct on this: clear and accurate statement descriptors can reduce chargebacks and disputes. Card networks and banks ask for details that help a cardholder read their statement and know who charged them. When your customer can read the line and know it was you, an "I don't recognize this charge" call is less likely.

The fix is never to make cancellation harder or to hide the cancel path. If a customer disputes because they forgot a subscription, the answer is a descriptor that names the plan, and a cancel flow they can find. For a plain-language overview, see what a payment descriptor means.

Common descriptor mistakes, with corrections

Mistake: legal name instead of DBA.

Bad: JLS VENTURES LLC
Good: SUNRISE BAKERY

Mistake: single common term.

Bad: SUBSCRIPTION
Good: DAILY BRIEF NEWS

Mistake: bare URL.

Bad: dailybrief.com
Good: DAILY BRIEF NEWS

Mistake: processor code with no brand.

Bad: SQ *4419
Good: SUNRISE BAKERY

Mistake: descriptor longer than the limit.

Bad: SUNRISE BAKERY AND CAFE DOWNTOWN
Good: SUNRISE BAKERY

The last one risks truncation, and a cut-off name looks unfamiliar. Check every descriptor the way your customer will see it: on a statement line, next to other charges, months after the purchase. If it still reads as yours, it works.

Sources

Copy-ready statement descriptor examples for card statements, subscriptions, and Stripe, plus the rules that keep charges recognizable.