Do You Need a Local Entity to Accept Payments?
V2 - did not use the previous version as a base & rewrote the piece entirely fresh using the master prompt & editorial brief Do You Need a Local Entity to Accept Payments Internationally? A merchant prepares to launch in a new country. The commercial team assumes it needs to form
V2 - did not use the previous version as a base & rewrote the piece entirely fresh using the master prompt & editorial brief
Do You Need a Local Entity to Accept Payments Internationally?
A merchant prepares to launch in a new country.
The commercial team assumes it needs to form a local subsidiary.
Its payment provider says domestic acquiring may require a local company.
Finance wants settlement into a domestic bank account.
Legal has not yet determined whether selling the product creates a local licensing, tax, or establishment issue.
Everyone is discussing “the local entity.”
They may be discussing four different problems.
Before incorporation begins, the merchant should ask one question:
Who actually requires the local entity—and what are we trying to use it for?
That question often changes the expansion plan.
A company may be able to sell to customers in a country and accept their payments through an international payment provider without incorporating there.
It may also be able to charge customers in local currency without having a domestic entity.
But if it wants a particular domestic acquiring relationship, domestic merchant ID, bank account, local settlement arrangement, regulated licence, or operating presence, another requirement may appear.
Those distinctions matter because:
Selling into a country, accepting payments there, accessing local acquiring, receiving local settlement, and maintaining a local company are separate decisions.
One can trigger another.
One does not automatically imply another.
Start by separating five different questions
“Do we need a local entity?” is too broad to answer accurately.
Replace it with five narrower questions.
Can we sell to customers in the country?
This is primarily a market-access, consumer, tax, licensing, sanctions, product-regulation, and commercial question.
It is not automatically an acquiring question.
A foreign merchant may be permitted to sell into a jurisdiction without forming a subsidiary, while still having:
tax registration obligations
consumer-protection obligations
privacy obligations
customs requirements
licensing requirements
reporting responsibilities
The precise answer depends on the jurisdiction and activity.
Can customers there pay us?
This is the payment-access question.
A foreign merchant may be able to accept:
International cards
Cross-border card acquiring
Bank transfers
Wallets
Alternative payment methods
Payments through a Merchant of Record
without forming a separate company in every customer market.
Whether that is available depends on provider coverage and merchant eligibility.
Can we obtain domestic or local acquiring?
This is narrower.
A particular local acquiring structure may require:
Eligible merchant establishment
Domestic contracting entity
Local MID
Domestic bank account
local tax information
Specific merchant category
Provider or acquirer approval
Another provider or sponsored structure may have different requirements.
For a detailed explanation of acquiring mechanics, link to What Is Local Acquiring?
Can we receive settlement locally?
That introduces:
Bank-account eligibility
Settlement currency
Payout destination
Entity name
Treasury
Reserves
FX
Reconciliation
Local settlement can create an entity dependency even when accepting the customer payment did not.
Does the business itself need a local presence?
That can arise independently from payments because of:
Regulated business activity
Employment
Inventory
offices
Local licensing
Tax
Marketplace operations
Foreign-ownership rules
Banking
Long-term commercial strategy
These five questions should be answered separately.
Payment acceptance does not automatically equal establishment
A customer in Country A can buy from a merchant incorporated in Country B.
That is a basic feature of cross-border commerce.
The payment may be:
Customer
→ foreign-issued or domestic card
→ card network
→ international/acquiring provider
→ merchant's foreign entity
The merchant might present the purchase in:
Customer's local currency
Merchant's home currency
Another supported currency
It might later receive payout:
In its home country
In another supported banking jurisdiction
In a different currency
That does not establish whether the merchant has:
A local subsidiary
A local branch
A permanent establishment
A domestic acquiring relationship
A local bank account
Those require separate analysis.
Hypothetical example: foreign merchant accepting payments
A U.S. SaaS company begins selling subscriptions to customers in New Zealand.
Its PSP is willing to onboard the U.S. entity for New Zealand customer transactions.
Customers pay using supported cards.
The provider settles the merchant internationally.
In this hypothetical structure, payment acceptance itself has not created a New Zealand-incorporation requirement.
The merchant must still separately review:
Tax
Consumer law
privacy
Product-specific regulation
Merchant-category eligibility
The point is not that New Zealand never requires establishment.
The point is that the customer being in New Zealand does not, by itself, prove that incorporation is required for payment acceptance.
Who can create the local-entity requirement?
A useful investigation identifies the party imposing the constraint.
Law or government
National law may require a particular business activity to be carried out by:
Locally incorporated company
Branch
Licensed local operator
Registered foreign enterprise
Another specified entity form
If that applies to the merchant's activity, changing PSP will not necessarily solve it.
Financial regulator
A regulated activity may require:
Authorization
Registration
Local establishment
Local representative
Capital
Local management
Specific legal form
But regulation should not automatically be translated into “subsidiary required.”
Canada provides a useful illustration. The Bank of Canada explicitly states that foreign PSPs can fall within the Retail Payment Activities Act even when they have no place of business in Canada. Such PSPs may still have registration and Canadian agent/mandatary obligations. (Bank of Canada)
That is a PSP example, not a rule governing every merchant.
It nevertheless demonstrates that:
Being subject to local regulation and being required to incorporate locally are distinct questions.
Acquirer
A domestic acquirer may say:
“We only contract with qualifying domestic entities.”
That may be a real condition of the proposed acquiring product.
But the merchant should ask whether it comes from:
Law
Network rule
Acquirer underwriting
Settlement-bank requirement
Merchant-category policy
That determines whether another acquiring model could change the answer.
PSP
A PSP may have a simpler commercial rule:
“Our local acquiring product is available only to companies incorporated in that country.”
If the underlying jurisdiction does not impose the same universal rule, this is primarily a provider eligibility requirement.
Another PSP may operate differently.
Bank
The acquirer may accept the merchant.
But the settlement bank may require a local company before it will open:
A corporate account
Settlement account
Currency account
Reserve account
The entity dependency then comes from banking or treasury design.
Card network
Network rules can influence:
Merchant location
Acquiring relationships
Sponsored merchants
Transaction classification
Acceptance structures
Visa's current rules recognize payment facilitators and sponsored merchants, demonstrating that merchant card acceptance is not limited to one direct merchant-acquirer configuration. (Visa)
That does not mean every merchant in every country can bypass incorporation.
It means network architecture itself accommodates multiple merchant relationship models.
Tax
A merchant can have tax obligations without forming a subsidiary.
Likewise, forming a subsidiary does not automatically settle every tax issue.
Tax concepts such as permanent establishment follow their own legal definitions. Canada's tax guidance, for example, describes permanent establishment generally through a fixed place of business such as an office, branch, factory, workshop, or warehouse. (Canada)
So:
Incorporation and taxable presence are related but not equivalent concepts.
Legal requirement versus provider policy
This distinction should become standard operating procedure for international expansion teams.
Suppose the PSP says:
“You need a Brazilian company.”
The merchant should not put the statement into an executive deck as:
“Brazil requires foreign merchants to incorporate.”
Instead document:
“PSP A says its proposed Brazilian acquiring configuration requires an eligible Brazilian contracting entity. We have not yet established whether this is a statutory requirement, underlying-acquirer requirement, bank requirement, scheme rule, or PSP policy.”
That wording may seem overly precise.
It can prevent an unnecessary company formation.
Why provider rules differ
Two PSPs can have different requirements because they may use:
Different acquirers
Different licences
Different payment-facilitator models
Different settlement banks
Different entity structures
Different underwriting policies
Different merchant-category restrictions
Provider A saying “no” does not prove the market says “no.”
Local entity versus local acquiring
A local entity is a legal structure.
Local acquiring is a payment/acquiring structure.
They can overlap.
They are not the same thing.
Local entity
Answers:
Which legal person operates or contracts in the market?
Local acquiring
Answers:
Through which acquiring relationship are eligible card transactions submitted?
A merchant could hypothetically have:
Local company
local bank account
local tax registration
cross-border card acquiring
The existence of the company does not automatically make its card processing domestic.
The reverse can also occur under eligible sponsored or facilitated structures:
Foreign merchant entity
provider-sponsored domestic acquiring configuration
Whether such a model is available depends on the country, network, provider, acquirer, merchant category, and settlement arrangement.
That subject belongs in depth in Can You Access Local Acquiring Without Incorporating?
Local entity versus MID
A merchant ID is not a company.
A legal entity may hold or be associated with:
One MID
Several MIDs
Different MIDs by country
Different MIDs by acquirer
Different MIDs by business unit or channel
A MID may also be provisioned within a payment-facilitator or sponsored-merchant structure.
Therefore:
“We need a local MID” does not automatically answer “Do we need to incorporate?”
Ask instead:
Who provisions the MID?
Which merchant entity is associated with it?
Which acquirer sits behind it?
Does that acquirer require domestic establishment?
Can a sponsored structure use a different model?
Detailed MID mechanics belong in Domestic Merchant IDs Explained.
Local entity versus local bank account
A domestic bank account is also a separate dependency.
A merchant may want one for:
Acquirer settlement
PSP payout
Refund funding
Payroll
Supplier payments
Tax payments
Local expenses
Treasury
Reserves
A bank can impose its own eligibility requirements.
So:
Entity required for bank account
is not automatically the same as:
Entity required to accept customer payments.
Hypothetical example: settlement creates the dependency
An international software merchant can access a provider-sponsored local card route without forming a local company.
The PSP can pay the merchant internationally.
Finance instead wants all domestic card proceeds paid directly into a merchant-owned local-currency bank account.
The selected bank only opens that account type for domestic companies.
Now the dependency is:
Preferred domestic bank account
→ qualifying domestic company
The entity is necessary for that treasury configuration.
Another settlement model could potentially avoid it.
Detailed bank-account analysis belongs in Do You Need a Local Bank Account?
Local settlement versus local entity
These are related but not interchangeable.
A merchant may be locally acquired while:
Provider settles internationally
PSP converts currency before payout
Funds are delivered to a foreign bank account
A merchant may also receive a currency matching the customer transaction while using an international acquiring model.
Therefore, merchants should separately document:
Where transaction acquiring occurs
Where provider settlement occurs
Where merchant payout occurs
Payout country
Payout currency
Merchant bank
A useful payment map is:
Customer payment
→ acquiring
→ clearing
→ provider settlement
→ PSP balance
→ currency conversion, if any
→ merchant payout
→ merchant bank
A local entity may be needed at only one of those stages.
Merchant of Record versus merchant-owned local entity
A Merchant of Record model is not simply a shortcut around incorporation.
It changes the commercial structure.
Depending on the arrangement, the MoR may become the seller/payment merchant for defined transactions and may take responsibility for specified elements such as:
Payment acceptance
Tax
invoicing
Refunds
Chargebacks
Customer support
The contractual details matter.
By contrast, when a merchant creates its own local subsidiary:
That entity may itself become the contractual seller
The merchant group retains the operating structure directly
Local tax and corporate obligations remain within the merchant organization
Therefore:
MoR and local subsidiary are different business models, not two names for the same payment technique.
This article should mention MoR only as one alternative.
The detailed no-incorporation comparison belongs in How to Accept Payments Without Local Incorporation.
Five merchant scenarios
These scenarios make the distinctions concrete. They are deliberately hypothetical unless otherwise noted.
Scenario 1: foreign merchant accepts cross-border payments
A Canadian software company sells to customers in Singapore.
The PSP boards the Canadian entity.
Customers pay by international card.
The PSP settles into the merchant's Canadian account.
Payment conclusion
No local entity has been shown to be necessary for this payment model.
Still to verify
Singapore tax
Consumer obligations
Product regulation
PSP merchant eligibility
Output
Entity potentially unnecessary for payment acceptance.
Scenario 2: local acquirer requires domestic entity
A European retailer wants direct domestic acquiring in Market A.
Acquirer A requires the merchant agreement to be signed by an eligible company established in Market A.
Payment conclusion
The entity is required for Acquirer A's direct-acquiring model.
Still to verify
Whether the requirement is acquirer policy or legal
Whether another acquirer accepts foreign merchants
Whether sponsored domestic acquiring exists
Settlement implications
Output
Entity required for chosen model; market-wide requirement not yet established.
Scenario 3: PSP provides sponsored local access
A foreign digital merchant is eligible for a payment-facilitator structure through a PSP connected to a domestic acquirer.
Visa's current rules formally recognize payment facilitators and sponsored merchants, while BIS research describes sub-acquirers/payment facilitators as a route through which merchants can access card acceptance via an acquirer. (Visa)
Payment conclusion
A direct local entity may not be necessary under this hypothetical provider model.
Still to verify
Country eligibility
Merchant category
Merchant agreement
MID structure
Domestic transaction treatment
Settlement
Refunds
Chargebacks
Output
Alternative structure may remove payment-specific incorporation requirement.
Scenario 4: merchant establishes locally for broader business reasons
A marketplace enters Country B.
It plans to:
Hire 60 employees
Sign seller contracts
Lease an office
Operate local customer service
Maintain domestic treasury
Hold local operating cash
It also wants domestic acquiring.
Payment conclusion
Even if payment acceptance might technically be possible without incorporation, the business has broader reasons for establishing locally.
Output
Entity commercially/operationally justified beyond payments.
Scenario 5: regulated vertical changes the answer
A gaming or financial-services merchant wants to accept payments in Market C.
The underlying activity is regulated and requires an eligible licensed operator.
Payment conclusion
A PSP offering card acceptance does not remove the licensing question.
Output
Specialist legal/regulatory review; entity may be required independently of payment acceptance.
When acquiring changes the answer
Acquiring is often the point at which a merchant first encounters an entity requirement.
The merchant may begin with:
“We want higher authorization and domestic processing.”
The provider responds:
“Then you'll need a local entity.”
That answer should trigger four checks.
Check 1: Is direct acquiring actually necessary?
Could the merchant achieve the commercial objective through:
Cross-border acquiring
Payment-facilitator model
Sponsored acquiring
Global PSP local route
Merchant of Record
without direct domestic contracting?
Check 2: What measurable benefit is expected?
Possibilities include:
Domestic-card access
Lower payment cost
Better authorization
Better descriptors
Local settlement
Reduced FX
Local payment methods
None should be assumed.
Check 3: Does the entity itself create the benefit?
Often it does not.
The acquiring route may create the potential authorization or fee effect.
The entity may simply be an eligibility condition for obtaining the route.
That distinction matters when valuing the company formation.
Check 4: Is the benefit worth the operating burden?
That is the business-case question.
Do not justify incorporation using an untested authorization assumption
A common argument is:
“Local acquiring gets better approval, so we should incorporate.”
That is incomplete.
Local acquiring may improve authorization for some markets and merchant populations because the route can change characteristics including:
Acquirer
Transaction classification
Currency
authentication
Merchant information
Routing
Issuer familiarity
But the issuer still controls authorization.
Outcomes are also affected by:
Available balance or credit
Card type
Fraud rules
Customer profile
Transaction value
Authentication result
Merchant category
Retry strategy
So if an entity is being justified partly on authorization improvement, test the underlying acquiring configuration.
Authorization rate
Approved authorization attempts
÷ eligible authorization attempts
× 100
Compare matched cohorts by:
Country
Issuer
Card type
Currency
Order value
Authentication
Fraud strategy
Customer segment
Time period
If the proposed domestic route does not improve performance, the entity business case should not continue to include an assumed authorization uplift.
When banking changes the answer
Payment acceptance may work without a local entity.
Treasury may still decide it needs one.
Examples include:
Domestic settlement account
Local supplier payments
Payroll
Tax payments
Local refund funding
Working-capital needs
The correct sequence is:
What bank account do we need?
→ Why do we need it?
→ Who can open it?
→ Does the bank require a local entity?
→ Is another settlement structure acceptable?
Do not begin with:
“Local acquiring needs a local bank account.”
That may be true for one provider and false for another.
When regulation changes the answer
Some businesses have regulatory obligations that exist whether they use local or cross-border payments.
Potential examples include:
Gambling
Payment services
Stored value
Financial services
Consumer credit
Insurance
Marketplace funds movement
The merchant should ask:
Which entity actually performs the regulated activity?
For example, a marketplace that simply sells its own inventory presents a different regulatory profile from a platform that:
Collects buyer funds
Holds those funds
Deducts fees
Pays third-party sellers
Payment-provider technology does not determine the regulatory answer by itself.
When tax changes the answer
Tax registration does not automatically require incorporation.
Likewise, incorporation does not automatically define the entire tax treatment.
Permanent establishment illustrates why.
Canadian tax guidance defines permanent establishment in terms that generally focus on a fixed place of business and specified activities, while treaty rules can create additional tests. (Canada)
Different jurisdictions use different rules.
So the payment team should not say:
“No entity means no tax presence.”
Nor should it say:
“Tax registration means we need a subsidiary.”
Tax must be reviewed separately.
The Local Entity Requirement Tree
Use this framework before approving incorporation.
START
|
v
We want to accept customers in Country X
|
v
Does law or regulation require local establishment
for the underlying business activity?
|
|-- YES --> Identify required entity/branch/licence.
| Specialist review.
|
|-- NO / NOT ESTABLISHED
v
Does the chosen payment/acquiring model require
a domestic merchant entity?
|
|-- YES --> Who requires it?
| Law?
| Network?
| Acquirer?
| PSP?
|
|-- NO
v
Does the desired bank or settlement model
require a local entity?
|
|-- YES --> Is domestic settlement essential?
| Could international payout work?
|
|-- NO
v
Does tax or broader operating presence
independently justify or require an entity?
|
|-- YES --> Tax/legal/commercial review.
|
|-- NO
v
Could another payment model achieve the objective?
|
|-- Cross-border acquiring
|-- Sponsored acquiring
|-- Payment facilitation
|-- Global PSP local route
|-- Merchant of Record
|
v
Compare the economic value unlocked
with the full entity burden.
|
v
DECISION
Required documentation for every branch
Question
Evidence
Owner
Alternative
Decision consequence
Does law require establishment?
Statute/regulator guidance
Legal
Branch/registration/partner where permissible
Mandatory or specialist review
Does the activity require licence?
Regulator
Legal/compliance
Different business model
Mandatory or constrained
Does acquirer require entity?
Acquirer policy/contract
Payments
Alternative acquirer/provider
Model-specific
Does PSP require entity?
PSP onboarding policy
Payments
Alternative PSP
Provider-specific
Does settlement require entity?
Bank/PSP requirements
Treasury
International settlement
Treasury-specific
Does tax justify entity?
Qualified tax analysis
Tax
Foreign registration/other structure
Tax decision
Does another payment model work?
Provider evidence
Payments
Sponsored/MoR/cross-border
Entity may be avoidable
Is incorporation economic?
Approved financial model
Finance
Continue alternative structure
Capital allocation
Four possible outcomes
Outcome 1: entity likely required
Use this when reliable evidence shows:
The underlying activity requires eligible local establishment; or
The only acceptable payment/acquiring model requires it; or
The required settlement/banking arrangement makes it unavoidable; or
Broader operating requirements independently require the structure.
Outcome 2: entity required for chosen provider model
Use when:
PSP A requires it
Acquirer A requires it
but no broader market rule has yet been established.
The decision becomes:
Change entity structure or change provider structure?
Outcome 3: alternative payment structure may exist
Use when evidence indicates the merchant may be eligible for:
Cross-border acquiring
Sponsored acquiring
Payment facilitation
Provider-supported domestic acquiring
Merchant of Record
without the same direct local entity.
Do not interpret this as guaranteed eligibility.
Outcome 4: entity optional for payments but strategically justified
Use when the merchant is establishing:
Employees
Office
Inventory
Local suppliers
Local licences
Domestic treasury
Long-term commercial presence
and the entity has value beyond card acceptance.
The entity business case
Once the merchant knows that incorporation is not universally mandatory, it can evaluate whether it is still worth doing.
This article is not primarily a cost analysis, but at minimum the decision should include:
Entity setup cost
Incorporation
Legal
Tax review
registrations
Licensing
Banking setup
Acquirer onboarding
Systems work
Annual entity burden
Corporate filings
Accounting
Tax compliance
Local governance
Registered office where applicable
Audit where applicable
Bank fees
Legal/compliance
Treasury
Reconciliation
Additional payment operations
Value unlocked
Incremental payment volume
Lower total payment cost if demonstrated
Authorization improvement if demonstrated
Local payment methods
Local settlement
Reduced unnecessary FX
Better treasury matching
Local business capability
Operational control
Simple decision model
Annual value enabled by the entity
− annual incremental entity and payment-operating cost
Do not evaluate only interchange or PSP pricing.
Time to launch is part of the cost
The merchant should compare two timelines.
Entity-first route
Incorporation
→ tax/banking
→ provider underwriting
→ MID/acquiring
→ integration
→ launch
Foreign-merchant route
Where eligible:
Existing entity
→ PSP underwriting
→ cross-border or sponsored acquiring
→ integration
→ launch
→ validate market
→ revisit entity
Neither route is automatically faster.
Actual timing should be obtained from:
Legal advisers
Corporate-services providers
Banks
Acquirers
PSPs
Avoid generic promises such as “weeks instead of months.”
What evidence would disprove the need for incorporation?
This is an unusually useful question.
The hypothesis might be:
“We must form a local company to launch payments.”
Evidence against it could include:
Another eligible PSP can process the foreign merchant
Sponsored local acquiring is available
Cross-border acceptance performs adequately
The bank account is optional
Local settlement is not commercially required
No applicable business licence requires incorporation
Tax can be handled through another lawful registration model
The domestic acquiring benefit does not justify entity cost
If the merchant refuses to define what evidence could change the recommendation, incorporation has become an assumption rather than a decision.
What to verify before forming the company
Payments
Which payment methods require local establishment?
Who is the acquirer?
Is local acquiring actually required?
Is a domestic MID required?
Is a sponsored model available?
Are foreign merchants eligible?
Which merchant categories are allowed?
What does local acquiring change?
Banking and settlement
Is a domestic account required?
Who requires it?
Which settlement currencies are available?
Can the merchant receive international payout?
Does settlement location affect refunds?
Are reserves held locally?
Where does FX occur?
Legal and compliance
Does the underlying activity require local establishment?
Branch or subsidiary?
Local licence?
Foreign-ownership restrictions?
Local representative?
Consumer obligations?
Data rules?
Tax
Registration requirements
Permanent-establishment analysis
VAT/GST/sales tax
Withholding
Corporate-tax exposure
Transfer pricing
Intercompany arrangements
Business
Employees
Inventory
Local contracts
Office
Suppliers
Customer support
Long-term market commitment
Short decision-specific FAQ
Do I need a company in every country where customers pay me?
No universal payment rule requires that.
A merchant may be able to accept customers cross-border through an eligible PSP or acquiring model. Country-specific legal, tax, licensing, consumer, sanctions, and provider requirements still need to be checked.
Do I need a local company to use local acquiring?
Sometimes, but not universally.
The requirement may come from:
Acquirer
Provider
Network structure
Bank
Regulation
Merchant category
Sponsored-merchant structures recognized in card-network models demonstrate that direct local incorporation is not the only possible merchant-acquiring architecture. (Visa)
If a PSP says a local entity is required, does that mean the country requires one?
No.
Ask the PSP to identify whether the requirement comes from:
Law
Regulation
Acquirer
Card network
Settlement bank
PSP onboarding policy
Until established otherwise, a PSP onboarding rule should be described as a provider requirement.
Is a local bank account the same as a local entity?
No.
A bank may require a local entity for a particular account, but bank-account eligibility and incorporation are separate questions.
See Do You Need a Local Bank Account?
Does accepting local currency mean we have a local entity or local settlement?
No.
Presentment currency, processing currency, settlement currency, payout currency, and merchant entity are separate attributes.
See Multi-Currency Settlement Explained.
Can a merchant be subject to local regulation without incorporating?
In some frameworks, yes.
For example, Canada's retail-payment regime can apply to foreign PSPs with no Canadian place of business when they direct covered services at Canadian users. (Bank of Canada)
That does not determine an ordinary merchant's acquiring eligibility, but it demonstrates the legal distinction between local obligations and incorporation.
Final merchant recommendation
A local entity should not be the default first step in international payment acceptance.
Begin with the commercial goal:
What do we actually need the entity to enable?
Then trace the requirement.
If the chain is:
Regulated activity
→ eligible domestic operator required
then incorporation or another prescribed establishment may genuinely be necessary.
If the chain is:
Direct domestic acquirer
→ domestic contracting entity required
the requirement may apply to that acquiring model rather than all payment acceptance in the country.
If the chain is:
Domestic settlement account
→ bank requires domestic company
the issue is banking and treasury.
If the chain is:
PSP A local product
→ domestic companies only
another provider may change the answer.
If the chain is:
Customers live there
→ therefore we must incorporate
the merchant has not yet identified a requirement at all.
The decision discipline should be:
Create a local entity when a specific legal, regulatory, acquiring, banking, tax, licensing, or operating requirement makes one necessary—or when the measurable commercial value the entity unlocks justifies its full cost. Do not incorporate merely because accepting foreign customers has been mistaken for establishing locally.
Original practical asset: Local Entity Requirement Tree worksheet
The downloadable version should allow teams to turn a vague statement into an auditable decision.
Requirement
Source
Evidence
Responsible owner
Alternative available?
Entity consequence
Business activity
Legal
Business licence
Legal/compliance
Foreign ownership
Legal
Payment acceptance
Payments
Domestic acquiring
Payments
Domestic MID
Payments
PSP onboarding
Payments
Settlement
Treasury
Bank account
Treasury
Settlement currency
Treasury
Tax registration
Tax
Permanent establishment
Tax/legal
Customer contracting
Legal
Local employees
HR/legal
Local inventory
Operations/tax
Entity setup cost
Finance
N/A
Annual maintenance
Finance
N/A
Launch delay
PMO/operations
N/A
Acquiring benefit
Payments/finance
Settlement benefit
Treasury
Final decision
Cross-functional approval
Executive owner
Measurement plan
This should not become a payments-performance article, but merchants should capture enough evidence to test the entity business case.
Time to launch
Date production processing becomes available
− date entity/acquiring project begins
Measure separately for:
Incorporation
Bank-account opening
PSP onboarding
Acquirer onboarding
Technical implementation
Annual entity cost
Corporate administration
accounting and tax
legal/compliance
banking
attributable staffing
other recurring entity costs
Incremental payment value
Where a new local acquiring route is the reason for incorporation:
Incremental retained payment revenue
verified payment-cost savings
verified settlement/FX savings
Compare against matched pre-entity or alternative-route cohorts.
Settlement benefit
Possible measures include:
Settlement delay
FX cost
Reconciliation exceptions
Local-expense coverage
Working-capital effect
Decision indicator
Quantifiable annual value enabled by entity
− annual incremental entity and operating burden
No universal break-even threshold should be asserted.
Concise interpretation of the editorial brief
This article should become the conceptual entry point for the broader Entity, Settlement & Cross-Border Funds cluster.
Its purpose is not to teach incorporation, nor to explain every no-incorporation structure. It should answer a more basic merchant question:
Does accepting payments from customers in another country actually require a local company there?
The article's central insight is that several questions that merchants often collapse together are actually separate:
Can we sell into the country?
Can we accept payments from customers there?
Can we obtain local acquiring?
Can we obtain a domestic MID?
Can we receive local settlement?
Do we need a local bank account?
Do we need a local legal entity?
Those answers sometimes line up. They do not automatically do so.
The article should therefore work backward from the apparent entity requirement and ask who imposes it, for which activity, and whether an alternative payment structure changes the answer. This follows the supplied brief's decision-investigation structure.
Unique evidence anchor
A useful regulatory counterexample comes from Canada. The Bank of Canada states that a foreign payment service provider can fall within the Retail Payment Activities Act even if it does not have a place of business in Canada, provided it directs covered retail payment activities at Canadian end users. Foreign PSPs within scope must register and identify a Canadian agent or mandatary, but the framework does not make Canadian incorporation the universal condition for being regulated. (Bank of Canada)
That example concerns PSP regulation rather than ordinary merchant acquiring eligibility, but it demonstrates the principle this article needs:
A jurisdiction can impose obligations on a foreign business without necessarily requiring it to form a local subsidiary.
Visa's current rules also recognize sponsored-merchant/payment-facilitator structures in addition to direct merchant-acquirer relationships, while BIS research describes payment facilitators or sub-acquirers as mechanisms through which merchants can reach card acceptance through an acquirer. (Visa)
Together, those sources make it unsafe to treat “local company required” as a universal property of international payment acceptance.
Editorial position
Local incorporation should be an evidence-based operating decision, not the default first step in accepting foreign payments.
Common assumption challenged
“To accept payments from customers in a country, we need a company in that country.”
Sometimes a merchant will need one.
Sometimes the acquirer requires one.
Sometimes only the selected PSP requires one.
Sometimes the bank account creates the dependency.
Sometimes licensing or tax makes the entity necessary regardless of payments.
And sometimes the merchant can accept payments without incorporating at all.
Merchant decision supported
The article should enable a merchant to classify its situation as one of four outcomes:
Local entity likely required
Entity required only for the selected payment/acquiring model
Another payment structure may remove the payment-related requirement
Entity may be optional for payments but justified by tax, licensing, banking, or broader operations
Selected format
Decision investigation + Local Entity Requirement Tree
Structural rationale
Follow the dependency backward:
International sales goal
→ desired payment acceptance model
→ acquiring eligibility
→ MID
→ settlement
→ bank account
→ legal entity
→ tax / licensing / operational consequences
That prevents a merchant from forming a company to solve the wrong constraint.
Proposed architecture
“You need a local company.” Who says so?
Five separate questions hidden inside the entity question
Accepting foreign payments without local incorporation
When acquiring changes the answer
When a bank account or settlement changes the answer
When law, licensing, or tax changes the answer
Entity, MID, bank account, acquiring, and settlement: the distinctions
The Local Entity Requirement Tree
Five merchant scenarios
When incorporation is commercially justified even if not mandatory
What to verify before incorporating
Short jurisdiction-qualified FAQ
Final merchant recommendation
SEO metadata
Recommended SEO title
Do You Need a Local Entity to Accept Payments Internationally?
Alternative titles
Do You Need a Local Company to Accept Payments Abroad?
Local Entity Requirements for International Payment Processing
Can You Accept Payments Without a Local Entity?
When Does International Payment Acceptance Require Incorporation?
H1
Do You Need a Local Entity to Accept Payments Internationally?
Meta description
You do not always need a local company to accept foreign payments. Learn when law, acquiring, banking, settlement, tax, licensing, or provider policy can create an entity requirement.
URL slug
/do-you-need-a-local-entity-to-accept-payments
do you need a local entity to accept payments
Secondary keywords
local entity payment processing
local entity international payments
accept payments without local company
foreign merchant payment processing
local incorporation payments
local entity PSP requirement
international merchant entity requirements
local acquiring entity requirement
Article excerpt
Accepting payments from customers in another country does not automatically require forming a company there. This guide explains how to determine whether the real requirement comes from law, licensing, an acquirer, a PSP, a bank, settlement, tax, or the merchant's broader operating model.
Related entities
Legal entity
Subsidiary
Branch
Permanent establishment
Foreign merchant
Local acquiring
Cross-border acquiring
Merchant ID
Payment facilitator
Sponsored merchant
PSP
Acquirer
Merchant of Record
Settlement account
Local bank account
Settlement currency
Payout currency
Internal-link recommendations
This page should function as the entry point for the entire cluster.
Do You Need a Local Bank Account?
Use after the bank/settlement dependency section.
Suggested anchors:
local bank-account requirements
whether domestic settlement requires a local bank account
How to Accept Payments Without Local Incorporation
Use after introducing cross-border, sponsored, payment-facilitator, and MoR alternatives.
Suggested anchors:
accept payments without incorporating
no-incorporation payment models
What Is Local Acquiring?
Use the first time domestic acquiring is introduced.
Suggested anchors:
how local acquiring works
local acquiring structure
Can You Access Local Acquiring Without Incorporating?
Use specifically in the acquiring section.
Suggested anchors:
domestic acquiring without incorporation
sponsored local acquiring
Multi-Currency Settlement Explained
Use after explaining that customer currency does not determine settlement.
Suggested anchors:
multi-currency settlement
settlement currency versus customer currency
Later cluster links
How to Choose Settlement Currencies
How Cross-Border Settlement Works
Repatriating Revenue From Foreign Markets
These should appear deeper in the payment-to-treasury journey rather than being overloaded into the opening article.
Authoritative source recommendations
Prioritize sources in this order for publication:
Country government/company-law authorities for actual incorporation requirements.
Financial regulators and central banks for regulated-payment and establishment rules.
Tax authorities and treaties for tax registration and permanent-establishment questions.
Visa and Mastercard rules for acquiring/payment-facilitator structure.
Acquirer documentation for direct merchant eligibility.
Bank documentation for account-opening requirements.
PSP onboarding terms for provider-specific rules.
BIS for neutral payment-system architecture.
Current useful sources include the Bank of Canada materials demonstrating that its retail-payment regime can extend to foreign PSPs without Canadian incorporation. (Bank of Canada)
Visa's April 2026 rules are useful for sponsored-merchant/payment-facilitator structures. (Visa)
BIS research provides an institution-neutral explanation of payment facilitators/sub-acquirers. (Bank for International Settlements)
Canadian tax guidance provides a precise illustration of why permanent establishment should not be treated as synonymous with subsidiary formation. (Canada)
Supporting visual
“Do We Actually Need the Company?”
The primary graphic should be a vertical decision tree.
Starting point
We want to accept customers in Country X
Gate 1
Does the business activity legally require local establishment?
Yes → determine permitted entity/licence
No → continue
Gate 2
Does desired local acquiring require one?
Law/network requirement → validate
Acquirer/PSP requirement → test alternatives
No → continue
Gate 3
Does settlement or banking require one?
Yes → test local versus international settlement
No → continue
Gate 4
Does tax/operating presence independently justify one?
Yes → specialist review
No → continue
Gate 5
Can another payment structure achieve the objective?
Cross-border acquiring
Sponsored acquiring
Payment facilitation
Merchant of Record
Final outcomes
Entity required
Entity required for selected model
Alternative model possible
Entity optional but commercially justified
Specialist review required
Caption
“A local entity should solve an identified requirement—not an assumption about international payment acceptance.”
Alt text
“Decision tree showing whether an international merchant needs a local entity based on law, licensing, acquiring, PSP policy, banking, settlement, tax, and alternative payment structures.”
Proposed author and reviewers
These are recommended publication roles rather than claims that review has occurred.
Author:
Regional payments specialist:
Review cross-border merchant-access assumptions and acquiring examples.
Acquiring specialist:
Validate direct, sponsored and payment-facilitator terminology.
Legal/compliance reviewer:
Required for all country-specific entity and licensing claims.
Tax reviewer:
Required where permanent establishment or entity-tax implications appear.
Treasury reviewer:
Review bank-account, local-settlement, payout and currency dependencies.
Last-reviewed date:
Display prominently because payment-provider eligibility and entity requirements can change.
Financial fact-check items
Before publication verify any claims involving:
Entity setup cost
Annual entity cost
Local acquiring fee savings
Cross-border fee savings
FX reduction
Settlement savings
Reserve cost
Banking cost
Reconciliation burden
Authorization improvement
Launch delay
Do not use universal numbers.
If comparing entity/no-entity models, include:
Payment-provider cost
acquiring cost
settlement/FX cost
banking
entity administration
tax/accounting administration
attributable engineering and operations
Banking fact-check items
For each country example verify:
Does a domestic bank account exist as a requirement?
Who requires it?
Which account type?
Must the company be locally incorporated?
Can a branch open it?
Can a foreign company open it?
Is an international IBAN/account accepted?
Can a PSP settle internationally instead?
Which currencies are supported?
Can the account receive acquiring proceeds?
Can it fund refunds?
Are reserve accounts separate?
Never turn:
“Bank A requires a local subsidiary”
into:
“Country A requires a local subsidiary.”
Currency fact-check items
Where currency appears, verify:
Customer presentment currency
Authorization currency
Processing currency
Settlement currency
Payout currency
Merchant functional currency
FX conversion point
FX spread or fee
Provider auto-conversion
Local-balance availability
Refund currency
Chargeback currency
Do not imply:
Local currency → local entity.
Country-specific fact-check items
For every jurisdictional example verify:
Legal entity requirements
Foreign-company registration
Branch availability
Acquirer eligibility
PSP eligibility
Payment-facilitator availability
Merchant-category restrictions
Local bank requirements
Tax registration
Permanent establishment
Local licences
Foreign ownership
Consumer obligations
Data/privacy
Effective date
Country statements should always identify the activity being discussed.
Regulatory, legal, tax, and treasury fact-check items
Every “merchant must” statement should be attributable to:
Statute
Regulation
Regulator
Card-network rule
Acquirer rule
PSP requirement
Bank requirement
Tax rule
Contract
Treasury policy
Do not combine them.
This article provides general information and does not constitute legal, regulatory, tax, accounting, investment, or treasury advice. Merchants should confirm applicable obligations and financial arrangements with qualified advisers, banking partners, payment providers, and relevant authorities.
Amber-flag claims
Require additional review before publication if the draft claims that:
Country X requires every foreign merchant to incorporate.
Local acquiring always requires an entity.
Local acquiring never requires an entity.
A domestic MID requires incorporation.
A local bank account is legally required.
A PSP can always eliminate the entity requirement.
A Merchant of Record eliminates all tax obligations.
A payment facilitator always preserves domestic transaction treatment.
Local incorporation increases authorization.
Local incorporation lowers payment cost.
Local incorporation eliminates FX.
Tax registration is equivalent to incorporation.
Permanent establishment is equivalent to a subsidiary.
Payment acceptance proves market-entry legality.
Local settlement proves domestic acquiring.
Cross-border acquiring coverage
Local acquiring coverage
Merchant-category restrictions
Provider-sponsored acquiring structures
Payment facilitator structures, if any
MID structure
Domestic MID availability
Merchant of Record model
Current Terminal3 model and role
Countries where merchants can accept payments without local incorporation
Local bank-account requirements
Supported settlement countries
Settlement currencies
International payouts
Multi-currency balances
FX
Refund funding
reserves
Tax/invoicing responsibility under MoR
Chargeback responsibility
Approved merchant data
Approved customer examples
Do not repeat unverified claims such as:
“190+ markets without incorporation”
“local acquiring everywhere”
“all tax and licensing obligations sit with the MoR”
“domestic processing guarantees higher approval”
unless current internal documentation supports the exact claim and scope.
Provider-specific verification requirements
For every provider, ask:
Can our existing foreign entity be onboarded?
Which countries can it sell into?
Does provider support cross-border acquiring?
Does provider support domestic acquiring?
Does domestic acquiring require a local entity?
Who imposes that requirement?
Does provider use payment facilitation?
Are we a sponsored merchant?
Do we receive a dedicated MID?
Which entity is Merchant of Record?
Is a local bank account required?
Can settlement occur internationally?
Which currencies can be settled?
Which currencies can be paid out?
Who handles refunds?
Who handles chargebacks?
Can we migrate later to direct acquiring?
Can tokens/data be ported?
Which merchant categories are restricted?
Does the contract create additional entity requirements?
Cluster sameness-audit fields
Article: Do You Need a Local Entity to Accept Payments?
Cluster role: Conceptual entry point for entity → bank account → settlement → currency → repatriation.
Primary merchant decision: Whether incorporation is actually necessary before accepting payments in a foreign market.
Opening device: Commercial, payments, finance and legal teams each mean something different by “local entity.”
Unique evidence anchor: Selling, accepting payments, local acquiring, local settlement and legal establishment are separate questions.
Regulatory supporting example: Canada's RPAA can apply to foreign PSPs without requiring a Canadian place of business.
Editorial position: Incorporation should follow a verified requirement or justified business case, not assumptions about international payments.
Common assumption challenged: Customers in Country X imply a company is required in Country X.
Writer influence: Atul Gawande's dependency- and responsibility-oriented reasoning, without imitation.
Primary format: Decision investigation.
Structural logic: Market goal → payment access → acquiring → settlement → banking → entity → legal/tax consequences.
Original framework: Local Entity Requirement Tree.
Primary examples: Foreign cross-border merchant; local-acquirer entity requirement; sponsored acquiring; broader commercial establishment; regulated vertical.
Acquiring depth: High-level only; detailed local-acquiring mechanics handed to the Local Acquiring cluster.
Bank-account depth: Dependency only; Article 2 owns the topic.
No-incorporation depth: Alternatives introduced only; Article 3 owns full comparison.
Settlement depth: Relationship to entity only; Articles 4–6 own mechanics.
Repatriation depth: Mention only; Article 8 owns it.
Primary measurement: Time to launch, entity cost, onboarding time, validated acquiring benefit, settlement benefit and ongoing operating burden.
Final recommendation: Form the entity when a specific requirement or measurable business advantage justifies it—not merely because customers reside in another country.
v1
Do You Need a Local Entity to Accept Payments?
For most merchants, the first time this question comes up isn't planned — it's prompted by a customer in a new country, a spike in traffic from a market the business never specifically targeted, or a partner asking "are you registered here?" The instinct is to assume that accepting payment from a country means having a legal presence in it. Usually, that's not true. But usually isn't always, and the exceptions are the ones that create real risk if missed.
This article covers general patterns in how entity and registration requirements typically work. It isn't legal or tax advice — the specific answer depends on the country, the vertical, and the business model, and should be confirmed with legal and tax counsel before making a decision.
The default case: no entity required to simply accept payment
In most markets, a card network transaction from a customer to a merchant based elsewhere does not, by itself, require the merchant to be incorporated in the customer's country. Global card schemes are built to support exactly this kind of cross-border transaction, and the majority of e-commerce, SaaS, and digital goods businesses operate this way without incident — accepting payment from customers worldwide through a PSP or MoR, without a local entity anywhere the customer happens to be.
This is a distinct question from local acquiring, which is about improving approval rates by processing through a domestic bank rather than across a border. A merchant can access local acquiring — often through a Merchant of Record or payment partner — without incorporating locally at all. (See When Does a Merchant Need a Local Entity? for that angle specifically.)
What actually triggers an entity requirement
The exceptions tend to cluster around a small number of causes:
Tax presence, not payment acceptance — many countries require registration for VAT, GST, or a digital services tax once a merchant crosses a revenue or transaction threshold in that market, regardless of whether a card transaction technically "needed" an entity
Permanent establishment risk — sustained local staff, offices, or business activity (not just sales) can trigger a tax presence that then cascades into broader registration requirements
Regulated financial activity — holding customer funds, operating as a payment institution, or certain lending/BNPL-adjacent models often require local licensing tied to an entity
Data localization laws — some markets require customer payment data to be processed or stored within the country, which in practice requires a registered local business
Marketplace and payout obligations — paying local sellers or contractors directly, rather than processing customer-side payment alone, more often triggers local registration requirements
Industry-specific licensing — gaming, gambling-adjacent, and certain regulated verticals frequently require a local entity as a condition of operating at all, independent of payment volume
None of these are triggered by the payment transaction itself — they're triggered by what the business does around it: how much revenue it generates in-market, whether it holds a license-requiring activity, or whether it stores data locally.
Accepting payment vs. holding a local bank account
A related but separate question is whether a merchant needs a local bank account to receive settlement. In most PSP and MoR relationships, settlement can be paid out in the merchant's home currency to a home-market bank account, with currency conversion handled by the provider. A local bank account becomes more relevant when:
Settlement speed in-market matters more than consolidated global payouts
The business wants to hold a local currency balance rather than converting on every settlement cycle
Local regulation specifically requires in-country settlement for certain transaction types
(See Do You Need a Local Bank Account? and Multi-Currency Settlement Explained.)
How to think through this before it becomes a compliance problem
Rather than treating entity requirements as a single yes/no question, it's more useful to track a small number of signals per market:
Revenue or transaction volume against that country's tax registration thresholds
Whether the business model itself is regulated in that market (gaming, lending, marketplace payouts)
Whether local staff or offices exist, which raises permanent establishment questions independent of payments
Whether the product involves storing or processing data subject to localization rules
A market that's simply generating card transactions from customers rarely needs anything more than a payment partner. A market where volume is growing, the vertical is regulated, or the business is building a physical presence needs an actual legal and tax review — not a payments decision.
Title
Do You Need a Local Entity to Accept Payments?
Url
/expand/internationally/entities-banking-settlement/do-you-need-a-local-entity-to-accept-payments/
Pillar
Expanding Internationally
Cluster
E — Entities, banking and settlement
Selling to customers in a country and being legally required to have a business there are two different questions. Here's how to tell them apart.
Status
draft — canonical figures verified against current site copy; no unverified claims used
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