Can You Access Local Acquiring Without Incorporating?

Can Merchants Access Local Acquiring Without Incorporating Locally? Three merchants want domestic card acquiring in the same foreign market. Merchant A incorporates a local company, opens a bank account, contracts directly with a domestic acquirer, and receives its own acquiring configuration. Merchant B does not incorporate. Instead, its global payment provider connects eligible transactions to a local acquiring relationship already maintained in that market. Merchant C does not contract directly with the domestic acquirer either. It becomes a sponsored merchant under a payment facilitator that contracts with the acquirer and submits transactions on the merchant’s behalf. All three may eventually reach local cardholders through domestic acquiring infrastructure. But they have not built the same payment system. They differ in who: * Contracts with the acquirer * Controls the merchant relationship * Assigns or sponsors merchant identifiers * Performs underwriting * Holds reserves * submits transactions * receives settlement * sets commercial terms * manages disputes * controls routing * owns or controls reusable credentials * can move the merchant to another acquirer That distinction answers the central question. Can you get local acquiring without incorporating? Sometimes, yes. A merchant does not necessarily need to hold the direct acquiring contract itself for its transactions to be processed through a provider-supported domestic acquiring arrangement.

Card-network rules explicitly recognize sponsored-merchant and payment-facilitator structures in which an intermediary works with an acquirer and provides payment acceptance to merchants that do not hold a conventional direct acquiring relationship. Visa describes its payment-facilitator model as a way to extend electronic acceptance to sellers without a traditional acquiring relationship; Mastercard similarly provides for Sponsored Merchant Agreements entered into by a payment facilitator on behalf of and as an agent of its acquirer. But that does not mean: No local company = automatically domestic acquiring. Nor does it mean: Payment facilitator = local merchant. Card-network merchant-location rules still matter. Visa’s April 2026 Merchant Data Standards, for example, require genuine business activity for a claimed card-not-present merchant location and explicitly state that a post-office box, payment function, server, URL, director, or investor alone is insufficient. Mastercard likewise requires the disclosed Sponsored Merchant location to correspond to business activity and transaction data. So local acquiring without incorporation is not a loophole in which the provider makes the merchant “local.” It is an alternative allocation of acquiring relationships and responsibilities. The important question becomes: What exactly has the provider localized—and who controls it?

Acquiring access is not acquiring ownership This distinction explains most of the confusion around local acquiring without a local entity. A merchant may gain access to: * A domestic acquirer * domestic transaction routing * a local card-processing configuration * local currency * potentially domestic pricing treatment * country-specific card coverage * local settlement options without itself owning or controlling every layer. The provider may instead control: * The underlying acquirer contract * Payment Facilitator registration * MID provisioning * domestic processing configuration * settlement account * reserve * reporting interface * routing * pricing * merchant migration That can be a very attractive trade at the beginning of a market expansion. It can become much less attractive once the country represents a significant percentage of the merchant’s revenue. The key is to understand which arrangement the merchant is actually buying.

First, identify who holds the acquiring relationship The phrase PSP local acquiring is not technically specific enough. “PSP” is a broad commercial term. A payment provider might be acting as: * Gateway * Processor * Acquirer * Payment facilitator * Merchant aggregator * Marketplace payment provider * Orchestrator * Merchant of Record * A combination of several of these roles The fact that a provider gives a merchant one API does not tell you who holds the acquiring relationship underneath. A card-network Payment Facilitator, by contrast, is a specific operating role. Visa’s framework allows a payment facilitator to sign a merchant-acceptance contract with a sponsored merchant on behalf of an acquirer and, depending on the arrangement, receive and distribute settlement proceeds. Visa requires payment-facilitator and sponsored-merchant identifiers in transaction processing. Mastercard’s June 2026 rules similarly state that a payment facilitator can enter into a Sponsored Merchant Agreement for the purpose of facilitating the acquirer’s acquisition of the sponsored merchant’s transactions. The agreement must make clear that the payment facilitator acts on behalf of and as an agent of the acquirer. That produces three separate relationships: Acquirer → Payment Facilitator → Sponsored Merchant instead of the simpler: Acquirer → Merchant The transaction still reaches an acquirer. What changes is who manages the merchant relationship on the way there.

The Local Acquiring Access Ladder A merchant does not need to jump directly from cross-border processing to a fully incorporated domestic acquiring operation. There are several possible levels of access. Level 1 — Cross-border acquiring Merchant → international acquirer/PSP → card network → issuer The merchant uses its existing international structure. Entity need Usually no new local entity solely for the acquiring arrangement. MID control Typically existing regional or international acquiring configuration. Underwriting Performed by the existing provider/acquirer. Settlement Usually centralized under the existing merchant contract. Pricing Cross-border or international treatment may apply depending on the transaction. Portability Often comparatively simple because no additional domestic structure exists. Operating burden Lowest. Best fit * Demand testing * Low-volume markets * early-stage expansion * internationally oriented customers * merchants prioritizing simplicity This remains a perfectly valid long-term model when its authorization, customer coverage, cost, and settlement performance are sufficient.

