When Does a Merchant Need a Local Entity?

Editorial review required. This material was imported from the project's research drafts. Provider-specific claims have been filtered, but factual accuracy, source attribution, original-use rights and current regulatory details must be reviewed before publication.

When Does a Merchant Need a Local Entity for Payment Acquiring? A payments team asks its provider a straightforward question: “Can we get domestic acquiring in this market?” The response is equally straightforward: “You'll need a local company.” That may be correct. But incorporation should not begin yet. The next question is: Why? Does national law require the merchant to incorporate? Does the local financial regulator require an entity for the activity the merchant performs? Does the card network require the merchant to be established in that market for the proposed configuration? Does the acquirer refuse to contract with foreign merchants? Does the PSP only support its domestic acquiring product through locally incorporated customers? Does settlement require a domestic bank account that the bank will open only for a local company? Or is the entity necessary for tax, licensing, employment, warehousing, or another commercial activity that would exist even if the merchant processed every card cross-border? Those explanations can lead to the same instruction— “Form a local company.” —but they describe very different problems. That distinction matters because a different PSP may solve a provider-policy constraint, while no change of payment provider will solve an actual statutory or licensing requirement. So the correct answer to “When does a merchant need a local entity?” is:

A merchant needs a local entity when the law, regulator, acquiring model, bank, settlement structure, tax position, licensing regime, or another required part of its operating model makes that entity necessary—and when no acceptable alternative structure removes that dependency. That answer is less convenient than a universal rule. It is also far more useful.

“Local entity required” is the beginning of the investigation A merchant evaluating domestic acquiring should classify every entity requirement before acting on it. There are at least eight possible sources. Requirement source What it could mean Can changing PSP/acquirer potentially change it? Law A statutory provision requires local establishment for an activity Usually not by itself Financial regulation A regulated activity requires authorization or an eligible local entity Usually not without changing the activity/model Card-network rule Scheme participation or merchant-location rules constrain the structure Sometimes, depending on model Acquirer policy Acquirer accepts only merchants with qualifying local establishment Potentially PSP policy Provider's product/onboarding model requires a local entity Often potentially Bank requirement Settlement account requires qualifying local customer/entity Potentially, depending on settlement model Tax structure Merchant operations create registration, filing, or establishment consequences Payment provider normally cannot remove the underlying tax issue Merchant-category/licensing rule The business itself needs local authorization or presence Usually independent of payment processing The first task is therefore not incorporation. It is requirement attribution.

Start with the activity the merchant actually wants “Operate locally” is too broad. Break the expansion plan into specific activities. A merchant may want to: * Sell goods into a country * Accept local cards * Obtain domestic acquiring * Receive a domestic MID * Receive settlement in local currency * Hold a local bank account * Employ staff * Rent an office * Store inventory * Operate a marketplace * Collect money for third parties * Pay sellers * Provide regulated gaming * Offer financial services * Issue stored value * Sign local consumer contracts * Invoice local businesses A local entity may be required for one and unnecessary for another. For example: Selling to local customers does not automatically prove that the merchant must incorporate locally. Likewise: Wanting a local settlement account does not prove that national law requires incorporation to accept customer payments. And: Forming a subsidiary does not guarantee that the merchant has obtained domestic acquiring. These are separate decisions.

Requirement source 1: the acquirer For direct acquiring, the acquirer is one of the first places to investigate. Visa's April 2026 rules state that an acquirer must have a merchant agreement with each of its merchants, while a payment facilitator must maintain merchant agreements with its sponsored merchants. Visa also requires those relationships to comply with applicable law and Visa rules. (Visa) That tells us there must be an eligible merchant relationship. It does not, by itself, establish one global rule that every merchant must incorporate in the acquiring country. The acquirer may impose its own underwriting conditions concerning: * Merchant establishment * Contracting entity * Business address * Bank account * tax registration * Directors or beneficial owners * Merchant category * Operating history * Transaction volume * Currency * Settlement * Geographic sales activity Those conditions must be checked against the specific acquirer and market. Clearly labeled acquiring-policy example Illustrative example—not a statement about all acquirers in the named market: Suppose an international SaaS merchant wants direct domestic acquiring in Japan. Acquirer A tells the merchant: “Our direct merchant-acquiring product is available only to a Japanese contracting entity with an eligible domestic settlement account.” The relevant fact is not: “Japan requires all foreign SaaS companies to incorporate.” The relevant fact is: Acquirer A's proposed direct-acquiring model requires that contracting structure.

The merchant should now investigate: 1. Is Acquirer A's requirement based on law, scheme rules, banking rules, or its own underwriting policy? 2. Does another Japanese acquirer support a different structure? 3. Can a payment facilitator or global PSP provide domestic acquiring access? 4. Would changing structures affect the MID, transaction classification, settlement, pricing, or control? Only then does the entity decision become clear.

Requirement source 2: the PSP Providers often bundle multiple requirements into one onboarding answer. A PSP may say: “We require a local company.” That can mean: * Its domestic-acquiring product is configured only for local entities. * Its sponsor acquirer requires one. * Its settlement partner requires one. * Its risk policy permits only domestic merchants. * Its legal contracting model does not support foreign merchants. * Its product was never built for another structure. Those are not laws. They are properties of the provider's operating model. This creates one of the most important distinctions in the entire local-acquiring cluster: Provider capability is not the same as market eligibility. A merchant that is ineligible for Provider A's local route may be eligible under Provider B's structure. That does not mean either provider is wrong. Their acquiring models can simply differ.

