Billing Descriptor Best Practices: Stop "I Do Not Recognize This Charge"

Show the brand the customer saw at checkout plus a support phone or website, inside the processor's character limits, and test it on a real statement. A descriptor in the legal entity name produces "does not recognize" disputes that issuers often code as fraud, that merchants rarely win and that count in the ratio either way. Use a DBA when the brand differs from the entity, and a soft descriptor only for brands the acquirer approved.

A billing descriptor is the line that identifies your business on the cardholder's card statement. The best practice: show the brand the customer saw at checkout, add a support phone number or website in the second field, stay inside your processor's character limits, and check the result on a real statement. A descriptor that shows the legal entity name produces the classic card-not-present dispute: the cardholder does not recognize the charge, calls the bank, and the issuer files a chargeback the merchant rarely wins and that counts in the ratio whatever the outcome.

What appears on the cardholder's statement

The descriptor is set on your merchant account when the MID is boarded and travels with every transaction from your gateway to the acquirer, through the card network, to the issuer, which prints it on the statement. The issuer can shorten it, drop punctuation and display it in capitals, so the boarding form is the best case, not a promise of what the cardholder reads. Ask your processor for the exact limits, then test on your own card and read the line as a customer would.

Match the descriptor to the brand the customer saw

The typical descriptor dispute is a mismatch between the storefront and the statement. The customer bought from a brand; the descriptor shows the legal entity, a name chosen for a state filing that means nothing to a buyer three weeks after the order. Use one string everywhere, from the checkout page and the confirmation email to the receipt, the shipping label and the descriptor, and when the brand is longer than the field, choose one abbreviation and use it in the email too.

• One brand string everywhere. Checkout, confirmation email, receipt, packaging insert and descriptor carry the same name in the same spelling; no codes, no invoice numbers, no legal suffixes.
• Tell the customer in advance. A line at checkout and in the confirmation email, "this charge will appear as BRAND on your statement", removes the surprise.
• A phone that answers as the brand. The number must reach someone who can find the order and refund it; a voicemail box is a dispute in waiting.

When you need a DBA, and how it reaches the statement

The acquirer underwrites a legal entity: the name on the articles and on the EIN letter. If your brand differs from that name, the acquirer generally wants a documented link between the entity and the brand before it prints the brand on a statement. That link is usually a DBA, also called a trade name or fictitious name, registered with the state or county and entered in the DBA field of the merchant application; some acquirers accept the brand disclosed with the website, others want the registration itself. Whether your state requires one, and where to file it, is a legal question: a professional decides, and IBOCore gives no legal or tax advice. Put the legal name where the form asks for it, the brand in the DBA field, and both on the website's legal pages, so the underwriter and the customer see the same pair.

The documents then show the director on the state filing and on the EIN letter, and the trade name on the DBA registration. At the time of writing, FinCEN's interim final rule of March 2025 exempts domestic companies and US persons from beneficial ownership reporting, while companies formed under foreign law that register in a US state remain subject to it; verify the current FinCEN guidance before relying on that status.

How a bad descriptor becomes a fraud-coded dispute you rarely win

The path from a confusing statement line to a chargeback runs through the issuer, not through you. The cardholder reads the statement, does not recognize the merchant, and calls the bank. Asked whether the purchase was theirs, the honest answer is "I do not know", so the issuer files the dispute under a fraud or "does not recognize" reason code. No one calls your support line, because the descriptor gave them nothing to call. The amount is debited, the dispute fee is billed and the case counts in your monthly ratio. It is hard to win: your evidence proves that the order was placed and delivered, while the issuer asks whether its cardholder authorized it, and the cardholder has already said no. Without authentication on the sale, issuers tend to side with the cardholder, and a won case usually stays in the count. The chargeback fees guide on this blog walks through the cost of one such case; the friendly fraud guide covers the confused but honest customer.

Handling a customer who does not recognize the charge

Because the cardholder's first instinct is to call the bank, be found first and close the question in one contact; the descriptor's phone number and website are the interception layer. Subscription merchants have an extra reason to move fast: a cardholder who reports a charge as unrecognized often receives a new card number, so every future rebill fails. Hours, tooling and refund authority behind that number are covered in the customer support guide on this blog; the steps below are the descriptor-specific part.

