A Merchant ID, usually shortened to MID, is an identifier used within a merchant's payment-processing setup.
It helps an acquiring bank, processor or payment platform identify the merchant account or processing relationship associated with a transaction.
However, modern payment setups can contain several different identifiers, which is why the term “Merchant ID” can become confusing.
A business might have:
- a merchant account ID;
- one or more acquiring MIDs;
- transactional or child MIDs;
- terminal IDs;
- store IDs;
- gateway or organisation IDs;
- merchant category codes;
- statement descriptors;
- processor account references; and
- settlement-account details.
These identifiers do different jobs and should not automatically be treated as interchangeable.
For a small merchant, this may never become particularly important.
For a larger business with several locations, brands, channels, currencies or acquiring relationships, MID structure can become an important part of the wider payment architecture.
What is a Merchant ID?
A Merchant ID is an identifier associated with a merchant's payment-processing account or acquiring relationship.
The precise terminology and format depend on the acquirer, processor and payment platform.
Visa Acceptance Solutions describes an acquiring MID as a unique identifier assigned by the acquiring bank or processor to the business account.
Merchant IDs are used within payment-processing systems so that transactions can be associated with the correct merchant configuration.
That configuration can include information such as:
- merchant identity;
- acquiring relationship;
- merchant category;
- processing currencies;
- card-present or card-not-present activity;
- risk settings;
- authentication configuration;
- settlement arrangements;
- reporting; and
- other processing rules.
A MID is not necessarily a 15-digit number
This is a common oversimplification.
Merchant ID formats vary between acquirers, processors and payment platforms.
For example, current Visa Acceptance documentation describes acquiring MIDs that can contain between 8 and 24 alphanumeric characters in one payment-authentication environment, while other processor reporting formats use 15-character merchant-ID fields.
Businesses should therefore use the exact identifier supplied by their acquirer or processor rather than assuming a MID must have a particular number of digits.
What does a Merchant ID actually do?
The MID helps identify which merchant processing configuration a transaction belongs to.
When a payment is submitted, the payment environment needs to know which merchant is requesting the transaction and which acquiring setup applies.
Depending on the architecture, the MID can therefore help determine or reference:
- which merchant account is processing the transaction;
- the relevant acquirer;
- accepted currencies;
- processing channel;
- risk settings;
- 3D Secure configuration;
- reporting hierarchy;
- transaction routing; and
- the wider merchant configuration.
It is an important processing identifier, but it should not be thought of as the merchant's bank-account number.
Is a Merchant ID the same as a merchant account?
Not exactly.
A merchant account describes the broader acquiring or processing relationship that allows a business to accept card payments.
A Merchant ID is an identifier used within that relationship.
In a simple setup, the merchant may effectively think of the merchant account and MID as one thing because it only has one processing configuration.
In a more complex environment, one merchant relationship can sit above several transactional accounts or MIDs.
Visa Acceptance Solutions, for example, supports a hierarchy where a merchant-level account can contain multiple transacting MIDs underneath it.
This becomes relevant for businesses with more complicated payment estates.
Is a Merchant ID the same as a bank account number?
No.
The MID identifies the merchant within the payment-processing environment.
The business's bank account is where settlement funds may ultimately be paid.
Those are different identifiers.
Visa Acceptance documentation specifically notes that an acquiring Merchant ID can be different from the business deposit identifier used in settlement.
A business changing its settlement bank account therefore should not assume that this automatically means its MID must change.
Likewise, changing acquirer will normally involve a new acquiring setup even if the business continues settling into the same bank account.
Merchant ID vs Merchant Category Code
A MID and MCC are completely different.
Merchant ID / MID: identifies a merchant account or processing relationship within the payment infrastructure.
Merchant Category Code / MCC: is a four-digit code used to classify the merchant according to its principal business activity.
For example, two separate businesses might both operate under the same MCC while having completely different Merchant IDs.
The MCC can affect areas such as:
- provider underwriting;
- scheme rules;
- interchange treatment;
- risk monitoring;
- cardholder rewards;
- sector restrictions; and
- transaction reporting.
See our guide to Merchant Category Codes for the wider MCC structure.
Merchant ID vs Terminal ID
A Terminal ID, usually shortened to TID, identifies a particular transaction terminal or processing endpoint rather than the overall merchant relationship.
One MID can therefore potentially sit above several terminal IDs.
For example, a retailer might have:
Merchant MID
- Terminal 001 – Nottingham store till 1
- Terminal 002 – Nottingham store till 2
- Terminal 003 – Leicester store
- Terminal 004 – mobile events terminal
The exact hierarchy depends on the provider.
Visa Acceptance documentation treats merchant IDs and terminal IDs as separate processor-assigned values and notes that merchants can have several of each.
Merchant ID vs payment gateway ID
A gateway can also have its own merchant, organisation or account identifier.
This is not automatically the same as the acquiring MID.
A merchant using a separate gateway and acquirer may therefore have:
- a gateway account or organisation ID;
- an acquiring MID;
- one or more transactional MIDs;
- terminal or channel IDs;
- 3D Secure configuration IDs; and
- other processor references.
This distinction becomes especially important when a business uses an independent or acquirer-agnostic gateway.
See our Acquirer-Agnostic Payment Gateway guide for more complex gateway structures.
Merchant ID and statement descriptor are not the same thing
Your MID is mainly a processing identifier.
The name a customer sees on their bank statement is normally controlled through the transaction or statement descriptor.
Payment providers can use terms such as:
- statement descriptor;
- billing descriptor;
- shopper statement;
- transaction description; or
- doing-business-as name.
These descriptors should help customers recognise the transaction.
A confusing descriptor can contribute to customer enquiries and chargebacks even though the underlying MID is configured correctly.
Can one business have more than one MID?
Yes.
Multiple MIDs can be entirely legitimate and can form part of a well-designed payment architecture.
Current Visa Acceptance processor documentation specifically notes that merchants may have multiple MIDs for reasons such as:
- processing different currencies; or
- separating card-present and card-not-present activity.
Businesses may also use different merchant-processing accounts for other operational reasons, depending on the acquirer and provider structure.
Examples can include:
- different brands;
- different countries;
- separate ecommerce sites;
- different business units;
- retail vs online;
- MOTO vs ecommerce;
- different risk profiles;
- different settlement arrangements;
- different currencies;
- different acquirers; and
- different legal entities where separately boarded.
When can multiple MIDs be useful?
The value of multiple MIDs is normally operational rather than simply having more identification numbers.
A well-designed structure can make it easier to separate:
- transaction volumes;
- chargebacks;
- refunds;
- settlement;
- currencies;
- sales channels;
- business units;
- brands;
- countries;
- risk profiles; and
- reporting.
However, multiple MIDs can also add complexity.
The business may need to manage:
- several settlement files;
- multiple statements;
- different pricing schedules;
- different reserves;
- several gateway configurations;
- different transaction descriptors;
- additional reconciliation; and
- more complicated support investigations.
Need a new MID or a more complex merchant-account structure?
Tell us how your business takes payments, which gateways or acquirers you use and whether you need separate processing by channel, currency, brand, entity or location.
Merchant Advice Service can help you understand the acquiring requirement before identifying providers that may be suitable.
Find suitable merchant account providers
Can different locations have separate Merchant IDs?
Potentially, yes.
The appropriate structure depends on the acquirer and how the business operates.
A multi-location merchant could potentially organise processing by:
- merchant account;
- store;
- MID;
- terminal ID;
- legal entity;
- business unit; or
- a combination of these.
Modern processors can support hierarchical structures where stores or transactional accounts sit beneath a wider merchant account.
The best architecture depends on how the business wants to handle:
- settlement;
- reporting;
- pricing;
- refunds;
- chargebacks;
- user access;
- business entities; and
- finance reconciliation.
Can one MID be used for multiple legal entities?
Businesses should not assume that one acquiring MID can simply be shared between separate companies.
The acquirer needs to understand which legal entity is the merchant responsible for the transaction.
That affects areas including:
- underwriting;
- KYC;
- merchant agreement;
- settlement;
- tax and accounting;
- chargebacks;
- customer contracts; and
- card-scheme transaction data.
Payment facilitators and platform models can support more complex structures, but that does not mean unrelated or separately contracted legal entities should process through a MID without the provider's approval.
Businesses with group structures should explain the legal entities and flow of funds when designing the payment setup.
Multiple MIDs for ecommerce and face-to-face payments
Some businesses separate ecommerce and card-present processing.
This can be useful because the two channels can have different:
- fraud profiles;
- chargeback rates;
- authentication requirements;
- pricing;
- gateway technology;
- terminal infrastructure;
- reporting; and
- operational ownership.
Visa Acceptance processor guidance specifically recognises that merchants can have different MIDs for card-present and card-not-present processing.
Whether that is necessary for a particular business depends on the acquirer and payment architecture.
Multiple MIDs for different currencies
International businesses may also have MID structures that vary by processing currency.
Again, this depends on the acquirer and processor.
Currency structure can interact with:
- acquiring location;
- settlement currency;
- merchant entity;
- customer country;
- cross-border fees;
- FX costs;
- gateway routing; and
- reconciliation.
Large international merchants should therefore consider MID architecture as part of the wider acquiring design rather than simply opening another account whenever a new currency is added.
Using multiple acquirers
Larger businesses may process payments through more than one acquiring bank.
Reasons can include:
- international expansion;
- local acquiring;
- sector appetite;
- resilience;
- commercial negotiation;
- different legal entities;
- different card types;
- processing performance; and
- risk diversification.
Each acquiring relationship can introduce its own merchant identifiers.
An acquirer-agnostic gateway or orchestration layer may then route transactions to different acquiring MIDs.
Read our Multi-Acquirer Gateway guide for more detail.
More MIDs do not automatically mean better resilience
A business can have several MIDs that all depend on the same acquirer or processing platform.
That is different from having genuinely separate acquiring relationships.
Likewise, opening another MID does not automatically solve:
- provider termination;
- scheme restrictions;
- poor underwriting fit;
- gateway outages;
- fraud problems;
- chargeback problems; or
- a weak business model.
Resilience needs to be designed across the complete payment stack rather than measured by the number of merchant IDs alone.
Can a MID be used with a different payment gateway?
Potentially.
Some merchant accounts can be connected to several compatible payment gateways, while other acquiring products are tightly tied to the provider's own gateway.
A business wanting to keep its acquiring relationship while changing gateway should establish:
- whether the acquirer supports the new gateway;
- whether the gateway supports the acquirer;
- whether the existing MID can be boarded;
- supported currencies;
- 3D Secure configuration;
- token migration;
- recurring-payment requirements;
- fraud configuration;
- testing requirements; and
- commercial charges.
This is one reason gateway and merchant-account selection should not always be treated as the same decision.
What happens to your MID when you switch acquirer?
A merchant switching to a different acquiring bank or processor will normally be boarded into a new acquiring relationship.
That generally means new merchant-processing identifiers are issued by the new provider.
The old MID does not usually become a portable identifier that the business simply takes from one acquirer to another.
If the business keeps its existing gateway, the gateway may need to be reconfigured or boarded with the new acquiring MID.
Businesses should also consider:
- stored payment tokens;
- recurring payments;
- 3D Secure;
- refunds against historic transactions;
- chargebacks after migration;
- open authorisations;
- settlement files;
- reporting history; and
- cutover testing.
Where can I find my Merchant ID?
The location varies by provider.
Businesses may be able to find the relevant MID in:
- the merchant statement;
- the provider portal;
- merchant-account onboarding documentation;
- gateway configuration;
- terminal information;
- processing reports; or
- support documentation.
The safest option is to ask the acquirer or processor which identifier it means if somebody requests “your MID”.
This is particularly important for larger merchants because the business may have several valid merchant IDs.
Should you keep your MID secret?
A MID should not be treated like a cardholder PAN, online-banking password or API secret.
It is a merchant-processing identifier rather than a credential that should independently authorise access to money.
However, businesses should still avoid publishing internal payment identifiers unnecessarily.
MIDs can form part of:
- merchant support verification;
- gateway configuration;
- processor onboarding;
- reporting;
- technical integrations; and
- payment investigations.
They should therefore be shared with legitimate providers, gateways and technical partners when required rather than posted publicly without a reason.
Merchant IDs and payment reconciliation
MID structure can have a significant effect on finance reporting.
A business using several MIDs may need to reconcile:
- transaction → MID;
- MID → business unit;
- MID → store;
- MID → currency;
- MID → acquirer;
- MID → settlement batch;
- settlement → bank account; and
- fees → general ledger.
This can become complex where the business has several providers or payment channels.
See our Payment Reconciliation guide .
MIDs and integrated payment systems
Businesses integrating payments with ERP, EPOS, CRM or other software may need the correct merchant and terminal identifiers configured in the integration.
For example, a payment environment might need to determine:
Store A → Merchant MID A → Terminal group A → settlement account A
while:
Website → Ecommerce MID → gateway → settlement account B
The merchant architecture therefore needs to be reflected correctly in the software architecture.
Businesses with this type of requirement can also read our Integrated Payments guide .
Merchant IDs for platforms and embedded payments
Software platforms and payment facilitators introduce another layer of complexity.
A platform may have:
- a master or portfolio-level relationship;
- platform merchant identifiers;
- merchant-level accounts;
- sub-merchants;
- transactional MIDs;
- stores;
- balance accounts; and
- other provider-specific identifiers.
This is very different from a conventional merchant opening one standalone acquiring account.
SaaS companies and platforms considering this model should read our Embedded Payments guide .
High-risk Merchant IDs
There is not a universal special number format called a “high-risk MID”.
When people use this phrase, they normally mean a merchant account or MID issued by an acquirer that is willing to support a higher-risk business category.
The actual underwriting can involve:
- business sector;
- MCC;
- transaction volume;
- average ticket;
- customer locations;
- chargebacks;
- fraud;
- fulfilment;
- processing history;
- financial strength;
- reserves; and
- provider risk appetite.
The important part is therefore finding an acquirer whose underwriting model supports the merchant, not obtaining a differently formatted identification number.
See our High-Risk Merchant Accounts guide for more detail.
Can your MID be terminated?
A payment provider can terminate or restrict a merchant-processing facility in accordance with the merchant agreement and applicable rules.
If that happens, transactions may no longer be accepted through the affected merchant account or MID.
Potential reasons can include:
- material changes in the business;
- prohibited activity;
- excessive chargebacks;
- fraud concerns;
- misrepresentation during onboarding;
- financial risk;
- scheme-compliance issues;
- processing outside the approved business model; or
- other contractual reasons.
A merchant should establish why the facility was terminated before immediately applying elsewhere.
If an active MATCH, VMAS or equivalent terminated-merchant listing is the primary issue, Merchant Advice Service does not provide placement, removal, appeal or dispute services for those listings.
What should larger businesses consider when designing MID structure?
For a larger merchant, the question should not simply be “how many MIDs can we get?”
The more useful questions are:
- Which legal entities actually sell to the customer?
- Which acquirers are being used?
- Which countries are involved?
- Which currencies are processed?
- Which channels need to be separated?
- Do ecommerce and retail need different reporting?
- Which settlement accounts should receive funds?
- How will refunds and chargebacks be assigned?
- How will finance reconcile each MID?
- Does the gateway support multiple acquirers?
- How will tokens and recurring payments work?
- What happens if one acquirer becomes unavailable?
- How are customer statement descriptors controlled?
- How will new brands or locations be added?
The MID architecture should follow those requirements rather than become the starting point itself.
Design the merchant-account structure around the business
A straightforward merchant may only need one acquiring relationship.
A larger business may need several merchant IDs, currencies, channels, entities, gateways or acquirers working together.
Merchant Advice Service can help you define those requirements before identifying payment providers that may be suitable.
Review your merchant account requirements Explore merchant account providers
How Merchant Advice Service helps with MID and merchant-account requirements
Merchant Advice Service does not issue Merchant IDs.
MIDs and related processing identifiers are issued or configured by the relevant acquirer, processor or payment platform.
Our role is to help businesses understand the payment architecture they require before identifying providers that may be suitable.
That can include:
- new merchant accounts;
- multiple MIDs;
- multiple legal entities;
- different business units;
- ecommerce and retail;
- MOTO;
- multiple currencies;
- international acquiring;
- multiple acquirers;
- gateway compatibility;
- integrated payments;
- settlement;
- reporting;
- reconciliation;
- provider switching; and
- larger payment-provider tenders.
Businesses planning a larger provider review can also read our Payment Provider RFP & Tender Guide .
Editorial & Commercial Disclosure
This guide provides general information about Merchant IDs, merchant accounts and payment-processing account structures.
Merchant-ID terminology, formats and hierarchy vary between acquiring banks, processors, gateways and payment platforms. A MID should therefore not be assumed to use one universal number format or account structure.
Merchant Advice Service does not issue Merchant IDs or control payment-provider account configuration.
Payment providers determine merchant-account structure, underwriting, MID allocation, settlement, pricing and technical configuration.
MAS is an independent payments information and provider-matching service. MAS may receive a referral fee or commission from some payment providers where a business proceeds following an introduction. Commercial relationships do not determine the factual information or provider-selection principles contained within this guide.
Businesses with complex entity, acquiring, gateway or international structures should confirm their proposed architecture directly with the relevant payment providers before implementation.
Information is provided for general guidance and should not be treated as legal, accounting, regulatory or technical implementation advice.