Requirement source 3: card-network and sponsored-merchant structure The card networks recognize different ways merchants can connect into acquiring. Visa's current rules distinguish direct merchant relationships from payment-facilitator and sponsored-merchant structures. An acquirer contracting with a payment facilitator must register that facilitator, and the model includes identifiers for both the facilitator and sponsored merchant. (Visa) The BIS similarly describes payment facilitators or sub-acquirers as entities that give merchants card acceptance without the sub-acquirer having its own direct network connection; the sub-acquirer reaches the card network through an acquirer. (Bank for International Settlements) That matters because the choice is not always binary: Foreign merchant or Locally incorporated merchant with direct acquirer There can be intermediate structures. But this article should not turn that observation into: “You can always access local acquiring without incorporating.” You cannot assume that. Sponsored structures remain subject to: * Network rules * Acquirer approval * Market availability * PSP configuration * Merchant category * Risk * transaction volume * Settlement * Merchant location * Applicable law The detailed alternatives belong in Can You Access Local Acquiring Without Incorporating? The lesson here is narrower:

Before treating incorporation as unavoidable, determine whether the requirement belongs to direct acquiring or to all eligible acquiring structures in that market.

Requirement source 4: the MID Merchants frequently hear: “You need a local entity to get a local MID.” That statement also needs to be decomposed. A merchant ID (MID) identifies the merchant within an acquiring or acceptance configuration. It is not the same thing as the legal entity itself. A merchant can have: * One legal entity and several MIDs * Different MIDs for different acquirers * Different configurations by country * Different channel or business-unit MIDs * MIDs provisioned through a payment facilitator or PSP structure The precise design varies by provider and acquirer. So the merchant should ask: Who will issue or sponsor the MID, which entity will be associated with it, and why does that party require a domestic entity? The answer may expose an acquiring-policy requirement rather than a statutory one. For the deeper MID architecture, this article should link to Domestic Merchant IDs Explained rather than recreating that article.

An entity and a MID solve different problems This distinction deserves to be explicit. Legal entity Answers: Which legal person is conducting the relevant business activity and signing the contract? It affects areas such as: * Contracting * Liability * Tax * Licensing * Employment * Ownership * Banking * Corporate governance MID Answers: Which merchant configuration identifies the transaction within the acquiring system? It can affect: * Routing * Merchant identification * Reporting * Descriptor configuration * Merchant category * Settlement configuration * Acquirer relationship * Reconciliation A company can form an entity and still lack the MID or acquiring route it wanted. Conversely, a provider may support an eligible sponsored merchant without requiring the merchant to hold precisely the same direct MID structure used by a directly acquired local merchant.

Requirement source 5: the settlement bank account Sometimes the payment discussion produces an entity requirement indirectly. The merchant wants: Domestic acquiring * local-currency settlement * direct payout into a domestic account The acquirer may support the first two. The bank may create the third constraint. Suppose the settlement bank will open the required business account only for an eligible locally established company. The dependency becomes: Local settlement account → qualifying bank customer → domestic entity The local entity is therefore being required because of the chosen banking and settlement configuration. That does not prove the acquiring relationship itself could never exist without it. Clearly labeled settlement example Illustrative example: A merchant is eligible for Provider X's sponsored domestic card route. Provider X can pay the merchant internationally in EUR. The merchant instead requests direct domestic settlement in Country B's currency to an account under the merchant's own name. The proposed settlement bank requires a local incorporated company for that account type. The merchant now has two operating models: Model A Sponsored domestic acquiring → provider settlement infrastructure → international merchant payout Model B Domestic acquiring → merchant-owned domestic settlement account → locally incorporated entity required by the bank The payment requirement did not change. The treasury choice did.

That distinction can materially change whether incorporation is economically justified.

Entity versus bank account These concepts also should not be collapsed. A local entity does not automatically mean: * The bank will open the account * The account supports the necessary currencies * The acquirer will accept it * The settlement account can receive card proceeds * Cross-border payouts are permitted * FX is avoided And a local bank account is not always identical to incorporation. Eligibility depends on the bank, jurisdiction, account type, corporate structure, KYC/KYB standards, and business model. Ask: Is the entity needed to acquire, or is it needed to open the settlement account we selected?

Requirement source 6: regulation The merchant also needs to distinguish being regulated in a country from having to incorporate there. Canada provides a current example. The Bank of Canada states that the Retail Payment Activities Act can apply to foreign PSPs that do not have a Canadian place of business but direct retail-payment services at Canadian individuals or entities. A foreign PSP without a Canadian place of business must identify a Canadian agent or mandatary for notices and orders. (Bank of Canada) That is a legal obligation. It is not the same legal obligation as: “Create a Canadian subsidiary.” The example is about PSP regulation rather than ordinary merchant card acceptance, so it should not be used to infer Canadian acquiring eligibility for a particular merchant. It demonstrates the broader analytical point: Regulatory presence requirements can take forms other than local incorporation. Payment teams should therefore ask counsel: * Which activity is regulated? * Which entity performs it? * Is registration sufficient? * Is licensing required? * Is a branch sufficient? * Is a local representative required? * Is incorporation required? * Does the merchant perform the activity, or does its PSP/acquirer? That final question matters especially for: * Marketplaces * Payment facilitation * Seller payouts * Stored value * Money transmission * Financial services * Gambling * Other regulated verticals

Requirement source 7: business or merchant-category licensing For some merchants, the entity problem exists even before acquiring is discussed. Examples can include regulated activities such as: * Gambling * Financial services * Insurance * Certain credit products * Stored-value products * Regulated marketplace activity The exact rules are jurisdiction-specific. Suppose a country's gambling regulator requires the licensed operator serving residents to be a specified form of domestic entity. In that situation, finding a PSP willing to process a foreign company may not solve the merchant's broader legal problem. The business itself needs the permitted operating structure. This is why the sequence matters: Do not ask only, “Can PSP X board our foreign company?” Also ask: “Is that company legally allowed to conduct the underlying activity in the market?”

Payment access and market access are different questions A merchant can sometimes technically accept a customer's card before it has completed every step needed for a long-term local operating presence. That does not prove the merchant's broader market structure is correct. Likewise, a merchant can have: * Local employees * Tax registrations * Local inventory * A domestic subsidiary without having local acquiring. Payment access asks: Can this entity accept the payment through this model? Market access asks: Can this business lawfully and commercially perform all of the activities required to sell and operate in the jurisdiction? The answers can diverge.

