Statement descriptors, explained

A statement descriptor is the short line of text that appears next to a charge on a buyer's card or bank statement. It is often the only thing a buyer sees about your business when they check their statement weeks after an order. If they recognize it, they move on. If they do not, they may call their bank.

Stripe's documentation states that clear and accurate statement descriptors can reduce chargebacks and disputes. This page explains Stripe's requirements, how static and dynamic descriptors work, and how to choose a descriptor that matches your business.

Why descriptors matter

Banks and card networks require certain information on statements so that cardholders can understand their charges. The descriptor provides it. Stripe's dispute documentation notes that inquiries, the pre-dispute requests some networks use, often arise because the cardholder does not recognize the transaction description. An unclear descriptor turns a legitimate order into a question, and a question can become a dispute.

Card network rules point the same way. Visa's public rules require that the name used to identify a merchant is the name it mainly uses with its customers, is shown on its website, and is used consistently in every place it appears, including transaction receipts and dispute records. They also require the acquirer to correct merchant names that do not comply or that cause cardholder confusion.

Stripe's descriptor requirements

Stripe's documentation states that a complete statement descriptor, whether a single static descriptor or a prefix plus suffix, must:

• Contain only Latin characters.
• Be between 5 and 22 characters long, inclusive.
• Contain at least one letter. If you use a prefix and a suffix, both need at least one letter.
• Not contain angle brackets, backslashes, single or double quotation marks, or asterisks.
• Reflect your Doing Business As (DBA) name.
• Contain more than a single common term or a common website URL. A website URL alone is acceptable only if it gives a clear and accurate description of the transaction.

Stripe also notes that most banks display descriptors consistently, but some display them incorrectly or not at all. That is one reason to repeat the descriptor in your own emails and receipts.

Static descriptors, prefixes and dynamic suffixes

Static descriptor

You set a single static descriptor in your Stripe account settings. It appears on every customer statement for non-card payments, and Stripe uses it for card payments if you do not set a separate prefix. Stripe suggests a static descriptor is enough if you sell a single product line, your customers understand one value for every transaction, or you prefer the same descriptor on all charges.

Prefix and dynamic suffix

For card payments, you can set a shorter static prefix, which Stripe calls a shortened descriptor in the Dashboard, and add a dynamic suffix to each payment. The prefix must be between 2 and 10 characters. Stripe joins the prefix, an asterisk, a space and the suffix into the full descriptor, and the total must not exceed 22 characters. If you set a static descriptor but no prefix, Stripe uses the static descriptor as the prefix and truncates it if it is longer than 10 characters.

A suffix is useful for transaction-specific detail. For example, a store whose prefix is YOURLAB could show YOURLAB* ORD 10482, so the buyer can match the charge to an order confirmation.

Choosing a descriptor for a research supply business

• Use the name buyers see. The descriptor should match the business name on your website, invoices and receipts. If your site is known by its domain, Stripe recommends using your website domain or business name.
• Describe the business accurately. The descriptor should identify your actual business. A name chosen to make the charge look like something else misleads the cardholder and the card network, and it is the kind of mismatch reviewers look for.
• Keep one business per account. Stripe's dispute guidance says each Stripe account should represent a single business, which allows separate statement descriptors and contact information. Do not run another business's sales under your descriptor, or yours under someone else's.
• Use the suffix for references, not products. An order number or invoice reference helps the buyer match the charge. Product names in a suffix add nothing for the buyer and can be truncated.
• Keep one fixed prefix. Stripe's monitoring program documentation explains that Visa identifies an account partly by the fixed part of its statement descriptor, and recommends giving every descriptor the same static prefix so your dispute and fraud rates are counted together. Do not use separate descriptors to separate parts of your business. If you change your descriptor, read Stripe's guidance on timing first.

Tell buyers what to expect

A descriptor works best when the buyer has already seen it.

• Show a line at checkout, such as: "This charge will appear on your statement as YOURLAB."
• Repeat it in the order confirmation email and the receipt.
• Include it in your FAQ, alongside your support contact details.
• If you authorize at checkout and capture later, explain that the buyer may first see a pending amount before the order is confirmed.

The checkout copy checklist covers where to put this text, and the checklist for reducing disputes covers the other common causes of disputes.

A quick descriptor check

1. Look up your current descriptor and prefix in your Stripe account settings.
2. Compare them with the business name on your site, receipts and invoices.
3. Check the character rules above.
4. Make a test purchase and look at how the charge appears on a real statement, if you can.
5. Check that checkout and your emails mention the descriptor.
6. Review your recent disputes for the reason codes that point to unrecognized charges.

What a descriptor cannot do

A clear descriptor prevents disputes that come from confusion. It does not prevent disputes about products, delivery or fraud, and it does not change how a processor or card network views your business. For how disputes work once they are filed, see disputes and chargebacks: the basics.