Merchant descriptor
explained.

Why descriptors cause chargebacks

American Express lists, among the causes of its "No Knowledge" inquiries (codes 127 and 176), a charge descriptor showing a business name, location or purchase type the Card Member doesn't recognize. Unrecognized charges often become fraud disputes, such as Visa 10.4, even when the customer did buy from you. Stripe likewise notes that clear, accurate statement descriptors can reduce chargebacks and disputes.

Descriptor rules (Stripe example)

Each processor sets its own limits. Stripe requires a complete descriptor to:

• use only Latin characters, between 5 and 22 characters, with at least one letter;
• avoid the characters < > \ ' " and *;
• reflect your doing-business-as (DBA) name, not just a common term or generic URL.

For card payments Stripe also supports a static prefix (2 to 10 characters) with a dynamic suffix per charge, joined with an asterisk, for example RUNCLUB* OCT MARATHON. Stripe notes most banks display the descriptor consistently, but some show it incorrectly or not at all.

What a good descriptor looks like

American Express's guidance:

• Include your DBA name and physical location or website, consistent across charges.
• Add a customer service phone number so Card Members can call you instead of the bank.
• Describe the purchase; avoid generic descriptors.
• Label special charges, for example "no show", "advance deposit" or "installment".

Consistency also matters for Visa CE 3.0

Visa's Compelling Evidence FAQ advises displaying descriptors as consistently as possible so transactions match: keep the leftmost characters the same, keep the part before an asterisk fixed and vary only the rightmost portion of dynamic descriptors. See Compelling Evidence 3.0.

A worked example

A skincare brand called "Luma Botanicals" bills through its legal entity, "LBX HOLDINGS LLC". A customer sees "LBX HOLDINGS 8005550100" next to $48 and calls their bank. After switching to "LUMABOTANICALS.COM" with a dynamic suffix like "LUMA* SUBSCRIPTION", the brand's "unrecognized" disputes fall because customers can now place the charge.

Common mistakes

• Using the legal entity or a parent company name customers have never seen.
• Changing descriptors between processors or stores so the same customer sees different names.
• Billing subscriptions with the same descriptor as one-off orders, so renewals look unfamiliar.
• Truncation: long names cut off at the character limit.

Mastercard's Ethoca Consumer Clarity goes further, showing merchant names, logos and digital receipts inside banking apps. See Ethoca Alerts.

How Verdikx helps

Verdikx is a fraud, chargeback and dispute platform for e-commerce and SaaS merchants, made by Verdikx LLC. When a connected processor reports the statement descriptor (Stripe does), Verdikx adds it to the payment record in the dispute packet, so the issuer sees exactly what the cardholder saw. For "unrecognized" disputes the packet pairs that descriptor with the order, customer and delivery records that connect the charge to the purchase. Fixing the descriptor itself is done in your processor or store settings. See friendly fraud for how unrecognized charges turn into disputes.