Requirement source 8: tax Tax can make the entity discussion particularly confusing because incorporation and taxable presence are not the same concept. For example, the Canada Revenue Agency describes a permanent establishment as generally involving a fixed place of business such as an office, branch, factory, warehouse, or similar location. (Canada) Canada's tax treaty with the United States also explicitly notes that control of a company in one country by a company in the other does not, by itself, make one company a permanent establishment of the other. (Canada) The important conceptual distinction is: Local incorporated entity A separate legal person formed under the jurisdiction's company law. Permanent establishment A tax concept whose precise definition depends on domestic law and applicable tax treaties. A foreign company might create a taxable presence without incorporating a subsidiary. A company might also incorporate a subsidiary for reasons unrelated to acquiring. Therefore: Do not make an acquiring architecture decision and assume the tax answer follows automatically. Tax review needs to consider the actual business footprint: * Employees * Offices * Warehousing * Contracting * Agents * services * customer location * Digital-services rules * Inventory * Marketplace activity * Intercompany arrangements This article should not provide tax-structuring advice.

|-- NO --> Incorporation may be optional for payments | v 5. Compare economics | |-- Expected incremental retained value | versus | setup + annual + banking + compliance + operations | v DECISION Possible outputs Entity likely required Use when: * The required business or payment activity legally requires it * No acceptable alternative structure exists * The chosen direct acquiring model requires it and alternative routes are unsuitable * Banking/settlement requirements make it unavoidable for the desired operating model Entity required only for the chosen provider model Use when: * PSP or Acquirer A requires it * But the requirement is not established as a general jurisdictional rule * Another eligible structure may exist Alternative structure may exist Use when: * Payment facilitator * Sponsored merchant * Aggregated acquiring * Global PSP * Merchant of Record could potentially remove the direct-incorporation requirement. This is an investigation result, not proof that the merchant qualifies. Specialist review required Use when: * Tax * licensing * regulated activity * foreign ownership * funds flow * marketplace operation * banking * permanent establishment cannot be separated cleanly from the acquiring decision.

Five scenarios that look similar but are not Scenario 1: acquirer requires the domestic contracting entity Illustrative provider-policy example Merchant wants a direct domestic MID. The acquirer will contract only with an eligible domestic company. Result: The entity is required for that direct acquiring model. Next question: Is that the only acceptable acquiring model?

Scenario 2: the PSP requires the company, but the jurisdiction may not Illustrative provider-policy example PSP A's local-acquiring product only supports companies registered in the target market. No legal authority has yet been identified as imposing the same incorporation requirement. Result: Treat this initially as a PSP eligibility requirement, not as a statement of national law. Compare other providers before incorporating solely for the payment setup.

Scenario 3: settlement creates the entity dependency Illustrative treasury example The merchant can use a sponsored domestic acquiring route. But its preferred structure requires settlement to a merchant-owned domestic bank account. The bank only offers the relevant account to eligible domestic companies. Result: Entity dependency originates in banking/settlement, even though the acquiring route itself may support another structure.

Scenario 4: sponsored acquiring avoids direct incorporation Visa's payment-facilitator model demonstrates that card acceptance can involve an acquirer, payment facilitator and sponsored merchant rather than requiring every merchant to maintain an identical direct relationship with the network/acquirer. (Visa) BIS research similarly describes sub-acquirers/payment facilitators as providing merchants access to card acceptance through an acquirer. (Bank for International Settlements) Result: A different merchant-acquiring structure can sometimes change the contracting requirements. But availability must be verified for the actual country, merchant category and provider.

Scenario 5: payment processing is not the deciding factor at all Illustrative regulated-business example A gaming business discovers that its desired local operating licence requires an eligible domestic licensee. A global PSP could technically provide cross-border card acceptance. Result: The payments architecture does not remove the underlying business-licensing issue. A local entity may still be necessary even though accepting a card itself did not create the requirement.

Local entity versus Merchant of Record These are fundamentally different operating models. Local entity The merchant typically remains: * Customer seller * Contracting party * Operator * Merchant responsible for its own tax and commercial obligations subject to the exact setup The entity may contract directly or indirectly with acquiring providers. Merchant of Record Under an MoR structure, another entity can become the seller/payment merchant for defined transactions and assume contractual responsibilities specified in the arrangement. Depending on the model, these can include: * Payment acceptance * Tax * Invoicing * Refunds * Chargebacks * Customer support But Merchant of Record is not simply a technique for borrowing another company's MID. It changes the commercial and legal structure of the customer transaction. The exact allocation must be confirmed contractually. This distinction is important enough that the detailed operating model should live in a separate MoR article rather than being compressed into the local-entity discussion.

Local entity versus sponsored acquiring A sponsored merchant arrangement is also not automatically a Merchant of Record model. In Visa's payment-facilitator framework, the payment facilitator and sponsored merchant remain separately recognized participants, and merchant agreements and identifiers are required under the network structure. (Visa) Therefore: Payment facilitator ≠ Merchant of Record. Sponsored merchant ≠ aggregated merchant with no merchant identity. Domestic acquiring access ≠ transfer of seller-of-record responsibility. The precise contract determines the relationship.

Local entity versus permanent establishment These deserve separate legal and tax analysis. A company may: * Have a subsidiary * Have a branch * Have a permanent establishment * Be tax registered * Have none of those in different combinations depending on jurisdiction and facts. CRA's permanent-establishment guidance illustrates that PE analysis focuses on business presence and activity, not simply whether a subsidiary was incorporated. (Canada) Do not let a payments team use these statements interchangeably: “We need a local MID.” “Therefore we have a permanent establishment.” or: “We do not need a subsidiary.” “Therefore we have no local tax exposure.” Neither conclusion follows automatically.

