What is a billing descriptor? The text next to your charge

A descriptor is a fixed-width business card

A billing descriptor is the alphanumeric string a merchant configures to appear on cardholder statements. It identifies the merchant to the customer — and its whole design goal, per the card networks, is cardholder recognition: a name the customer will recognize so they do not call their bank and file a dispute.

In practice the descriptor is a tiny budget: 22 characters for card payments, as Stripe and other processors document. Within that budget the merchant fits its doing-business-as name, sometimes a city, and often a processor prefix.

Static and dynamic descriptors

Merchants can use a static descriptor — the same text on every transaction, like AMZN MKTP US — or a dynamic descriptor with a per-transaction suffix that changes, like SQ *DAILY GRIND CAFE 0427, where the suffix identifies the store or order.

The static part is the brand; the dynamic part is the detail. Dynamic descriptors are why one merchant can produce dozens of different-looking lines, all traceable to the same company.

Who writes the name you see

The chain has four links, and each can alter the text. The merchant provides its business name to the processor. The processor formats it (adding its own prefix when required, as payment facilitators must). The card network transmits it within its character limits. And your bank displays it, sometimes reformatting it again.

The result: the name on your statement is the product of a relay race, not a single decision. A pharmacy that processes through Square appears as SQ *MYPHARMACY, with the processor’s marker mandated by network rules rather than chosen by either party.

Why the descriptor is not the legal name

Merchants are supposed to use their doing-business-as name — the brand on the storefront — not their legal entity name. But the two can diverge: a statement reading SMITH HOLDINGS LLC is a merchant using the wrong name, and a statement reading URBANSTEP is the same company using the right one.

The gap between legal entity and brand is one of the biggest sources of "who is this?" moments — and it is the exact situation the descriptor guide and the charges lookup on this site exist for.

1. Split the line at the * Prefix = processor, suffix = merchant. The processor tells you the rail; the suffix tells you who to contact.
2. Check for a brand you know Before assuming fraud, mentally complete the truncated name — a cut-off brand is still the brand.
3. Use the phone or website if present Many descriptors include a phone number or domain; that is the merchant’s real contact channel.
4. Decode before you dispute The decoder maps descriptor patterns to the companies behind them, so you dispute the right entity.

When descriptors break trust

Unclear descriptors are a business problem, not just a consumer nuisance: the networks themselves say unrecognizable merchant names drive dispute calls. For the cardholder, the practical defense is the same one used by fraud departments — match the descriptor against what you bought, when, and through which processor, before concluding anything.

If a descriptor genuinely matches nothing you bought, treat it as an unknown charge: contact the merchant if identifiable, otherwise your bank, within the dispute window that applies to your card.