Payment facilitators, merchants of record, marketplaces, and PSPs that board sub-merchants under their own MID carry a confusion problem nobody else has — the statement line has to introduce your name and your sub-merchant's in the space of a license plate, and the cardholder recognizes neither of them.
Network rules put your name at the front of the descriptor, abbreviated, followed by an asterisk and whatever fits of the sub-merchant. So the cardholder's eye lands first on a company they have no relationship with — shortened, sometimes to two or three characters, into something that reads as a code rather than a business.
The prefix is you. It means nothing to the cardholder — two letters can't. What follows is a digital product they may know by a different name than the company that bills for it.
They don't recognize the first part. They can't place the second. The only control their bank offers is the dispute button.
Facilitator and merchant-of-record models concentrate in digital services — games, in-game purchases, streaming and downloadable content, SaaS, memberships, adult and creator platforms. That mix removes almost every cue a person normally uses to place a charge.
There was no store, no city, no card physically presented. Nothing about the purchase is tied to somewhere the cardholder went or a day they remember.
They bought a game, a channel, or a subscription by its product name. The entity that bills is the studio, the publisher, or the platform — a name they never saw.
Subscriptions and trials renew months after sign-up, at a price the cardholder never re-approved and often can't connect to anything current.
An acquirer can point a confused cardholder at the merchant. You can't — you are the merchant of record, or the support function your sub-merchants outsourced to you. Every question your platform's name provokes comes back to your team.
Your agents field “what is this charge?” for thousands of small businesses whose brand recognition you were never in a position to build.
Confusion-driven disputes across the whole sub-merchant book roll up into your ratios and your standing with the networks — not into anyone else's.
The sub-merchant sees chargebacks and support friction on charges their own customers didn't recognize, and concludes the platform is the problem.
Most merchant-identity data assumes one charge means one business. That model breaks the moment a facilitator sits in the middle. Descriptors.com treats the platform and the sub-merchant as what they are — two real parties, both of whom the cardholder is entitled to see.
The record shows who the cardholder bought from and who processed it, in language that needs no payments knowledge: “You bought Nova Studios VOD. The charge was processed by PX Payments.”
The sub-merchant's mark for recognition — the product logo the cardholder actually saw — and the platform's for reassurance. Two familiar things where there used to be one unfamiliar string.
Platform and sub-merchant relationships shown clearly — so a cardholder understands why an unfamiliar company appears on a purchase they do remember making.
When the cardholder calls their bank instead of you, the issuer's agent looks up the same verified record and can explain the relationship — rather than opening a case because nobody could account for the name.
Resolution paths route to the right party. A receipt request, a refund, or a cancellation reaches whoever is actually able to action it — which for most facilitator models means fewer tickets arriving at your desk by default.
Sub-merchants are exactly the population that never adopts anything requiring an API. So nothing is asked of them up front: you board the book in bulk from your existing records, every profile is live from day one, and enrichment is a short self-service step whenever each sub-merchant gets to it.
Facilitators resell on the same wholesale terms as acquirers and ISOs — a recurring margin on every sub-merchant descriptor you board, positive from the first one.
Your book's VAMP position against the 1.5% merchant line, and what confusion-dispute reduction is worth in dispute costs and support contacts.
—
Board every sub-merchant descriptor in bulk from records you already hold. Dual-brand display puts your sub-brand in front of the cardholder.
The ratio is (fraud reports + disputes) ÷ settled transactions, in events. The merchant Excessive threshold shown — 1.5% for US, Canada and EU — took effect April 2026, down from 2.2%. Program thresholds change; verify against current Visa documentation before relying on them.
The ladder reduces disputes (TC15) only, and applies the same percentage to your unrecognized-charge support contacts. Recognition pressure on fraud reports (TC40) is real upside the model leaves out.
Dispute and contact costs are your own inputs. The defaults are placeholders, not benchmarks — the model is only as good as the numbers you put in.
This is an arithmetic model of your own inputs, not a performance guarantee, a forecast, or a compliance determination. Actual program standing depends on Visa's calculations and your full portfolio mix.
Early-adopter PayFac and MOR partners lock in grandfathered pricing, shape the product around portfolio-scale operations, and keep a seat at the table as the platform grows.
