If you operate more than one MID, avoid reusing the same billing descriptor across them — especially if you use alert services like Ethoca, CDRN, or RDR.
Reusing a descriptor can cause alerts to be mapped incorrectly, missed, or delayed.
Why this matters
Alert providers use the billing descriptor as one of the key identifiers to match a dispute or alert back to the correct merchant account. When two or more MIDs share the same descriptor, that matching process becomes unreliable.
What can go wrong
Misrouted alerts – If the same descriptor appears on multiple MIDs, the provider may struggle to determine which MID an alert actually belongs to.
Reduced alert coverage – When a provider can't confidently match an alert to a MID, it may not deliver the alert at all, creating coverage gaps.
Enrollment conflicts – Enrolling a descriptor in Ethoca/CDRN or RDR while it's tied to multiple MIDs can complicate the process, or cause one MID to take priority over the other.
Inconsistent routing – Even if both MIDs are actively processing, the network may not be able to distinguish them by descriptor alone.
Harder reporting and reconciliation – It becomes more difficult to trace which MID actually generated a given alert, especially across different processors or gateways.
Example
MID | Descriptor |
#12345 |
|
#67890 |
|
If a customer disputes a charge processed through MID #67890, the alert provider only sees MY STORE — with nothing to indicate which MID it should route to. This can result in the alert going to the wrong MID, not being delivered at all, or getting stuck in enrollment.
Best practice: keep descriptors unique per MID
Give each MID its own distinct descriptor wherever possible:
MID | Descriptor |
#12345 |
|
#67890 |
|
This small change makes it much easier for alert networks and processors to correctly associate each transaction and alert with the right MID.
Good to know
Matching logic varies by network and alert type, so a duplicate descriptor won't necessarily cause every alert to fail. But it does raise the risk of mapping errors and coverage gaps, which is why we recommend unique descriptors any time you're running multiple MIDs.