Renewal Rules Directory ↓

What a billing descriptor is and how to make it clear

As of

Switch within Billing descriptors

What a billing descriptor is (definition and meaning)

A billing descriptor is the name a cardholder sees on their bank or card statement next to your charge. It is the short line of text that tells them who billed them. Say you run a gym called Riverside Fitness. Your descriptor might read RIVERSIDE FIT. Or it might read PMT*PROCBILL, a name your customer has never heard of.

The billing descriptor meaning matters more for subscription sellers than for one-time shops. A one-time buyer can often figure out a charge. A customer who bought a lamp once can usually figure out the charge. A customer billed every month may see a processor name in the descriptor. They may not connect it to you at all.

Card networks and banks require certain information on statements. This helps customers understand what they bought. Stripe's documentation says clear and accurate statement descriptors can reduce chargebacks and disputes. If you want the related terms, a payment descriptor covers similar ground from the processor side.

Why unclear descriptors cause chargebacks and disputes

Some chargebacks from honest customers start with confusion, not theft. A cardholder sees a charge they do not recognize, calls their bank, and the bank files a dispute. The customer is not lying. They do not know that STRIPE PMT 8842 is their gym membership.

Commenters on the FTC's click-to-cancel amendments described a related pattern. The FTC published its amended Negative Option Rule in the Federal Register on November 15, 2024. The Eighth Circuit's opinion in Custom Communications v. FTC, No. 24-3137, was filed on July 8, 2025. The Eighth Circuit vacated the FTC's 2024 amendments to the Negative Option Rule. The FTC's conforming final rule was published at 91 FR 6507 on February 12, 2026. After the Eighth Circuit's vacatur, the FTC restored the Negative Option Rule to the form it had before the 2024 Rule became effective. The FTC's advance notice of proposed rulemaking was published at 91 FR 12318 on March 13, 2026. That notice asks questions and changes nothing yet. State statutes and ROSCA stay current. Commenters said they often resort to disputing the subscription charge with credit card companies because cancellation is so difficult. Some said they cancel by disputing the charge or cancelling the card altogether.

The networks treat this seriously. Mastercard's guide says a cardholder can dispute a recurring transaction when the cardholder did not know they were agreeing to one. Mastercard's guide also says non-face-to-face recurring disputes need a description of the goods or services. So your paper trail matters as much as your descriptor.

Visa's rules add that a cardholder must try to resolve a dispute with the merchant before the issuer may start one. A clear descriptor helps that call go well. A vague one makes that call harder to place.

What a good billing descriptor looks like (with examples)

A billing descriptor example should pass one test. Would a customer who forgot about your company a month ago still recognize it? Stripe's documentation says a complete statement descriptor must reflect the business's Doing Business As name. That is the standard to aim for.

Good examples:

  • RIVERSIDE FITNESS
  • NORTHSTAR YOGA
  • CLARKDATA SAAS

Bad examples:

  • PMT*4417
  • 8842CHG.COM
  • STRIPE 4455 CA

The bad ones fail because they show a processor or a code instead of your name. Stripe's documentation says a descriptor must contain more than a single common term or common website URL. So a bare word like "SOFTWARE" or a lone domain will not do. Stripe's documentation also says a complete descriptor must contain only Latin characters. The exception is the kanji and kana descriptors Stripe offers.

Length limits are real. Stripe's guide says descriptors exceeding the maximum length are truncated. If your name gets cut off, the most useful part may disappear. Plan for the cut.

How to look up or check your billing descriptor

A billing descriptor lookup is simple in principle: make a small live charge to a real card, then read the statement. Test cards will not show you what customers see. Charge a dollar to your own card, wait for the statement to post, and read the line.

If you use Stripe, you have better tools. Stripe's guide says a static descriptor appears on all customer statements. Check the one set on your account. Stripe's guide also says the calculated_statement_descriptor in API responses is always the Latin descriptor. Pull a PaymentIntent response and read what the customer will see. Our page on the Stripe statement descriptor walks through this in detail.

Check it again whenever you change processors, business names, or products. A descriptor that was fine last year can break after a migration.

How subscription merchants should handle descriptors for recurring charges

Recurring billing needs more care than one-time sales. The customer sees your descriptor many times and may forget the first purchase.

Use a dynamic suffix when you sell more than one thing. 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. So a prefix of RIVERSIDE with a suffix of YOGA reads as RIVERSIDE* YOGA on the statement. You set the suffix in the statement_descriptor_suffix parameter on the PaymentIntent. Our page on the statement descriptor suffix covers the details. For full samples, see these statement descriptor examples.

For subscriptions, the rules shift. Stripe's documentation says you cannot set the statement descriptor or its suffix on a PaymentIntent for subscription charges because Stripe creates them automatically. To override the default, update the invoice. Or specify the descriptor when you create or update a Product. That is where you control what monthly gym members see.

Mastercard's guide says merchants must flag a recurring payment in both authorization and clearing. The merchant-initiated recurring value looks like M1XX. Get the descriptor and the transaction flags right together.

Pair this with honest trial terms. If your free trial converts to a paid plan, say so at signup. Otherwise you create the confusion that free trials that are not free produce.

Common descriptor mistakes that trigger "what is this charge?" calls

These mistakes show up again and again:

  • Using the processor's name instead of yours. The customer has no relationship with your gateway. Show your name.
  • Using a legal entity name nobody knows. Say you incorporated as 4472 Holdings LLC. If everyone knows you as Riverside Fitness, the descriptor should say Riverside Fitness.
  • Abbreviating badly. RVSDFIT means nothing. Cut the least important word, not the most recognizable one.
  • Changing the descriptor and not telling customers. If you rebrand or switch processors, email customers before the first charge under the new name.
  • Sending no receipt. Visa's rules say a merchant must send a receipt right after the first transaction. Each recurring transaction also needs a receipt at the time of the transaction. A receipt with your name reinforces the descriptor.
  • Making cancellation hard. When people cannot cancel, they dispute instead. Mastercard's guide says a cardholder can dispute a recurring transaction when the merchant kept billing after being told to cancel. Build a smooth cancellation flow so customers cancel with you rather than through their bank.

The bottom line on descriptors

Your descriptor is your name on the one document customers actually read each month. Make it say who you are, keep it short enough to survive truncation, and back it with receipts and easy cancellation. A clear descriptor can reduce those calls and your disputes.

Sources

A billing descriptor is the name a cardholder sees on their statement for your charge. Here is how to set one that customers recognize, and why it prevents chargebacks.