How a billing descriptor works
The descriptor travels in the merchant name and location fields of the authorisation request and of the clearing record. The issuer displays what it receives, first for the pending payment and then for the posted one.
A static descriptor is the same for every payment. A dynamic, or soft, descriptor is set per transaction, for example to add a product name or an order number after the brand. A payment facilitator's descriptor combines its own name with the sub-merchant's.
What the Visa rules say about the merchant name
In the Visa Core Rules of 18 April 2026, the name used to identify a merchant must be the name the merchant primarily uses to identify itself to its customers. The name is displayed at the outlet or on the website, and used consistently in the receipt, the authorisation request and the clearing record.
For e-commerce the website address may be used, unless the address is not directly related to the merchant name. The acquirer must correct names that do not comply or that confuse cardholders.
Why the descriptor matters
A cardholder who cannot place a charge calls the bank, and the call often ends as a fraud dispute on a genuine sale. A trading name the customer knows, with a web address or phone number where the field allows, prevents many of them.
Where a billing descriptor shows up in a platform
Modules that do the work
- Merchant onboardingBusiness sign-up, verification and underwriting, from application to first payment.
- Card acquiringCard acceptance on the phone, in store and online, through the acquirer you choose.
- BackofficeOne console to run the platform: customers, money, risk, content and staff permissions.
Platforms that need it
Where it is written
The laws and standards this page's facts come from.
General information, not legal advice: what applies to you depends on your services and your market.