Skip to content
The ValyrPayMerchant Services

Disputes and monitoring

Payment descriptors: how to stop customers disputing charges they made

What a billing descriptor is, soft and hard descriptors, why unclear ones cause friendly-fraud chargebacks, the scheme rules, and how to choose a good one.

8 min readUpdated 23 October 20266 sources

Contents9 sections
  1. What a descriptor is
  2. Why unclear descriptors cause chargebacks
  3. What the scheme rules require
  4. How to choose a good descriptor
  5. Dynamic descriptors
  6. Beyond the descriptor
  7. A short checklist
  8. What to do next
  9. Sources

What a descriptor isLink to this section

When a customer pays you by card, the transaction carries information about your business: a merchant name, a location (usually a city, or for online merchants a website address or telephone number), a country and a merchant category code. Your acquirer sets these up when it boards your account. The issuer — the customer’s bank — takes that information and shows it on the statement and in the banking app. The text the customer sees is your billing descriptor, also called a statement descriptor.

The card schemes require the descriptor to do two jobs. Visa requires issuers to show, on the cardholder’s statement, the data from the clearing record that identifies the merchant and enables the cardholder to contact it (Visa Core Rules, section 1.4.3.3). Mastercard’s receipt rules refer to the “doing business as” merchant name and location carried in the card acceptor name and location field of the transaction (Transaction Processing Rules, rule 3.13.1). In both cases the descriptor is meant to answer the customer’s two questions: who charged me, and how do I reach them.

Soft and hard descriptorsLink to this section

“Soft” and “hard” are industry terms rather than scheme terms, but they describe something real:

  • The soft descriptor comes from the authorisation. It is what the customer sees on a pending transaction in their banking app — often within seconds of paying.
  • The hard descriptor comes from the clearing record when the transaction settles. It is what appears on the final statement.

Visa expects the merchant name to be used consistently, including in the authorisation request and the clearing record (section 1.5.1.12). In practice, differences creep in through processor settings, truncation or dynamic descriptors. If the pending entry says one thing and the posted entry another, a customer checking their app may decide the charge is suspicious.

Why unclear descriptors cause chargebacksLink to this section

Visa’s own merchant guidance puts it plainly: one of the most common reasons customers contact their bank is that they do not recognise a transaction, and in many of those cases the transaction was valid but the business name, billing descriptor or transaction details were unfamiliar (Visa Dispute Management Guide for Merchants, October 2026).

When a customer does not recognise a charge, they rarely search the web for the name. They contact their bank, and the easiest path is often to report the payment as unauthorised. The result is a fraud report and a chargeback for a purchase the customer made — commonly called friendly fraud or first-party misuse. It costs you twice:

  • The chargeback itself — the lost sale, the fee and the time spent responding.
  • Your monitoring ratios. Visa’s Acquirer Monitoring Program (VAMP) counts both fraud reports (TC40 records) and disputes (TC15 records) against your settled transactions. A confusing descriptor can push up both numbers at once (Visa VAMP fact sheet, 2025).

Where descriptor confusion comes fromLink to this section

Most problems have ordinary causes:

  • The legal entity name instead of the brand. Customers bought from a brand; the statement shows a holding company they have never heard of.
  • Truncation. The merchant name field is short, so a long name is cut off mid-word, or the part customers would recognise disappears.
  • One descriptor for several brands. A group trading under different names bills everything under one, so customers of the second brand see a name they do not know.
  • Intermediary names. Purchases through a payment facilitator or marketplace show the intermediary’s name first.
  • Delayed and recurring charges. A renewal charged eleven months after sign-up, or a trial converting weeks later, arrives when the customer has forgotten the purchase.
  • Unexpected location or currency. A UK brand with an overseas billing entity, or a city that does not match where the customer thinks the business is.

What the scheme rules requireLink to this section

VisaLink to this section

  • The name you actually use. The merchant name must be the name the merchant primarily uses to identify itself to its customers, displayed on its website or app, and used consistently in receipts, authorisation requests, clearing records and dispute records. For e-commerce, the website address may be used unless it is not directly related to the merchant name. The acquirer must correct non-compliant names and names that cause cardholder confusion (section 1.5.1.12).
  • Intermediaries name both parties. For payment facilitator transactions the receipt must show the name of the payment facilitator and the name of the sponsored merchant (or an abbreviation); similar rules apply to marketplaces and their retailers, digital wallet operators and their retailers, and up-selling merchants, which must be clearly distinguished from the original merchant (section 5.9.2.2). The statement must identify the sponsored merchant and its payment facilitator (section 1.4.3.3).
  • Recurring payments in Europe. For a recurring transaction within Visa’s Europe region, which includes the UK, the clearing record must contain the website address in the merchant name field for an e-commerce merchant, or an internationally accessible telephone number in the city field for other merchants (section 1.4.3.3).
  • Receipts that match. If you send receipts by email or message, the subject line or first line must include your merchant name as it will appear in the clearing record and on the cardholder’s statement (section 5.9.1.2).

MastercardLink to this section

  • Negative option billing of physical products. Every recurring charge after a trial must use the same merchant ID and the same merchant name as the first transaction, and before the first full-price charge the customer must be told the merchant name as it will appear on their statement (Transaction Processing Rules, rule 5.4.2).
  • Combined names use an asterisk. Mastercard’s rule for instalment providers shows the convention many processors follow for intermediaries: the provider’s name and the retailer’s name separated by an asterisk, such as “Provider*Retailer” (rule 5.5.2).

A change coming in January 2027Link to this section