Level 2 — Provider-mediated local acquiring Merchant → global/regional PSP → provider’s domestic acquiring connection → network → issuer Here the merchant still contracts primarily with its payment provider, but eligible traffic is passed into a domestic acquiring configuration available through that provider. The exact structure can vary substantially. The provider could itself have: * An acquiring licence * A domestic acquiring affiliate * A local acquirer partnership * Payment Facilitator registration * A sponsored acquiring arrangement * another approved card-network structure The merchant should not infer the model from the checkout or API.

That is evidence of one provider-specific access model. It does not establish that: * Every merchant qualifies * every MCC qualifies * every network uses identical treatment * every local-acquiring relationship works this way * incorporation is unnecessary in Indonesia for every commercial or regulatory purpose The commercially useful point is narrower: A merchant can, under at least some approved provider/acquirer structures, access a domestic acquiring route without first incorporating a local merchant entity. The exact contractual, card-network, settlement, tax, merchant-location, and regulatory basis should still be confirmed for the merchant being onboarded.

Level 3 — Sponsored or sub-merchant local acquiring This is the classic payment-facilitator model. Merchant → Payment Facilitator → domestic acquirer → card network → issuer The merchant remains the underlying seller. But it does not manage the acquiring relationship in the same way a directly acquired merchant would. Visa’s current rules require an acquirer working with a Payment Facilitator to register the facilitator appropriately, require unique identifiers for the Payment Facilitator and Sponsored Merchant, define the jurisdictions and merchant categories the facilitator may support, and remain responsible for the activity submitted through the program. (Visa) Mastercard requires the payment facilitator to submit sponsored-merchant transactions to its acquirer, monitor sponsored merchants, maintain merchant information, and pay sponsored merchants for transactions submitted on their behalf. The rules also permit sponsored-merchant agreements to provide for chargeback reserves. (Mastercard) The convenience comes from delegating significant operational work. The dependency comes from delegating significant control.

Who owns the customer relationship? Usually, the sponsored merchant still sells the product and remains responsible to the customer for the underlying goods or services. Visa’s acceptance framework identifies the seller as the merchant in its Payment Facilitator model rather than the facilitator itself. That is one of the most important distinctions from a Merchant of Record model.

Who owns the acquiring relationship? The acquirer remains the network participant with ultimate acquiring responsibility. The Payment Facilitator manages much of the sponsored-merchant relationship on the acquirer’s behalf. Under Mastercard’s current rules, the Sponsored Merchant Agreement explicitly reflects that the Payment Facilitator is acting on behalf of and as agent of the Acquirer. Under Visa, acts and omissions of sponsored merchants can flow through the Payment Facilitator to the acquirer for network responsibility purposes. (Visa) The arrangement therefore does not remove acquiring risk. It redistributes its management.

Why acquirers and providers offer sponsored models There is an economic reason for this architecture. Traditional acquiring requires an acquirer to: * Find the merchant * assess the business * underwrite it * integrate it * configure acceptance * monitor transactions * administer disputes * manage compliance * pay or settle funds * support the relationship Doing all of that directly for thousands of smaller merchants can be inefficient. Visa describes the payment-facilitator model as one that can reduce the cost of signing and supporting long-tail or specialized merchants while extending payment acceptance to more sellers. A Payment Facilitator can aggregate those functions. That creates a trade: Acquirer gains * Distribution * operational scale * delegated merchant management * access to more merchant segments Payment Facilitator gains * Merchant relationship * transaction volume * commercial margin * control over the payment product * distribution economics Merchant gains * Faster market access * simpler onboarding * one integration * potentially local acquiring * less direct acquiring administration Merchant gives up Potentially: * Direct pricing negotiation * direct acquirer relationship * control of the MID structure * settlement flexibility * portability * routing independence * reserve negotiation * migration simplicity That is the real bargain.

Level 4 — Dedicated local merchant configuration through a provider The next rung is more subtle. A merchant may continue to use a provider while receiving a more individually identifiable domestic acquiring configuration. That may involve: * A dedicated MID * a dedicated merchant identifier * country-specific merchant configuration * separate settlement terms * separate MCC configuration * independent reserves * specific acquiring routing But the merchant may still not hold the direct commercial relationship with the acquirer. Unique identifier does not automatically mean direct MID ownership Visa’s current rules require Sponsored Merchants to be individually identified in Payment Facilitator transaction processing. Visa’s Merchant Screening documentation also contemplates a merchant identification number assigned either by an acquirer or, for a Sponsored Merchant, by a Payment Facilitator. (Visa) That is why merchants must avoid asking only: “Do I get my own MID?” Ask instead: * Who assigns it? * Who controls it? * Is it a network identifier, provider identifier, or acquiring MID? * Which legal merchant is attached to it? * Is it portable? * Can another provider use it? * Which acquirer owns the merchant relationship? * Which currencies does it support? * Which MCC is attached? * Where does it settle? * What happens if the provider contract ends? A “dedicated MID” can provide better reporting and merchant isolation while leaving the underlying acquiring relationship provider-controlled.

