Descriptor code is the short string of text that identifies a merchant on a cardholder's bank or card statement, typically a trading name, a prefix set by the payment provider, and sometimes a city or phone number. It travels in the authorization and clearing messages, for example 'SQ *BLUE BEAN CAFE' for a Square merchant. A static descriptor is fixed at onboarding, while a dynamic one is sent per transaction to add a product or order name, with the provider prefix locked. Unrecognised descriptors drive friendly fraud: at 0.5% of 20,000 monthly transactions, that is 100 chargebacks a month counting toward scheme thresholds. Misleading descriptors breach scheme rules and, across a merchant portfolio, can signal transaction laundering.
What is a descriptor code made of
The field is short, usually a couple of dozen characters for the name portion, so every character is negotiated. A typical structure is a provider prefix, a separator and the merchant's own text, for example "SQ *BLUE BEAN CAFE" for a coffee shop taking payments through Square, or "PAYPAL *STEAMGAMES". Card networks also carry a city or customer-service phone number and the merchant country alongside it, and online merchants often put a support URL or phone number in the city slot.
Payment descriptor code meaning: static vs dynamic
A static descriptor is fixed at the merchant account level during onboarding and appears on every transaction. A dynamic, or soft, descriptor is sent per transaction through the API, letting a merchant append a product name or order number, such as "ACMEFIT* ANNUAL PLAN". Acquirers restrict what can be sent dynamically; the prefix normally stays locked so the merchant cannot impersonate another business.
The broader concept, including how descriptors differ between debit and credit statements and in banking apps, is covered under payment descriptor.
Statement descriptor code explained through chargebacks
Unrecognised charges are one of the most common sources of "friendly fraud" disputes. A subscription business trading as "Northwind Labs" but selling an app called "FitPulse" will see cardholders dispute "NORTHWIND LABS 4471" because they never heard of the legal entity. If 0.5% of 20,000 monthly transactions are disputed for this reason, that is 100 chargebacks a month, each carrying a fee and counting toward the card schemes' monitoring thresholds. Changing the descriptor to "FITPULSE APP" often cuts that category sharply. Every avoided claim is one less case entering the dispute flow.
Who controls the descriptor
On platforms, the payment facilitator usually sets the prefix and lets each sub-merchant choose the remainder, subject to review. Card schemes expect the descriptor to match the name the customer saw at checkout, and misleading descriptors are a compliance breach that can lead an acquirer to terminate the account.
Descriptors in due diligence
When a buyer reviews a payment business with many merchants, descriptor hygiene is a quick signal of onboarding quality. A portfolio where descriptors bear no relation to merchant websites often hides transaction laundering, which is a scheme violation and a potential licensing problem for the acquirer or PSP.