When forming the entity may still be the right decision The article's recommendation is not “avoid local entities.” A local company can make considerable sense when it supports the broader business. Examples include situations where the merchant is: * Hiring employees * Operating offices * Warehousing inventory * Signing significant local B2B contracts * Obtaining local licences * Maintaining domestic bank relationships * Managing substantial local expenses * Building a long-term national business * Seeking direct acquiring control * Requiring local treasury infrastructure In those circumstances, the entity may serve many purposes at once. The payment decision then becomes: Given that we already have—or need—the local entity, does direct domestic acquiring now produce enough additional value to adopt it? That's different from: “We should incorporate because our PSP said local cards approve better.”

Volume by itself does not create an entity requirement One of the main problems with the previous draft is the suggestion that sustained high volume makes the entity “genuinely necessary.” High volume can make incorporation economically attractive. It does not by itself create a legal requirement. A merchant processing $100 million in a country through an eligible sponsored structure does not automatically become legally required to incorporate merely because the volume crossed an arbitrary threshold. What volume changes is the business case. At sufficient scale: * Direct acquiring economics may become attractive * Provider markups may matter more * Authorization improvements may create more value * Local treasury may become useful * Direct bank relationships may become worthwhile * Operational control may justify the overhead That is a capital allocation decision, not a universal entity rule.

The entity business case Once the requirement investigation is complete, compare the economics. Do not ask only: “How much does incorporation cost?” Ask: What is the annual incremental value of the operating model the entity unlocks? Potential value * Lower total payment cost * Improved authorization, if demonstrated * Domestic-card access * Better settlement * Lower FX * Improved treasury * Direct provider relationships * Local payment methods * Better operational control Incremental entity cost Include: Setup * Incorporation * Legal review * Tax structuring * registrations * Banking setup * Licensing * Provider onboarding Recurring * Corporate filings * Accounting * Tax preparation * Audit where required * Registered office * Directors or local governance where applicable * Banking * Legal/compliance * Entity management * Payroll/HR if applicable Payment operations * Additional PSP/acquirer contract * MID management * Settlement reconciliation * reserves * Treasury * Chargebacks * Finance systems * Support * Engineering Do not assume direct acquiring is cheaper until these costs are included.

A simple entity-investment model Annual incremental acquiring value Incremental retained revenue from improved payment performance * verified payment-cost savings * verified FX/settlement savings * measurable operational value minus Additional acquiring/provider operating cost Then compare that value with: Annual entity burden Annual legal and corporate administration * accounting and tax * banking and treasury * licensing/compliance * local staffing attributable to the structure * payment operations * amortized setup cost Decision indicator Entity-enabled annual value − entity-related annual burden This is not a universal incorporation formula. It is a way to stop the acquiring team from evaluating only basis-point savings while finance absorbs every other expense.

Authorization gains should be proven, not assumed The previous version opens by calling local acquiring one of the more reliable ways to improve approval rates. That is too strong without comparable evidence. Local acquiring may improve authorization for some merchant populations because it can change: * Transaction classification * Acquirer * Routing * Currency * Merchant descriptors * Authentication context * Issuer familiarity * Data quality But authorization still depends heavily on: * Issuer decisioning * Available funds or credit * Fraud * Card type * Authentication * Merchant category * Customer behavior * Transaction amount * Retry policy So when an entity is being justified partly through authorization gains, require a matched comparison. Authorization rate Approved authorization attempts ÷ eligible authorization attempts × 100 Compare like-for-like: * Same country * Same issuers * Same card type * Same currency * Similar transaction values * Same authentication strategy * Same fraud settings * Same customer mix * Same time period If the purported local route produces no meaningful gain, do not continue valuing the entity using an assumed uplift.

Measure total payment economics, not just interchange Likewise, do not justify incorporation solely because someone expects “domestic interchange.” Visa explicitly notes that merchants negotiate and pay a merchant discount to their financial institution rather than paying interchange as an isolated merchant bill. (Visa) Relevant economics may include: * Interchange * Scheme assessments * Cross-border assessments * Acquirer markup * PSP markup * Authorization fees * Processing fees * Refund fees * Chargebacks * FX * Settlement * Bank costs * reserves * Integration * Reconciliation The detailed calculation belongs in How Local Acquiring Reduces Payment Costs. For this article, the key principle is: Do not form a company to save one visible fee while ignoring the cost of running the company.

Time to launch matters too An entity can make economic sense eventually and still be the wrong initial operating model. Compare: Route A: incorporate first Company formation → banking → tax registrations → acquiring underwriting → MID setup → integration → launch Route B: eligible sponsored/cross-border structure first Provider underwriting → acquiring configuration → integration → launch → prove demand → revisit direct entity/acquiring model The second route is not automatically available or better. But where it is available, the merchant can treat incorporation as an optimization decision rather than a market-entry prerequisite. The choice should be evaluated using actual provider onboarding estimates rather than generic claims such as “weeks versus months.”

The merchant should ask these questions before approving incorporation Start with the provider “You said we need a local entity. Who imposes that requirement?” Then ask: 1. Is the requirement based on law? 2. Which law or regulatory rule? 3. Is it a card-network requirement? 4. Which network rule and which merchant model? 5. Is it the acquirer's underwriting policy? 6. Is it your PSP policy? 7. Is the entity required to obtain the MID? 8. Is it required only for the settlement account? 9. Is a local bank account required separately? 10. Can a foreign merchant use another acquiring structure? 11. Can a payment facilitator sponsor the merchant? 12. Would that produce the same domestic transaction treatment? 13. Who would contract with the acquirer? 14. Who would hold or sponsor the MID? 15. Who would settle the funds? 16. Which currency would be paid out? 17. Would another structure change fees? 18. Would another structure change refund or dispute ownership? 19. What merchant categories are eligible? 20. Which parts of the requirement are contractual rather than regulatory? Then take the answers to: * Legal * Tax * Treasury * Finance * Payments before approving the company formation.

The four-owner entity decision Entity formation should not be owned by payments alone. Payments owner Validates: * Acquiring requirement * MID * Route * Network * Eligibility * Authorization hypothesis * Cost hypothesis Legal/compliance owner Validates: * Corporate requirement * Licensing * Regulatory perimeter * Merchant category * Contracts * Consumer obligations * Foreign ownership Tax owner Validates: * Registration * Corporate-tax implications * Permanent establishment * Transfer pricing * VAT/GST/sales tax * Withholding * Intercompany structure Treasury/finance owner Validates: * Bank account * Settlement * Currency * FX * repatriation * reserves * liquidity * Reconciliation * Entity cost A decision becomes credible only when the same entity structure works across all four.

