Merchant ID (MID)

Every business that accepts card payments processes under a MID. The number is assigned when the acquirer or payment facilitator approves the account, and it travels with every transaction the merchant runs, through authorization, clearing, settlement, and into the card networks’ reporting and compliance systems. Chargebacks, fraud flags, and network fines all attach to the MID.

How it works

A traditional merchant account gets its own MID directly from the acquirer after full underwriting. Under the PayFac model, the facilitator holds a master MID and issues each business a sub-merchant ID beneath it; the networks still see the sub-merchant’s descriptor and identifiers in the transaction data, but the master relationship belongs to the PayFac. Larger businesses often hold multiple MIDs deliberately: one per location, per sales channel (eCommerce versus retail), or per legal entity, because separating volume keeps reporting clean and isolates risk events. Each MID also carries an MCC describing the merchant’s line of business, which affects interchange rates and card-network rules.

Why it matters

MID structure shapes day-to-day operations more than most merchants expect. If one MID covers three channels, a chargeback spike in one channel can jeopardize processing for all three. If a platform’s merchants share identifiers too loosely, statement descriptors confuse cardholders and disputes rise. When evaluating a processor, ask how MIDs and sub-merchant IDs are structured, how quickly new ones can be issued, and whether reporting lets you slice activity per MID without manual work.

On QorPay’s QorCommerce platform, sub-merchant accounts are created through API-driven boarding with Automated Underwriting, and QorCommerce Reporting covers activity down to the individual merchant account.