Detailed MID architecture belongs in Domestic Merchant IDs Explained. The important point here is ownership.

Level 5 — Direct local acquiring At the top of the ladder: Local merchant/entity or otherwise eligible merchant → domestic acquirer → network → issuer The merchant contracts directly with the acquirer. This can provide the most control over: * Commercial terms * acquiring configuration * MID architecture * reserve negotiation * settlement * reconciliation * provider choice * routing * switching It can also impose the largest operating burden. Potential requirements include: * Qualifying local merchant presence * entity * bank account * tax registration * domestic licences * business permits * locally acceptable merchant documentation * direct underwriting * reserves * finance operations * treasury * reconciliation Which are actually required depends on the country, acquirer, network, merchant category, and commercial structure. The article When Does a Merchant Need a Local Entity? should own that determination.

Access ladder comparison Model New local entity Direct acquirer contract Merchant identifier Underwriting Settlement control Pricing control Portability Merchant operating burden 1. Cross-border acquiring Usually not for the route itself Existing relationship Existing setup Existing provider High centralization Existing terms Usually strongest Low 2. Provider-mediated local route Provider/country dependent Usually no Provider-dependent PSP/acquirer Provider-dependent Moderate to low Provider-dependent Low–medium 3. PayFac / sponsored merchant Country and merchant-location dependent Usually indirect initially Sponsored-merchant identifier/configuration PayFac + acquirer oversight Often PayFac-mediated Usually provider-led Lower Medium 4. Dedicated domestic configuration through provider Provider/country dependent May remain indirect More merchant-specific Provider + acquirer Potentially greater Greater negotiating scope Medium Medium 5. Direct domestic acquiring Often more likely where jurisdiction requires it Yes Direct acquirer configuration Acquirer Highest Highest potential Highest conceptual control High This table is a decision framework, not a universal card-network rule. Exact requirements must be confirmed for the country and provider.

Aggregation is not the same thing as a dedicated merchant relationship “Aggregation” is often used loosely. At the broadest level it means an intermediary is bringing multiple merchants into a payment-acceptance structure rather than each merchant independently building a direct acquiring relationship. Visa itself describes the Payment Facilitator framework as a merchant aggregation model. But two aggregated merchants can still have materially different configurations. Merchant X might receive: * Individual merchant identifier * individual MCC * recognizable descriptor * separate transaction reporting * individual risk monitoring while Merchant Y might receive a more shared provider configuration. The merchant should therefore ask what is aggregated: * Acquirer contract? * MID? * settlement? * reserve? * reporting? * descriptor? * underwriting? * fraud model? * pricing? “Aggregated” is not sufficiently precise on its own.

Payment Facilitator versus PSP This distinction deserves explicit treatment. PSP A payment service provider is a broad commercial description. A PSP can provide combinations of: * Gateway * acquiring * routing * tokenization * local methods * fraud tools * settlement * reconciliation Its card-network role may differ by country. Payment Facilitator A Payment Facilitator is a specific acquiring-intermediary structure recognized by card-network rules. Mastercard describes a Payment Facilitator as a service provider registered by an acquirer to facilitate transactions for submerchants. (Mastercard) Visa’s model similarly involves an acquirer, Payment Facilitator, and Sponsored Merchant, with the facilitator able to manage merchant acceptance and settlement functions under the program. Therefore: Every PayFac is functioning within a payments-provider ecosystem. But: Not every PSP relationship is a Payment Facilitator relationship. This matters because underwriting, liability, merchant identifiers, settlement, and portability can be different.

Sponsored acquiring is not Merchant of Record This distinction is commercially fundamental. Sponsored merchant / PayFac The underlying merchant generally remains the seller. The provider facilitates payment acceptance. The customer buys from the merchant. The merchant generally remains responsible for: * Product * delivery * customer service * commercial refund policy * underlying sale Visa’s acceptance model identifies the seller itself as the merchant under the Payment Facilitator structure. Merchant of Record Under a Merchant of Record structure, another entity takes the merchant-facing position in the customer transaction under the relevant commercial model and assumes responsibilities defined by that arrangement. That can involve responsibility for areas such as: * Customer contracting * payments * tax * invoicing * refunds * compliance functions depending on the service.

A merchant should not accept the statement: “You do not need a local entity.” without asking whether the provider means: * Sponsored acquiring * Payment Facilitation * a provider-mediated acquiring route * Marketplace model * Merchant of Record Those structures are economically and legally different.