When should a merchant probably not incorporate just for payments? An entity deserves further scrutiny when: * The merchant is only testing demand. * Payment volume is small relative to operating cost. * The only identified requirement comes from one PSP. * Another eligible acquiring model exists. * Local acquiring has not demonstrated an authorization or cost benefit. * Domestic settlement is unnecessary. * The merchant has no broader local operations. * Entity maintenance would materially exceed the likely payment benefit. * The market may be exited quickly. * Internal legal, tax, finance and compliance teams are not prepared to operate another entity. None of these proves incorporation is wrong. They indicate that the merchant should demand a clearer business case.

When may a local entity be justified or unavoidable? A stronger case exists when: * The intended business activity legally requires a qualifying entity. * A licence needed to serve the market requires one. * The only acceptable acquiring model requires one. * The required domestic bank/settlement arrangement requires one. * Foreign ownership or operating rules dictate the structure. * The company is establishing substantial long-term operations anyway. * Direct acquiring creates a demonstrated economic or performance benefit large enough to cover entity costs. * The merchant needs operational control unavailable through sponsored models. The key difference is evidence.

What an alternative acquiring model can—and cannot—solve A different acquiring model can potentially change: * Direct versus sponsored merchant relationship * Need for a direct acquirer contract * MID configuration * Settlement path * Provider relationship * Onboarding burden It cannot automatically eliminate: * Business licensing * Tax exposure * Consumer rules * Data requirements * Employment obligations * Product regulation * Marketplace regulation * Foreign-exchange controls This is why Can You Access Local Acquiring Without Incorporating? should be a separate article. That article answers: Which alternative acquiring structures exist? This article answers: Why was an entity required in the first place?

Jurisdiction-qualified FAQ Does local acquiring always require a local entity? No universal rule supports that statement. Eligibility depends on the jurisdiction, acquirer, provider model, network requirements, merchant category, settlement arrangement and other factors. Payment-facilitator structures recognized by Visa and described by BIS demonstrate that merchants can sometimes access card acceptance through sponsored relationships rather than identical direct-acquirer arrangements. (Visa)

If my PSP says I need a local entity, is that a legal requirement? Not necessarily. Ask the PSP to identify the source of the requirement. It may come from: * Law * Regulation * Network rules * Acquirer policy * PSP policy * Banking * settlement * Merchant-category underwriting Do not present a provider policy as national law without verification.

Do I need a local entity to get a domestic MID? Sometimes, depending on the acquirer and acquiring model. The correct questions are: * Who issues or sponsors the MID? * Which entity is associated with it? * Which acquirer is involved? * What requirement makes the domestic entity necessary? The detailed mechanics belong in Domestic Merchant IDs Explained.

Do I need a local bank account if I have a local entity? Not automatically. Bank eligibility and acquiring settlement requirements must be reviewed separately. Likewise, having a domestic bank account does not itself prove domestic acquiring.

Can a foreign company be regulated without incorporating locally? Yes, in some jurisdictions and regulatory frameworks. For example, Canada's RPAA can apply to foreign PSPs without a Canadian place of business when they direct covered services at Canadian users; those PSPs must meet the applicable registration obligations and appoint a Canadian agent or mandatary. (Bank of Canada) That is a PSP example rather than merchant acquiring guidance, but it demonstrates why regulatory obligation and incorporation requirement are separate concepts.

Is permanent establishment the same as local incorporation? No. Permanent establishment is a tax concept governed by applicable domestic law and treaties. CRA guidance, for example, describes PE in terms of a fixed place of business and related activity rather than treating incorporation as the definition. (Canada) Tax counsel should assess the merchant's actual facts.

Should high payment volume trigger incorporation? High volume can make a direct local structure economically attractive. It does not itself create a universal legal requirement. The decision should compare verified incremental benefits with the complete entity and operating cost.

Final merchant recommendation Do not start with: “Do we need to form a company?” Start with: “What exactly are we trying to unlock, and who says an entity is required to unlock it?” Then trace the dependency. If the chain is: Law or licence → qualifying domestic operator required the entity may be unavoidable. If the chain is: Direct Acquirer A → Acquirer A requires domestic contracting entity the requirement may belong to that acquiring model. If it is: Domestic settlement account → bank requires domestic company the requirement may be treasury-driven. If it is: PSP A product → local entities only another provider or sponsored structure may change the answer. And if the chain is: Local entity → projected cost savings and authorization uplift without validated data, the merchant does not yet have an entity requirement. It has a hypothesis. The correct decision is therefore: Create a local entity when the required market activity or chosen operating model genuinely requires one, or when the measurable commercial value it unlocks exceeds the full financial and operational cost of maintaining it. Do not incorporate solely because “local acquiring requires a local entity” has been repeated without identifying who imposes that requirement and why.

Original practical asset: Local Entity Requirement Tree For the published article, turn the framework into a downloadable or interactive worksheet. Question Finding Evidence Owner Outcome What activity requires local presence?

Statute/provider/acquirer contract Legal + Payments

Who imposes the requirement?

Named source Legal

Is it law or regulation?

Primary authority Legal

Is it network-related?

Current network rule Payments

Is it acquirer policy?

Written acquirer requirement Payments

Is it PSP policy?

Provider onboarding terms Payments

Is the entity required for the MID?

Acquirer confirmation Payments

Is the dependency actually the bank account?

Bank eligibility Treasury

Is local settlement required?

Treasury model Treasury

Does another acquiring model remove the dependency?

Alternative provider evidence Payments

Does a licence independently require the entity?

Regulator guidance Legal

Does tax create separate obligations?

Tax analysis Tax

Expected annual payment value unlocked

Matched performance data Finance

Entity setup cost

