What Is a Merchant ID (MID)? Finding and Using Yours
What is a merchant ID? Learn what your MID identifies, where to find it, how it differs from a terminal ID, and when multiple MIDs make sense.
On this page 6 sections
Key takeaways
- Your MID identifies the whole account (business name, MCC, deposit account, pricing); a terminal ID identifies one device or gateway running under it.
- Get the full MID from page one of your statement or your merchant portal. Some receipts show only the last digits, and gateway API keys are different credentials.
- A second MID pays off when separate deposits, descriptors or dispute reporting save more bookkeeping time than the processor's per-MID fees cost.
- Every MID must be underwritten for what it actually sells. Extra MIDs used to spread chargebacks or dodge volume limits break card network rules.
What is a merchant ID? It's the unique number your acquiring bank or processor assigns to your merchant account when you're approved to take cards. Every sale you run carries it. Your MID number tells the payment system which business made the sale and which bank account gets the deposit. You'll need it whenever you call support or connect a new terminal or website.
What a Merchant ID Ties Together
Think of the MID as the account number for your card-acceptance relationship. Your processor attaches these account-level details to it:
- Your legal business name and the "doing business as" name customers see
- The merchant category code (MCC) that tells the card networks what kind of business you run (our guide to how merchant category codes affect fees explains why that code matters)
- Your deposit bank account
- Pricing plan and fee schedule
- The statement descriptor printed on cardholders' bank statements
- Volume and ticket-size limits approved during underwriting
Who issues the MID depends on how your account is structured. It comes from the acquiring bank or from a processor acting on the bank's behalf. If those roles blur together, see processor vs. acquirer vs. gateway. The format depends on the processor as well. MIDs are long strings of digits, and the length varies from one processor to the next. A MID that looks different from a friend's isn't wrong.
Two other numbers get mixed up with the MID. Your EIN identifies your business to the IRS. Your bank account number identifies where money lands. Neither one is your merchant identity in the card system. American Express adds a wrinkle. If you accept Amex under a direct agreement with Amex instead of through your processor, Amex issues its own merchant number for that relationship, and that number is separate from your processor's MID.
How to Find Your Merchant ID
Check whichever of these you can reach first:
- Your monthly processing statement. The MID sits near the top of the first page, next to your business name. A business with more than one MID gets a separate statement or section for each.
- The merchant portal. Look under account details or business profile.
- Approval paperwork. The welcome email or letter sent when your account opened lists the MID.
- The terminal itself. Terminals display the MID in an admin or merchant-information menu. The settlement reports they print show it too.
- Gateway settings. Online sellers find it in the gateway's processor or merchant information section.
- Your processor's support line. Support will read it to you once they confirm you're an authorized signer on the account.
Watch for two traps. Some receipts mask part of the MID and print only the last few digits, so a receipt may not give you the full number. On the e-commerce side, the gateway's API login ID and transaction key are different credentials. Those keys connect your website to the payment gateway, and the gateway connects to your MID behind the scenes. Pasting one in place of the other is a common reason a new website integration fails its first test.
Merchant ID vs. Terminal ID
The MID identifies your account. The terminal ID (TID) identifies one device or endpoint that runs transactions under that account. A coffee shop with three countertop terminals and a website has one MID and four TIDs: one for each terminal and one for the gateway.
| Merchant ID (MID) | Terminal ID (TID) | |
|---|---|---|
| Identifies | Your merchant account | One terminal, POS station, gateway or virtual terminal |
| How many | One per merchant account | One per device or endpoint, many per MID |
| Tied to | Business name, MCC, pricing, deposit account, descriptor | The device's setup and its batches |
| Changes when | You switch processors or change the legal entity | You replace a device or add a new one |
| Used for | Support calls, statements, deposits, disputes | Troubleshooting a device, tracing a batch |
The difference matters most when you close out. On standalone terminals, batches close device by device, so the TID tells you which register a batch came from. Deposits post at the account level under the MID. When a deposit comes up short, the TID is how you find the missing batch. That tracing is the core of matching deposits to sales every month, and a written list of every TID and its station makes the job faster.
Replacing a broken terminal gets you a new or reprogrammed TID under the same MID. Your pricing and deposit account stay as they were. Switching processors means a new MID, so every gateway connection and recurring-billing setup has to point at the new account before the old one closes.
When Multiple MIDs Make Sense
A single-location business with one sales channel needs one MID. Multiple MIDs earn their keep when parts of the business differ in ways the processor's records have to reflect.
Separate legal entities or bank accounts. When each location is its own LLC with its own bank account, each one needs its own MID. The legal name and the deposit account both attach to the MID.
Different business types under one roof. A hotel with a restaurant is the classic case. The front desk and the dining room fit different merchant categories, so separate MIDs keep each one categorized and reported accurately. A retailer with a repair counter faces the same question. For lodging setups, see how MannyPay handles payment processing for hotels.
In-store and online sales kept apart. Card-present and card-not-present sales carry different fraud profiles and different interchange rates. Our explainer on how interchange rates are set covers that cost gap. A dedicated online MID shows that channel's costs and disputes on their own.
A clearer statement descriptor. Each MID carries its own descriptor. You could use the store name for in-person sales and the store name plus "ONLINE" for web orders. Customers who recognize a charge have less reason to dispute it as unfamiliar.
Extra MIDs carry costs. Processors charge account-level fees per MID, such as statement fees and monthly minimums. Those charges are one processor's pricing, not network rules, so get the per-MID cost in writing before you open a second account. Ask whether each MID needs its own PCI validation, too. You'll also have twice the statements to read and twice the deposits to reconcile. Our guide to the Visa fixed acquirer network fee (FANF) covers another fixed monthly charge to check on your statement.
One line can't be crossed. Every MID must be underwritten for what it sells and must describe the business accurately. Opening extra MIDs to spread chargebacks thin or to stay under approved volume limits breaks card network rules. Running a product line the original account wasn't approved for breaks them as well. The consequences can include termination of your accounts and a listing on the terminated-merchant databases that other processors check before they approve anyone. If a product line needs a different kind of account, apply for that account openly. Businesses in regulated categories should apply for high-risk merchant accounts from the start.
Example: A Restaurant With Dine-In and Online Ordering
This example is illustrative. It uses your numbers instead of invented ones.
Assumptions:
- One location with one legal entity and one bank account
- The bulk of card sales happen tableside and at the counter
- A smaller share comes through the restaurant's own website ordering
- Delivery-app orders make up the rest
Delivery-app orders drop out of the decision entirely. The marketplace charges the customer's card on its own merchant account and pays the restaurant separately, so those sales never touch the restaurant's MID. Only orders taken on the restaurant's own website or app run through its account.
Option A: one MID. Website orders run through a gateway that appears as its own TID under the existing MID. All deposits arrive together. You separate online sales in reporting by filtering on the gateway's TID, provided your processor's reports offer that filter.
Option B: two MIDs. Online orders run on their own MID with a separate deposit and descriptor. Disputes on web orders, where "I didn't make this purchase" claims cluster, land on their own statement instead of blending into the dining-room numbers.
To decide, compare two annual figures. The first is what your processor charges per year in account-level fees for a second MID. The second is the bookkeeping time you spend splitting combined deposits by channel, multiplied by what that time costs you. If the second figure is bigger, the extra MID pays for itself in cleaner books before you count the benefit of seeing online disputes separately. If your processor's reports already split sales by TID and nobody reconciles by hand, the second figure is close to zero and Option A wins.
The choice comes down to whether mixing channels costs you real bookkeeping time and whether you need online disputes visible on their own. For more on dining setups, see restaurant and bar payment processing.
Keeping Your MID Number Secure
A MID is not cardholder data. Knowing it doesn't let anyone charge a card or withdraw money, which is why processors print it on statements and reports.
It does help an impostor sound legitimate. A caller who knows your MID and business address makes a convincing "processor representative" when asking you to confirm bank details or accept a replacement terminal. Keep the MID internal and off public documents.
A few habits close most of the gaps:
- Treat any unsolicited call or email about your account as suspect. Hang up and dial the support number printed on your statement.
- Turn on multi-factor authentication for your merchant portal, and restrict who can change deposit details.
- Shred old statements and batch reports.
- Watch your deposits. A sudden drop or a missing deposit is worth a same-day call to your processor.
These habits sit alongside your broader card security obligations, covered in our plain-English PCI DSS guide. For the card readers themselves, see our guide to point-to-point encryption (P2PE) for card readers. If something does go wrong, follow a step-by-step breach response plan.
Your next step is a short desk exercise. Pull your latest statement and build a one-page map that lists every MID on it, with each terminal and gateway listed by TID underneath. If the map shows channels mixed together that you'd rather separate, or a second MID you're paying for and don't use, request a free processing quote. A MannyPay specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

