Credit Card Billing Descriptors: Stop 'I Don't Recognize This' Chargebacks
Visa's credit card billing descriptor rules, the character limits processors really allow, and how to write a name customers recognize instead of disputing.
Photo: Pixabay
On this page 7 sections
- What Visa Requires in a Credit Card Billing Descriptor
- How a Vague Descriptor Becomes a Chargeback
- Visa's 25 Characters Are the Maximum, Not What You Get
- Static and Dynamic Descriptors, and Where the Line Is
- Descriptor Choices by Business Type
- Bank Apps Can Show More Than Your Descriptor
- How to Change Your Statement Descriptor
Key takeaways
- Visa says don't use your legal entity name unless customers actually see it. If your brand name doesn't say what you sell, add a word such as SALON.
- Visa allows 25 characters for the merchant name, but that's the network's maximum, not your limit. Stripe allows 22, and a dynamic suffix uses 2 of them for the "* " separator.
- For online and phone sales, Visa requires a phone number, URL or email in a 13-character field. Most full domain names won't fit there, but a phone number will.
- Visa's post-trial wording option applies to the location field, not the name. Ask your processor whether it can send that wording before you count on it.
A credit card billing descriptor is the line of text next to your charge on a customer's card statement and in their banking app. For an in-store sale, it shows your business name and city. For an online or phone order, Visa requires the city slot to hold a customer service phone number, web address or email instead. If that line doesn't match a name the customer knows, a real sale can come back as an "I don't recognize this" dispute.
Fixing it usually takes an afternoon. Send the name printed on your sign or website, and make it fit your processor's character limit before the platform cuts it off for you. For remote sales, put a phone number someone answers where the customer will see it.
What Visa Requires in a Credit Card Billing Descriptor
The rules are in the Visa Merchant Data Standards Manual. They reach you through your acquiring bank and processor as part of your merchant agreement. They are network rules. They aren't law, and they aren't one processor's preference.
The name. Visa Rule ID 0027816 is restated in a December 2020 Visa reminder to acquirers. It says the merchant name must be the one you mainly use with customers and display at your location or on your website. The name also has to be spelled the same way on the receipt, the authorization request, the clearing record and any dispute records. The same document says you shouldn't use your legal or company registration name unless customers actually see and recognize it. The name has to stay consistent, so you can't rotate it or vary it from sale to sale. If you rebrand, change it through your processor.
The space. Visa's systems allow 25 characters for the merchant name, counting spaces and symbols. If your name is longer, Visa requires a sensible abbreviation, not a cutoff at character 25. The location field holds 13 characters. A store puts its city there. For card-absent sales, meaning online, mail and phone orders, the field must hold a customer service phone number, a URL or an email address.
Visa also requires merchant data to stay consistent for the life of a transaction, so the pending authorization and the posted charge should read the same. Visa can require corrections to merchant data it considers noncompliant or confusing. Mastercard, Discover and American Express publish their own merchant data requirements, so ask your processor how your descriptor is set up for each brand.
When Your Brand Name Isn't Enough
The usual advice is "use your brand name." That's incomplete. Visa's manual covers names that make sense on site but confuse people on a statement. Its examples are a parking garage called John's Farm and a restaurant called Ship Chandler. If a name doesn't match the merchant category code (MCC, the four-digit code that classifies your business), Visa requires extra words that tell the cardholder what kind of business it is. So the garage's descriptor has to read John's Farm Parking.
Picture a hair salon called The Foundry (illustrative). At the shop, the scissors in the window explain it. On a statement, between a grocery bill and a streaming charge, "THE FOUNDRY" could be a bar or a steel supplier. "THE FOUNDRY SALON" solves the problem with six more characters.
How a Vague Descriptor Becomes a Chargeback
These disputes rarely start as fraud. A customer sees a name they can't place, decides the card was stolen and taps "dispute" in the app, because that's faster than looking up your phone number.
The same triggers show up in every industry. A holding company name like "JRB HOLDINGS LLC" (illustrative) appears instead of the salon the client visited. A renewal posts months after signup. A spouse reads the statement. So does a client's bookkeeper who never met you. On platforms that add their own prefix, that prefix can push your name almost out of the field.
You can fight these disputes with proof of purchase, and our chargeback rebuttal letter template lists the evidence that tends to win. Winning still costs staff time, and every filed dispute adds to the ratios that networks and processors track. Our breakdown of chargeback ratio limits that put merchant accounts at risk shows where those limits are. Fixing the descriptor costs less than either.
Visa's 25 Characters Are the Maximum, Not What You Get
Merchants who read Visa's manual often write a 25-character name and expect all of it to show. It may not. Twenty-five is the size of Visa's field. Your processor has to produce one descriptor that works for every card brand, so it often sets a smaller limit. Dynamic descriptors also use part of that limit for a separator.
Stripe makes a useful example because it publishes its limits. Its Payment Intents API documentation caps statement descriptors at 22 characters. It bans the characters <, >, \\, ', " and *, and it rejects descriptors made up only of numbers. When you add a dynamic suffix, Stripe joins it to your prefix with an asterisk and a space, and those two characters count toward the 22. These are one processor's rules, not a network standard, so get your own processor's limit in writing.
Worked Example: Fitting Two Businesses Into 22 Characters
Assumptions (illustrative): the platform allows 22 characters and cuts off anything longer, and the contact field matches Visa's 13 characters. The business names and phone number are made up.
| Situation | Descriptor Sent | Characters | What the Customer Sees |
|---|---|---|---|
| Online store, legal name first | NORTHSHORE HOLDINGS LLC DBA TINY WAVE GOODS | 43 | NORTHSHORE HOLDINGS LL |
| Same store, brand name | TINY WAVE GOODS | 15 | TINY WAVE GOODS |
| Contact field, full domain | TINYWAVEGOODS.COM | 17 | Doesn't fit in 13 |
| Contact field, phone number | 800-555-0123 | 12 | 800-555-0123 |
| Gym renewal, long prefix | IRONPEAK FITNESS* ANNU | 22 | Plan name cut to four letters |
| Gym renewal, short prefix | IRONPEAK* ANNUAL RENEW | 22 | Brand and charge type both fit |
With the legal name first, the store uses all 22 characters before the customer reaches a word they know. A line like "NORTHSHORE HOLDINGS LL" is exactly the kind that gets disputed. In the contact field, the 17-character domain is too long for Visa's 13, while the 12-character phone number fits with one to spare. The phone number is the better choice there, as long as a person answers it. For the gym, cutting the prefix from 16 characters to 8 leaves 12 after the separator. That's exactly enough for "ANNUAL RENEW."
Static and Dynamic Descriptors, and Where the Line Is
A static descriptor is set on your merchant account and goes out with every sale. A dynamic descriptor, also called a soft descriptor, is text your gateway or POS adds to a single transaction, usually as a suffix after a fixed prefix. It helps when one account sells different things, such as a membership and a class pack, or when you want an order number on the statement. Whether you can use one depends on your processor and payment gateway, so confirm support before you write checkout code that relies on it.
The suffix can describe the purchase. The merchant name in front of it stays fixed, because Visa requires the name to stay consistent and not rotate from sale to sale. Using descriptors to disguise what a business sells, run another company's sales through your account or make one business look like another breaks network rules and gets accounts terminated. If you're adding a brand or product line, tell your processor before the first sale under it. Our guide on when to tell your payment processor about business changes covers what to report.
Descriptor Choices by Business Type
Online Stores
Many small shops are registered to the owner's LLC, while customers only ever see the store's brand. Gift orders add another reader: someone in the buyer's household who never placed the order. Lead with the brand. In the contact field, use a staffed phone number, or a domain if it fits in 13 characters, and put the same name in the order confirmation email. MannyPay's page on low-risk e-commerce payment processing covers online setups.
Professional Services
For accounting and law firms, the person reading the statement often isn't the client. You bill after the work is done, and the charge lands with the client's bookkeeper, who flags anything unfamiliar. Say the firm is registered as SA Professional Corp, but its website and engagement letters say Harbor Tax Advisors (both illustrative). The descriptor should say HARBOR TAX ADVISORS, which is 19 characters. Card numbers taken by phone and entered in virtual terminals count as card-absent sales, so the contact field needs a phone number, URL or email. MannyPay also has a page on payment processing for professional services firms.
Subscriptions and Memberships
The first paid charge after a free trial or introductory price is a common source of confusion. The customer signed up weeks earlier at a different price and may not connect the two. Visa deals with this in the location field, not the name. On that first recurring charge, the manual says the field may include wording that tells the cardholder the trial or promotion has ended and the regular price now applies.
Something like "TRIAL ENDED" (11 characters, illustrative) fits. Not every platform can send it, so ask before you plan around it. For a later annual renewal, a suffix like "IRONPEAK* ANNUAL RENEW" does similar work in the name field. Our explainer on free trial billing rules from Visa and Mastercard covers what you have to disclose. Gyms can put all of this to work with our guide to gym membership billing without chargebacks.
Salons and Spas
Deposits, late-cancellation fees and no-show charges all go through while the client is out of the chair, sometimes days after a missed appointment. Use the name on the door, and add SALON or SPA if the name doesn't make the business clear. Put the fee policy in the booking confirmation. When you charge a no-show fee, text the client so the statement isn't the first they hear of it. MannyPay's salon and spa payment processing page lists the options.
Bank Apps Can Show More Than Your Descriptor
Visa and Mastercard each have a service that sends order details to the cardholder's bank, so a confusing charge can be explained before it becomes a dispute. Visa's is Order Insight. Mastercard's is Consumer Clarity, from Mastercard-owned Ethoca. Dispute-management firms that sell enrollment describe how they work. Chargeback Gurus explains that Order Insight can show a cardholder whose name was on the shipping address. ChargebackHelp says Consumer Clarity can show your logo, store name and order data.
Both depend on the cardholder's bank taking part, and on you or a dispute vendor enrolling and sending data. They support a clear descriptor but can't fix a bad one. If unrecognized-charge disputes continue after you've fixed the name, ask your processor what enrollment involves and what it costs.
How to Change Your Statement Descriptor
Most processors change a static descriptor through a support request, not a dashboard setting, so most of the work is preparation.
Take the name from wherever customers see you: the sign, the website header, the booking page, the invoice. Count its characters against your processor's limit. Include any prefix, the two-character separator if you use dynamic suffixes, and the 13-character contact field. If the new name differs from your legal name, the processor will likely ask for your registered DBA or trade name filing, so have a scan ready before you send the request.
Make the request in writing and get two answers: the date the change takes effect, and whether it covers card-present sales, card-not-present sales or both. On that date, update your receipts, confirmation emails and invoices to the same spelling, since Visa expects the name to match across the receipt and the transaction records.
Then buy something small from your own business with a personal card. Check the charge in your banking app while it's pending and again after it posts. If someone who bought from you three weeks ago wouldn't recognize that line right away, keep working on it.
If you're opening a new account or reviewing your current setup, request a free quote from MannyPay. Ask to see how your descriptor will appear for in-store sales and for online payment processing. A MannyPay specialist replies within one business day, or you can reach the MannyPay team directly.
Sources
- Visa Merchant Data Standards Manual, October 2026 edition (Visa)
- Visa Merchant Data Standards Manual, April 2026 edition (Visa)
- Article ID AI10651: Merchant Data Standards, Standards Reminders for the Merchant Name Descriptor Field (Visa, December 15, 2020)
- Visa Merchant Data Standards Manual, card-absent and trial-period location field provisions (hosted copy)
- The Payment Intents API: statement descriptor limits (Stripe Docs)
- Order Insight: A Comprehensive Overview (Chargeback Gurus)
- Preventing Friendly Fraud with Ethoca's Consumer Clarity (Chargeback Gurus)
- Ethoca Consumer Clarity (ChargebackHelp)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
