What Is a Statement Descriptor? Examples and Rules

Who this helps: you run a subscription business, customers are disputing charges they did make, and you want to know whether the line on their statement is the reason.

Your customer never sees your checkout page again after they pay. They see one line of text on a card statement, weeks later, next to a coffee and a train ticket. If that line does not say who you are, a real customer calls their bank about a real charge, and a sale you earned becomes a dispute.

What is a statement descriptor?

A statement descriptor, also called a billing descriptor or merchant descriptor, is the short text that identifies your business on a customer's card or bank statement. It is no longer than 25 characters on Visa and 22 on Stripe and Braintree, and for most customers it is the only information they have about a charge when they read their statement.

Visa's merchant data manual calls the merchant name "the most important factor in cardholder recognition of transactions", and says getting it right "reduces costs to Acquirers, Issuers and Merchants."

A descriptor has two possible parts. The static part names your business and stays the same on every charge. An optional dynamic part, written after an asterisk, says what the specific charge was for, such as a plan name or an order number.

What does your customer actually see?

Your customer sees the descriptor your processor sends, though not always in the form you set. Banks and banking apps shorten or reformat it, and Stripe notes that while most banks display descriptors consistently, "some might display it incorrectly or not at all."

Some banking apps now replace the raw text with an enriched version: a clean merchant name, a logo and contact details drawn from card network data. Visa offers this to issuers as Merchant Search and says it "reduces disputes and chargebacks." In most of Europe, according to vendors implementing it, Visa requires issuers to show enhanced merchant data in digital channels by 23 January 2027; no equivalent requirement applies to US banks. Enrichment starts from the merchant data your processor sends, and banks that have not adopted it still show the raw descriptor, so a clear descriptor matters either way.

What are the rules for a statement descriptor?

Two sets of rules apply, and they come from different places. The card networks set what the descriptor must say and how much space it has; your payment processor sets the exact character limit and format it will accept.

What Visa requires. Visa's systems "provide 25 spaces in which to describe the Merchant name", and acquirers must be able to use all 25. The name must be "the name most prominently displayed by the Merchant and by which cardholders recognize the Merchant", while also reflecting your DBA. A name longer than 25 characters must be abbreviated rather than "just truncated after the 25th character", and "the part of the name that uniquely identifies the Merchant to the cardholder must not be abbreviated." Visa also "retains the right to require corrections to non-compliant or confusing Merchant data."

What Visa requires for online sales. A second field travels next to the name. Visa's manual gives the merchant city field 13 characters and says that for card-absent transactions, which include every online subscription charge, it "must contain the Merchant's customer service telephone number, the Merchant's universal resource locator (URL) or internet/e-mail address." Stripe takes these contact details from the public business information in your account settings, and says customers see that information on their card statements or in email receipts.

What your processor allows. Processors can allow fewer than Visa's 25 characters, and set their own format rules. Stripe and Braintree both cap the full descriptor at 22, with the limits below.

What are good statement descriptor examples?

Good statement descriptor examples use the name your customer remembers buying from and add what they bought when it fits, such as NORTHLIGHT, NORTHLIGHT* PRO PLAN or NORTHLIGHT* ANNUAL. A good descriptor does not use your legal entity name, your parent company, or your payment processor's name.

Visa's own manual gives the clearest example. A magazine sold by a publishing house has to appear under "the name of the magazine, as that is the name that was displayed to the cardholder", and may only use the publisher's name if the publisher was clearly shown as the seller. A subscription business is in the same position: customers buy the product, not the company that owns it.

Four patterns work for most subscription businesses.

A long name should be abbreviated, not cut off. Visa's manual asks for exactly that when a name runs past its 25 characters, and says the part customers know you by must stay whole. The same approach works at Stripe's 22, so NORTHLIGHT DGTL STUDIO keeps the brand while NORTHLIGHT DIGITAL STU just stops at the limit.

