What is a Merchant ID (MID)?

A Merchant ID (MID) is the unique identifier — usually a 15-digit number — that an acquiring bank assigns to a business when it opens a merchant account. Every card transaction carries the MID so the network knows which account to credit at settlement and which to debit fees from. Businesses with multiple stores, websites, or sales channels often hold several MIDs, one per environment.

A Merchant ID — almost always abbreviated to MID — is the identifier an acquiring bank stamps onto a merchant account so card networks can route transactions correctly. It's typically a 15-digit number, though some acquirers use shorter formats. Every authorisation, settlement and fee deduction is tagged with the MID, so it's the closest thing card payments have to an account number for the merchant. If you accept cards in more than one channel — phone, web, in-store — you'll usually have a separate MID for each, because each environment has its own risk profile and pricing.

The MID isn't really a customer-facing number. It lives on remittance reports, gateway configs, and the Merchant ID line of receipts (often labelled merchant number on a printed slip). What it actually does is tie three things together: the acquirer's view of who you are, the card scheme's view of which Merchant Category Code (MCC) you trade under, and the interchange table that decides how much each transaction costs you. Change any one of those and you usually need a new MID.

What's actually encoded in a MID

A MID isn't random. The acquirer issues it from a block they've registered with Visa and Mastercard, and the number is bound to a specific MCC, a specific legal entity, and a specific channel. That's why you can't just "reuse" your in-store MID for a new website — the e-commerce risk profile is different, the chargeback liability is different, and the interchange categories you qualify for are different. Acquirers will set up a second MID for the new channel rather than re-classify the old one.

It's also bound to your bank account. Funds settled against a MID land in whichever sort code and account the acquirer has on file for that MID. Multi-entity groups sometimes use this deliberately — one MID per subsidiary, settling to that subsidiary's bank account, even though the group runs on a single platform.

MID vs Terminal ID (TID)

This trips people up constantly. The MID identifies the merchant account; the Terminal ID (TID) identifies a single terminal — physical or virtual — operating under that MID. A coffee shop with three tills typically has one MID and three TIDs. A call centre using Paytia has one MID and a TID per agent or per workflow. Reconciling sales by terminal is a TID job; reconciling fees and chargebacks is a MID job. Both numbers travel with every transaction, but they answer different questions.

Multiple MIDs and when you need them

You'll end up with more than one MID in a few common situations:

  • Separate channels — most acquirers issue a distinct MID for card-present, MOTO/phone payments, and e-commerce, because each has its own interchange treatment
  • Separate brands or trading names under the same legal entity
  • Separate legal entities in a group, each settling to its own bank account
  • Multi-currency processing, where the acquirer issues a MID per settlement currency
  • High-risk segments split off into a ring-fenced MID so a chargeback spike on one product doesn't put the whole business on the MATCH list

What you don't need is a MID per location for the same brand and channel — most acquirers handle that with sub-IDs or store numbers under a single MID.

Switching acquirers means a new MID

If you move from one acquirer to another, you get a fresh MID. That sounds administrative, but it has a real consequence: stored card tokens are usually MID-bound. The token your old gateway gave you for a returning customer's card is meaningless to your new acquirer's gateway, because tokens are issued against the original MID. You'll either need to re-tokenise (have the customer re-enter the card, or use a network token migration if your scheme supports it) or arrange a credential migration with the previous provider. Plan for this before you cut over — it's the part of an acquirer switch that bites unprepared finance teams.

PSPs, payfacs and sub-merchant IDs

Stripe, Square, SumUp and similar payment facilitators work differently. They hold one master MID with the acquirer and onboard you as a sub-merchant underneath it, with a sub-merchant ID rather than a MID of your own. That's why you can start taking payments through Stripe in an afternoon — you're not being underwritten as a standalone merchant, you're being added to Stripe's account. The trade-off is less control: the master MID's risk policies apply to you, and if the payfac decides to freeze or offboard you, there's no separate acquirer relationship to fall back on. Above a certain volume most businesses move to a dedicated MID for exactly that reason.

How Paytia Uses This

Paytia sits in front of your existing acquirer, so we use whatever MID you already have — there's no need to apply for a new one or change your settlement banking. When a phone agent triggers DTMF masking and the customer keys their card, the transaction is submitted to your gateway tagged with your MID exactly as it would be for any other MOTO sale. Your acquirer sees a normal transaction on a normal merchant account.

If you run separate MIDs for separate channels — and most of our clients do — we map each Paytia workflow or queue to the correct MID at config time. That keeps your MOTO interchange clean and your reporting line up with the rest of your finance stack. It also means switching acquirers later is a Paytia config change, not a re-platforming exercise.

Frequently Asked Questions

Is a Merchant ID the same as a merchant account number?

Yes, in practice. The MID is the identifier for your merchant account with the acquiring bank. Some acquirers print it as 'Merchant Number' on statements and receipts, but it's the same thing.

Can I have one MID for multiple websites?

Often yes, if the sites trade under the same legal entity, the same MCC, and settle to the same bank account. If any of those differ — different brands settling to different accounts, for example — your acquirer will usually require a separate MID per site.

Why do my stored card tokens stop working when I change acquirer?

Tokens are usually issued against a specific MID. When you move to a new acquirer you get a new MID, and the old tokens are tied to the previous one. You'll need to re-tokenise the cards or arrange a credential migration with your previous provider before you cut over.

What's the difference between a MID and a TID?

The MID identifies the merchant account; the Terminal ID (TID) identifies a specific terminal — physical till, virtual terminal, or agent workflow — operating under that account. One MID typically has many TIDs underneath it.

See how Paytia handles merchant id (mid)

Book a personalised demo and we'll show you how our platform works with your setup.

PCI DSS Level 1
Cyber Essentials Plus

Trusted by law firms, insurers, healthcare providers and regulated businesses worldwide. Learn more about Paytia