Transaction locality is not the same as incorporation This is perhaps the hardest distinction in the entire article. The merchant asks: “Do I need a company there?” The card network asks a different question: “What is the legitimate merchant location represented in the transaction?” Visa’s April 2026 Merchant Data Standards require relevant commercial substance for card-not-present merchant locations. A permanent location conducting the business activity associated with the sale may be relevant; a post-office box, payment function, servers, URL, director, or investor alone is not sufficient. Mastercard similarly requires a Sponsored Merchant’s disclosed location to reflect where the business activity governed by the Sponsored Merchant Agreement occurs and requires the location shown to customers to match authorization and clearing data. (Mastercard) This means incorporation and merchant location are related questions, but not interchangeable terminology. A provider may legitimately offer a structure that does not require a new local incorporated company. That does not authorize the merchant or provider to invent a merchant location.

Underwriting does not disappear One of the biggest misconceptions about provider-mediated acquiring is that the merchant somehow escapes underwriting. It does not. The underwriting process moves. A direct merchant may be underwritten primarily by its acquirer. A sponsored merchant can be evaluated by: * Payment Facilitator * acquirer * network risk systems * specialist compliance processes Visa requires acquirers to oversee Payment Facilitators and Sponsored Merchants, defines information and monitoring requirements, and operates merchant-screening infrastructure used in acquiring due diligence. (Visa) Mastercard places ongoing monitoring and compliance obligations on Payment Facilitators while preserving the acquirer’s responsibility within the acquiring program. (Mastercard) The merchant may therefore still need to provide: * Corporate documentation * beneficial ownership * financial statements * product information * website * licences * processing history * dispute history * expected volume * source of funds * business model The absence of incorporation is not the absence of underwriting.

Who carries the financial risk? This reveals why provider-mediated acquiring costs money. A Payment Facilitator may assume responsibilities involving: * Merchant onboarding * monitoring * transaction submission * settlement * reserve management * fraud controls * dispute administration Mastercard’s current rules require the Payment Facilitator to pay each Sponsored Merchant for transactions it submits to the acquirer on that merchant’s behalf and allow the Sponsored Merchant Agreement to provide for reserves for chargebacks or similar purposes. (Mastercard) Visa places network responsibility on the acquirer for activity submitted through its Payment Facilitator program, including the sponsored-merchant activity covered by the rules. (Visa) The commercial price a merchant pays to the provider therefore compensates for more than API calls. It can compensate for: * Acquiring access * underwriting * risk capital * reserves * monitoring * domestic relationships * settlement * reporting * compliance infrastructure * operational overhead A direct acquirer relationship may remove some intermediary margin. It also returns some of those responsibilities to the merchant.

Settlement: follow the money The cardholder paying locally does not tell you where the merchant receives money. Under a sponsored structure, the funds may move: Issuer → network → domestic acquirer → Payment Facilitator/provider → merchant payout Mastercard explicitly requires the Payment Facilitator to pay its Sponsored Merchants for transactions submitted on their behalf. (Mastercard) Visa’s rules contemplate Payment Facilitator settlement arrangements and require specific controls where the acquirer settles proceeds submitted by a Payment Facilitator on behalf of Sponsored Merchants. That means the merchant must distinguish: * Network settlement * acquirer settlement * Payment Facilitator funding * merchant payout And separately: * Settlement currency * payout currency * payout country * merchant bank account A merchant can have domestic acquiring with international payout. That is not a contradiction. It simply means acquiring and treasury are different layers.

Why settlement control matters Provider-mediated local acquiring may centralize payouts beautifully. Or it may create dependency. Ask: * Are domestic proceeds converted automatically? * Who selects the FX rate? * Can funds remain in local currency? * Can the merchant use them for local refunds? * Are payouts net or gross? * Which fees are deducted before payout? * Are reserves held separately by market? * Can multiple markets be consolidated? * Can settlement instructions be changed? * Does changing provider require a new bank or MID structure? A merchant with little market volume may happily trade control for simplicity. A merchant generating 20% of global revenue from that country may not.

Local acquiring does not automatically eliminate FX Suppose the customer pays IDR. The transaction is processed domestically. The merchant receives USD. The card processing may be local. The treasury outcome still includes foreign exchange. Conversely, a cross-border acquiring provider may allow the merchant to hold or settle the transaction currency. Therefore the merchant should map: Customer currency → processing currency → acquirer settlement currency → provider balance currency → merchant payout currency → merchant functional currency The acquisition model changes only part of that chain. Detailed treatment belongs in Local Settlement vs International Settlement.

The hidden cost: provider dependency The main economic disadvantage of sponsored access often becomes visible only when the merchant tries to leave. A provider may control: * Domestic acquirer relationship * merchant identifiers * recurring tokens * card vault * routing * reporting * settlement history * chargeback workflow * local payment contracts * fraud profiles Migrating can therefore involve more than changing an API endpoint. It may require: * New underwriting * new MIDs * token migration * cardholder reauthentication * new 3-D Secure configuration * descriptor changes * reserve duplication * settlement cutover * dispute overlap * historical reconciliation * new finance reports The merchant should price migration risk before signing the original contract.

