The short answer
A hard descriptor is the fixed-per-MID text that always appears at the start of a customer's billing descriptor on their bank statement. It represents the merchant of record — the legal entity the acquirer underwrote. The hard descriptor cannot be changed transaction-to-transaction; it is locked to the MID at underwriting time. The soft descriptor follows the hard portion (separated by an asterisk or space) and names the specific sub-brand or product that transaction represents.
Format
Visa and Mastercard mandate a total 25-character descriptor. That budget is split into a hard component and a soft component, and the split is set by the acquirer at MID underwriting. Three standard configurations:
- 3/21 split: 3-character hard descriptor (e.g., "GEN"), asterisk, 21-character soft ("GEN*PEAKBIO RESEARCH LA"). Common for high-volume PayFac-style setups.
- 7/17 split: 7-character hard descriptor ("GENESIS"), asterisk, 17-character soft ("GENESIS*PEAKBIO RES"). Most common middle-ground.
- 12/12 split: 12-character hard ("GENESIS LABS"), asterisk, 12-character soft ("GENESIS LABS*PEAKBIO"). Best recognition when the parent DBA is already known to the customer.
What operators need to know
- The hard descriptor is locked to the legal entity. You cannot change it without changing the underlying DBA registered with the acquirer, which requires re-underwriting (articles of incorporation amendment, new bank verification, 3–5 day turnaround).
- It must exactly match the DBA on your merchant agreement. Typos, abbreviations not present on the underwriting paperwork, or stylization (hyphens, underscores) will be rejected by the acquirer compliance review. Uppercase alphanumeric + space only.
- It's the primary signal customers use to identify the charge. Poor hard descriptor design drives chargebacks. "PAYMENTS LLC" tells the customer nothing — they dispute the charge as unrecognized. "PEPTIDE CO" at least hints at the purchase. Choose the hard descriptor with future customer-recognition in mind.
- Changing your DBA is a bigger decision than you think. Every sub-brand under your parent MID is stamped with that hard descriptor on every past charge. A DBA change resets customer recognition on historical charges, which inflates chargeback disputes temporarily.
Hard + soft descriptor interplay
The customer sees HARD*SOFT on their statement. For multi-brand operators, the strategy is: pick a hard descriptor broad enough to stay accurate across the portfolio (your parent LLC's DBA, or a parent brand umbrella), and use soft descriptors to carry the specific sub-brand. Example: hard="GENESIS LABS" as the parent umbrella; soft rotates per sub-brand — PEAKBIO, HERO RESEARCH, NEUROLABS. Customer sees "GENESIS LABS*PEAKBIO" and knows exactly what they bought. Customer sees "GENESIS LABS*HERO RESEARCH" on a different transaction and recognizes both the sub-brand and the parent umbrella.
How multiflow configures this
At parent merchant account underwriting, we coordinate the hard descriptor choice with the acquirer's compliance review based on the DBA structure you submit. We default to 12/12 splits when the DBA fits, or 7/17 when it doesn't. Changes post-underwriting are rare and require acquirer sign-off; the operator portal tracks descriptor requests end-to-end.