Billing descriptor: what it is, with examples

A billing descriptor is the name your business goes by on a customer's card statement: the short line of text beside the date and the amount. On a Visa sale, it comes from the merchant name and city fields your acquirer sends with the transaction, and Visa's rules say the name should be the one your customers know. When a customer sees a name they can't place, some of them skip calling you and call their bank.

That makes the billing descriptor one of the cheapest chargeback fixes there is. This guide explains what a billing descriptor is and what each part means, shows weak and clear examples, sets out Visa's character limits, and walks through changing yours and looking up one you don't recognize. Rules are current as of October 2026.

What is a billing descriptor?

It's the merchant name a cardholder sees on the statement, plus the details that travel with it, such as a city or a store number. Visa's Merchant Data Standards Manual (April 2026) says the merchant name should be the name the merchant displays most prominently and by which cardholders recognize it, while still reflecting the DBA. A legal or company registration name shouldn't be used unless it's also the name presented to and recognized by cardholders (Visa).

Put simply, the descriptor should look like your sign, your website or your app, not your incorporation papers. Here's the meaning of each piece you might see on a statement line:

Static vs dynamic billing descriptors

A static descriptor is set once on your merchant account and reads the same on every charge. A dynamic descriptor changes from one transaction to the next, because your gateway sends part of the text with each sale, such as a product line or an order number. Not every processor offers dynamic descriptors, and whatever you send still has to fit the network's fields.

For most small businesses with one brand, static is the right choice. Dynamic earns its keep when one merchant account sells under more than one name, or when an order number on the statement would help customers match a charge to a receipt.

Billing descriptor examples: weak vs clear

Below are made-up businesses and two ways each descriptor could read. Every clear version fits within Visa's 25-character merchant name field, covered with the rest of Visa's rules further down.

The dental practice shows why blind truncation is the trap to watch. Its full name runs 38 characters, so a system that simply cuts at 25 leaves "THE FAMILY DENTAL GROUP O," which could be any practice in the country. The clear version drops "The" and "Group of" and keeps "Alder Point," the words that make it findable.

What makes a good billing descriptor?

One test covers most of it: could a customer who bought from you last month recognize the line in three seconds, without opening their email? A descriptor that passes usually has four things going for it:

1. It uses the name customers actually say, taken from your sign, website or app.
2. Its identifying words survive intact, even if generic words like "company" or "services" get shortened.
3. It adds a location detail when you run more than one outlet, so the customer knows which visit it was.
4. It matches everything else the customer saw: the payment page, the receipt and the order confirmation.

Leave out legal suffixes such as LLC or Inc., internal codes, and abbreviations only your staff would understand. If your brand name is already short, don't pad it.

When isn't a dynamic descriptor worth the trouble? When one account sells one brand, a per-transaction descriptor adds setup and testing without telling customers anything new. Start static, and switch only if your dispute log shows customers confusing product lines or orders.

What are Visa's billing descriptor rules?

Visa's April 2026 Merchant Data Standards Manual sets the format for Visa transactions, and it puts the job on acquirers, which send the data with each sale (Visa):

Thirteen characters is tighter than it sounds. Nashville fits with room to spare. Salt Lake City runs 14 characters, so a business in Salt Lake City can't fit it in full. If your city is long, ask your processor how it will be shortened, then check the result on a real statement.

That table is Visa's. For Mastercard and the other networks, ask your processor what fits rather than assuming Visa's numbers apply everywhere.

Why do unclear descriptors cause chargebacks?

Because a cardholder who can't place a charge tends to assume it isn't theirs. Visa lists confusion over a merchant's name or billing descriptor among the common causes of friendly fraud, which it calls first-party misuse (Visa). Its dispute guide names an unclear merchant name among the usual causes of a 10.4 fraud dispute on a card-absent sale (Visa). Mastercard gives the problem a reason code of its own: 4863, Cardholder Does Not Recognize (Mastercard).

Not every case is an honest mix-up, and some cardholders dispute on purpose. But the unrecognized-charge disputes are the ones a better name can prevent, and they can cost more than the sale itself. Visa says first-party misuse can cost merchants up to double the original transaction amount (Visa).