Token portability deserves special attention For a one-time ecommerce merchant, portability may be inconvenient. For a subscription merchant, it can be strategic. Before relying on a provider-mediated local acquiring model, establish: * Who operates the token vault? * Is the network token associated with the merchant or provider configuration? * Can credentials be migrated? * Under what PCI process? * Is issuer reauthentication required? * What happens to merchant-initiated transactions after migration? * Can an existing token be routed to another acquirer? * What fees or contractual approvals apply? A local acquiring route that materially improves subscription authorization today can create a much larger migration problem later if credentials cannot move.

Who controls pricing? Direct acquiring usually gives the merchant the clearest line of sight between: * Network economics * acquiring markup * processing * FX * settlement * reserve A sponsored model may instead quote: * Blended rate * interchange-plus model * bundled rate * country-specific rate * network fee plus provider markup Neither is inherently inappropriate. But a merchant evaluating local-acquiring benefits needs to know which savings the provider retains and which flow through. Measure: Effective payment cost All attributable acquiring, network, provider, FX, settlement, reserve-financing, and payment-operation cost ÷ processed volume Do not compare the provider’s quoted processing rate with the acquirer’s interchange number. Those are different layers.

Local acquiring share One useful metric for a multi-market merchant is: Local-acquiring share Eligible card-payment attempts routed through verified local-acquiring configurations ÷ eligible card-payment attempts × 100 The word verified matters. Do not classify transactions as local because: * The customer is local * currency is local * PSP has a local office * processor server is local * merchant sees a “domestic” dashboard label Verify the underlying acquiring structure.

Authorization still has to be measured Provider-mediated local acquiring may improve authorization for some merchant populations. That outcome is not guaranteed. Compare sponsored/local and cross-border routes using similar: * Issuer * card type * country * currency * MCC * transaction value * customer cohort * authentication * fraud strategy * time period Measure: Authorization rate Approved eligible authorization attempts ÷ eligible authorization attempts × 100 And, more importantly: Completed-order rate Completed paid orders ÷ eligible checkout attempts × 100 If provider-mediated local acquiring does not improve a commercially meaningful outcome, its “local” label has little strategic value.

The merchant should measure seven things 1. Time to launch Days from approved commercial decision to first compliant production transaction Provider-mediated access should usually justify itself partly through reduced launch time.

2. Total payment cost Include: * Acquiring * network * processing * provider margin * FX * settlement * reserves * banking * payment operations

3. Authorization performance Use comparable transaction cohorts. Do not attribute an improvement to local acquiring without controlling for important differences.

4. Local-acquiring share Measure how much eligible traffic actually uses the domestic route. A product offering “local acquiring” that sends only a small fraction of relevant traffic locally should be evaluated accordingly.

5. Settlement time Define the clock carefully: Confirmed capture/settlement event → merchant access to usable funds Do not mix acquirer funding and merchant payout.

6. Provider dependency Create an internal dependency inventory. For example, score whether the provider exclusively controls: * Acquirer relationship * MID * tokens * settlement * reporting * dispute records * local methods The exact score is merchant-defined rather than an industry-standard KPI. Its purpose is to expose switching risk.

7. Migration cost Estimate: **Engineering * underwriting * legal/commercial work * token migration * duplicate reserves * finance migration * support migration * expected revenue disruption** A low initial integration cost can hide a high exit cost.

When should a merchant move up the ladder? The answer is usually not based on country count. It is based on economic concentration and control requirements. Stay with cross-border acquiring when * Market volume is small. * authorization performs adequately. * total costs are acceptable. * domestic cards are sufficiently covered. * centralized settlement works. * no critical domestic capability is missing.

Use provider-mediated local acquiring when * The merchant wants to test domestic economics. * incorporation is premature. * the provider can demonstrate a genuine local acquiring route. * onboarding is faster than direct acquisition. * the merchant accepts the provider’s control model. * settlement and portability are adequate. This is frequently the most rational intermediate state.

Use PayFac-sponsored acquiring when * The merchant fits the PayFac’s permitted category. * the provider can onboard it under a valid domestic program. * speed is valuable. * volume does not yet justify direct acquiring. * the merchant can tolerate provider-managed pricing, settlement, and reserves.

Seek a more dedicated merchant configuration when * Volume becomes material. * issuer-level performance matters. * reporting needs increase. * the merchant wants merchant-specific reserves or settlement. * descriptor control matters. * multiple routes will be tested. * provider portability becomes strategically important.

