Billing Descriptor Chargebacks: Mistakes and Fixes
Chargebacks, Fraud & Security

Billing Descriptor Mistakes That Trigger 'Unrecognized' Chargebacks

Billing descriptor chargebacks start when customers can't recognize your name on a statement. See Visa's rules, the common mistakes and how to fix yours.

On this page 6 sections
  1. How an Unrecognized Charge Turns Into a Chargeback
  2. What Visa's Rules Say About Your Descriptor
  3. Where Descriptor Mistakes Hide: Subscriptions, Brands and Phone Orders
  4. Static or Dynamic Descriptors: Decide by What You Sell
  5. Changing Your Billing Descriptor With Your Processor
  6. Make the Name Familiar Before the Statement Arrives

Billing descriptor chargebacks almost always come down to a short list of fixable mistakes. The statement shows your legal entity name instead of the brand the customer bought from. Or the name gets cut off partway through. Or an online sale carries no phone number or web address the customer could use to place the charge. The customer then calls their bank, says they don't recognize the purchase, and the dispute is often filed as fraud. You lose the sale, pay your processor's chargeback fee and add a dispute to your ratio.

Fixing it costs almost nothing. You need a descriptor that follows the card network rules, a test charge to see what actually prints, and receipts that repeat the same name.

How an Unrecognized Charge Turns Into a Chargeback

A billing descriptor is the text your processor sends with each transaction to identify you on the cardholder's statement and in their banking app. It has a name field and a location field. For a deeper definition, see our glossary entry on what a merchant descriptor is and how to fix confusing statement names.

Customers see that text more often than most merchants think. It shows up as a pending charge in the app minutes after checkout, again as the posted transaction a day or two later, on the monthly statement, and in any purchase alerts the issuer sends. The pending and posted versions can look different if your authorization and settlement data don't match. Every one of those views is a chance for the customer to stop and wonder what the charge is.

Visa has put a number on how big the problem is. Its developer page for Order Insight says that in 2016, close to 3 million disputes came from cardholders who didn't recognize a transaction. The usual pattern: the customer calls the number on the back of the card, the agent asks whether they made the purchase, and "I don't think so" becomes a fraud claim. On a card-not-present sale, a fraud-coded dispute puts the burden on you to show the real cardholder made the purchase.

Some of these disputes are friendly fraud, where the customer did buy and simply forgot. A bad descriptor makes that forgetting much easier. Each one also counts toward the monitoring thresholds covered in our explainer on Visa's VAMP fraud and dispute thresholds.

What Visa's Rules Say About Your Descriptor

These requirements are network rules. They come from Visa's Merchant Data Standards Manual and a related Visa standards reminder on the merchant name field. They are not one processor's preferences.

  • Field sizes. Visa's authorization and clearing systems provide 25 characters for the merchant name and 13 for the merchant city. Acquirers must be able to use all 25.
  • Which name. The merchant name must be the one you display most prominently and the one cardholders know you by, while also reflecting your DBA. Visa's reminder says your legal or company registration name should not be used unless customers also see that name in store or online.
  • Long names. A name over 25 characters must be abbreviated, not just cut off after the 25th character. The part of the name that identifies you to the cardholder must not be abbreviated at all.
  • Consistency. Visa says the merchant name must stay consistent and must not be modified or periodically changed.
  • Location field. For most transactions the city field shows the city where the merchant outlet is located. Card-absent sales are an exception: PayKings' summary of the Visa manual notes that for those sales the field must hold a customer service phone number, URL or email address.
  • Payment facilitators. If you process through a payment facilitator, Visa allows the name field to show the facilitator's name, an asterisk and your name, and asks for whichever is more recognizable.

Here is the rule most merchants get wrong. A cut-off name usually isn't your customer's bank at fault. Visa's reminder says issuers must pass the merchant name field through without truncating it. Names normally get chopped earlier, either because they are longer than 25 characters or because a platform gives you a smaller field. Stripe, for example, uses only the first 22 characters of a card statement descriptor, according to PayKings. Banking apps sometimes replace raw descriptors with a cleaner name or logo, but that layer isn't yours to control. Write the raw text so it works with no cleanup at all.

Worked Example: Counting the Characters

This example is illustrative. Ledgerly is a fictional bookkeeping app owned by Northfield Digital Holdings LLC. Assume its processor set the descriptor to the legal name and sends it in a 25-character field. We also show a 22-character platform limit for comparison.

DescriptorLengthPrints in 25 charactersPrints in 22 characters
NORTHFIELD DIGITAL HOLDINGS LLC31NORTHFIELD DIGITAL HOLDINNORTHFIELD DIGITAL HOL
THE BOOKKEEPING APP BY LEDGERLY31THE BOOKKEEPING APP BY LETHE BOOKKEEPING APP BY
LEDGERLY BOOKKEEPING20LEDGERLY BOOKKEEPINGLEDGERLY BOOKKEEPING

The first row breaks two Visa rules at once: it uses a legal name customers have never seen, and it cuts that name off instead of abbreviating it. The second row puts the one word that matters at the end, so the 22-character version drops "Ledgerly" completely. The third row fits both limits and leads with the brand. In the 13-character location field, "LEDGERLY.COM" fits with one character to spare.