If you sell through a merchant of record such as Paddle, or as a sponsored merchant under a payment facilitator, Visa allows the platform name, your name, or both joined by an asterisk, and says the merchant "should choose the name that is the more recognizable to the cardholder." That is usually yours, not the platform's.

What should the first charge after a free trial say?

The first charge after a free trial or introductory price should say that the trial has ended. Visa's trial rules, effective 18 April 2020 for merchants offering a subscription with a free or promotional trial, require that first paid charge to stand out on the statement, as Stripe summarizes them.

The requirement is the outcome, not a specific phrase. Visa's merchant data manual lists wording it accepts after your name, "End Trial", "End Offer", "End Free Trial", "End Trial Period", "End Discount" or similar language, and marks the exact text as optional. Its example is MERCHANTNAME END TRIAL, and the same kind of language is also allowed in the 13-character contact field. The same rules require express consent to the terms at signup, one reminder before the trial converts, and an online or SMS way to cancel.

On Stripe this happens automatically if you use Stripe's trial features with a product or account descriptor. Stripe appends * TRIAL OVER to the first paid charge. If you set the descriptor manually on the invoice, you have to add the trial text yourself.

The automatic version has a catch that matters. Stripe's own documentation says that because descriptors are capped at 22 characters, "anything after the 10th character is overwritten with * TRIAL OVER." A descriptor longer than 10 characters is cut to 10 on exactly the charge a customer is most likely to dispute.

The fix is a shortened descriptor of 10 characters or fewer that still reads as your brand. Our guide to Stripe's shortened descriptor covers how to set one.

How does your statement descriptor affect your chargeback ratio?

Your descriptor affects your ratio in two ways: it decides how many disputes customers file, and it decides which account Visa counts them against.

Ana starts a free trial of a meal-planning app in March and forgets about it. In April a charge appears reading MEALPLANPR* TRIAL OVER, which she half-recognizes at best, and she tells her bank she did not make it. One unclear line has now produced a fraud report and a dispute from a customer who meant to pay.

The direct effect. A customer who does not recognize a charge often tells their bank it was fraud, which on Visa arrives as reason code 10.4 and on Mastercard as 4863. That fraud claim files a TC40 report no refund removes, and a transaction appearing as both a dispute and a fraud report counts twice in Visa's VAMP ratio.

The structural effect, which is rarely mentioned: Visa "identifies an account by the static component of its statement descriptor and its acquiring bank." A business using three different static descriptors is three separate accounts to Visa, each with its own ratio.

Splitting your volume across descriptors cuts both ways. Separate descriptors can hide a problem inside a healthy blended number, or put one product line over a threshold on its own. To combine them, Stripe's guidance is to give every descriptor the same static prefix, ask your processor to have Visa aggregate them, and "make the change at the end of a month so it doesn't affect the rate calculations for that month."

How do you change your statement descriptor?

On Stripe, you set the static descriptor and the shortened prefix in the Dashboard under Business details, and they apply to every charge from then on. For subscriptions, Stripe uses the descriptor on the Invoice first, then the one on the Product, then your account default, so a Product descriptor is the simplest way to name each plan.

For one-off card payments on Stripe, the per-charge part is the statement_descriptor_suffix parameter on the PaymentIntent, or payment_intent_data.statement_descriptor_suffix on a Checkout Session. Stripe joins it to your prefix with an asterisk and a space, as in its own example RUNCLUB* OCT MARATHON. Card payments accept only the suffix; the full statement_descriptor parameter works only for non-card payments.

Other processors offer the same pieces under different names: a fixed business name and an optional per-charge part. On a merchant-of-record platform such as Paddle, the platform sets its own portion.

Change it before a dispute teaches you to. Read your own card statement, or use the descriptor checker to see the line exactly as a customer would, and ask whether a customer who forgot they subscribed would recognize it.

FAQ

Facts checked against Visa's Merchant Data Standards Manual (April 2026), Stripe's statement descriptor, payout descriptor, trial compliance and monitoring programs documentation, Stripe's summary of Visa's 2020 trial subscription rules, and Braintree's descriptor documentation. Last reviewed 28 September 2026.