Move toward direct acquiring when The strategic advantage of ownership exceeds the convenience of sponsorship. Typical signals include: * Significant annual processing volume * Material negotiating leverage * sophisticated treasury * multiple acquiring routes * need for direct settlement control * local entity already exists * requirement for domestic card-network access * need to own the acquiring relationship * need for portability * concentration risk with one provider Network rules can also affect this progression. Under Visa’s April 2026 rules, for example, an acquirer generally must enter into a direct Merchant Agreement with a Sponsored Merchant once that merchant exceeds US$1 million in annual Visa transaction volume, subject to defined exceptions and conditions; the Payment Facilitator may continue providing payment services. Mastercard’s June 2026 rules use a different framework: Sponsored Merchants exceeding US$10 million in combined annual Mastercard and Maestro volume generally require a direct Merchant Agreement unless specified Sponsored Merchant Threshold Conditions are satisfied. These are network rules with exceptions, not universal commercial graduation thresholds. (Visa) That difference itself is instructive: The acquiring model is determined by rules, contracts, and market design—not by one universal definition of “sub-merchant.”

Graduating from sponsored to direct acquiring A merchant should plan migration before it needs migration. Stage 1: preserve data Maintain internal copies of: * Provider transaction ID * Merchant order ID * Acquirer reference where available * network reference * merchant identifier * authentication result * refund history * dispute record * settlement batch Stage 2: understand token ownership Document: * Vault provider * token type * portability * network-token relationship * recurring-payment consequences Stage 3: negotiate transition terms Before scale arrives, establish: * Termination notice * token-transfer process * historical reporting * reserve release * dispute responsibility * pending-refund responsibility * settlement overlap Stage 4: parallel-run Where feasible: * Keep existing sponsored route active. * add new direct route. * compare matched traffic. * migrate gradually. * preserve rollback capability. Stage 5: migrate only if economics justify it Direct acquiring is not a graduation ceremony. It should solve a measurable problem.

The merchant-control spectrum The access ladder can also be understood as a transfer of control. Cross-border PSP Merchant owns little country-specific infrastructure. ↓ Provider-mediated local route Provider localizes acquiring on merchant’s behalf. ↓ Sponsored merchant / PayFac Merchant is individually underwritten and identified, but acquiring relationship is mediated. ↓ Dedicated domestic configuration Merchant gains more isolation and potentially more control, but provider may still own the underlying relationship. ↓ Direct acquiring Merchant takes direct responsibility for more of the acquiring architecture. As control increases, so can: * Negotiating leverage * routing flexibility * data transparency * portability * treasury options But so can: * Engineering * compliance * finance operations * provider management * reconciliation * legal cost * operational risk The correct rung is the lowest one that provides the merchant with the economics and control it actually needs.

Model-comparison FAQ Does a merchant need a local legal entity to obtain local acquiring? Not universally. The requirement may come from local law, regulation, card-network merchant-location rules, an acquirer, a PSP, a settlement bank, tax structure, or the chosen acquiring model.

That should not be generalized to another country or provider.

Is a payment facilitator the Merchant of Record? Not necessarily. Under the Visa Payment Facilitator model, the sponsored merchant remains the underlying seller/merchant while the Payment Facilitator facilitates acceptance. A Merchant of Record structure changes who takes the merchant-facing role in the customer transaction and may change tax, invoicing, refunds, and contractual responsibility.

Can a sponsored merchant have its own MID? It can have an individually assigned merchant identifier under sponsored structures, and provider/acquirer programs may provision dedicated merchant configurations. Visa’s current rules require individual Sponsored Merchant identification; its screening documentation also contemplates merchant identification assigned by the acquirer or Payment Facilitator for Sponsored Merchants. (Visa) But a unique identifier should not automatically be interpreted as a portable direct acquirer MID. Confirm ownership and portability.

Does provider-sponsored local acquiring guarantee domestic interchange? No. Domestic or cross-border economic treatment depends on the applicable network rules, issuer/acquirer geography, merchant location, card type, transaction type, jurisdiction, and regulatory framework. The provider must identify which parts of the transaction actually receive domestic treatment.

Does a merchant lose control under a PayFac? It typically delegates more control than under a direct acquiring relationship. The degree varies by contract. Potential provider-controlled areas include: * Acquirer * underwriting * MID configuration * pricing * reserves * settlement * routing * reporting The resulting reduction in launch complexity is one reason the model exists.

Is a dedicated local MID the same as direct local acquiring? No. A provider can potentially provision a merchant-specific identifier while retaining the acquirer relationship. The merchant should determine who contracts with the acquirer and whether the identifier survives a change of provider.

When should a merchant incorporate and go direct? Usually when the country is sufficiently strategic that improved control, economics, settlement, or portability justifies the fixed cost and operating burden. The legal necessity of incorporation is a separate country-specific question.

* Underlying acquiring model * contracting entity * acquirer * merchant-location treatment * MID structure * entity requirements * eligible MCCs * processing currency * settlement currency * payout country * reserves * refunds * recurring support * token portability * production availability The promise should be access to evaluated infrastructure—not a blanket promise that every merchant can acquire locally without incorporating.

