Your Billing Descriptor Is Causing Chargebacks: How to Fix It

On this page 8 sections

1. Why Online Stores Get Unrecognized-Charge Disputes
2. What Visa's Rules Say a Billing Descriptor Must Show
3. The Asterisk Belongs to Someone
4. Static vs. Dynamic Descriptors
5. Worked Example: Fitting Harbor & Pine Into 22 and 13 Characters
6. Renewals and Preorders Post When Nobody's Looking
7. How to Change the Name on Credit Card Statements
8. Open Disputes Still Need Evidence

Key takeaways

• Visa's rules call for the brand customers recognize on the statement. Your LLC's legal name often fails that test.
• Plan around your processor's limit (Stripe's is 22), not Visa's 25. When something has to go, cut the product text and leave the name that identifies you whole.
• On online sales, the 13-character city field should hold a phone number or web address that a person actually answers.
• A payment facilitator's prefix, or Stripe's 10-character limit on the fixed part, can take up the room you need for a subscription or preorder label.

A billing descriptor is the merchant name and contact detail printed next to a charge on your customer's card statement. If it doesn't match the store the shopper remembers, they call their bank and dispute the charge as unrecognized. The fix is mostly mechanical: put the name shoppers know in the name field, and put a phone number or web address someone actually answers in the field beside it. Visa's data rules already require most of this, and your processor makes the change.

Take a Shopify candle store called Harbor & Pine (an illustrative business used in every example below). Its merchant account was opened under the owner's company, HPG Holdings LLC, so that's the name on the statement three weeks after the order. The shopper doesn't connect the two names, and the store loses a sale it legitimately made.

Why Online Stores Get Unrecognized-Charge Disputes

Most of these disputes aren't fraud. The cardholder made the purchase and can't place the statement line. Visa made the same point in a December 2020 reminder to acquirers (Article AI10651). Issuers often tell cardholders to contact the merchant first, and that "requires a correct merchant name / descriptor to avoid unnecessary disputes."

Online sellers see more of this than shops with a counter. An online order placed at midnight leaves little memory. Many e-commerce brands also sell under a storefront name while the merchant account sits under an LLC. Timing makes it worse, because preorders post days after checkout and renewals arrive without the customer doing anything.

A lost dispute costs you the sale and the product you already shipped, and your processor may charge a fee on top. Each one also counts toward your dispute ratio, which your acquirer and the card networks watch. Our explainer on how to calculate your chargeback ratio shows why even a small rise matters. A clear descriptor won't stop every dispute, but it removes the easiest kind to avoid.

What Visa's Rules Say a Billing Descriptor Must Show

The requirements are in Visa's Merchant Data Standards Manual, a public document that Visa revises regularly. The newest edition on Visa's site is dated October 2026. These are network rules, not law, and they aren't one processor's preference either. Your acquirer is responsible for meeting them.

The merchant name field holds 25 characters, counting spaces and symbols, and Visa requires acquirers to be able to use all 25. A longer name must be abbreviated, not just cut off at the 25th character. The part that uniquely identifies you can't be abbreviated at all. Visa's own example shortens the 35-character NEW YORK HOME HARDWARE DISTRIBUTORS to "NEW YORK HOME HDW DISTR."

For purchases of goods or services, the manual lets you add detail after the name and an asterisk, such as an order or reference number for the transaction. The catch is that the required name can't be shortened or cut to make room for that extra text.

Visa's 2020 reminder also limits what can go in the field. A gateway or other service provider doesn't belong there unless it acts as your payment facilitator, which the next section covers. Nothing unrelated to the transaction belongs there either, and that includes marketing. So "HARBOR & PINE*20% OFF" is out, however tempting.

The second field, normally the merchant city, holds 13 characters. On card-absent transactions, Visa requires it to show your customer service phone number or web address in place of a city, and an email address also qualifies. If your online merchant account still shows a town name there, a confused cardholder has no way to reach you from the statement.

Visa tells issuers to pass the name through without cutting it, so what you send is what the cardholder should see. Your processor's limits are a separate question, and many give you fewer than Visa's 25 characters. Stripe's documentation caps statement descriptors at 22. When you add a per-charge suffix, Stripe joins it to your name with an asterisk and a space, and both count toward the 22. A third-party comparison from chargeback.io puts Shopify Payments at 19. Ask your processor for its exact limits before you write anything.

The rule most owners get backwards: a legal entity name feels like the safe, compliant choice, but Visa's rule points the other way. The merchant name must be the one you show most prominently and that cardholders recognize, while still reflecting your DBA (your registered "doing business as" name). For Harbor & Pine, HPG Holdings LLC fails that test, because no customer has ever seen it.

The Asterisk Belongs to Someone

In Visa's rules, the asterisk has a specific job. The 2020 reminder told payment facilitators and similar intermediaries to identify themselves in the name field, with an asterisk between their name and the seller's. That's where the familiar PROVIDER*STORE format comes from.

Visa has since loosened the requirement. In the April 2026 edition of the manual, a facilitator may fill the name field with the sponsored merchant's name alone. It may also use its own name (or an abbreviation), followed by an asterisk and the merchant's name. The October 2026 manual has since replaced that edition, so ask your facilitator which format it uses under the current rules.

The answer matters because a facilitator's prefix uses up part of your character limit. If you have a direct merchant account instead, keep everything left of the asterisk as your fixed, recognizable name and put any changing text on the right.

Static vs. Dynamic Descriptors

In e-commerce, a soft descriptor usually means the changing part of a dynamic descriptor: a short label after the fixed name that identifies your business. Harbor & Pine's fixed part might be "HARBOR & PINE," with "MONTHLY" added on subscription charges, so the statement reads "HARBOR & PINE*MONTHLY." Support varies by gateway and account type, and some gateways accept the field only through the API. Before you build a process around it, confirm that your payment gateway and integrations support it.