Run the numbers on a made-up yoga studio in Nashville that bills 400 members $89 a month under its holding company's name. Say four members a month don't recognize the charge and dispute it:

• Reversed sales: 4 × $89 = $356.
• Chargeback fees, at an example $25 each: 4 × $25 = $100.
• Total: $456 a month, or $5,472 a year.

A clear descriptor won't take that to zero, but putting the studio's own name on the statement removes the easiest reason for an honest member to call the bank. Our friendly fraud guide covers how to fight the deliberate cases, and how to prevent chargebacks works through every other cause.

A charge the cardholder doesn't recognize can also lead the bank to ask you for a copy of the sale first. That's a retrieval request, and a clear descriptor gives the cardholder less reason to start one.

How do you set or change your billing descriptor?

Through your processor or acquirer. You don't edit the descriptor at the card network; your acquirer sends the merchant name with each sale, which is why Visa's manual addresses its descriptor rules to acquirers. Here's the order we'd follow:

1. See what customers see. Buy something from your own business with a personal card, then read the statement line or the charge in your banking app.
2. Choose the name on your sign, website or app, which is usually your DBA.
3. Ask your processor to update the descriptor, and ask how it will be abbreviated if it runs past 25 characters.
4. If you have several locations, ask about adding a city or store number to each.
5. If you're with a payment facilitator, ask whether your name can appear alone or after its name and an asterisk.
6. Put the exact statement name on receipts, order confirmations and renewal reminders.
7. Make another test purchase after the change and read the new line.

If customers know your online store by a different name, a separate merchant ID can carry its own descriptor; our merchant ID guide covers when the extra account is worth it. While you're talking to your processor, confirm your merchant category code as well, since it travels with your merchant ID on every sale. If you process with Clearo, your dedicated rep can check both for you.

Subscriptions need extra care

Recurring charges land when the customer isn't thinking about you, which makes a vague descriptor even riskier. Send a reminder before each renewal or trial conversion that names the amount and the exact statement line. Clearo's virtual terminal handles recurring billing, and our chargeback alerts guide covers the early warnings that give you a chance to refund a confused customer before a dispute is filed.

How do you look up a billing descriptor you don't recognize?

Work from your own records outward. We know of no official public directory of billing descriptors, so a billing descriptor lookup is mostly detective work with the clues on the statement. As a cardholder:

1. Match the amount and date against your email receipts and order confirmations.
2. Read the descriptor in pieces. On a Visa transaction, a name followed by an asterisk usually belongs to a payment facilitator, and the business you paid comes after it.
3. Look for a city or store number that points to a place you've been.
4. Open the charge in your banking app. Some apps show more: Mastercard's Ethoca Consumer Clarity puts recognizable purchase details in the cardholder's banking app (Mastercard).
5. Ask your bank. In Mastercard's developer documentation, a cardholder's question in the bank's app or call center sends a request to the merchant, which answers in real time with the purchase details (Mastercard Developers). Visa's Order Insight shares order details with issuers so they can clear up confusion over a legitimate charge (Visa).
6. Once you know who charged you, and the charge is wrong, ask that business for a refund before you file a dispute.

Merchants can use the same tools from the other side. Ask your processor whether you can connect to Order Insight or Consumer Clarity, so the bank can show your customer what they bought before anyone files a dispute. Since an April 2026 update, merchants can also share Compelling Evidence 3.0 data through Order Insight (Visa).

Don't confuse any of this with a BIN number lookup. That identifies the bank that issued a card, not the business that charged it, so it won't explain a strange line on a statement.

Common billing descriptor mistakes

• Billing under a legal or holding company name nobody has seen.
• Letting a long name get cut off at 25 characters, losing the part that identifies you.
• Using one descriptor for two brands that customers know separately.
• Switching processors or facilitators without checking how the new descriptor reads.
• Changing the name without telling repeat customers and subscribers.
• Never making a test purchase to see the real statement line.

Visa's descriptor rules come from the network, not from state law, so they apply the same way to merchants across the United States.

Your next step

Make a test purchase this week and read the statement line the way a customer would. If it doesn't say your name, call your processor. If disputes are already showing up on your statements, send one for a free statement review, and we'll show you what they're costing you. Clearo's payment processing comes with chargeback management tools and a dedicated rep, and you can contact us to talk it through.