1. Answer under the brand name, on the phone and on the page. The caller is checking whether the statement line and the business match; the legal entity name fails that check.
2. Publish a page search engines find for the exact statement line: what the charge is, what the brand sells, how to look up an order by the last four card digits, the date and the amount.
3. Find the order from those data points and read it back: product, date, email address, shipping address. Many callers recognize the purchase at that point.
4. If the caller still does not recognize it, refund at once and confirm in writing; a refund before the dispute costs the sale only, a chargeback adds the fee and the ratio count. Once a chargeback has posted, answer through the acquirer's dispute process instead, as the customer support guide explains.
5. Log the descriptor string each caller read out; a cluster of such calls is a descriptor problem, not a customer problem.

Several brands on one entity: the soft descriptor option

A soft descriptor, sometimes called a dynamic descriptor, is text your processor lets you set per transaction inside an approved pattern, typically a fixed prefix that identifies the merchant account, an asterisk, and a variable suffix for the brand or product. Each store's customer sees that store's name; the acquirer still sees one merchant account. Three limits apply. The prefix eats characters, so the suffix must be short. Not every acquirer offers dynamic descriptors on high-risk MIDs, and those that do generally expect to approve each website and suffix in advance. And a soft descriptor does not split the file: every brand under the prefix shares one chargeback ratio, one reserve and one termination; brands that should be underwritten on their own need one entity per MID, the structure the multiple merchant accounts guide on this blog describes.

Setting the descriptor on a fresh US entity from IBOCore

An IBOCore package is a US LLC or C-Corp incorporated in the director's home state with its EIN issued, a business bank account at Bluebanc or Relay in the company's name with full operational access, and the complete director and business documentation, from the government ID and proof of address to the articles, the operating agreement and the EIN letter. The director is the IBO (Independent Business Operator): a real, KYC-verified US resident, exclusive to one merchant, with a zero criminal record and a credit score of 650 or more, who takes the acquirer's verification calls and stays out of the business. For the descriptor, two facts matter. The entity name on the articles is the legal name the acquirer underwrites. The brand is yours to name on the application, filed through your own ISO or directly with the acquirer; DBA registration and descriptor setup are not part of the package.

• Fill both name fields. The legal name from the articles, the brand in the DBA or descriptor field, a website that carries the brand.
• Brief the director. A verification call may ask what the company sells and under which name customers see it; keep the descriptor in the briefing you give your account manager in the private Telegram group.
• Expect the entity name on settlements. The bank account is in the company's name; settlements arrive under the legal name while the customer sees the brand.
• The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. On the package, ongoing billing starts 30 days after delivery.
• No clawbacks. If a MID is terminated, IBOCore charges nothing; board the package with another acquirer, with the descriptor fixed.

Questions merchants ask

Can I change the descriptor after the MID is live?

Usually yes, through the processor or the ISO, but not silently. A descriptor change alters the merchant record, and acquirers want it to match the website, the DBA and the offer they underwrote, so file it as a formal request and tell the director. Change it once, early, to the string customers recognize, then keep it; a descriptor that moves every month looks like a merchant hiding from its disputes.

Should the descriptor show the legal company name or the brand?

The brand, with the legal name disclosed on the application and shown on the website's legal pages. The customer recognizes the brand; the issuer prints what the acquirer sends; the acquirer sends what the merchant record holds. A legal-name descriptor is correct on paper and wrong on the statement, the only place it is read. If the acquirer insists on the legal name first, put the brand right after it and shorten both.

Does a clear descriptor lower my chargeback ratio?

It targets one category of dispute, the "does not recognize" case, and does nothing for disputes about the product, the delivery or a refund policy the customer could not find; those belong to the refund policy and checkout compliance guides on this blog. Count the disputes and support calls that quote the statement line before and after the change, and change it before scaling traffic, since reported cases stay in the ratio.

Compliance touchpoints that survive audit

Clean setups disclose beneficial ownership, file BOI, use genuine IDs, and keep the IBO informed of website and descriptor changes. Processors re-scan for prohibited products, undisclosed aggregation, and transaction laundering. Violations land on MATCH and kill future MID applications.

• AML / CDD: customer due diligence on the merchant entity.
• PEP screening: politically exposed persons get enhanced review.
• OFAC / SDN: sanctions lists checked on owners and signers.
• Website compliance: refund policy, terms, pricing visible before checkout.

Compliance shortcuts that trigger MATCH

Fake guarantors, borrowed SSNs, cloaked websites, and third-party processing through your MID are the fastest paths to MATCH listings. Recovery requires legal work and years of delay. Disclose, document, and keep the IBO in the loop.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.