Final merchant recommendation A startup or mid-market merchant should not incorporate in every new country merely to prove that it is serious about localization. Nor should it assume that a global provider’s “local acquiring” label gives it the same control as a direct domestic acquiring relationship. Use the Local Acquiring Access Ladder. Start at the lowest level that solves the actual merchant problem. Stay cross-border where cross-border acquiring performs well. Move into provider-mediated or sponsored local acquiring where it creates a measurable improvement in: * Market access * authorization * total payment cost * settlement * customer coverage without requiring fixed infrastructure that the market cannot yet support. Then move toward a dedicated or direct acquiring relationship only when volume, strategic importance, control requirements, or network/provider constraints make ownership more valuable than convenience. The central question is not: “Can I get local acquiring without a company?” It is: “Who will hold the local acquiring relationship for me, what control will that give them, and is the convenience worth the dependency?” Local acquiring without incorporation can be a powerful market-entry structure. It works because another participant takes on part of the acquiring relationship. Understanding exactly which part is the difference between outsourcing complexity and simply hiding it.

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. Original asset: The Local Acquiring Access Ladder The visual should be a five-rung vertical ladder rather than another local-versus-cross-border comparison table: Cross-Border Acquiring ↓ Provider-Mediated Local Acquiring ↓ PayFac / Sponsored Merchant ↓ Dedicated Domestic Configuration Through Provider ↓ Direct Local Acquiring Beside each rung, show seven control variables: Entity Need · Acquirer Contract · MID Control · Underwriting · Settlement · Pricing · Portability. A second axis should run from low merchant operating burden / high provider dependency at the top to high merchant operating burden / high merchant control at the bottom. Purpose: Help expansion teams decide how much acquiring infrastructure they need to own. Suggested caption: “Local-acquiring access exists on a spectrum: the merchant can gain more domestic control as it assumes more direct acquiring responsibility.” Alt text: “Five-level local acquiring access ladder comparing cross-border processing, provider-mediated acquiring, payment facilitator sponsorship, dedicated domestic merchant configuration, and direct acquiring.”

This article follows the uploaded brief closely: it owns alternative ways to reach local acquiring without first building a local corporate/acquiring stack, rather than deciding whether incorporation is legally required in any particular country. Its organizing question is: who actually holds the acquiring relationship, and what does the merchant give up when somebody else holds it? Editorial decision Direction Unique evidence anchor A merchant can sometimes access a domestic acquiring route without holding the direct domestic acquirer relationship Editorial position Provider-mediated local acquiring is useful when it accelerates entry without surrendering too much economics, control, settlement flexibility, or portability Assumption challenged “No local company means no local acquiring.” Merchant decision Choose the lowest rung of acquiring infrastructure that provides the required market access and economics Format Operating-model comparison Distinctive structure Follow ownership: contract → MID → underwriting → transaction → settlement → migration Original asset The Local Acquiring Access Ladder

SEO package Recommended SEO title: Can You Access Local Acquiring Without a Local Entity? Recommended H1: Can Merchants Access Local Acquiring Without Incorporating Locally? Meta description: Learn how merchants can sometimes access local acquiring without incorporating through PSPs, payment facilitators and sponsored merchant models—and what control they give up. URL slug: /local-acquiring-without-local-entity/ Primary keyword: local acquiring without incorporating Secondary keywords: local acquiring without local entity, domestic acquiring without incorporation, PSP local acquiring, payment facilitator local acquiring, local payment processing without entity, international merchant domestic acquiring, sponsored local acquiring, local acquiring global PSP. Related entities: acquirer, acquiring bank, payment facilitator, sponsored merchant, sub-merchant, merchant ID, MID, merchant account, payment service provider, payment gateway, merchant aggregator, Merchant of Record, local settlement, cross-border acquiring, merchant location. Article excerpt: A merchant does not always need to contract directly with a domestic acquirer to access local acquiring infrastructure. Payment facilitators and provider-mediated models can shift acquiring relationships, underwriting and settlement to another participant—but that convenience changes merchant control, pricing and portability.

Structured data: Article or BlogPosting, BreadcrumbList, FAQPage because this article contains a genuinely article-specific visible model-comparison FAQ, and ImageObject for the Access Ladder. Internal-link recommendations The first mention of country-specific incorporation requirements should link to When Does a Merchant Need a Local Entity? rather than expanding that analysis here. Link Domestic Merchant IDs Explained from the section distinguishing a sponsored identifier, provider-controlled MID, and direct MID. Link Local Acquiring vs Cross-Border Acquiring from the discussion of whether local access produces enough authorization or cost value to matter. Link Local Acquirers by Country from the provider-eligibility discussion, where readers will naturally need the next level of geographic detail. A secondary contextual link to Local Settlement vs International Settlement belongs in the settlement section, but this article should not become the cluster’s settlement authority. Authoritative source recommendations The strongest continuing sources for this page are Visa’s current Core Rules, Merchant Data Standards Manual, and Payment Facilitator Model, plus Mastercard’s current Mastercard Rules. They directly establish sponsored-merchant relationships, merchant-location requirements, identifiers, settlement responsibilities, and the allocation of risk between acquirer, Payment Facilitator, and merchant. (Visa)

