Merchant IDs, MCC Codes & Acquiring Terms

Merchant IDs, MCC Codes & Acquiring Terms

Understanding merchant acquiring is essential for running or integrating any payment system. Merchant IDs, MCC codes, acquirers, and settlement structures define how businesses accept payments, how risk is managed, and how transactions flow from customer to merchant across global payment networks.

Below is a clean, clear, copy-paste-ready explanation of all core acquiring terms with a real-life example using Germany, USA, Brazil, Saudi Arabia, and Sweden.

1. Merchant ID (MID)

A Merchant ID (MID) is a unique identifier assigned to a business by an acquirer or PSP when the merchant is approved to accept card payments.

What an MID does

  • Identifies the merchant in card networks
  • Links transactions to the merchant’s account
  • Defines settlement rules
  • Defines risk profile
  • Used for chargebacks, refunds, and reconciliation

Every merchant that accepts cards must have an MID, either directly or through an aggregator’s master MID.

Types of MIDs

  • Direct MID: merchant fully underwritten (larger businesses)
  • Sub-MID: merchant onboarded under an aggregator (small merchants)

2. MCC Code (Merchant Category Code)

MCC is a 4-digit code assigned to a merchant that describes the type of business they operate.

Why MCC matters

  • Determines interchange fees
  • Determines risk level
  • Affects chargeback classification
  • Affects whether transactions are high-risk
  • May impact compliance checks
  • May limit card acceptance for some categories (for example gambling)

Examples

  • 5411: Supermarkets and grocery
  • 5812: Restaurants
  • 5732: Electronics stores
  • 5999: General retail
  • 4814: Telecom services
  • 6012: Financial institutions

MCC codes influence fees, fraud controls, and regulatory rules.

3. Acquirer (Acquiring Bank)

An acquirer is a licensed financial institution that enables merchants to accept card payments and communicates with card networks on their behalf.

What the acquirer does

  • Underwrites the merchant
  • Provides MID
  • Connects to Visa and Mastercard networks
  • Handles authorizations and settlements
  • Manages chargebacks and disputes
  • Enforces compliance requirements
  • Performs fraud and risk checks

Acquirers are the backbone of card acceptance.

Examples of acquirers

  • Germany: PayOne, Deutsche Bank
  • USA: Fiserv, Chase Paymentech
  • Brazil: Cielo, Rede
  • Saudi Arabia: HyperPay (acq partner), STC Pay partners
  • Sweden: Swedbank, Bambora

4. Payment Processor vs Acquirer

These are commonly confused.

RoleAcquirerProcessor
Provides merchant accountYesNo
Communicates with card networksYesYes
Handles authorization routingYesYes
Manages disputesYesNo
Manages settlementYesNo
Performs underwritingYesNo
Provides APIsNoYes
Manages technical processingNoYes

Some companies act as both.

5. Aggregators and Sub-Merchant Models

Aggregators onboard merchants without giving them direct MIDs. Examples include Stripe, PayPal, MercadoPago, PayTabs (sub-merchant model in GCC), and Klarna. Merchants receive a sub-merchant ID, and the aggregator holds the master MID. This is ideal for SMEs needing fast onboarding.

6. Terminal ID (TID) and Store ID (SID)

Used mostly for retail and physical stores.

  • TID identifies each POS terminal
  • SID identifies each store location

These help with reconciliation and risk monitoring.

7. Descriptor (Billing Descriptor)

A descriptor is the text customers see on their bank or card statement.

Examples:

  • AMAZON EU S.A.R.L.
  • STARBUCKS 0123 BERLIN

Proper descriptors reduce chargebacks.

8. Interchange Fees

Interchange is the fee paid from the acquirer to the cardholder’s bank for each transaction.

Factors affecting interchange include MCC code, card type (credit, debit, premium), region (EU, US, BR, GCC), and transaction type (online, physical). Fintechs must understand interchange to calculate margins.

9. Chargebacks and Dispute Terms

  • Chargeback: customer disputes a transaction
  • Reason code: classification of dispute (fraud, not delivered)
  • Retrieval request: issuer requests transaction info
  • Representment: merchant provides proof
  • Arbitration: final decision by card network

High chargeback rates cause MIDs to be frozen or shut down.

10. Settlement Cycles

Settlement is how quickly merchant funds are paid out.

Examples:

  • Germany: 1 to 2 days
  • USA: same-day or next-day
  • Brazil: instant or T+30 (with fees)
  • Saudi Arabia: T+1 or T+2
  • Sweden: instant or T+1

Settlement cycles affect merchant cash flow.

11. Real-Life Example (German Merchant Selling to Customers in USA, Brazil, and Saudi Arabia)

Scenario: A mid-size online electronics store in Berlin, Germany begins selling internationally.

Process

  1. Acquirer issues merchant ID. PayOne assigns MID and MCC 5732 (electronics retail).
  2. Payment gateway processes requests. Customers from USA, Brazil, and Saudi Arabia attempt payment. Gateway encrypts and passes to acquiring bank.
  3. Card networks route the transaction. US Visa cards to US issuers, Brazil cards to local networks, Saudi Arabia Mada cards to local network plus international rails.
  4. Acquirer receives authorization. PayOne receives approval or decline and passes result to merchant.
  5. Settlement occurs. EUR settlement to German merchant. Interchange varies per region. Risk rules applied per MCC.
  6. Chargeback example. A US customer disputes a transaction. Acquirer processes chargeback using MCC-specific rules. Merchant provides delivery proof in representment.

12. Summary

  • MID is the merchant identity in the card network
  • MCC is the category code defining risk and fee structure
  • Acquirer is the bank enabling merchants to accept cards
  • Gateway is the secure payment entry point
  • Aggregators provide simplified merchant onboarding
  • Descriptors, settlement cycles, and disputes define merchant experience

These terms form the backbone of card acceptance and acquiring operations in modern fintech environments.