A dynamic descriptor is for clarity, not concealment. Visa requires the name field to let the cardholder identify the merchant. Using descriptor text to hide what you sell, or whose sale it really is, can be treated as transaction laundering and can end your merchant account.

Running several storefronts is an underwriting question first and a descriptor question second. Dynamic descriptors on one account can work when the brands sell similar products and you disclosed them at approval. Brands with different products or risk levels need their own accounts. Never add a brand or product category without telling your processor. Your merchant category code and your approval rest on what you disclosed, so selling something else under that account breaks your agreement even if the descriptor is accurate.

Worked Example: Fitting Harbor & Pine Into 22 and 13 Characters

Every assumption here is illustrative. Harbor & Pine sells candles as one-off orders and through a monthly box. Its domain is harborpine.com, and its customer service line, 888-555-0142, is answered during business hours. "Harbor & Pine" is a registered DBA of HPG Holdings LLC. Its processor allows 22 characters in the name field.

The contact row is where owners get caught. A domain that looks short in a browser can run one character past the 13-character field, and a cut-off URL helps nobody. Harbor & Pine uses the phone number, which only works if someone picks up. A full voicemail box sends cardholders straight to their bank. A store with a shorter domain and an inbox someone checks often could use the URL instead, as long as the page it opens explains recent charges and offers an order lookup.

The first subscription row shows why you plan around your processor's limit, not Visa's. The tempting fix is to squeeze the brand into something like "HRBRPN" and keep "MONTHLY BOX." Don't. Visa doesn't allow the identifying part of the name to be shortened to make room for extra detail, so cut the product text instead.

Platform formatting changes the math again. On Stripe, the fixed part in front of a suffix (Stripe calls it the shortened descriptor) runs 2 to 10 characters. Stripe also warns that a longer account descriptor left in that role can be cut off unpredictably. "HARBOR & PINE" is 13 characters, so the store would set the shortened descriptor to "HARBORPINE." That's exactly 10 characters, and it matches the domain customers type. With Stripe's asterisk and space, "HARBORPINE* MONTHLY" comes to 19 characters.

Now suppose Harbor & Pine sold through a facilitator that adds a four-letter abbreviation and an asterisk in front (again illustrative). "PFCO*HARBOR & PINE" already uses 18 of the 22 characters, and no plan label fits after it. If your business depends on subscription billing, weigh that before choosing a facilitator over a direct merchant account.

Renewals and Preorders Post When Nobody's Looking

Recurring charges invite descriptor disputes because they happen without the customer doing anything. Put a plan label in the soft descriptor when you have room. Before each renewal, send a reminder that shows the amount and the exact statement text. Make cancellation easy to find, since a customer who can't cancel tends to dispute instead. Retries after a failed renewal need the same care, and our guide to dunning management for failed subscription payments covers retry schedules that don't surprise people.

Preorders have a timing problem. If you charge weeks after the order, a "*PREORDER" label plus a shipping email that repeats the statement text closes the gap. Our piece on whether to charge preorders now or at shipment covers the rest of that decision.

How to Change the Name on Credit Card Statements

1. Buy something from your own store. Check how the charge appears while pending and again after it posts. Ask a colleague with a different bank to do the same.
2. Confirm the new name is registered. Processors want the descriptor to match your legal name or a registered DBA. If your storefront brand isn't filed as a DBA, file it first. Filing rules vary by state and county, so check the process with your attorney or accountant.
3. Send your processor a written change request. Attach your DBA filing and spell out the exact name and contact text you want. Ask when the change takes effect and whether it also applies to dynamic descriptors.
4. Set up your gateway or platform. If dynamic descriptors are approved, configure them in your e-commerce platform or billing system and run a live test transaction.
5. Tell customers what to look for. Add a line to order confirmations and receipts: "This charge will appear as HARBOR & PINE on your statement."
6. Track unrecognized-charge disputes for the next few billing cycles. Ask your processor whether it offers tools that send order details to the card issuer when a cardholder questions a charge. Those can settle the question before it becomes a dispute.

Open Disputes Still Need Evidence

A new descriptor protects future orders. It does nothing for disputes already filed, which you answer with order records and proof of delivery. Our chargeback rebuttal letter template lays out the evidence that holds up.

Start this week with the test purchase. If the statement shows a name your customers wouldn't recognize, or a city where your phone number should be, gather your DBA paperwork. Then ask your processor which descriptor options your account supports. MannyPay provides merchant accounts for e-commerce businesses, with integrations for the Authorize.net and NMI gateways as well as Shopify and WooCommerce stores. To talk through your processing options, including how descriptors are set on your account, request a free processing quote. A MannyPay specialist responds within one business day.

Sources

1. Visa Merchant Data Standards Manual (October 2026, current edition)
2. Visa Merchant Data Standards Manual (April 2026 edition; payment facilitator name formats)
3. Visa, Standards Reminders for Merchant Name / Descriptor Field (Article AI10651, December 2020)
4. Stripe Docs, Card Payments on the Charges API (22-character limit, asterisk-and-space suffix, 2-10 character shortened descriptor)
5. Clearo Payments, Billing Descriptor: What It Is, With Examples (25-character name field and 13-character city field per Visa's manual)
6. Chargeback.io, Statement Descriptor: Requirements by Processor and Chargeback Risk (Shopify Payments 19-character limit)

IC

About the author

Isabella Cruz

Isabella Cruz is Business Growth & Commerce Editor for Beyond the Swipe, writing for small businesses, restaurants, retailers, entertainment venues and e-commerce sellers.

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.