Approved budget Finance

Annual entity cost

Approved budget Finance

Expected launch delay

Project plan Operations

Final decision

Cross-functional approval Executive owner

This framework is materially different from the Local Acquiring Component Map used in What Is Local Acquiring?: that article decomposes the acquiring architecture; this one traces the source and necessity of the entity dependency.

Editorial-brief interpretation The previous draft has the right instinct—a local entity is not always required—but it makes the answer depend too quickly on merchant volume and implies that traditional local acquiring “normally requires” incorporation, a local bank account, and tax registration. Those conditions can occur together, but they are not a universal definition of domestic acquiring. The stronger article should investigate the requirement rather than generalize it. The article owns this question: When someone tells a merchant, “You need a local entity for local acquiring,” who exactly requires that entity—and why? The answer may come from the acquirer, a PSP's commercial model, a bank, regulation, licensing, network rules, tax structure, settlement requirements, or the merchant's own operating choices. Those are materially different constraints. The uploaded editorial brief correctly makes that distinction the article's intellectual anchor and assigns this article the entity-requirement question rather than the broader no-incorporation alternatives question. Unique evidence anchor The strongest evidence is that payment rules and legal obligations can attach to entities without requiring the same type of local incorporation.

Visa's April 2026 rules require an acquirer to have a merchant agreement with its merchants, while a payment facilitator must have one with each sponsored merchant. The same rules explicitly recognize sponsored-merchant structures rather than requiring every merchant to maintain an identical direct-acquirer relationship. (Visa) Canada provides an especially useful regulatory counterexample. The Bank of Canada states that the Retail Payment Activities Act can apply to foreign PSPs that have no place of business in Canada but direct services at Canadian individuals or entities. Such foreign PSPs need a Canadian agent or mandatary for notices, but the regulatory framework does not turn that requirement into a blanket rule that every covered PSP must incorporate a Canadian subsidiary. (Bank of Canada) That is exactly the distinction merchants need to learn: A legal obligation in a market is not necessarily an incorporation obligation. Editorial position Do not incorporate merely because a PSP says local presence is required. Trace the requirement to its source, determine which activity it applies to, and test whether a different acquiring structure changes the requirement. Common assumption challenged “Local acquiring always requires local incorporation.” It does not. But the opposite claim—“you never need a local entity because a global PSP can handle it”—is equally unsafe. Merchant decision supported The merchant should leave knowing whether the entity is:

* Actually required for the intended acquiring model * Required only by the selected provider/acquirer * Needed for banking or settlement rather than acquiring * Needed independently for licensing, tax, employment, inventory, or another operating reason * Potentially avoidable through another acquiring structure * Economically justified even when technically avoidable Selected format Entity-requirement investigation + decision tree Structural rationale Instead of beginning with a generalized list of situations where merchants “usually need” entities, trace the requirement backward: Desired acquiring model → acquirer eligibility → merchant agreement/MID → settlement → bank account → entity → regulatory and tax consequences That prevents a merchant from solving the wrong problem.

SEO package Recommended SEO title When Does a Merchant Need a Local Entity for Payment Acquiring? Alternative titles 1. Do You Need a Local Entity for Local Acquiring? 2. Local Entity Requirements for Payment Processing Explained 3. When Is Local Incorporation Required for Domestic Acquiring? 4. Local Acquiring and Local Entities: What Merchants Need to Know H1 When Does a Merchant Need a Local Entity for Payment Acquiring? Meta description A local entity is not always required for local acquiring. Learn how to identify whether the requirement comes from law, an acquirer, PSP, bank, settlement model, tax, or licensing. URL /expand/internationally/local-acquiring/when-does-a-merchant-need-a-local-entity/ Primary keyword when does a merchant need a local entity Secondary keywords * local entity for payment processing * local entity local acquiring * incorporate for local acquiring * local company payment processing * domestic acquiring entity requirement * local merchant entity * local bank account acquiring * international merchant local entity Article excerpt When a PSP says local acquiring requires a local company, don't begin incorporation until you know why. The requirement may come from law, regulation, the acquirer, the PSP, a settlement bank, licensing, or tax—and those constraints require different solutions. Related entities * Merchant acquirer * Payment facilitator * Sponsored merchant * Merchant ID * MID * Merchant account * Merchant establishment * PSP * Settlement account * Local bank account

* Permanent establishment * Merchant of Record * Card network * Domestic acquiring * Cross-border acquiring * Visa * Tax registration

Internal-link recommendations Use the article to route readers into deeper cluster ownership. Can You Access Local Acquiring Without Incorporating? Anchor: “alternative acquiring structures” / “local acquiring without a local entity” Domestic Merchant IDs Explained Anchor: “domestic MID” / “how MIDs relate to merchant entities” Local Acquirers by Country Anchor: “country-specific acquiring eligibility” Local Settlement vs International Settlement Anchor: “local bank account and settlement requirements” What Is Local Acquiring? Anchor: “how local acquiring actually works” How Local Acquiring Reduces Payment Costs Anchor: “whether direct domestic acquiring justifies entity costs” Benefits of Local Card Processing Anchor: “potential commercial benefits of domestic processing” The article should not heavily link to generic “Merchant of Record vs PSP” content until that page is confirmed as part of the site architecture.

Authoritative external-source recommendations Primary references for the published article should include: * Visa Core Rules and Visa Product and Service Rules for merchant agreements, payment facilitators and sponsored merchants. (Visa) * Visa's public rules hub for country- and regional-specific network requirements. (Visa) * BIS work on sub-acquirers/payment facilitators for neutral structural explanation. (Bank for International Settlements) * Bank of Canada RPAA materials as an example of a regulatory framework applying to foreign PSPs without requiring a Canadian place of business. (Bank of Canada) * Bank of Canada acquiring scenarios illustrating that the legal treatment of acquiring/payment activities depends on the functions actually performed. (Bank of Canada) * Relevant jurisdiction's company registry, financial regulator and central bank whenever a country-specific entity requirement is asserted. * Relevant tax authority and treaty documentation for permanent-establishment or tax-presence statements. Avoid relying on competitor PSP blogs to explain these requirements.