From 23 January 2027, issuers of Visa cards in most of Visa’s Europe region — the UK is not among the excluded markets — must make the merchant’s “trading as” or “doing business as” name available in their banking app or online banking, and, where available, the merchant’s address, telephone number and website (Visa Core Rules, section 4.1.8.9). That makes it even more important that the data your acquirer holds about you is accurate and recognisable.

How to choose a good descriptorLink to this section

Treat your descriptor as part of your brand, not a technical setting.

  1. Lead with the name customers know. Use the brand on your website, packaging and emails — not your legal entity — unless they are the same.
  2. Add a way to reach you. A short website address is usually the most useful second element, because customers can type it in. A customer service telephone number is the alternative.
  3. Design for truncation. The name field is short, so put the recognisable part first and check how the full string displays. Avoid special characters and abbreviations customers would not guess.
  4. One brand, one descriptor. If you trade under several brands, ask your acquirer for separate merchant accounts or descriptors so each customer sees the brand they bought from.
  5. Make subscriptions obvious. For recurring charges, a name that signals the product helps customers place a renewal.
  6. Tell customers what to expect. Show “This payment will appear on your statement as …” at checkout, in the order confirmation and in renewal reminders, and use the same wording in your email subject lines.
  7. Check it in the real world. Make test purchases with cards from different banks and look at both the pending and the posted entry in the banking apps.
  8. Change carefully. A new descriptor can itself cause confusion. If you must change it, tell existing subscribers before their next charge.

An illustrationLink to this section

Imagine a hypothetical brand, “Fernleaf”, selling plant-care subscriptions at fernleaf.example, operated by a company called Greenline Holdings Ltd. A descriptor of GREENLINE HOLDINGS LTD tells the customer nothing. FERNLEAF.EXAMPLE puts the brand first and gives the customer a website to visit. If Fernleaf sold through a payment facilitator, the statement would also carry the facilitator’s name, so keeping the brand element short and distinctive matters even more.

Dynamic descriptorsLink to this section

Many gateways and processors let you vary part of the descriptor for each transaction — for example a fixed prefix with your brand and a variable suffix with a product or order reference. Used well, a dynamic descriptor helps customers match a charge to a specific purchase. Three cautions:

  • The part that identifies you must stay constant and must remain the name you use with customers; Visa’s consistency rule still applies.
  • Your acquirer must permit it, and not every issuer displays the full string.
  • The variable part must never mislead — for example, by naming a product the customer did not buy or a business you are not.

Beyond the descriptorLink to this section

Banking apps increasingly show more than a line of text. Services operated with the card schemes can add detail to the customer’s view of a transaction or intercept a query before it becomes a dispute:

  • Ethoca, a Mastercard company, offers Consumer Clarity, which helps cardholders recognise purchases in their banking app, and Ethoca Alerts, which share fraud and dispute information between issuers and merchants.
  • Verifi, a Visa solution, offers Order Insight, which lets participating merchants share transaction details with participating issuers when a cardholder queries a charge, and Rapid Dispute Resolution (RDR), which resolves eligible Visa disputes automatically under rules the merchant sets. A dispute resolved through RDR does not count towards Visa’s VAMP ratio, though a fraud report on the same transaction still does.

These tools work best when the underlying descriptor is already clear; they are a second layer, not a substitute. See chargeback alerts explained.

A short checklistLink to this section

  • The descriptor shows the brand customers buy from.
  • It includes a website address or customer service telephone number.
  • It reads correctly after truncation, in both pending and posted form.
  • Each brand you trade under has its own descriptor.
  • Your checkout, confirmation emails, receipts and renewal reminders state exactly how the charge will appear.
  • Your email receipts use the same merchant name in the subject line.
  • Your merchant category code accurately describes what you sell.
  • You review the descriptor whenever you rebrand, add a product line or change provider.

What to do nextLink to this section

Descriptor fixes are among the quickest wins in reducing disputes. The ValyrPay Merchant Services reviews descriptors as part of our chargeback prevention work, alongside receipts, renewal communications and pre-dispute tools. We are not a bank or a payment institution, and your acquirer sets up the descriptor itself. See chargeback prevention.

Sources

Each source was read on the date shown. Card-scheme rules and regulations change; check the current edition before relying on a detail.

  1. Visa Core Rules and Visa Product and Service Rules, edition 18 April 2026 (sections 1.4.3.3, 1.5.1.12, 4.1.8.9, 5.9.1.2, 5.9.2.2) (external site)usa.visa.com · read 23 October 2026
  2. Visa Dispute Management Guide for Merchants, October 2026 (transaction recognition; Order Insight; RDR) (external site)usa.visa.com · read 23 October 2026
  3. Visa Acquirer Monitoring Program Overview (fact sheet, 2025) (external site)corporate.visa.com · read 23 October 2026
  4. Mastercard Transaction Processing Rules, 10 June 2025 (rules 3.13.1, 5.4.2, 5.5.2) (external site)mastercard.com · read 23 October 2026
  5. Ethoca (a Mastercard company) — Ethoca Alerts and Consumer Clarity (external site)ethoca.com · read 23 October 2026
  6. Verifi (a Visa solution) — Resolve disputes: RDR and CDRN (external site)verifi.com · read 23 October 2026

Keep reading

Rules and compliance

Website compliance checklist for card acceptance

What acquirers and card schemes expect on a merchant website before approval: legal pages, pricing, refunds, subscriptions, contact details, card marks.

9 min read11 sources

Getting approved

What “high risk” really means to an acquirer

Why acquirers label some merchants high risk — business model, MCC, chargeback history, jurisdiction — what scheme registration involves and what changes.

11 min read9 sources