Update Statement DescriptorThe 20-Character Elevator Pitch
How to Set Up & Update Your Statement Descriptor: A Step-By-Step Guide
You have roughly 20 characters to tell your customer who you are, what they bought, and why they shouldn’t call their bank to report suspected fraud. So…no pressure.
In principle, setting up a statement descriptor sounds easy. That is, until you realize your legal entity name is 40 characters long and looks nothing like the website your customer just visited.
Setting up a billing descriptor feels like an administrative task. While it is a more behind-the-scenes activity, it’s also a branding exercise. The goal is to bridge the gap between your marketing and your finance operations so that your descriptor helps your customers recall their purchases.
So, how do you start? Here’s a step-by-step guide on how to set up your billing descriptor.
Statement Descriptors
Statement descriptors, which range from 12-to-25 characters in length, are a common source of confusion for customers and chargeback for merchants. Understanding the difference between soft, hard, static, and dynamic descriptors can help sellers optimize their descriptors according to best practices. Rigorous testing and ongoing updates can also help merchants remain proactive about preventing cardholder confusion.
Step 1 | Identify Your Most Recognizable Business Name
The IRS or your acquirer may identify you by your legal name, but your customers likely recognize you by another.
In most cases, you should feature your “doing business as” (or “DBA”) name on your billing descriptor. Use your legal name only if it happens to be your customer-facing brand name as well. If you run an online-only business, your domain name is often the strongest trigger for recognition, to display that on your descriptor.
Step 2 | Account for Character Limits
This is where some merchants run into trouble. While processors often claim you have 25 characters, issuing banks frequently truncate descriptors to just 15–22 characters. To play it safe, aim for a “global safe zone” of 15 characters or less.
If you have a long DBA name that brushes against these limits, you’ll need to abbreviate it strategically. You should remove corporate filler words like “Inc.,” “LLC,” “The,” or “Corp.” Also, use standard abbreviations (like “Co” for “Company”), and avoid random letter combinations that look like a cipher.
For example, shorten “The Local Coffee Company LLC,” which is 22 characters long, including spaces, to “Local Coffee Co,” which is just 15 characters long. Run the stranger test on your abbreviations, and spell things out to see how your descriptor reads.
Step 3 | Add Contact Information
When possible, add a phone number. Contact information is a separate field that doesn’t eat into your business name’s character limit, so you don’t have to worry as much about fitting everything in.
One benefit of including your phone number is that it may nudge confused customers to call you, which gives you a chance to defuse fraud fears before they become chargebacks. However, make sure this number is staffed by customer service representatives who are trained to deal with billing descriptor issues; a dead line or inexperienced reps will frustrate customers and compel them to file disputes.
If you are strictly online, you can put in a URL (e.g. “STORE.COM”) in lieu of a phone number, provided that your website is short and easily searchable on Google
Step 4 | Decide Between a Static or Dynamic Descriptor
Should you go with a static descriptor, or a dynamic one? Refer back to your business model to make this decision.
If you sell a single product or offer a small catalog of items, a static descriptor is sufficient and easier to maintain. However, if you operate a marketplace, sell high-value items, or sell a large catalog of items spanning multiple departments, a dynamic descriptor may be a better option.
Still not sure? Revisit the last chapter in this guide, where we go into static vs. dynamic descriptors in detail.
Step 5 | Submit to Your Payment Processor
How you submit your descriptor to your payment processor depends on your provider.
For example, Stripe and Square allow you to do this via an online merchant portal, while legacy providers like Chase or First Data may require you to email to an account manager. Meanwhile, processors like PayPal or Authorize.net may require you to phone in.
When submitting your billing descriptor information, specify the exact, character-accurate descriptor text, a phone number or URL if you’re including one, and the type of descriptor (i.e. static or dynamic) that you’re using.
Always request written confirmation that your billing descriptor has been set up, and keep the ticket number or email on file. If an error occurs later, you need proof that you submitted the correct descriptor information.
| Processor | Dynamic Support | API Required | Update Process | Typical Timeline |
| Stripe | Yes | Yes | Dashboard or API | Immediate |
| Square | Limited | No | Support ticket | 3-5 days |
| PayPal | Yes | Yes | Developer account | 24-48 hours |
| Authorize.net | Yes | Yes | Merchant interface | Immediate |
| Braintree | Yes | Yes | Control panel | Immediate |
| Chase Paymenttech | Static Only | N/A | Account manager | 5-10 days |
| First Dad | Yes | Yes | Terminal config | 3-5 days |
When to Update Your Statement Descriptor
You should update your descriptor immediately after a rebrand, merger, or acquisition, or if you notice a spike in fraud-related chargeback reason codes, or receive complaints from customers saying they didn’t recognize a charge.
Descriptors are not permanent. Instead, they should evolve alongside your business.
If you’re going through a rebranding, merger, or acquisition, your descriptor should change the moment your customer-facing identity does. More critically, if you notice a spike in fraud-related chargeback reason codes, or receive complaints from customers saying they didn’t recognize a charge, you should diagnose and update your descriptor immediately.
On the other hand, you have a slightly longer runway if you’re planning changes that can be foreseen in advance. For instance, if you’re launching a major new product line, expanding into new sales channels, or redesigning your website with a new domain, aim to update your statement descriptor within a month of launch. Doing so can ensure that early adopters of your new product don’t get confused by legacy branding on their billing statements.
Even if you don’t anticipate any changes to your brand or operations on the horizon, audit your billing descriptor at least annually to ensure that it hasn’t been altered during processor updates or migrations. Likewise, conduct a routine “Googleability check” to make sure that your domain is still ranking at or near the top of the search results if a customer types your billing descriptor into their search bar.
Managing Statement Descriptors If You Have Multiple Merchant Accounts
If you have multiple MIDs, you should keep a centralized list of all descriptors. Routinely update and test the list.
As businesses scale, they often accumulate multiple merchant IDs (MIDs). For example, you might have one for your main site, one for an Amazon store, and another for a wholesale division. Because each MID is paired with a different descriptor, things can easily slip through the cracks.
Centralize recordkeeping to keep tabs on all your billing descriptors. Maintain a master document listing every MID and its corresponding descriptor.
Whenever you make a branding update, test all channels; not just your primary one. Also, make sure your customer service team is trained on every variation. If a customer calls about a charge from “Acme Wholesale” and your staff only knows about “Acme Retail,” the caller may be convinced that the perfectly legitimate transaction is fraudulent and open a dispute.