Supporting visual “Who Actually Requires the Local Entity?” The primary image should be a decision tree rather than an acquiring-chain diagram. Opening node Provider says: “Local entity required.” Branches Law / regulator → identify exact regulated activity → local company, branch, registration, representative, licence? Card network → identify scheme rule → direct merchant or sponsored structure? Acquirer → law or underwriting policy? → alternative acquirer? PSP → provider product limitation? → different provider/model? Bank → entity needed for domestic settlement account? → international payout alternative? Tax / operating model → would obligation exist without local acquiring? Final outputs * Entity required * Entity required for selected model only * Alternative acquiring structure possible * Specialist review needed Alt text “Decision tree for determining whether a merchant needs a local entity for payment acquiring by tracing requirements to law, regulator, card network, acquirer, PSP, bank, tax, or settlement.”

Proposed author and reviewers These are publication roles to fill, not claims that review has already occurred.

Required acquiring reviewer: Validate acquirer eligibility, MID, payment-facilitator and sponsored-merchant descriptions. Required legal/compliance reviewer: Validate every country/entity/licensing claim. Required tax reviewer: Review permanent establishment, tax-registration and entity-tax distinctions. Required treasury reviewer: Validate bank-account, settlement and payout dependencies. Recommended payment architect: Confirm that acquiring, settlement and provider responsibilities remain technically separated. Last reviewed: Add a publication date because entity, network and provider requirements can change.

Acquiring fact-check items Before publication, verify: 1. Current Visa merchant-agreement rules. 2. Current Visa payment-facilitator rules. 3. Sponsored-merchant identifiers and responsibilities. 4. Mastercard equivalent structures if Mastercard examples are added. 5. Which acquiring arrangements actually require direct merchant contracting. 6. MID/entity relationships in every factual example. 7. Which requirements come from acquirer underwriting. 8. Which requirements come from card-network rules. 9. Which local routes are available to foreign merchants. 10. Which merchant categories are excluded. 11. Whether local acquiring produces domestic transaction treatment in each stated example. 12. Direct versus sponsored settlement structure.

Cost fact-check items Do not use the previous draft's implicit assumption that direct local entities eventually produce better economics without calculating: * Entity setup * Annual corporate administration * Legal * Accounting * Tax * Audit * Local banking * Licensing * Acquirer fees * PSP fees * Network fees * Cross-border assessments * FX * reserves * Reconciliation * Treasury * Engineering * Operations Any payment-cost savings should use comparable transaction populations.

Country-specific fact-check items Whenever a country is named as a factual example, verify: * Entity type * Acquirer eligibility * Foreign merchant rules * Foreign ownership * Domestic banking * MID requirements * Merchant-category restrictions * Network rules * Settlement * Tax registration * Licensing * Branch alternatives * Payment facilitator availability * Effective date Do not convert one acquirer's rule into a statement about the whole country.

Entity and regulatory fact-check items For every “required” claim, record: Claim Requirement source Local entity Law / regulator / network / acquirer / PSP / bank / tax / merchant model Local directors Exact jurisdictional or provider source Local address Exact source Bank account Bank/acquirer/provider source Tax number Tax/acquirer/provider source Minimum capital Company/licensing source Licence Regulator Local operating presence Exact source Ownership limits Company/sector law Permanent establishment Tax law/treaty analysis This article provides general information and does not constitute legal, regulatory, tax, or accounting advice. Merchants should confirm applicable obligations and operating requirements with qualified advisers, acquiring partners, and relevant authorities.

Amber-flag claims requiring specialist review Review carefully before publishing any statement that: * A particular country requires local incorporation. * A local MID requires incorporation. * A bank account requires incorporation. * A particular PSP can eliminate entity requirements. * Sponsored acquiring qualifies as domestic acquiring. * A local entity produces domestic interchange. * A local entity improves authorization. * A local entity reduces fees. * A local entity eliminates FX. * A Merchant of Record assumes all tax obligations. * A provider-sponsored model transfers merchant-of-record status. * One entity structure works for every merchant category. * High payment volume creates a legal incorporation requirement.

Specifically verify: * Terminal3's current legal/product definition * Whether Terminal3 is the Merchant of Record in the relevant transaction structures * Which countries/markets the product can actually serve * Whether “190+ markets” remains the approved figure * Whether those markets all involve local acquiring * Whether merchants avoid incorporation in each supported market

* Which local acquirer is used by market * Sponsored/acquiring model * MID structure * Merchant-of-record status * Tax responsibility * Licensing responsibility * Settlement * currencies * Refunds * Chargebacks * Merchant-category restrictions * Country exclusions

* Approved evidence of authorization improvement * Approved evidence of cost improvement In particular, remove or substantiate this previous-draft concept: “Merchants get the approval-rate benefits of a domestic processing relationship.” Local acquiring can potentially improve authorization, but the benefit cannot be assumed from architecture alone. Likewise, do not say that all “entity, licensing, and tax obligations sit with the MoR” without contractual and jurisdictional verification.

Provider-specific verification requirements For every PSP or acquirer under consideration, ask separately whether: * Foreign merchants are eligible * A local entity is required * Requirement comes from PSP or underlying acquirer * Domestic MID is offered * Dedicated MID is offered * Payment-facilitator structure is used * Merchant is a sponsored merchant * Merchant remains Merchant of Record * Domestic transaction treatment applies * Local bank account is required * International payout is allowed * Local settlement is available * Merchant categories are restricted * Tokens are portable * Merchant data is portable * Acquiring relationship is portable * Direct contracting becomes available above a threshold Do not accept “local acquiring supported” as the answer to these questions.

