The line a cardholder reads on a statement is set at boarding. Someone on the onboarding team keys a merchant name into the processor's set-up screen, and that string travels in every authorization and clearing message until somebody changes it. When it does not match the name on the shopfront, the website or the receipt, the cardholder does not recognise the charge, and an unrecognised charge is a dispute waiting to be filed.
Both card networks have rules about that string, and both changed them in 2025. In June 2025 Mastercard brought an anti-impersonation requirement, previously in its Security Rules and Procedures, into the Mastercard Rules. In September 2025 Visa moved its merchant name rule into the Visa Core Rules, which on Visa's own schedule carry the higher of its two tiers of non-compliance assessments. This piece sets out what the rules say as of October 2026, from the Visa Core Rules and Visa Product and Service Rules dated 18 April 2026 and the Mastercard Rules dated 2 June 2026, with earlier editions used to date the changes.
Visa: One Name, Everywhere
Visa's rule, Merchant Name Assignment, says the name used to identify a merchant must be the name it primarily uses to identify itself to its customers. It must be displayed at each merchant outlet, or on an e-commerce merchant's website or app, and used consistently, spelling included, everywhere it appears. The rule names the transaction receipt, the authorization request, the clearing record, and dispute, dispute response and acquirer-initiated pre-arbitration records.
Two footnotes give some room. An e-commerce merchant may use its website address, unless the address is not directly related to the merchant name. And the name in the clearing record may differ from the one on the receipt where abbreviations are required or supplementary data is used. The rule then puts the fix on the acquirer: it must correct non-compliant merchant names, or names causing cardholder confusion.
The wording has not changed in years. Its place in the rulebook has. In the April 2025 edition it sat in the Visa Product and Service Rules, as section 5.2.1.11. The October 2025 edition moved it into the Visa Core Rules as section 1.5.1.12, under a change titled Global Non-Compliance Assessment Schedules and Data Quality Requirements Clarified, effective 18 September 2025. The same change moved the rules on MCC assignment and on payment facilitator identifiers.
The move matters because of how Visa prices violations. Under its general schedule, a breach of a rule in the Core Rules chapter is assessed on Tier 1: a USD 1,000 compliance case fee, then USD 25,000 at the first level, rising in steps to USD 150,000 and then by USD 25,000 a month until the violation is fixed. Every other rule falls under Tier 2, which starts at USD 5,000 and reaches USD 50,000 before rising by USD 10,000 a month. Visa may depart from either schedule at its discretion, so this is the default, not a guarantee. On the default, a merchant name the acquirer fails to correct is now priced as a core violation.
A separate rule covers deliberate changes. If Visa determines that an acquirer, merchant, sponsored merchant or third-party agent changed the merchant name or merchant data to get around the Visa Acquirer Monitoring Program or the Visa Integrity Risk Program, it may assess the acquirer USD 25,000 per merchant per month and permanently disqualify the merchant and its principals. A new descriptor on a merchant with a rising dispute ratio is the pattern that rule is written for.
Where Visa Expects the Name to Appear
Visa's receipt rules require the name the merchant uses to identify itself, with exceptions for businesses that sit between the cardholder and the seller:
- a payment facilitator transaction must show the name of the payment facilitator and the name of the sponsored merchant, or an abbreviation;
- a marketplace transaction must show the marketplace and the retailer;
- a back-to-back transaction for a retailer signed by a digital wallet operator must show both the wallet operator and the retailer;
- an up-selling merchant must be named in a way that clearly distinguishes it from the merchant the cardholder first bought from;
- a consumer bill payment service must show its own name and the biller's.
An emailed or texted receipt must carry, in the subject line or first line, the merchant name as it will appear in the clearing record and on the cardholder's billing statement. On the issuer side, Visa requires the billing statement to carry the clearing-record data that identifies the merchant, or the sponsored merchant and its payment facilitator, and that lets the cardholder contact it. An e-commerce site must show a customer service email address or phone number, an address for cardholder correspondence, and the merchant's country, either on the checkout screen that shows the final amount or within the checkout pages. A link to a separate page does not count.
Mastercard: The Name Has to Belong to the Merchant
Mastercard's Rule 5.5.1 requires each merchant to disclose its name prominently and clearly at every point of interaction, so the cardholder can easily tell the merchant apart from any other party, such as a supplier. The merchant must also disclose its physical address before the cardholder is asked for card details. The name and country shown at the point of interaction and on receipts must be the same as those sent in authorization and clearing messages. Rule 5.6.1 applies the same to a payment facilitator's sponsored merchants, and Rule 5.7 requires that the cardholder can easily understand that the merchant is responsible for the transaction, including customer service and dispute resolution.
Rule 5.8.3 is the one that changed. In the June 2023 and June 2024 editions it covered only sponsored merchants. The edition of 3 June 2025 retitled it Merchant and Sponsored Merchant Name Information and added text taken from Mastercard's Security Rules and Procedures. The acquirer must now ensure that merchant names, and a payment facilitator that sponsored merchant names:
- do not belong to other legal entities, to prevent unlawful use of an existing trademark, including impersonating those names to scam consumers, and, where the law allows, use controls that include matching merchant names against scam negative lists where they exist;
- are used consistently in authentication and authorization messages and in merchant registrations, where applicable.
The rule also fixes the payment facilitator format. The merchant name field, DE 43 subfield 1, must contain the payment facilitator's name, in full or abbreviated, followed by an asterisk and the sponsored merchant's name.
Mastercard's Transaction Processing Rules, in the 9 December 2025 edition, add three points that touch the name. A merchant or acquirer must not manipulate data in a resubmitted authorization, including by changing the acceptor name or acceptor ID, or by moving the merchant's volume to a different acceptor ID, to evade a cardholder's cancellation. A negative-option merchant selling physical products must process every later recurring payment under the same merchant ID and merchant name as the first transaction. And an installment provider's transactions carry the provider's name and the retailer's, separated by an asterisk.
What the Processor's Set-Up Screen Adds
Neither public rulebook gives a character limit for the name. Processors do, and the two we checked both use 22 characters. Stripe's documentation requires a descriptor of 5 to 22 characters that reflects the merchant's DBA name, with a prefix, an asterisk, a space and a per-charge suffix counting toward the 22. Adyen's says anything past 22 characters, spaces included, is truncated before the name is sent with the city and country, and that the description should carry the brand most recognisable to the cardholder, as required by the card schemes.
Twenty-two characters is not much once a payment facilitator prefix and an asterisk have taken their share. A sponsored merchant behind a six-character platform prefix and an asterisk has fifteen characters left, and a name such as Riverside Family Dental, at 23, does not fit even on its own. Whoever builds the descriptor needs to decide what survives the cut, because the processor will cut it either way.
What a Merchant-Services Team Should Check
- At boarding, capture the trading name the merchant actually uses with customers, from the shopfront, website or app, and record where you saw it. The legal name on the application is often not the name on the door.
- Build the descriptor from that name and check it after truncation, including any payment facilitator prefix and asterisk.
- For card-not-present merchants, check that the website shows the same name, a customer service contact, a correspondence address and the merchant's country within checkout.
- Screen new names against the brands they resemble. Mastercard now requires the acquirer to ensure a merchant name does not belong to another business, and to match names against scam negative lists where the law allows and such lists exist.
- Treat a descriptor change on a live merchant as a risk event. Log who asked for it and why, and look at the merchant's dispute and fraud ratios before approving it. A change made to escape VAMP or VIRP can cost the acquirer USD 25,000 per merchant per month.
- When a merchant reports unrecognised-transaction disputes, compare the descriptor with the receipt and the website first. Sometimes the fix is the name, not the refund policy.
- For negative-option merchants selling physical products, Mastercard requires every recurring charge to carry the same merchant ID and name as the first transaction. On any merchant, changing the name or merchant ID on a declined payment to get round a cardholder's cancellation breaches Mastercard's rules.
None of this needs new tooling. It needs the descriptor stored on the merchant record beside the DBA, the website and the boarding notes, so that the person answering a dispute call and the person approving a name change are looking at the same string the cardholder sees.
Tags
About the author

Kyle Hall
Founder
Kyle Hall is a fintech entrepreneur, software engineer, and marketing strategist with over a decade of experience in high-risk payment processing and SaaS development. He is the CEO of PayKings, a leader in high-risk merchant services, and the founder of PulseCRM, a purpose-built CRM platform for the payments industry. Kyle specializes in building custom payment processing systems and growth strategies that empower merchant services providers to scale and succeed in the digital marketplace.
