How Merchant Location Affects Card Fees
A company is: Where is the merchant? For tax? For the customer contract? For card-network data? For interchange? For a provider's international-card pricing? For settlement? Those questions can produce different answers. That is why merchant location is not one variable. The paym
How Merchant Location Affects Card Fees: Why Your Entity and Acquiring Setup Matter
A company is:
incorporated in the United States;
staffed by a European commercial team in France;
selling heavily to German customers;
processing some payments through a MID associated with the Netherlands;
using an acquirer whose own legal and processing structure must be verified separately;
and receiving settlement into another bank account.
Where is the merchant?
For tax?
For the customer contract?
For card-network data?
For interchange?
For a provider's international-card pricing?
For settlement?
Those questions can produce different answers.
That is why merchant location is not one variable.
The payment-cost question is not:
It is:
“Which merchant-side legal or acquiring location does this particular payment rule recognize?”
Your website market does not automatically determine your merchant location
A German storefront can:
display German;
price in euros;
advertise to German consumers;
ship from Germany;
use a .de domain;
and still not necessarily represent a German merchant location for the card-pricing rule being analyzed.
European law provides a useful concrete example.
For purposes of Regulation (EU) 2015/751 on interchange fees, an ecommerce “point of sale” is the address of the fixed place of business where the merchant conducts its business, regardless of the website or server location through which the transaction is initiated. If there is no fixed place of business, the Regulation supplies further address tests.
That definition is jurisdiction- and regulation-specific rather than a universal global network definition.
But it demonstrates the general point:
customer-facing geography and payment-system geography are different data.
Start by decomposing “merchant location”
When a payment team says:
“Merchant country: Germany.”
the next question should be:
“Which Germany?”
Possible meanings include:
Brand or website market
Where the customer thinks the business is operating.
Operating market
Where products are marketed, distributed or serviced.
Legal entity country
Where the merchant legal entity is incorporated or registered.
Merchant-of-record location
The jurisdiction of the entity acting as the seller/payment recipient for the relevant commercial flow, according to the merchant's actual contractual structure.
Merchant account or MID country
The geography associated with the merchant account/MID used for that transaction under the acquiring setup.
Acquirer country
Where the relevant acquiring institution is located for the payment rule.
Settlement-account country
Where merchant funds are ultimately paid.
Principal place of business
A network or regulatory location concept that can matter under particular rules.
These variables may coincide.
Internationally, they often do not.
Legal entity is important—but it is not automatically the complete answer
A merchant's incorporation country is commercially and legally important.
It can affect:
contracts;
onboarding;
underwriting;
tax;
regulatory obligations;
eligibility for payment services.
But the mere fact that the parent company is incorporated in the United States does not prove every transaction must be priced as a U.S.-located merchant transaction.
The acquiring arrangement can involve additional merchant entities, MIDs or recognized merchant locations.
Conversely, the existence of a subsidiary abroad does not automatically make every sale through the group “local.”
The payment team needs to answer:
Which entity is actually participating in this transaction?
Operating market is not the same as legal location
Suppose the U.S. company has:
an office in Paris;
ten French employees;
French-language customer support;
French customers.
That establishes genuine business activity.
It does not by itself tell you which merchant location should be submitted into the card ecosystem.
Visa's merchant-location guidance illustrates the distinction. For card-absent commerce, Visa's published merchant guidance says the principal place of business is generally the baseline location and lists more substantive conditions for assigning certain additional locations. It specifically notes that a payment or customer-service function, server, URL, director or investor does not by itself satisfy the described criteria.
That Visa guidance dates from 2019. Visa still lists it in its current merchant resource library, but the document itself says the published Visa Core Rules prevail if there is any difference. Visa's current rules page likewise instructs merchants to consult the current rules and their acquirer for region- and country-specific requirements.
So use the guidance to understand the concept, then verify the current rule before making a commercial decision.
Merchant of record answers a different question
“Merchant of record” is sometimes used too casually as a synonym for:
the company whose logo appears at checkout.
For this analysis, treat it as a commercial-role question:
Which entity is actually acting as the merchant/seller for the relevant payment arrangement?
That entity may affect:
merchant onboarding;
contracting;
transaction descriptors;
risk allocation;
tax and legal structure;
acquiring eligibility.
But “merchant of record” itself is not a universal substitute for:
MID country
or:
acquirer country.
A cost model should preserve those fields separately.
The MID is an operational payment identity
A Merchant ID is an identifier tied to the merchant relationship used in acquiring.
The exact assignment and structure depend on the acquirer/provider.
One global company can have:
one MID;
several MIDs by market;
several MIDs by entity;
several MIDs by card brand or processing setup;
backup acquiring relationships.
Current Mastercard gateway documentation reflects this operational separation: it describes an acquirer merchant ID as the identifier allocated to the merchant by its acquiring institution and separately records the acquirer's country.
That is useful evidence for an important architectural point:
merchant identity and acquirer identity are linked, but they are not the same field.
“Our MID is European” is still not precise enough
Europe is not one card-pricing country.
A useful merchant inventory records:
MID ID: ______
Merchant entity: ______
Merchant-location country represented: ______
Acquirer: ______
Acquirer country: ______
Card-network region: ______
Payment methods: ______
Transaction currencies: ______
Settlement currencies: ______
Without that mapping, statements such as:
“our European MID”
can conceal the exact geographic relationship that controls a fee.
Acquirer country is another independent location
An acquirer is the payment-service provider on the merchant/payee side that accepts and processes the card transaction under the acquiring relationship.
The EU Interchange Fee Regulation formally defines an acquirer as the PSP contracting with a payee to accept and process card-based transactions resulting in a transfer of funds to the payee.
Under that Regulation, “cross-border payment transaction” explicitly references issuer and acquirer location, and in another part of its definition can reference the issuer relative to the point of sale.
That does not create a universal worldwide card definition.
It does show why:
merchant incorporation country
and:
acquirer country
cannot simply be treated as interchangeable.
Acquirer geography can change while the merchant brand stays identical
Consider one ecommerce brand.
The customer sees the same:
website;
products;
checkout;
statement descriptor.
But the merchant routes eligible transactions through:
Acquirer A
in one country.
and:
Acquirer B
in another.
The merchant's brand has not moved.
Its payment path has.
That change can alter the geographic relationship used in:
interchange classification;
network assessments;
PSP/acquirer commercial pricing;
regulatory scope.
The exact financial result must be verified for the specific network, corridor and contract.
Provider headquarters is not acquirer country
Suppose a PSP's corporate headquarters is in Country A.
That does not prove a specific merchant transaction is acquired in Country A.
A provider can connect to multiple acquiring institutions or operate through different legal/acquiring structures.
Current Mastercard gateway specifications explicitly allow a merchant to have one or more acquirers and record the acquirer's country separately.
Therefore a cost-analysis spreadsheet should never populate:
Acquirer country = PSP HQ country
without verification.
Ask the provider:
Which acquiring relationship handles this transaction segment?
Visa transaction data likewise distinguishes merchant identifiers and location fields
Visa's current acceptance API documentation contains separate fields for:
card-acceptor identification;
merchant address;
business registration identifiers;
service-location country;
card-acceptor location information.
The implementation details are product-specific.
But they reinforce the same principle:
payment geography is represented through structured transaction and acceptance data, not inferred from a brand's homepage.
The settlement bank account is another boundary
A merchant might have:
a Netherlands MID;
an acquiring relationship in the EEA;
a German operating entity;
settlement into a U.S. dollar bank account elsewhere.
That settlement destination matters for:
treasury;
FX;
banking;
cash management;
payout mechanics.
It should not automatically be used as the merchant's card-acquiring location.
The card-processing analysis should ask:
What location determined the card transaction's classification?
The settlement analysis should separately ask:
Where and in what currency did the merchant receive funds?
Those questions belong to different layers.
The deeper bank-account and treasury implications should be linked to the Entity, Settlement & Cross-Border Funds cluster rather than reproduced here.
The EU example makes the distinction unusually clear
Regulation (EU) 2015/751 defines:
the issuer;
the acquirer;
a cross-border payment transaction;
a domestic payment transaction;
the point of sale.
For ecommerce, that point of sale is tied to the merchant's fixed place of business rather than its website or server location.
The Regulation also explains that card schemes historically used the “point of sale” country in interchange application and that EU rules were designed in part to facilitate cross-border acquiring rather than force simple one-country merchant/acquirer assumptions.
That makes one lesson especially useful:
even within one legal regime, merchant location, acquiring location and customer-facing website location are distinguishable concepts.
Visa's merchant-location rules add another practical lesson
Visa's published guidance says that providing the correct merchant location is important for:
cardholder recognition;
risk and authorization decisions;
correct fee and interchange assessment.
For fixed-location card-present transactions, that guidance generally connects merchant location with the physical transaction location. For card-absent merchants, the guidance uses principal place of business as the baseline and sets criteria for certain additional locations.
It also says ecommerce merchants should display the merchant country used to process the transaction during the checkout flow so the cardholder can understand whether a transaction is domestic or international before purchase.
Again, the document itself directs merchants to current Core Rules where there is any conflict, so any production implementation should be validated with the merchant's acquirer.
Merchant location is therefore a rule-specific identity
A better internal vocabulary is:
Corporate location
Where the company is legally headquartered or incorporated.
Commercial location
Where the business sells or operates.
Transaction merchant location
The location represented for the transaction under applicable card rules.
Acquiring location
The location of the acquiring institution/setup relevant to the transaction.
Settlement location
Where merchant proceeds are paid.
Do not compress all five into:
Merchant country.
A German customer does not make a German transaction by itself
Return to the opening example.
The customer:
lives in Germany
and:
uses a German-issued card.
The website:
targets Germany.
But suppose the transaction is represented using a qualifying merchant location outside Germany and acquired through a different market.
From the customer's perspective:
German purchase.
From a marketing perspective:
German market.
From the relevant card-cost perspective:
potentially not a German domestic acquiring relationship.
The exact classification depends on the applicable network/provider framework.
That is why the payer-side geography article and this merchant-side geography article must remain separate.
Card country and merchant country form a relationship
The merchant-side location has little cost meaning without its counterpart.
For card payments, a useful cost map may compare:
merchant/MID/acquirer geography
→
issuer geography.
For example:
Merchant/acquiring setup
Card issuer
Classification under verified rule
Effective cost
Setup A
Country A
Setup A
Country B
Setup A
Region C
Setup B
Country A
Setup B
Country B
The merchant-side location is one half of the corridor.
The issuer/customer article owns the other half.
Do not substitute customer residence for issuer country
A German shopper can pay with:
a German-issued card;
a U.S.-issued card;
a U.K.-issued card;
a corporate card issued elsewhere.
So:
checkout country = Germany
is not sufficient for card-cost segmentation.
The brief explicitly requires card/customer geography to remain distinct and states that issuer/card geography can matter more than physical location for card-cost analysis.
Merchant country can change which “domestic” baseline is meaningful
Suppose finance wants to calculate:
domestic card effective rate
versus:
international card effective rate.
Before computing either rate, define the merchant-side baseline.
For MID A:
domestic may mean one issuer relationship.
For MID B:
the same issuer country can belong to a different geographic relationship.
If finance pools both MIDs together, the blended rate can conceal the reason costs differ.
So domestic/cross-border reporting should be generated at least at the level where the merchant-side acquiring geography changes.
Segment by entity before blaming the country
Suppose European payments cost more this quarter.
Potential explanations include:
more traffic through a different entity;
a changed MID mix;
new acquirer;
more foreign-issued cards;
card-product mix;
price changes;
FX;
network changes.
A country-level dashboard may show the symptom without the cause.
The first decomposition should be:
entity
→ MID
→ acquirer
→ issuer geography
→ card segment
→ cost.
The Merchant Location Cost Map
For every card-processing setup, map eight identities.
Brand / website
What the customer sees.
Examples: domain, storefront, app market.
Card-cost significance: Do not use as the default merchant-location proxy.
Operating market
Where the merchant actively sells or operates.
Card-cost significance: Commercially important but not automatically the card-pricing location.
Legal entity
The company/entity participating in the commercial relationship.
Card-cost significance: Can affect onboarding, eligibility and transaction structure.
Merchant of record
Which merchant entity is actually the seller/payment recipient for this flow.
Card-cost significance: Important to commercial and acquiring structure, but must not be substituted automatically for MID or acquirer country.
MID / merchant account
The merchant acceptance identity used for the transaction.
Card-cost significance: Critical operational segmentation field.
Acquirer
The institution/acquiring setup processing the merchant-side card transaction.
Card-cost significance: Frequently central to issuer/acquirer geographic classification.
Settlement account
Where proceeds ultimately arrive.
Card-cost significance: Important to settlement, banking and FX; not a safe proxy for card transaction geography.
Card issuer / payer geography
The other side of the geographic relationship.
Card-cost significance: Compare only after merchant-side identity is resolved.
Add a ninth field: rule owner
For every conclusion, document:
Classification according to:
Visa rule;
Mastercard rule;
EU regulatory definition;
acquirer pricing term;
PSP pricing definition;
other payment-method rule.
This prevents teams from saying:
“The transaction is cross-border.”
without knowing who defined it that way.
Scenario 1: U.S. parent, French office, Dutch payment setup, German customer
This is the editorial brief's ambiguity in practical form.
Brand
European ecommerce storefront.
Parent incorporation
United States.
Staff
France.
Customer
Germany.
Card
Assume German-issued for the hypothetical.
MID
Associated with a Netherlands setup.
Acquirer
Must be verified.
Settlement
Could be somewhere else again.
Can finance call the transaction:
“German domestic”?
No—not from those facts alone.
The correct sequence is:
determine which merchant location is represented for the transaction;
identify the acquirer and its relevant geography;
identify the issuer;
identify the applicable network/provider rule;
classify;
calculate fees.
The website's German storefront answers none of those questions by itself.
Scenario 2: Local office, foreign MID
A merchant has a substantial office in Italy.
It employs local staff and serves Italian customers.
But payments for that product continue through a merchant/acquiring setup elsewhere.
The Italian operating presence may matter for commercial and legal reasons.
It does not automatically mean:
Italian domestic card pricing.
The team should investigate whether the merchant has a recognized local merchant/acquiring setup for those transactions rather than infer it from the office.
Scenario 3: Local bank account, foreign acquiring
A merchant opens a German bank account.
Finance begins calling Germany a “local settlement market.”
That may be a valid treasury description.
But if the card transaction is still processed through another acquiring geography, the existence of the German bank account does not by itself establish German local acquiring.
Use two columns:
Acquiring geography
and:
Settlement account geography.
Never overwrite one with the other.
Scenario 4: Multiple MIDs under one legal entity
A single legal merchant entity has several acquiring relationships.
Traffic is routed:
MID A for Market A;
MID B for Market B;
MID C as backup.
Corporate legal location has not changed.
Yet the merchant's payment geography can differ by transaction route.
That is why finance should be able to calculate:
effective cost by MID
not merely:
effective cost by legal entity.
Scenario 5: Multiple legal entities, one global brand
The customer sees one global brand.
Behind it, different legal entities sell in different markets.
This architecture may make local acquiring possible in certain countries.
But the merchant must verify:
which entity owns the sale;
which MID belongs to it;
which acquirer handles the payment;
how the transaction is represented;
where settlement occurs;
what local obligations follow.
Do not assume every subsidiary automatically creates a valid local-acquiring setup.
Multi-entity architecture can improve or worsen economics
More local structures can potentially change:
international-card classification;
interchange treatment;
network assessments;
PSP/acquirer pricing;
authorization behavior.
They can also create:
additional merchant accounts;
compliance work;
banking complexity;
reconciliation;
treasury work;
tax/legal obligations;
implementation and maintenance.
Therefore:
more local ≠ automatically cheaper.
The economic comparison is:
Gross processing benefit
minus:
Incremental entity/acquiring operating cost
equals:
Net structural benefit
The detailed local-acquiring break-even calculation belongs in the dedicated local-acquiring article.
EU cross-border acquiring provides an important counterexample to simplistic geography
EU Regulation 2015/751 was designed in part to facilitate acquiring services across Member States and prohibits specified territorial restrictions and country-specific licensing requirements within its scope.
That means:
acquirer in another Member State
does not automatically imply the simplistic economic conclusion:
“merchant is foreign, therefore use some global cross-border rate.”
The applicable regulatory and network rules still have to be applied precisely.
This is why the article should resist replacing one oversimplification—
merchant country = headquarters
—with another—
merchant country = acquirer country.
Which merchant-side locations can affect cost?
Rather than ranking locations universally, evaluate each against the actual fee.
Interchange
Ask which merchant/acquirer or point-of-sale geography the applicable network/regulatory rule uses.
Network assessment
Identify the network's actual geographic trigger.
Acquirer pricing
Identify the acquiring entity/setup and contract.
PSP markup
Determine whether provider pricing changes by merchant entity, MID, card issuer geography or route.
FX
Identify transaction and settlement currency separately.
Settlement cost
Identify payout currency, bank account and treasury path separately.
Every row should answer:
Which location activates this cost?
Do not call every merchant-location cost “cross-border interchange”
If a merchant sees a higher international rate, the cause may be:
interchange;
scheme/network assessment;
acquiring surcharge;
PSP commercial markup;
fixed international charge;
FX.
The article should not try to reproduce all of those mechanics.
Its job is upstream:
identify the merchant-side geography needed to attribute the cost correctly.
The International Card Fees and Cross-Border Assessments articles own the deeper fee decomposition.
Location can affect eligibility for local acquiring
That establishes a narrow, current public capability statement.
It does not establish:
which countries are available to every merchant;
which merchant entity is required;
which MID country applies;
which underlying acquirer handles a given merchant;
card-network classification;
pricing;
authorization uplift for a specific merchant;
guaranteed cost reduction.
Those details require current merchant-specific/internal verification.
A local MID can be economically useful only if it changes a meaningful layer
Suppose a merchant can create or access a local acquiring setup.
Before approving it, ask:
What changes?
Possible answers might be:
network classification;
applicable interchange;
provider international pricing;
approval performance.
Then ask:
What does not change?
Potential examples:
product price;
customer country;
some PSP fixed fees;
settlement FX;
compliance overhead.
Local acquiring should be judged by the actual delta, not by the label local.
Merchant location can also affect customer clarity
Visa's published guidance says ecommerce merchants should prominently display the merchant country used to process the transaction within checkout so the cardholder understands whether the transaction may be domestic or international before committing.
That means merchant-country accuracy is not merely an internal finance exercise.
It can also be a transaction-data and customer-disclosure issue under applicable network rules.
Any implementation should be checked against the current network rule set rather than relying only on the older guidance document.
Build a merchant-location inventory
For every production card path, create one row.
Field
Value
Brand/storefront
Customer market
Selling legal entity
Merchant of record
Merchant location submitted/recognized
MID
Merchant account country
Acquirer
Acquirer country
PSP
Card network
Issuer country
Transaction currency
Settlement currency
Settlement bank country
Classification source
Domestic/intra-regional/cross-border status
Effective processing rate
Do not merge these columns even where they currently contain the same country.
The point of the map is to reveal when they diverge.
Then measure cost by merchant-side identity
At minimum track:
Entity volume
Successful card value by selling/merchant entity.
MID volume
Successful card value by MID.
Acquirer volume
Successful card value by acquirer.
Cross-border share
Using the verified classification for that segment.
Effective processing rate
included merchant card costs
÷ successful processed card value
Approval rate
Successful authorization outcomes divided by relevant attempts, using the merchant's standard methodology.
Cost per completed payment
Useful when alternative merchant/acquiring structures have different authorization performance.
Start reporting at MID × issuer geography
A useful first analytical cube is:
MID
× acquirer
× issuer country/region
× card segment.
Then record:
volume;
transaction count;
effective rate;
cross-border classification;
approval rate.
This allows finance to ask:
Does the same issuer country cost differently when processed through MID A versus MID B?
If yes, merchant/acquiring geography may be part of the explanation.
Add entity only where it actually changes the structure
If multiple MIDs all belong to the same merchant entity, entity-level reporting can obscure rather than explain variation.
Use the lowest structural level that changes the economics.
Typically that means at least:
merchant entity → MID → acquirer → issuer geography.
Keep currency in its own column
Merchant location and transaction currency are related operationally but not synonymous.
A U.S. entity can transact in EUR.
A European MID can process USD.
A local-currency checkout can still involve a cross-border card relationship.
A cross-border card payment can occur without an additional merchant-side conversion at that stage.
Therefore:
EUR ≠ European merchant location
and:
local currency ≠ local acquiring.
The brief explicitly requires FX and card geography to remain separate.
Use actual fee ownership before restructuring anything
Suppose a corridor appears expensive.
First identify:
Is the excess cost network-defined?
Is it interchange?
Is it PSP commercial markup?
Is it acquirer pricing?
Is it actually FX?
Changing merchant location or creating another MID is unlikely to be a good response if the expensive layer would remain unchanged.
The structural lever should match the cost owner.
Do not create entities to save a theoretical basis-point amount
Entity and acquiring changes can have real implementation costs.
The brief explicitly requires the merchant to account for possible entity setup, banking, compliance, reporting, reconciliation, settlement, treasury and maintenance overhead before treating local acquiring as net savings.
Therefore any proposal should show:
Current annual eligible volume
$____
Verified merchant-location premium affected
____ bps
Gross annual processing benefit
$____
Added provider/account cost
$____
Added operational cost
$____
Entity/compliance cost if included
$____
Net annual benefit
$____
Do not fabricate default values.
A local structure may still be worthwhile for performance
Merchant-location decisions should not be evaluated only on direct fees.
A different acquiring relationship can potentially affect:
authorization performance;
latency;
fraud tooling;
method availability;
settlement;
operational resilience.
So the investment case should measure actual merchant performance rather than assume an uplift.
Compare net contribution, not only basis points
Route A may cost:
less per approved transaction
but approve fewer customers.
Route B may carry:
higher processing cost
but produce more completed orders.
Where performance differs materially, compare:
Net contribution per 1,000 attempts
rather than:
Payment fee per successful transaction
The cluster brief explicitly prohibits blind cost-only routing and requires authorization performance to remain part of international-payment economics.
Merchant-location restructuring should pass four tests
Test 1: Classification
Does the proposed structure actually change the merchant/acquirer classification that causes the fee?
Test 2: Volume
How much eligible payment volume receives the new treatment?
Test 3: Performance
What happens to authorization, customer access and payment-method coverage?
Test 4: Complexity
What new entity, account, compliance, reporting, settlement and operational costs are created?
Only then calculate net benefit.
The Merchant Location Cost Map
For every merchant structure, use four layers.
Layer A — Customer-facing identity
Brand
Website
Operating market
These describe where the merchant appears to operate.
↓
Layer B — Commercial/legal identity
Legal entity
Merchant of record
These describe who is conducting the sale and entering the relevant commercial/payment relationships.
↓
Layer C — Card-acceptance identity
Merchant location represented
MID / merchant account
Acquirer
These are the first fields to inspect when analyzing card geographic classification.
↓
Layer D — Funds identity
Settlement currency
Settlement account
Bank country
These describe where proceeds ultimately move.
↓
Counterparty side
Issuer/card geography
Now determine:
domestic / intra-regional / interregional / other network-provider classification
under the actual rule.
Give every layer a “relevance” label
For each location, mark:
Direct
Explicitly used by the relevant pricing or network rule.
Eligibility
Affects whether the merchant can access the acquiring setup.
Operational
Affects routing, reporting or reconciliation but is not itself the fee trigger.
Settlement
Affects post-processing funds movement.
Customer-facing
Affects presentation/localization but is not the acquiring classification.
This prevents teams from assuming every geographic field changes interchange.
A merchant location audit should answer 12 questions
Which legal entity sells the product?
Which entity is merchant of record for the payment flow?
What merchant location is represented in transaction data?
Which MID processes the payment?
Which entity owns or is associated with that MID?
Which acquirer processes it?
Where is that acquirer located for the applicable rule?
Where was the card issued?
Which network classification applies?
What transaction currency is used?
Where and in what currency are proceeds settled?
Which one of those fields actually triggers the cost being investigated?
If question 12 cannot be answered, the merchant is not ready to restructure geography.
Final recommendation
International merchants should stop asking:
“Where are we based?”
when they are investigating card cost.
That question is too broad.
Instead map:
brand
→ operating market
→ legal entity
→ merchant of record
→ merchant location represented
→ MID
→ acquirer
→ settlement
and finally connect that merchant-side map to:
issuer geography.
Then identify the rule that converts that relationship into:
domestic;
intra-regional;
interregional;
cross-border;
or another provider/network category.
The most important result may be surprising.
The French office may not matter.
The German website may not matter.
The bank account may matter only after processing.
The legal entity may be necessary to obtain the setup without being the sole card-cost classifier.
The MID/acquirer relationship may be the part finance should investigate first.
The answer is not:
“Put the merchant in the same country as the customer.”
It is:
“Identify which merchant-side geographic identity actually changes the card-cost rule, then decide whether changing that identity produces enough net processing and performance benefit to justify the new structure.”
That is the difference between geographic optimization and geographic guesswork.
Legal, regulatory and commercial note
This article provides general information and does not constitute legal, regulatory, tax, accounting, financial or commercial advice. Merchants should verify current pricing, network rules, acquiring requirements, merchant-location definitions and regulatory treatment with qualified advisers, payment providers, acquirers, card networks, banks and relevant authorities.
I’m treating the new upload as Editorial Brief 6: How Merchant Location Affects Card Fees. Its core distinction is that “merchant location” is not one field: the article needs to separate legal entity, operating market, merchant of record, MID/merchant account, acquirer and settlement account, then identify which one actually matters under the relevant network/provider rule.
The strongest editorial distinction is that this article should not answer “Which country is the company in?” It should teach the reader to ask “Which merchant-side identity does this particular card-cost rule recognize?” That keeps it tightly differentiated from the broader cross-border cost and local-acquiring articles while remaining anchored to the cluster problem, PAYMENTS COST TOO MUCH.
How Merchant Location Affects Card Fees — Editorial Package
Current-state verification date: August 15, 2026
Editorial interpretation
Merchant cross-border cost problem: An international merchant says, “We are based in Country X,” but that statement can conceal several different payment identities. The company might be incorporated in one country, operate in another, sell through a different legal entity, hold a MID elsewhere, use an acquirer in another market and settle to a bank account in yet another jurisdiction.
Geographic classification: There is no safe universal “merchant country” field for all card-cost purposes. The relevant merchant-side geography depends on the network, regulatory rule, acquiring arrangement and fee being analyzed. The editorial brief explicitly requires merchant legal address, MID country, acquiring country, merchant-of-record location, customer-facing market and bank-account location to remain distinct.
Merchant location: Must be resolved attribute by attribute rather than inferred from headquarters, website domain or customer market.
Customer/card issuer location: A separate variable. It becomes useful only after the merchant-side geography is known.
Acquirer/provider location: A critical independent variable. Current Mastercard gateway documentation, for example, separately represents a merchant's acquirer merchant ID, the acquirer's country code and the merchant's address country rather than treating them as one field.
Primary cost owner: Depends on the layer that changes—issuer/acquirer interchange economics, network/scheme charges, acquiring pricing or PSP commercial pricing. These should not be collapsed into one generic “merchant-country fee.”
Unique evidence anchor: A merchant can sell to customers in one country while its legal entity, MID, acquirer and bank account sit in several others. Only some of those identities may determine card-cost classification.
Editorial position: Before declaring a payment inherently cross-border, map the merchant's actual legal and acquiring geography and identify which merchant-side location the relevant payment rule recognizes.
Common assumption challenged: “Our website serves Germany, so German customer transactions are domestic.”
Merchant decision: Determine which merchant-side identity is actually driving the transaction classification and cost, then decide whether changing that identity—through acquiring, MID, entity or merchant-of-record structure—creates enough net benefit to justify the operational complexity.
Selected format: Merchant geography identity map.
Structural rationale: Unlike the domestic-versus-cross-border article, this piece does not start from a fee waterfall. It starts from an identity problem: Where is this merchant, according to the part of the payment system that is pricing the transaction? Article 6 explicitly owns merchant-side geography rather than payer-side geography or the complete local-acquiring strategy.
Proposed architecture
Where is an international merchant actually located?
The website is not the merchant country
Legal entity
Operating market
Merchant of record
MID and merchant account
Acquirer country
Why provider headquarters is another separate variable
Settlement bank account: economically relevant, but not a safe card-location proxy
How networks and regulation can define merchant location
Merchant Location Cost Map
Worked merchant-structure scenarios
Multi-entity and multi-MID structures
How location changes the cost analysis
Local acquiring as a structural choice
Measurement by entity, MID and acquirer
Merchant decision framework
Final recommendation
Complete article
Original practical asset: Merchant Location Cost Map
Identity
Example question
Possible relevance
Verified value
Brand / website
Which market does the storefront target?
Customer-facing
Operating market
Where do we sell/service customers?
Commercial
Legal entity
Which company conducts the business?
Eligibility/legal
Merchant of record
Which entity owns the sale/payment relationship?
Commercial/acquiring
Merchant location
Which location is represented under the applicable payment rule?
Classification
MID / merchant account
Which acceptance identity processes the transaction?
Classification/reporting
Acquirer
Which acquiring institution handles it?
Classification/cost
Acquirer country
Which country applies to the acquirer under the rule?
Classification/cost
Settlement account
Where do proceeds arrive?
Treasury/settlement
Card issuer country
Where was the card issued?
Counterparty classification
Transaction currency
What currency is submitted?
Currency—not location proxy
Rule owner
Visa, Mastercard, regulation, PSP contract?
Verification
Merchant geography decision tree
Step 1
What cost are you investigating?
Interchange / network / acquiring / PSP / FX / settlement.
↓
Step 2
Which rule or contract defines that cost?
Network, regulation, acquirer or PSP.
↓
Step 3
Which merchant-side location does that rule use?
Legal entity?
Point of sale?
MID?
Acquirer?
Other?
↓
Step 4
What is the card/issuer geography?
↓
Step 5
What classification results?
Domestic / intra-regional / interregional / other.
↓
Step 6
Would a different merchant/acquiring structure change the cost?
No → do not restructure for this fee.
Yes → quantify eligible volume.
↓
Step 7
Does net benefit exceed operating complexity and performance risk?
Only then proceed to a local-acquiring or structural business case.
Measurement plan
Volume by MID
Successful processed card value by MID
Shows which merchant acceptance identities actually carry traffic.
Volume by acquirer
Successful processed value by acquirer
Useful where a merchant has multiple acquiring paths.
Cross-border share by MID
Transactions classified cross-border under verified rule
÷ relevant successful transactions for that MID
Do not define the numerator from customer country alone.
Effective processing rate by MID
Included processing fees
÷ successful processed card value
Keep FX/settlement outside unless deliberately scoped in.
Effective rate by MID × issuer geography
The primary diagnostic metric.
This can expose whether one merchant/acquiring setup generates systematically different economics for the same issuer geography.
Approval rate by merchant/acquiring setup
Track alongside cost where changing merchant location also changes acquiring route.
Cost per completed payment
Relevant payment cost
÷ completed payments
Use when authorization differences are significant.
Merchant-structure comparison template
Dimension
Current setup
Proposed setup
Selling entity
Merchant of record
Merchant location
MID
Acquirer
Acquirer country
Issuer corridor
Network classification
Effective processing rate
Approval rate
Settlement currency
Settlement account
Added operating cost
Net economic result
SEO metadata
H1: How Merchant Location Affects Card Fees: Why Your Entity and Acquiring Setup Matter
Meta description: Learn how legal entity, merchant location, MID, acquirer and merchant-of-record structure can affect card-payment geography and cross-border processing costs.
URL slug: /how-merchant-location-affects-card-fees
Secondary keywords: merchant country card fees; merchant location payment fees; merchant country cross-border fees; acquiring country fees; MID country card fees; international merchant card cost; merchant location processing cost.
Related entities: merchant ID, acquiring bank, merchant of record, card issuer, point of sale, local acquiring, cross-border acquiring, merchant entity, merchant account, interchange.
Article excerpt: A global merchant can operate in one country, incorporate in another, process through a MID elsewhere and settle into another bank account. Card cost depends on which merchant-side location the relevant network, regulatory or provider rule actually recognizes.
Suggested structured data: Article.
Internal-link plan
Article context
Suggested anchor
Target
Structural option after merchant map
local acquiring
Local Acquiring / How Local Acquiring Reduces Costs
Entity prerequisites
local entity requirements
Local Entity Requirements
Fee comparison after classification
domestic vs cross-border processing costs
Domestic vs Cross-Border Processing Costs
Payer-side counterpart
how customer/card location affects processing costs
Customer Location article
Deeper merchant funds structure
entity and settlement structure
Entity, Settlement & Cross-Border Funds
Fee attribution
international card fees
International Card Fees Explained
This article should remain merchant-side only. Customer/issuer geography enters merely as the counterparty needed to classify the corridor; payer-side analysis belongs to Article 7.
Authoritative source recommendations
Current Visa Core Rules / Visa Rules portal
Use Visa's current Rules and Policy portal as the controlling source for current Visa rules. Visa states that regional and country-specific rules apply to transactions, merchants, issuers and acquirers in their respective regions/countries and directs merchants to their acquirer for additional requirements.
Recheck the latest Core Rules immediately before publication.
Visa merchant-location guidance
Visa's “Providing the Proper Location of Your Merchant Business” is especially useful for explaining why:
ecommerce website location is not enough;
principal place of business can matter;
additional locations need substantive support;
merchant-location data must be consistent;
location affects fee/interchange assessment.
The document is dated 2019 and explicitly says current Visa Core Rules prevail if they differ. Cite it as explanatory guidance rather than proof that every detail remains unchanged in 2026.
Regulation (EU) 2015/751
Use the EU Interchange Fee Regulation where an EU-specific example is useful. It provides formal definitions for:
acquirer;
issuer;
domestic/cross-border transaction;
point of sale.
For ecommerce, the “point of sale” is tied to the merchant's fixed place of business rather than the website or server.
Do not extend this EU definition globally.
Mastercard official technical documentation
Mastercard gateway documentation is useful as implementation evidence that merchant and acquirer geography are independently represented: its data model carries an acquirer merchant ID, acquirer country code and merchant address information separately.
Do not use these API fields as a substitute for the actual Mastercard pricing/rule definition governing a transaction.
Use that only for the narrow capability statement.
Do not infer exact merchant-location classification, acquiring partner, country eligibility, pricing, savings or authorization uplift without internal verification.
Supporting visual
Merchant Location Cost Map
CUSTOMER-FACING
Brand / website
↓
Operating market
COMMERCIAL / LEGAL
Legal entity
↓
Merchant of record
CARD ACCEPTANCE
Merchant location
↓
MID / merchant account
↓
Acquirer + acquirer country
COUNTERPARTY
Card issuer country
→ Card geographic classification
→ Applicable card cost
SEPARATE FUNDS PATH
Transaction currency
↓
Settlement currency
↓
Settlement bank account
Main callout
The country visible to the customer is not necessarily the country that prices the card transaction.
Image alt text
Merchant Location Cost Map showing the differences between a merchant's website market, operating market, legal entity, merchant of record, MID, acquirer, settlement account and card issuer geography when determining card-payment costs.
Proposed author and reviewers
Primary reviewer: Acquiring specialist.
Architecture reviewer: Payments architect familiar with MID/entity/acquirer mappings.
Finance reviewer: International merchant finance or payments-pricing specialist.
Legal/regional reviewer: Qualified reviewer for entity and merchant-of-record statements where relevant.
Do not invent names or represent review as complete before it occurs.
Cross-border classification fact-check requirements
For each factual example verify:
Network: ______
Merchant entity: ______
Merchant location submitted/recognized: ______
MID: ______
Acquirer: ______
Acquirer country: ______
Issuer country: ______
Network region: ______
Card category: ______
Channel: ______
Currency: ______
Classification: ______
Rule/source: ______
Effective date: ______
Do not classify a transaction using only:
customer IP;
website country;
office location;
bank-account country;
provider headquarters.
Interchange/network fact-check requirements
If the final published article names any actual fee or rate, verify:
network;
fee name;
merchant/point-of-sale geography;
acquirer geography;
issuer geography;
card category;
transaction type;
regulatory scope;
currency condition where applicable;
effective date.
Do not publish a universal “merchant country interchange rate.”
Acquirer/provider fact-check requirements
Verify for every merchant structure discussed:
acquiring legal entity;
acquiring country;
MID owner;
merchant entity;
provider legal entity;
whether PSP and acquirer are the same party;
network registration/setup;
international-card pricing;
local-processing pricing;
fee pass-through;
settlement structure.
Do not infer the acquiring country from the PSP's brand or head office.
Merchant-location fact-check requirements
Confirm separately:
Legal
incorporation country;
relevant operating entity;
merchant-of-record role;
contracting entity.
Payment acceptance
merchant location under network/provider rule;
MID country;
acquirer;
acquirer country.
Commercial
customer-facing market;
product/service delivery market.
Funds
transaction currency;
settlement currency;
settlement bank country.
Each answer should remain in its own field.
Local-acquiring fact-check requirements
Where local acquiring is mentioned, verify:
merchant eligibility;
local entity requirement, if any;
local merchant location requirements;
MID availability;
acquirer;
network classification;
affected cost layers;
implementation;
compliance;
reporting;
settlement;
ongoing operational expense;
performance evidence.
Do not claim a new entity automatically produces domestic card economics.
Cost/performance fact-check requirements
For any proposed merchant-location change record:
Current route: ______
Proposed route: ______
Eligible volume: ______
Current effective rate: ______
Proposed rate: ______
Cost component actually changed: ______
Current approval rate: ______
Proposed approval rate: ______
Added fixed/operational cost: ______
Net annual impact: ______
Never call a gross fee reduction a net merchant saving without including added structure cost.
Regulatory fact-check requirements
Where EU law is used:
confirm the transaction is within the Regulation's scope;
distinguish acquirer from other processors;
use the Regulation's formal point-of-sale definition only for the relevant EU context;
confirm current amendments/status before publication;
do not extend the EU definition globally.
Where network rules are used:
use the current network edition;
identify region;
identify transaction type;
identify any specific merchant-location rule.
Amber-flag claims
“The merchant is located where it is incorporated.”
Too broad. Incorporation is one location field.
“The merchant is in Germany because the website is German.”
Unsupported.
“Our German office makes transactions domestic.”
Not without verifying the applicable merchant/acquiring location.
“MID country and acquirer country are the same.”
Do not assume.
“The PSP's headquarters is the acquiring country.”
Do not infer.
“Our settlement bank is in France, so we have French local acquiring.”
Incorrect as a general inference.
“Merchant of record always determines interchange geography.”
Do not generalize.
“Local currency means local acquiring.”
Incorrect.
“Local acquiring removes every cross-border fee.”
Unsupported.
“Adding a local entity lowers card fees.”
Requires proof that the new entity/acquiring setup changes the relevant pricing classification.
Current public material says selected markets, not universal availability.
Do not publish without approved merchant-specific evidence.
Before publication, internally verify:
exact current local-processing markets;
merchant eligibility;
acquiring entity/partner by market where publishable;
merchant-location requirements;
MID structure;
entity requirements;
merchant-of-record arrangements where relevant;
card-network registrations;
domestic/cross-border classification;
reporting of acquirer/MID;
issuer-country reporting;
pricing;
cross-border markup;
settlement geography;
settlement currency;
local bank-account requirements;
routing;
measured authorization performance;
approved cost evidence.
Do not turn the public Brick statement into a claim about:
specific merchant card classification
or:
specific cost savings
without merchant-specific verification.
Cluster sameness-audit fields
Field
How Merchant Location Affects Card Fees
Title
How Merchant Location Affects Card Fees: Why Your Entity and Acquiring Setup Matter
First two sentences
One global merchant has several geographic identities; which one prices the card?
Opening device
U.S. entity / French office / Dutch MID / German customer ambiguity
Geographic relationship
Merchant-side identities before issuer comparison
Merchant location
Variable to be decomposed
Customer/issuer location
Counterparty only
Acquirer location
Independent merchant-side field
Primary cost
Merchant-location-driven card processing differences
Primary format
Merchant geography identity map
Unique evidence anchor
One merchant can occupy several countries simultaneously in different payment roles
Editorial position
Map actual merchant/acquiring geography before calling a payment cross-border
Merchant decision
Identify which geographic identity actually changes a material cost
Original framework
Merchant Location Cost Map
Primary metric
Effective rate and cross-border share by MID/acquirer × issuer geography
Conclusion
Optimize the recognized payment geography, not the visible website geography
CTA
Build an entity/MID/acquirer map before restructuring
Closing element
Merchant geography decision tree
This avoids repeating the controlled $100 domestic-versus-cross-border waterfall from Article 2, the fee-stack analysis from Article 3, or the full local-acquiring business case from Article 5. Article 6 remains solely about merchant-side geography.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