Cluster sameness-audit fields * Article: When Does a Merchant Need a Local Entity? * Primary question owned: Who requires the entity, for what activity and under which acquiring model? * Opening: PSP says, “You need a local company”; merchant asks why before incorporating. * Unique evidence anchor: Requirement-source attribution. * Editorial position: Never incorporate solely because a provider labels local presence necessary. * Common assumption challenged: Local acquiring always requires local incorporation. * Writer influence: Atul Gawande's dependency-oriented systems reasoning, without stylistic imitation. * Primary format: Entity-requirement investigation and decision tree. * Structural logic: Acquiring goal → eligibility → MID → settlement → bank → entity → legal/tax consequences. * Main original framework: Local Entity Requirement Tree. * Main real-world regulatory counterexample: Canada's RPAA can regulate foreign PSPs without requiring a Canadian place of business, demonstrating that regulatory obligation and incorporation are distinct. * Primary acquiring example: Direct-acquirer policy versus sponsored-merchant alternative. * Primary merchant decision: Determine whether incorporation is mandatory, model-specific, optional, or economically justified. * Entity depth: Full ownership. * No-incorporation depth: Introductory only; Article 6 owns alternatives. * MID depth: Dependency only; Article 7 owns mechanics.

* Cost depth: Entity business-case calculation only; Article 4 owns detailed acquiring costs. * Settlement depth: Bank/entity dependency only; Article 9 owns settlement economics. * Authorization position: An economic hypothesis requiring matched testing—not justification by assumption. * Primary metrics: Annual market revenue, payment volume, validated payment savings, validated authorization gain, entity setup cost, annual entity cost, banking/treasury cost, operating cost, and launch time. * Conclusion: Form the entity when a required activity genuinely demands it or when the measurable value it unlocks exceeds its full cost—not because “local acquiring requires incorporation” was stated without identifying the source.

v1 When Does a Merchant Need a Local Entity? Local acquiring — processing a transaction through a bank in the customer's own country rather than routing it across a border — is one of the more reliable ways to improve approval rates in a new market. The question that follows is almost always the same: does getting it means setting up a local legal entity? Sometimes, yes. Often, no. The answer depends less on the market itself and more on which route into that market a merchant takes. This article covers general patterns in how local acquiring access is typically structured. It isn't legal or tax advice — entity, licensing, and registration requirements vary by country and by business model, and a specific expansion decision should be reviewed with legal and tax counsel. What local acquiring normally requires In its most direct form, local acquiring is tied to a domestic merchant ID, which is in turn typically tied to: * A registered local legal entity * A local bank account for settlement * Local tax registration * Compliance with that market's licensing and KYB requirements This is the traditional path, and it's the one that gives a merchant the most direct control — but it's also the most expensive and slowest to stand up, particularly in markets with unfamiliar incorporation or banking requirements. (See What Is Local Acquiring? and Domestic Merchant IDs Explained.) When a local entity genuinely becomes necessary

A local entity tends to become a real requirement rather than an option in a few recurring situations: * Sustained high volume in a single market, where the interchange and approval-rate benefits of a direct local merchant ID outweigh the setup cost * Regulated verticals — gaming, financial services, certain marketplace models — where local licensing is tied directly to having a registered local business * Markets with data residency or local banking laws that require in-country incorporation as a precondition for processing customer payment data at all * Long-term strategic presence, where the merchant is building out local operations, hiring, or holding inventory in the market anyway, and a payments entity is a natural extension of that * Card scheme or network rules specific to that market that require a domestic acquiring relationship tied to a local business Outside of these situations, incorporation is usually a choice made for control and economics, not a hard requirement to accept local payments at all. What lets a merchant get local acquiring without incorporating Several structures exist specifically to give merchants local acquiring benefits without the entity requirement: * Merchant of Record (MoR) models, where a partner already holding local entities and licenses processes on the merchant's behalf * Payment aggregation, where multiple merchants transact under a shared local merchant ID held by the provider

* Partner-of-record arrangements with a PSP that maintains its own local acquiring relationships across markets These routes trade some direct control and margin for a much faster path to market — a merchant can typically go live in a new country in weeks rather than the months or longer that direct local incorporation and licensing usually takes. (See Can You Access Local Acquiring Without Incorporating? and Merchant of Record vs. PSP.) The trade-off, plainly stated Neither path is categorically better — they optimize for different things: * Direct local entity: more control over economics and merchant-of-record status, but higher upfront cost, longer timelines, and ongoing local compliance obligations that persist for as long as the entity exists * MoR or aggregated acquiring: faster market entry and lower setup burden, but the merchant operates within the partner's compliance framework and local acquiring relationships rather than owning them directly Merchants entering a large number of markets at once, or testing demand before committing to a market, are far more likely to lean on an MoR or partner structure. Merchants with concentrated, high-volume presence in a specific country are more likely to eventually justify a direct entity there. Questions worth asking before deciding * What transaction volume in this market would justify the cost and timeline of direct incorporation? * Is this a market being tested, or one the business is already committed to for the long term?

* Does the vertical carry licensing requirements that force the entity question regardless of volume? * How much operational and compliance overhead can the business realistically take on in-market? * Is the priority speed to market, or long-term control of acquiring economics?

For merchants with a clear, sustained volume commitment to a specific market, a direct local entity may still be the better long-term structure — but it's a decision made from a position of already generating revenue there, not a prerequisite to start.

Internal links to build once corresponding pages are live: What Is Local Acquiring? · Domestic Merchant IDs Explained · Can You Access Local Acquiring Without Incorporating? · Merchant of Record vs. PSP · Do You Need a Local Entity to Accept Payments? · Do You Need a Local Bank Account? Figures used: 190+ markets — per current canonical figures. No unverified merchant-count or user-count claims used in this draft. Title When Does a Merchant Need a Local Entity? Url /expand/internationally/local-acquiring/when-does-a-merchant-need-a-local-entity/ Pillar Expanding Internationally Cluster D — Local acquiring Meta_description Local acquiring usually means better approval rates. It doesn't always mean incorporating in every market you sell into — here's when it does. Status draft — canonical figures verified against current site copy; no unverified claims used

Not sure which payment solution fits?

Use the merchant matching prototype to understand the types of providers to evaluate.

Explore matching ↗