Avoid relying on generic provider landing pages to prove a no-incorporation acquiring structure. Proposed author and reviewers

Required before publication — Acquiring partnerships reviewer: verify the five access-ladder models, sponsoring relationships, MID terminology, local-acquirer access, and migration assumptions. Required before publication — Commercial/legal reviewer: verify that the article distinguishes scheme structure, provider policy, contractual requirements, and legal incorporation requirements. Strongly recommended — Payments product reviewer: verify token portability, routing, identifiers, settlement, and recurring implications.

Acquiring fact-check items Before publication, confirm the current Visa and Mastercard definitions and rules for Payment Facilitators and Sponsored Merchants, merchant-location criteria, transaction identifiers, direct-acquirer agreement thresholds, network exceptions, supported merchant categories, and regional rule modifications. Visa’s currently published $1 million provision and Mastercard’s $10 million provision have different conditions and exceptions and should be checked immediately before each substantive update. (Visa) Confirm whether each level on the Access Ladder is actually available in any specific country cited. The ladder is an operating framework, not a statement that every country permits all five models. Cost fact-check items For any commercial version of the article, verify provider margin, acquirer markup, network costs, FX, settlement fees, reserves, banking cost, and migration cost separately. Do not claim that sponsored local acquiring is cheaper than direct acquiring or cross-border acquiring without comparable merchant evidence. The economic hypothesis to test is: Incremental retained value from local acquiring − incremental provider and operating cost not merely interchange reduction. Country-specific fact-check items The Indonesia example requires the strongest final check because it carries the article’s most important concrete claim. Confirm immediately before publication:

* Merchants without Indonesian entities remain eligible. * Which networks and cards are covered. * Merchant-category exclusions. * Local-acquirer underwriting requirements. * IDR processing. * settlement and payout currencies. * refund capability. * partial refunds. * recurring support. * local merchant-location treatment. * local versus international settlement. * whether the merchant receives a dedicated MID or another identifier/configuration.

Entity and regulatory fact-check items For every country example, identify whether the requirement comes from: * Statute * regulation * card-network rule * acquirer underwriting * Payment Facilitator policy * settlement bank * tax registration * merchant category * provider contract Do not use “no local entity required” as shorthand for: * no tax obligations * no permanent-establishment analysis * no merchant-location requirements * no bank-account requirements * no licensing issues Those are independent questions. Amber-flag claims Require current evidence before publishing any statement containing: * “No local entity required” * “domestic acquiring” * “local MID” * “dedicated MID” * “domestic transaction” * “domestic interchange” * “local settlement” * “higher authorization” * “lower payment cost” * “portable tokens” * “direct acquiring not required” * “merchant can migrate the MID” * “provider owns the MID” The article should always identify who controls the underlying object or relationship rather than using the label alone.

Before adding any broader positioning, internal owners should verify: * Country-by-country acquiring coverage * Acquirer relationships

* Merchant identifier architecture * local entity requirements * underwriting * settlement * payout * reserves * pricing * token portability * recurring support * merchant-category eligibility

Provider-specific verification requirements For any provider-mediated local-acquiring arrangement, require answers to these twelve questions before recommending it: 1. Who contracts directly with the acquirer? 2. What card-network role does the provider perform? 3. Who is the merchant in the transaction record? 4. What merchant location is transmitted? 5. Who assigns the MID or merchant identifier? 6. Is that identifier portable? 7. Who performs underwriting and monitoring? 8. Who holds reserves? 9. Who receives network/acquirer settlement first? 10. How and where is the merchant paid? 11. Who controls stored credentials and tokens? 12. What has to be rebuilt when the merchant leaves? A provider has not adequately explained “local acquiring without incorporation” until those questions are answerable. Cluster sameness-audit fields Title: Can Merchants Access Local Acquiring Without Incorporating Locally? First-paragraph device: Three merchants choose three ownership models. Primary format: Operating-model comparison. Unique evidence anchor: Acquiring access can exist without the merchant holding the direct acquirer relationship. Editorial position: Sponsorship is an allocation of responsibilities, not a regulatory shortcut. Merchant decision: Select the lowest Access Ladder rung that provides sufficient economics and control.

Main network examples: Visa and Mastercard Payment Facilitator/Sponsored Merchant structures. Original framework: Local Acquiring Access Ladder. Primary metrics: Time to launch, provider dependency, migration cost, plus authorization and total cost. Conclusion: Ask who holds the acquiring relationship and whether convenience justifies dependency. Closing device: Model-comparison FAQ followed by a direct ownership decision. Cluster differentiation: Unlike the entity article, this page does not determine when incorporation is legally required; unlike the MID article, it does not own identifier architecture; unlike the cross-border comparison, it does not decide the overall performance tradeoff.