MID & TID

Also called merchant ID, terminal ID, MID number, TID number

MID identifies your merchant account. TID identifies a specific terminal or lane under it. Both are on every statement and every support call.

What it is

A MID, or merchant identification number, is the unique number assigned to your merchant account. Every transaction, deposit, chargeback and fee is tagged to it. A business with multiple locations, multiple concepts or multiple sales channels commonly has multiple MIDs — one for the restaurant, one for the food truck, one for eCommerce — because the acquirer underwrites and reports on each separately. A TID, or terminal identification number, identifies an individual terminal, register or lane operating under a MID. If you have four registers and a handheld, you likely have five TIDs under one MID. TIDs are how you determine which lane processed a transaction, which register is short at close, and which device is misconfigured. Practically, the MID is what you give support, what appears on your statement header, and what your bookkeeper reconciles against. The TID is what you use to diagnose a device-level problem — a terminal that's not batching, a lane running an old tip configuration, a register that's still surcharging after you turned it off.

Why it matters to your business

When you call support, having your MID open cuts the call in half. When you have a device problem, knowing the TID tells them which unit to fix instead of guessing. This is unglamorous and it saves hours over a year. More substantively: if you have multiple locations or channels, audit that your MIDs are configured identically. Different MCC codes, descriptors or tip configurations across locations that do the same thing produce inconsistent interchange and inconsistent customer experience, and nobody catches it because nobody compares MIDs side by side.

Where it gets contested

MIDs create a specific and underappreciated hazard: merchant diversion. In agent-residual disputes, payments litigators describe a pattern where a merchant keeps processing but under a new MID, a new platform, or an altered business name, and the original salesperson's compensation evaporates. The recommended defense is to tie compensation to the merchant relationship broadly rather than to a specific MID number. The merchant-side version of the same hazard is quieter. A processor "reboarding" you onto a new MID can reset promotional pricing, restart a term, or move you to a different fee schedule, and because you never see the number change, you may not notice. Any time you're told you're being moved to a new platform or a new MID, that's the moment to request the rate schedule in writing. On the mundane side, multi-location businesses frequently have MIDs configured inconsistently — different descriptors, different MCCs, different tip settings — which produces reporting chaos and, occasionally, materially different interchange treatment across locations that should be identical.

How to check it yourself

Write your MID on a card and tape it inside the register drawer or by the phone. If you have multiple locations, pull all your MIDs and compare four things across them: the MCC code, the statement descriptor, the funding account and the tip configuration. Inconsistencies there are common and cost money.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.

In agent-residual disputes, merchants continuing to process under a new MID, platform or altered business name is a documented pattern of compensation diversion; litigators advise tying compensation to the merchant relationship broadly rather than a specific MID
romellp.com ↗
Gateways support transaction routing and load balancing across multiple MIDs on one gateway account
nmi.com ↗