Each unrecognized renewal costs Ledgerly the subscription payment, the chargeback fee in its processing agreement and the staff time to answer the dispute. Some customers also cancel afterward. Plug your own ticket size and fee into that formula, then use our guide to calculating your chargeback ratio to see how quickly a run of avoidable disputes adds up.

Where Descriptor Mistakes Hide: Subscriptions, Brands and Phone Orders

Subscriptions and free trials. A renewal lands weeks or months after signup, when the customer remembers the least. The first charge after a free trial carries the most risk because you've never charged that card before. Use the name from your signup flow and send a reminder before renewals. Several states require renewal notices, as our article on automatic renewal laws for subscription businesses explains. Visa's own manual gives a subscription example: the descriptor for a magazine must be the magazine's name, because that is the name the cardholder saw.

Several brands under one company. Each brand needs a descriptor its own customers will recognize, which can mean separate descriptors or separate merchant accounts. Disclose every brand and website to your processor during underwriting. Running one brand's sales under another brand's name can look like transaction laundering, which is grounds for termination. Let the processor decide how to set the brands up.

DBAs. If the descriptor uses a "doing business as" name, expect the processor to ask for proof you can use it. A filed DBA certificate or a live website showing the brand usually does the job.

Telehealth and other sensitive services. Patients may want a discreet statement line, but discreet still has to be recognizable. Use the brand they signed up under. Don't name a condition or treatment, and don't pick something so generic they can't place it. MannyPay works with telehealth and online pharmacy merchants on these setups. Rules vary by state and federal law, so treat this as general information and confirm details with your compliance counsel.

Phone orders. Keyed sales through a virtual terminal print whatever descriptor is set on that merchant account. If phone orders run on a different account from your website, the two descriptors may not match. Run a test charge, and tell callers exactly what will appear on their statement.

Static or Dynamic Descriptors: Decide by What You Sell

A static descriptor is set on your merchant account and prints the same on every sale. It suits most single-brand businesses because there's nothing to maintain.

A dynamic descriptor changes with each transaction. Your billing system sends text through the gateway with every charge, usually a fixed brand prefix plus a variable part, such as "LEDGERLYANNUAL PLAN" or "LEDGERLYADD-ON SEAT" (20 characters each). Some processors call the variable part a soft descriptor. The terms aren't standard, so ask what your processor's fields are called and how long each one is.

Use dynamic descriptors when customers need to tell charges apart: a software plan plus add-ons, or a deposit now and a balance later. Keep the brand portion identical on every charge. Visa says the required merchant name can't be abbreviated or cut short to make room for extra information, and it can't change from period to period. Not every processor supports dynamic descriptors, and some turn them on only when asked. If you check out through Authorize.net or NMI, confirm the field is enabled before your developer builds around it. Our payment gateways page lists the options MannyPay supports.

Changing Your Billing Descriptor With Your Processor

  1. See what prints today. Visa's dispute management guidelines suggest buying something on your own Visa card at each location and checking the name and location on your statement. Online sellers should check the pending and posted lines in a banking app too.
  2. Draft the new text within your processor's character limit, putting the brand first.
  3. Submit the request in writing with the exact name and location-field text, plus supporting documents such as a DBA filing or your website URL.
  4. Ask which records will change. Confirm that both authorization and settlement data are updated so the pending and posted lines match.
  5. Test again after the processor confirms the change.
  6. Update everything else that shows the old name: checkout pages, receipts, renewal reminders and your billing help page.

Expect the processor to review the request rather than approve it automatically. The descriptor has to match the business they underwrote.

Make the Name Familiar Before the Statement Arrives

A descriptor works best when the customer has already seen it. Add "This charge will appear on your statement as LEDGERLY.COM" at checkout, on receipts and in renewal reminders. Make sure the phone number in the descriptor reaches a person, or at least gets a quick callback. And make refunds easy for customers who forgot to cancel: a refund costs you the sale, while a chargeback costs the sale, a fee and a mark on your ratio.

Both major networks also run services that show customers more detail when they question a charge. Visa's Order Insight, formerly called Visa Merchant Purchase Inquiry, according to Solidgate, sends your order details to the issuer during the inquiry, before a dispute is filed. Mastercard's Consumer Clarity, run through Ethoca, gives issuers a clear merchant name, logo, location and, for some merchants, a digital receipt to show in the banking app. Merchants supply those details through Ethoca's Merchant Self Services API. Ask your processor which of these services you can use, then work through the rest of our chargeback prevention steps.

This week, run a test charge on your own card and read the line as a stranger would. If it isn't a name your customers would recognize, request the change. If you're comparing providers for online payments, ask each one how much control you'll have over your descriptor. A MannyPay specialist responds to every free quote request within one business day.

Sources

  1. Visa Merchant Data Standards Manual
  2. Visa: Standards Reminders for the Merchant Name Descriptor Field
  3. Visa Merchants Dispute Management Guidelines
  4. Visa Developer: Order Insight Digital
  5. Solidgate: Order Insight (OI) Glossary
  6. Mastercard Developers: Consumer Clarity Documentation
  7. Mastercard Developers: Ethoca Merchant Self Services
  8. PayKings: Billing Descriptor Examples, Rules & Chargebacks

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

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.

Related reading