Key takeaways
- A billing descriptor is the merchant name and contact line on your customer's statement, and Visa requires it to be the name you use with customers, spelled the same on the receipt, authorization and clearing record, apart from required abbreviations or added detail.
- Visa's merchant name field holds 25 characters and the city field 13; the familiar 22-character limit is a common processor limit, not Visa's field size, so write to whichever is shorter in your setup.
- For Visa card-not-present sales, the city field must hold a customer service phone number, website or email address, which is where "add a phone number" actually goes.
- When an unrecognized card-absent charge is disputed, it is typically filed as fraud, which requires a fraud report first, and Visa's VAMP ratio counts fraud reports and disputes together, so one confused customer can count twice.
- A dynamic descriptor keeps the same name and adds detail after an asterisk; altering the name to dodge Visa's monitoring can cost the acquirer USD 25,000 per merchant per month and get the merchant permanently disqualified.
- ACH has its own descriptor: a 16-character Company Name the payer recognizes and, since March 20, 2026, "PURCHASE" in the entry description for consumer online purchases of goods.
A billing descriptor is the name, and for online sales a phone number or web address, that appears next to a charge on your customer's card or bank statement. It is the one part of your checkout the customer reads weeks later, without context, while deciding whether the charge is theirs.
When the descriptor doesn't match the name they bought from, the customer calls their bank instead of you. In a card-not-present business, if that call becomes a dispute it is typically filed as fraud, and under Visa's rules a fraud dispute starts with a fraud report, so one confused customer can count against you twice. It is one of the simplest fixes in chargeback prevention because it is a setting and a habit, not a tool you buy.
What a billing descriptor is, and what your customer sees
On a Visa transaction the descriptor is mostly two fields, merchant name and merchant city, sent by your processor with the authorization and clearing record and printed by the card issuer. The issuer controls the final display, and one major processor warns that some banks show it incorrectly or not at all. Your job is to send correct, consistent data that matches what the customer saw at checkout.
Visa's Merchant Data Standards Manual is blunt: "The Merchant name is the most important factor in cardholder recognition of transactions."
Say a hypothetical company, Ridgeway Holdings LLC, sells skincare online as Lumora Skin. Its customer could see either line:
- Unrecognized:
RIDGEWAY HOLDINGS LLC WILMINGTON. The customer has never heard of Ridgeway. - Recognized:
LUMORA SKIN 888-555-0142. The brand from the checkout page, plus a number to call.
What the card network rules actually require
Most guides treat the descriptor as branding. Visa treats it as a rule. Section 1.5.1.12 of the Visa Core Rules (October 24, 2026 edition) says the name must be the one the merchant "primarily uses to identify itself to its customers," shown on its website or app and used consistently, spelling included, on the receipt, authorization, clearing record and dispute records, though the clearing-record name may differ where an abbreviation is required or supplementary data is added. The acquirer "must correct non-compliant Merchant names or those causing Cardholder confusion."
Issuers, in turn, must print the clearing-record data that identifies the merchant and "Enables the Cardholder to contact the Merchant" (Section 1.4.3.3). The field detail is in the Visa Merchant Data Standards Manual (October 2026):
| Field | Visa's space | What goes in it |
|---|---|---|
| Merchant name | 25 characters | The name customers know you by, reflecting your DBA. Abbreviate longer names rather than cutting them off, and never abbreviate the part that uniquely identifies you. |
| After an asterisk in the name | Within the 25 | Optional order number, reference number or other transaction detail; installment information such as "1 of 2" goes here. |
| Business type | Within the 25 | Words that say what kind of merchant you are, required when the name is inconsistent with your MCC. |
| Merchant city, card-absent sales | 13 characters | Must contain your customer service phone number, website address or email address. |
The phone number goes in the city field
"Add a phone number to your descriptor" is usually told as optional. For Visa card-absent transactions it isn't: the 13-character city field must hold a customer service phone number, URL or email. That rules out most full web addresses, so a phone number such as 888-555-0142 (12 characters) or a very short domain is the practical choice.
If your name doesn't say what you sell, add it
When the name is inconsistent with your merchant category code (MCC), Visa wants extra words. Its examples: a parking garage called John's Farm bills as "John's Farm Parking," and a restaurant called Ship Chandler bills as "Ship Chandler Restaurant."
American Express says the same
Amex's Merchant Operating Guide lists cardmembers asking about unrecognized transactions among the most common sources of disputes. Its tips: make the name in your submissions match your business name, include your phone number or web address and a description of what you sold, and tell cardmembers which name will appear on their statement.
What about "22 characters"?
The 22-character limit quoted everywhere is not Visa's field size; it is a common processor limit. One major processor requires 5-22 Latin characters, inserts its own asterisk between a fixed prefix and a per-charge suffix, and bans characters such as < > \ ' " *. Visa provides 25 characters and requires acquirers to be able to use all 25. Follow your processor's format for detail after the name, and write to whichever limit is shorter in your setup.
Why an unrecognized charge costs more than one chargeback
Here is how one "I don't know what this is" moves through Visa's system.
- If it is disputed, it is usually filed as fraud. Visa has no dispute condition for a charge the cardholder doesn't recognize. Denying a card-absent purchase falls under condition 10.4 (Other Fraud: Card-Absent Environment), which the issuer can file up to 120 days from the processing date.
- A fraud report comes first. The issuer must report the fraud to Visa before filing a 10.4 dispute (Visa Product and Service Rules 11.8.5.2), and reports fraud whatever the transaction's status, so a report can exist even if no dispute follows.
- Both can land in your ratio. The Visa Acquirer Monitoring Program (VAMP) ratio is fraud reports plus disputes, divided by settled card-not-present transactions. Read together, these rules mean one 10.4 dispute on an unrecognized charge can count twice.
- Winning doesn't take it back. VAMP counts disputes whatever the outcome. The only exclusions Visa lists are disputes resolved through pre-dispute solutions and fraud reports that qualify for Compelling Evidence 3.0, Visa's rules for defeating some "that's not me" disputes with the customer's earlier undisputed purchases.
As published in Visa's VAMP fact sheet, a US merchant is Excessive at a ratio of 1.5% or more with at least 1,500 fraud reports plus disputes in the month, lowered from 2.2% on April 1, 2026. Mastercard's Excessive Chargeback Program flags merchants at 1.5% or more with at least 100 chargebacks in a month. Confirm what applies to your account with your acquirer, and see the chargebacks hub for how each ratio is built.
A hypothetical: a subscription business settles 100,000 card-not-present Visa transactions in a month, with 700 fraud reports and disputes from ordinary causes (0.7%). Then 400 customers don't recognize a renewal and call their bank. If each produces a fraud report and a 10.4 dispute, that is 800 more: 1,500 in total, a 1.5% ratio that meets both of Visa's tests. To try your own numbers in the chargeback ratio calculator, enter fraud reports plus disputes as the count.
The law behind the statement line
Regulation Z requires a credit card issuer to show the seller's name on the statement, and its official interpretation expects it "in essentially the same form" as on the sale documents. Under 12 CFR 1026.13, a charge not identified that way is a billing error, as is a charge the consumer asks the issuer to clarify, with notice due within 60 days of the first statement showing it. Regulation E gives debit cardholders a similar right. These duties sit with the issuer, yours with the network rules and your merchant agreement, but the upshot is that "I don't know what this is" is a formal process. This is general information, not legal advice; ask your attorney about your situation.
How to write a billing descriptor customers recognize
- Use the brand the customer saw at checkout, not the LLC or the parent company.
- Abbreviate, don't truncate. Shorten the generic words; keep the distinctive part whole.
- Say what you sell if the name doesn't.
- Put a phone number or short domain in the contact field, and make sure it reaches someone who can issue a refund.
- Match it everywhere: checkout page, receipt and confirmation email. Tell customers what will appear on their statement.
- Use the asterisk for detail, not a new name. An order number helps a customer match the charge to an email.
- Flag the first charge after a trial. Visa allows wording such as "End Trial," "End Free Trial" or "End Discount" on the first recurring charge after a trial, introductory or promotional period.
- Check what prints. Buy from yourself and read the pending and posted lines in a banking app. Issuers reformat.
How that plays out for hypothetical businesses, written to fit a 22-character processor limit:
| Problem | Before | After (illustrative) | Rule behind it |
|---|---|---|---|
| Holding company name, city instead of contact | RIDGEWAY HOLDINGS LLC / WILMINGTON | LUMORA SKIN / 888-555-0142 | Name customers know; contact in the city field |
| Name hides the business | BLUE OTTER | BLUE OTTER MEAL KITS | Add business type when the name doesn't match the MCC |
| Cut off mid-word | NORTHERN LIGHTS FITNES | NORTHERN LIGHTS FTNSS | Abbreviate, keep the identifying part whole |
| Charge can't be matched to an order | LUMORA SKIN | LUMORA SKIN*58213 | Optional reference after an asterisk |
| First paid charge after a trial | LUMORA SKIN | LUMORA SKIN END TRIAL | Optional "End Trial" wording |
Contact details are about to matter more. For disputes such as 13.1 (merchandise or services not received) and several other consumer conditions processed from October 23, 2027, Visa will require the issuer to supply when the cardholder tried to resolve it with you, the contact details they used and the outcome.
A good descriptor fixes recognition and nothing else. It won't stop stolen-card fraud, real non-delivery, or a customer who recognizes the charge and disputes it anyway; for that, see friendly fraud, the chargeback type nobody warns you about.
Changing an existing descriptor
Ask your processor; the new name must still match your website and fit your MCC. Update checkout, receipts and emails the same day, and tell subscribers the new statement line before their next renewal. Never change a name to reset a ratio.
Static vs dynamic descriptors, and the rules that limit them
A static (or hard) descriptor is the same on every charge. Under Visa's rules, a dynamic (or soft) descriptor keeps the same name and adds per-transaction detail, such as an order number, product or event.
| Aspect | Static descriptor | Dynamic descriptor |
|---|---|---|
| What changes per charge | Nothing | A suffix after the asterisk |
| Example (hypothetical) | LUMORA SKIN | LUMORA SKIN*58213 |
| The merchant name | Fixed | Still fixed |
| Useful when | One product or a simple subscription | Several products, or orders customers match to an email |
| Extra limits | None beyond the name rules | Not for gambling merchants through agents (see below) |
Other supplementary data in the name field "must be static and must appear in all transactions," with narrow exceptions, and nothing may make the field confusing. Ask your processor how its fields map to what Visa receives.
Why some names start with "XYZ*"
A payment facilitator transaction may show the sponsored merchant's name alone or "Payment facilitator name*Sponsored Merchant name," and Visa says the facilitator "should choose the name that is the more recognizable to the cardholder." A marketplace may use its own name or "Marketplace*Retailer." If customers pay you through a platform, check which format applies.
High-risk traps: subscriptions, discreet billing, gambling and descriptor shuffling
Subscriptions and trials
Visa requires a simple cancellation procedure (at least an online one if the order was online) and, when a trial or promotional period is ending, a notice at least 7 days before the charge with the amount, the date and a simple way to cancel online or by text. Send it under your descriptor name.
Federally, the Restore Online Shoppers' Confidence Act (ROSCA) requires online subscription sellers to clearly disclose material terms, get express informed consent before charging, and offer simple ways to stop recurring charges. The FTC's 2024 "click-to-cancel" amendments were vacated by a federal appeals court, and as of November 2026 there is no new final rule. Ask your attorney how these apply to you.
Discreet billing
Some businesses, in health care or adult content for example, want a neutral descriptor. That works only if the neutral name is the one the customer saw at checkout and on the receipt. A discreet name the customer never saw isn't discretion. It is an unrecognized charge. The MCC rule above still applies: ask your processor whether a neutral name needs words saying what you sell.
Gambling
Visa's manual says "Acquirers must prohibit agents from utilizing dynamic Merchant descriptors for Gambling Merchants." The safe course is one static name, the brand players see when they deposit, on every charge. For the category codes involved, see gambling MCC codes 7995, 7801 and 7802 explained.
Descriptor shuffling
Rotating names so no single descriptor crosses a threshold is covered by Section 12.5.3.2 of the Visa Product and Service Rules. If Visa determines that an acquirer, merchant or agent changed the merchant name, data or performance to circumvent VAMP or the Visa Integrity Risk Program, it may assess the acquirer USD 25,000 per merchant, per month, and may permanently disqualify the merchant and its principals from the Visa system.
The legitimate version is separate lines of business: Visa requires two or more MCCs in cases such as outlets on the same premises showing different names, or an online store linking to a separate site that qualifies for a different MCC. If you sell under several brands, raise it with your processor at setup.
ACH has a billing descriptor too
Bank debits carry their own descriptor in the ACH file's Company/Batch Header Record. Per the Nacha ACH Developer Guide:
| Field | Length | What it should hold |
|---|---|---|
| Company Name | 16 characters | "Name of the Originator known and recognized by the Receiver" |
| Company Entry Description | 10 characters | The purpose of the entry; some entry types require specific values |
Since March 20, 2026, Nacha's rules require "PURCHASE" in the Company Entry Description for consumer e-commerce purchases: debits a consumer authorizes online to buy goods (tangible goods, per Nacha's FAQ), including recurring purchases first authorized online. Services and business-to-business payments are excluded. Nacha doesn't say how banks display the field.
ACH has no card network dispute rights, but customers can return a debit. R10 means the customer says the originator is not known to them or not authorized to debit the account; R11 means the entry didn't match the authorization's terms. Both count toward Nacha's 0.5% unauthorized return threshold, so a 16-character name the customer doesn't recognize is a direct route to R10.
How Flux fits
Most of a descriptor fix is yours: the name, the contact line, and receipts that match. No processor can opt you out of the card networks' monitoring programs. Here is what Flux brings to the rest.
- A person reviews every application. Flux works with high-risk businesses deliberately, though not every business qualifies. An individual review can raise an issue you can hear and sometimes fix, such as a descriptor or a refund policy. Talk to the Flux team about how your descriptor will read.
- Fraud detection for what a descriptor can't fix. Flux fraud detection scores each transaction as it comes in and flags or blocks risky ones before they settle, using rules you control.
- 3-D Secure on hosted checkout, payment links and invoices, on every card payment or only riskier ones. Its liability shift covers eligible fraud chargebacks only.
- Recurring billing that charges renewals on schedule, retries failed payments automatically, supports secure card-update links and lets subscriptions be paused.
Software companies work with Flux through its referral and partner program: each referred business applies to Flux, a person reviews it, and it gets its own Flux account, with Flux running the payments, security and support. To become a partner, email support@fluxpayments.com.
Frequently asked questions
What is a billing descriptor?
It is the name, and for online sales a phone number or web address, that appears next to a charge on the customer's card or bank statement. Visa requires the name to be the one the business uses with its customers, spelled the same way on the receipt and in the transaction records.
How many characters can a billing descriptor have?
In Visa's systems the merchant name field holds 25 characters and the merchant city field 13. Many processors set a shorter limit, often 22 characters, so check yours and write to the shorter one.
Can I put a phone number in my billing descriptor?
Yes. For Visa card-not-present transactions, the merchant city field must contain a customer service phone number, website or email address, so that 13-character field is where the number goes, not the name.
What is the difference between a static and a dynamic billing descriptor?
A static descriptor is the same on every charge. A dynamic, or soft, descriptor keeps the same merchant name and adds transaction detail after an asterisk, such as an order number; the name itself should not change.
Does a clear billing descriptor stop chargebacks?
It can prevent many disputes that start with a customer not recognizing a legitimate charge, which in card-not-present sales are typically filed as fraud. It does not stop stolen-card fraud, real non-delivery, or disputes from customers who recognize the charge.
Can I use different descriptors to keep my chargeback ratio down?
No. Under Visa's rules, changing a merchant name or data to get around its monitoring program can bring an assessment of USD 25,000 per merchant per month to the acquirer and permanent disqualification of the merchant and its principals.
Related reading
Want a person to look at your setup?
A person reviews every Flux application, and fraud detection uses rules you control. Tell us about your business and a real person will walk you through how it fits.
Get Started