What Is Local Acquiring?

What Is Local Acquiring? How Domestic Card Processing Works for International Merchants Two international merchants are told by their payment providers that they have local acquiring in France. Merchant A has a French company, a merchant account with a French acquirer, a merchant ID associated with that domestic acquiring relationship, processes eligible transactions through the French acquiring setup, and receives settlement in euros into a French bank account. Merchant B is headquartered elsewhere. It has no French subsidiary and no direct contract with the underlying French acquirer. Instead, its global payment provider has an acquiring arrangement that can place eligible transactions onto a domestic French acquiring route. The merchant receives its eventual payout into an account outside France. Both arrangements might reasonably be described by a provider as local acquiring. But they are not the same arrangement. Now consider three more merchants: * One has a domestic merchant ID but receives payouts internationally. * One charges customers in local currency but its cards are acquired cross-border. * One incorporated locally but continues routing its transactions through an international acquiring relationship. Those examples expose the problem with the phrase local acquiring. There is no useful merchant decision hidden inside the word local until you identify what, exactly, is local. The acquirer? The merchant establishment? The merchant ID? The network classification? The currency?

The settlement account? The answer may be one of those, several of them, or nearly all of them. That is why local acquiring is best understood as an acquiring relationship and transaction-configuration model, not as a geographic marketing label. A working definition In this article: Local acquiring refers to an acquiring arrangement in which eligible merchant card transactions are submitted through an acquiring relationship established for the relevant domestic market, with the merchant and transaction configured according to the applicable network, acquirer, provider, and market requirements. That definition deliberately does not say that local acquiring always requires: * A locally incorporated merchant * A merchant-owned direct acquirer contract * A local bank account * A local payout * Local-currency settlement * A dedicated domestic MID * A processor physically located in the country * Lower interchange * Lower total payment cost * Higher authorization rates Those characteristics may accompany local acquiring. They should be verified individually. The distinction matters because card networks themselves attach importance to acquiring identity and geography. Visa, for example, defines the acquiring BIN as the BIN used to clear and settle the transaction and identifies the country in which that BIN is licensed for use. (Visa Developer)

First: what does an acquirer actually do? Before defining local acquiring, it helps to separate acquiring from several services merchants commonly buy together. The PCI Security Standards Council defines an acquirer as an entity—typically a financial institution—that processes payment-card transactions for merchants and is recognized by the relevant payment brand as an acquirer. (PCI Security Standards Council) Visa describes acquirers as the organizations that solicit merchants, conduct due diligence, and ultimately contract with merchants so they can accept Visa payment cards. (Visa) That acquiring relationship sits on the merchant side of the card system. A simplified four-party card model looks like this: Cardholder ↓ Merchant ↓ Acquirer ↓ Card network ↓ Issuer The issuer is the cardholder’s side. The acquirer is the merchant’s side. Modern payment stacks often insert additional layers between the merchant and acquirer: Merchant ↓ Gateway / PSP / payment platform ↓ Processor ↓ Acquirer ↓ Card network ↓ Issuer Those roles may be combined inside one commercial provider, but they remain conceptually different.

Acquirer vs PSP A PSP, or payment service provider, may give a merchant: * A payment API * Hosted checkout * Card tokenization * Connections to several acquirers * Alternative payment methods * Fraud tooling * Routing * Reporting * Reconciliation * Currency conversion * Settlement aggregation That does not automatically mean the PSP itself is the card acquirer for every transaction. A PSP may: * Be an acquirer in one country * Work through a sponsoring acquirer in another * Use multiple acquirers * Operate a payment-facilitator model * Route an international merchant to different acquiring relationships This distinction is particularly important when evaluating “local acquiring.” The relevant question is not just: Who is my PSP? It is: Which acquiring relationship is actually submitting this transaction?

Gateway vs acquirer A payment gateway primarily provides the technical pathway through which payment information and transaction requests reach payment-processing infrastructure. An acquirer provides or sponsors the merchant-side network relationship. A gateway can therefore send transactions to: * One acquirer * Several acquirers * A PSP that selects an acquirer * An orchestration layer that selects among several PSPs A gateway does not become a domestic acquirer merely because its servers, API endpoint, or technical infrastructure operate in the customer’s country. Processor geography is not acquiring geography.

Processor vs acquirer A processor handles technical transaction processing. An acquirer owns or sponsors the acquiring relationship recognized by the card network. They can be the same organization. They can also be separate organizations. Visa’s acceptance APIs, for example, explicitly distinguish processors from the sponsoring acquirers through which those processors enter transactions into VisaNet. (Visa Developer) This leads to one of the article’s most important rules: The location of the processor does not, by itself, determine whether a merchant is locally acquired.

Payment facilitator vs direct acquirer relationship Merchants do not always contract directly with the underlying acquirer. Payment facilitators and other sponsored models can sit between the two. Visa’s current Payment Facilitator model identifies three distinct participants: * Acquirer * Payment facilitator * Sponsored merchant The payment facilitator can sign a merchant acceptance contract with the sponsored merchant on behalf of the acquirer under the applicable model. (Visa) The Bank for International Settlements similarly describes sub-acquirers or payment facilitators as entities that expand merchant card acceptance while reaching the card network through an acquirer rather than necessarily having a direct network connection themselves. (Bank for International Settlements) This is one reason an international merchant may sometimes gain access to a domestic acquiring arrangement without having the same direct local-acquirer contract that a large domestic merchant uses. Whether that is available depends on: * Market * Network rules * Acquirer * Provider * Merchant category * Merchant location * Volume * Risk * Underwriting * Settlement structure That topic deserves its own analysis in Can You Access Local Acquiring Without Incorporating?

The Local Acquiring Component Map Instead of asking whether acquiring is “local” as a yes/no question, break it into six components. Component Possible local configuration Possible international configuration Usually controlled or influenced by Merchant implication 1. Merchant establishment Merchant contracts through an entity established in the market Merchant contracts through a foreign entity Merchant, provider, acquirer, law/regulation Can affect eligibility, tax, contracts, banking and settlement 2. Merchant ID Transaction uses an acquirer-assigned merchant identifier associated with the domestic arrangement Transaction uses a MID associated with another acquiring arrangement Acquirer, PSP/payment facilitator Affects transaction identification, reporting, routing and potentially classification 3. Acquiring relationship Domestic licensed acquiring relationship handles eligible traffic Foreign or cross-border acquiring relationship handles traffic Acquirer, PSP, payment facilitator Core component of local vs cross-border acquiring 4. Transaction classification Network/acquirer treats eligible transaction as domestic under applicable rules Transaction is treated as cross-border/interregional Network rules, acquirer configuration, merchant/card attributes May affect network economics and transaction treatment 5. Processing & currency Transaction is processed/presented in local currency using local configuration Local currency may still be processed through international acquiring Merchant, PSP, acquirer

Currency alone does not prove domestic acquiring 6. Settlement Merchant receives settlement domestically and/or in local currency Merchant receives international payout or another currency Acquirer, PSP, merchant bank, treasury Affects liquidity, FX and reconciliation but is distinct from authorization acquiring The advantage of this map is that it prevents an unhelpful binary classification. A merchant may have a configuration of: International merchant establishment * provider-sponsored domestic acquiring * domestic acquiring identifiers * local-currency transaction * international merchant payout Another merchant might have: Domestic legal entity * domestic bank account * local currency * cross-border acquirer The second merchant is more locally incorporated but may be less locally acquired.

Component 1: merchant establishment The first question is: Which legal entity is selling to the customer and entering the merchant relationship? That may be: * U.S. parent company * French subsidiary * Singapore entity * Mexican subsidiary * Merchant of Record * Payment-facilitator sponsored merchant structure Merchant establishment can matter because acquiring access may depend on the market and operating model. But establishment is only one component. A local entity does not automatically mean local acquiring Imagine a U.K. software company incorporates a German subsidiary. It continues sending all European card transactions through the same cross-border acquiring arrangement it used before incorporation. The company now has a German legal entity. That does not prove its German card traffic is locally acquired. The acquiring route still needs to be examined. Local acquiring does not universally imply merchant incorporation In some payment-facilitator or provider-sponsored models, the merchant may obtain access to domestic acquiring infrastructure through a provider rather than signing precisely the same direct acquiring agreement as a locally incorporated large merchant. Visa and BIS materials both document sponsored structures in which payment facilitators operate through an acquirer, illustrating why the contracting chain can differ from a direct merchant-acquirer relationship. (Visa) Whether a specific international merchant qualifies must be verified for the relevant country and provider.

This is why the question: “Do I need a local entity?” should always become: Who requires the entity, in which country, under which acquiring structure, and for what reason? Possible answers include: * Acquirer underwriting policy * Provider policy * Card-network rules * Banking requirements * Tax * Financial regulation * Settlement requirements * Merchant-category restrictions Those are not interchangeable.

Component 2: the merchant ID A merchant ID, commonly abbreviated MID, is an identifier associated with the merchant within an acquiring configuration. Mastercard gateway documentation describes an acquirer merchant identifier as an identifier allocated by the acquirer to the merchant and notes alternative terminology including Card Acceptor Identification Code and Card Acceptor ID. (Anzegate) Visa likewise exposes an acquirer-assigned merchant identifier in its transaction and Click to Pay specifications. (Visa Developer) Merchant account and MID are not the same thing A merchant account refers broadly to the merchant’s commercial/acquiring relationship through which card acceptance is provided. A MID is an identifier used within that relationship or processing architecture. A merchant may have: * Multiple MIDs under one broader provider relationship * Different MIDs by country * Different MIDs by acquiring route * Different MIDs by business unit * Different MIDs by channel * Different MIDs by currency or processing configuration * Separate MIDs for different merchant categories or operational reasons The precise architecture varies by acquirer and provider. A local MID is not the same as a local entity The merchant legal entity answers: Who is the merchant? The MID answers something closer to: Which merchant acceptance configuration is this transaction associated with inside the acquiring system? They are related. They are not synonymous.

A MID is also not automatically proof of domestic classification A provider might call a MID “local,” “domestic,” or “country MID.” The merchant should still ask: * Which acquirer assigned it? * Which acquiring BIN sits behind it? * Which merchant country is represented? * Which legal entity is associated with it? * Which networks use it? * Which cards are eligible? * Which transaction types are routed through it? * How does the network classify those transactions? * Where does settlement go? The label itself is not enough. Visa also explicitly distinguishes its own global Visa Merchant ID from an acquirer-assigned MID, which illustrates why merchants should avoid treating every identifier containing “merchant ID” as equivalent. (Visa Developer)

Component 3: the acquiring relationship This is the core of the definition. The acquirer is the merchant-side participant recognized within the card-network model. Visa describes the acquirer as the network member that signs the merchant and directly or indirectly enters the merchant transaction into interchange. (Visa Developer) The acquiring relationship may be: Direct Merchant → domestic acquirer PSP-mediated Merchant → PSP → domestic acquirer Payment-facilitator model Sponsored merchant → payment facilitator → acquirer Orchestrated Merchant → orchestration layer → PSP A or PSP B → selected acquirer The international merchant does not necessarily need to know every technical hop to operate checkout. It does need to understand the acquiring structure well enough to evaluate: * Eligibility * Cost * Authorization * Settlement * Disputes * Reporting * Contract portability * Market coverage

Component 4: domestic transaction classification This is where many discussions of local acquiring become misleading. A transaction does not become domestic merely because: * The customer is domestic * The card is domestic * The merchant charges local currency * The merchant owns a local company * The PSP has a local office * The processor has a local data center Network treatment can depend on combinations of attributes established by card-network rules and the acquiring configuration. Mastercard, for example, currently describes its Canadian Acquirer Cross-Border Assessment as applying when the merchant and cardholder country codes differ. That is a specific Mastercard assessment in a specific market—not a universal definition for every network and fee—but it demonstrates that transaction geography is represented through network-assigned attributes rather than the physical path of an API call. (Mastercard) Visa's rules likewise contain separate local, domestic, regional, processing, merchant-location, acquiring and settlement provisions, reinforcing that these concepts have defined scheme meanings rather than one colloquial geographical meaning. (Visa) Domestic card does not equal domestic transaction Suppose: * Customer lives in Spain * Card was issued in Spain * Transaction is in euros That proves the card and customer relationship are Spanish. It does not, by itself, establish that the merchant transaction is domestically acquired. The acquirer and merchant configuration still matter.

A foreign card can be processed through a local acquiring relationship Now suppose: * Merchant uses a French domestic acquiring route * Customer uses a U.S.-issued card The merchant may still be using French local acquiring. But the individual transaction can have cross-border characteristics because the issuer/cardholder side is foreign. This distinction is essential: “The merchant has local acquiring” describes the acquiring arrangement. “This transaction is domestic” describes the treatment of an individual transaction under applicable network and market rules. Those are related but different statements.

Component 5: processing and currency One of the easiest mistakes is: “We're charging in pesos, so we're processing locally in Mexico.” The customer transaction currency says nothing conclusive about the acquiring model. An international merchant can often: * Present MXN * Authorize MXN * Process through a cross-border acquiring relationship * Receive settlement in USD Likewise, a locally acquired merchant may choose to have its PSP convert settlement into another currency later. Presentment currency The currency in which the customer sees and agrees to the transaction. Authorization or transaction currency The currency used in the authorization message. Processing currency A provider term that should be defined carefully because providers may use it differently operationally. Settlement currency The currency in which settlement occurs between relevant acquiring/provider entities. Payout currency The currency ultimately delivered to the merchant. Merchant functional or reporting currency The currency in which the merchant accounts for its business. These may all match. They do not have to. This leads to another rule: Local currency is useful evidence about localization. It is not proof of local acquiring.

Component 6: settlement Acquiring answers: How is the merchant-side card transaction accepted and introduced into the card system? Settlement answers: How are the resulting funds ultimately transferred through the payment chain and made available to the merchant? They should not be collapsed into one concept. A simplified post-authorization sequence is: Authorization → Capture → Clearing → Network settlement → Acquirer/PSP accounting → Merchant settlement or payout → Bank receipt → Reconciliation Visa's public rules separately identify authorization processing, clearing, and settlement, reinforcing that authorization and settlement are distinct stages. (Visa) Local acquiring with international payout This can occur where: * Provider uses a local acquiring route * Merchant is eligible under the provider's structure * Funds are aggregated or processed by the provider * Provider later pays merchant outside the acquiring country The exact mechanics depend on the provider and market. Local-currency settlement without fully local acquiring The reverse may also be possible under some provider structures: * Transaction uses an international acquiring configuration * Provider maintains multi-currency settlement capabilities * Merchant receives the same local currency That does not transform the acquiring route retroactively into domestic acquiring. Therefore: Local acquiring and local settlement should be evaluated as separate decisions.

How one locally acquired card payment moves Now put the components together. Imagine an international software merchant wants domestic card acquiring in Market X. 1. Merchant creates the purchase The merchant sends: * Amount * Currency * Customer data * Card or token * Order ID * Merchant information * Authentication information * Other transaction attributes to its PSP or payment platform. What may be local? * Merchant legal entity * Customer price * Merchant country configuration What may remain global? * Checkout application * API * Token vault * Fraud platform * Merchant headquarters

2. PSP selects the acquiring configuration The PSP may determine: * Which merchant account or configuration applies * Which MID applies * Which acquirer route should receive the transaction * Which currency and country attributes should be supplied * Whether the merchant is eligible for that route What may be local? * MID * Acquiring route * Country configuration What may remain global? * PSP contract * Routing engine * Merchant API * Reporting platform

3. Merchant ID identifies the acceptance configuration The transaction carries merchant-identifying information. Mastercard calls the acquirer-assigned identifier the Acquirer Merchant Identifier/Card Acceptor ID; Visa likewise defines an acquirer-assigned merchant identifier in its transaction specifications. (Anzegate) The MID can help associate the transaction with: * Merchant * Acquirer * Merchant category * Acceptance configuration * Reporting * Settlement configuration The exact associations vary by provider and network implementation.

4. Acquirer submits the authorization The acquirer or its processor places the authorization into the network. This is the step most central to local acquiring. Visa’s definition makes the connection explicit: the acquirer signs the merchant and directly or indirectly enters its transaction into interchange. (Visa Developer)

5. Network routes the transaction The card network identifies the issuer and routes the authorization. Network rules and transaction data can affect: * Routing * Applicable programs * Country treatment * Fees * Authentication data * Clearing * Settlement The network does not make the merchant's final authorization decision.

6. Issuer decides The issuer evaluates the transaction against factors including its own account and risk information. The result may be: * Approved * Declined * Referred * Authentication required * Other network- or issuer-defined response A local acquiring route can change characteristics visible to the issuer. It cannot force the issuer to approve the purchase.

7. Authorization response returns The response travels: Issuer → network → acquirer → processor / PSP → merchant The merchant then decides whether to: * Confirm the order * Fulfill immediately * Capture later * Retry under an approved strategy * Ask the customer for another payment method

8. Clearing and settlement occur later Once the transaction is captured and cleared, financial settlement follows. The merchant may receive funds: * Directly from its acquirer * Through its PSP * In local currency * In another currency * Into a domestic account * Into a foreign account This post-authorization arrangement should not be inferred from the word “local.”

One transaction, three different country boundaries A more useful acquiring diagram separates boundaries instead of drawing one box labeled “local.” CUSTOMER MARKET Customer | | card issued by local or foreign issuer v Issuer | === CARD NETWORK ================================== | Acquirer ^ | acquiring BIN / acquiring relationship === ACQUIRING MARKET ============================== ^ Processor / PSP ^ | Merchant MID ^ | Merchant legal entity === MERCHANT ESTABLISHMENT ======================== | Merchant operating company | === TREASURY / PAYOUT ============================= | Merchant bank account The important insight is that these boundaries can line up without being required to line up. That is the structural reason two providers can both say “local acquiring” while selling materially different operating models.

Five examples merchants should be able to distinguish Example 1: direct domestic acquirer A merchant: * Incorporates in Country A * Contracts directly with an acquirer in Country A * Receives an acquirer-assigned MID * Routes eligible domestic traffic through that relationship * Settles into a domestic bank account This is the clearest form of conventional domestic acquiring. Merchant receives * Direct acquiring relationship * Domestic configuration * Direct local settlement Merchant accepts * Local entity work * Bank-account requirements * Separate contract * Additional reconciliation * Local financial and tax operations

Example 2: international merchant accessing domestic acquiring through a global PSP A merchant: * Contracts with a global PSP * Does not separately integrate the local acquirer * Is approved for a provider-supported domestic acquiring structure * Routes eligible local transactions through the PSP's local acquiring relationship Payment-facilitator and sponsored-merchant structures show how merchants can sit downstream from an acquirer rather than always holding the identical direct relationship themselves. (Visa) Merchant receives Potentially: * Domestic acquiring access * One API * Simplified contracting * Aggregated reporting Merchant must verify * Who holds the acquiring contract * Whether it has a dedicated MID * Which legal entity is the merchant * Domestic classification * Settlement * Pricing * Refunds * Chargebacks * Portability * Eligibility

Example 3: domestic MID with international payout A merchant: * Has eligible transactions placed on a domestic acquiring configuration * Uses an acquirer-assigned merchant identifier associated with that configuration * Is paid by the PSP into an account in another country The transaction can be locally acquired while the merchant payout remains international, depending on the provider structure. Lesson Domestic MID and domestic acquiring do not prove domestic payout.

Example 4: local currency but cross-border acquiring A U.S. merchant sells in Brazil. It displays BRL and authorizes the Brazilian customer in BRL. But its provider routes the payment through a foreign acquiring relationship. What is local? * Customer * Issuer * Currency What may not be local? * Merchant establishment * MID/acquiring relationship * Acquirer Lesson Local-currency payment is not synonymous with local acquiring.

Example 5: local entity but cross-border acquiring A company forms a subsidiary in Country B for commercial reasons. Its PSP continues routing Country B cards through the merchant's existing international acquiring setup. What is local? * Legal entity Potentially: * Tax registration * Customer contract * Bank account What is not proven? * Domestic card acquiring Lesson Local incorporation creates eligibility possibilities. It does not automatically change the acquiring route.

So why do merchants pursue local acquiring? The foundational answer is that local acquiring may change the commercial, technical, or operational characteristics of accepting cards in a market. The potential advantages fall into five categories. 1. Market access Some merchants pursue domestic acquiring because it can provide access to: * Domestic card products * Local network programs * Locally relevant payment configurations * Acquiring arrangements unavailable through the original cross-border setup This can be more important than cost optimization.

2. Payment economics Depending on: * Network * Issuer geography * Acquirer geography * Card type * Merchant category * Transaction classification * Regulatory regime * Provider pricing local acquiring can change fee treatment. Mastercard explicitly notes that interchange is only one component of the merchant discount rate and that merchant pricing itself is determined through the acquirer/merchant relationship rather than by Mastercard alone. (Mastercard) That is why the correct cost question is not: Is domestic interchange lower? It is: Does the entire local-acquiring configuration reduce total cost per successful or completed payment? Detailed cost mechanics belong in How Local Acquiring Reduces Payment Costs.

3. Authorization performance Local acquiring can sometimes be associated with better authorization performance because the transaction may have different: * Domestic/cross-border attributes * Acquirer relationships * Issuer familiarity * Currency * Merchant descriptors * Routing * Authentication configuration * Local market data But none of those mechanisms guarantees an approval. The issuer still decides. A customer with insufficient funds can still be declined. A fraud rule can still reject the payment. A poorly configured merchant can still perform badly through a domestic acquirer. Therefore: Authorization improvement is a testable hypothesis, not part of the definition of local acquiring.

4. Settlement and treasury Some merchants pursue local acquiring partly because the overall arrangement can support: * Local settlement * Local currency balances * Matching of refunds and revenue * Reduced unnecessary conversion * Domestic treasury But settlement belongs to a different layer and needs to be verified separately. Detailed treatment belongs in Local Settlement vs International Settlement.

5. Operational control At sufficient scale, a local acquiring relationship may offer more direct control over: * Merchant account architecture * MIDs * Acquirer reporting * Disputes * Reserves * Settlement * Issuer analysis * Routing * Country expansion That control has a cost: * More contracts * More providers * More integrations * More compliance work * More reconciliation * More operational ownership Local acquiring is therefore not simply “more localization.” It is a tradeoff between market-specific financial infrastructure and operating complexity.

What local acquiring does not guarantee This is the section merchants should use when evaluating a sales pitch. It does not guarantee a local entity A provider-sponsored structure may exist for eligible merchants. Conversely, another provider or acquirer may require local establishment. The merchant must identify who imposes the requirement and why.

It does not guarantee a domestic MID The provider should explain exactly which merchant identifier and acquiring configuration are used.

It does not guarantee that every transaction is domestic An international card used with a domestic acquiring route can still have cross-border attributes. Specific network definitions and fee treatment vary.

It does not guarantee domestic interchange Interchange varies by: * Network * Country * Card type * Consumer versus commercial card * Channel * Merchant category * Regulation * Transaction classification * Other network conditions Mastercard's own documentation stresses that interchange is only one component of merchant payment cost. (Mastercard)

It does not guarantee lower total cost A local setup might reduce some charges and add others: * PSP fees * Acquirer markup * Entity expense * Local banking * Compliance * Reconciliation * Integration * Reserve requirements * FX elsewhere in the flow The correct metric is total economics.

It does not guarantee higher authorization The issuer still controls approval. Local acquiring must be evaluated using comparable merchant cohorts.

It does not guarantee local settlement Local acquiring may be followed by international PSP payout. Ask separately.

It does not eliminate FX Currency conversion can occur: * At the cardholder's issuer * In the network * At the acquirer * At the PSP * During merchant settlement * In treasury after payout

It does not guarantee access to every local card or payment method Local card acquiring and local alternative-payment-method coverage are separate capabilities.

Provider terminology vs underlying structure Providers commonly describe products with terms such as: * Local acquiring * Domestic acquiring * Domestic processing * Local processing * Local MID * Local card acceptance * Local settlement * Domestic routing Do not assume two providers use those phrases identically. Convert every phrase into verifiable components. Instead of asking: Do you have local acquiring in Japan? ask: For an eligible Japanese-issued card transaction, which merchant entity and MID are used, which acquirer and acquiring BIN submit the transaction, how is the merchant country represented, how is the transaction classified by the network, in which currency is it authorized and cleared, and where and in which currency do you settle the merchant? That question is longer. It is also much more useful.

The local-acquiring provider audit Use this before signing a provider agreement or accepting an architecture recommendation. Merchant establishment * Which merchant legal entity signs the provider agreement? * Which legal entity is presented as merchant for each country? * Is a local entity required? * If so, who requires it? * Is the requirement regulatory, network, acquirer, banking, tax, or provider policy? * Is another structure available? MID * Who allocates the MID? * Is it dedicated to the merchant? * Is it shared or sponsored? * Which country is associated with it? * Which acquirer is behind it? * Is the MID specific to currency, channel, entity, or merchant category? * Can reporting be segmented by MID? Acquirer * Who is the actual acquirer? * Is the PSP itself the acquirer? * Is there a sponsoring acquirer? * Is the acquiring BIN licensed for the relevant country? * Which cards and networks are eligible? * Which merchant categories are supported? Visa's licensing program itself emphasizes that licensed merchant acquirers are vetted against regional regulatory requirements, which is one reason acquirer licensing and country configuration matter. (Visa Partner) Transaction classification * Under what conditions is traffic treated as domestic? * Does that apply to every locally issued card? * What happens with foreign cards? * What happens with commercial cards? * What network-specific exceptions apply? * Which cross-border assessments remain? Currency * Which currencies can be presented?

* Which currencies can be authorized? * Which currencies can be processed? * Where does conversion occur? * Who sets the FX rate? Settlement * Where is settlement calculated? * Who pays the merchant? * Which settlement currencies are supported? * Is a domestic bank account required? * Can payout occur internationally? * Are funds converted before payout? * What reserves apply? * How are refunds and disputes deducted? Operations * Who manages chargebacks? * Who manages scheme inquiries? * Which descriptor appears? * Which acquirer data are exposed? * How are authorization results segmented? * Can the merchant compare local and cross-border routes? * How are settlement and fees reconciled?

How to measure whether local acquiring is actually being used A merchant that operates several routes should not rely on the provider's country-coverage slide. Measure the traffic. Local-acquiring share Payment attempts routed through approved local-acquiring arrangements ÷ eligible payment attempts × 100 Example: If 800,000 card attempts were eligible for a domestic route and 620,000 were actually submitted through it: Local-acquiring share = 77.5%. The remaining 22.5% should be understood. Possible reasons: * Unsupported card * Provider fallback * Route outage * Merchant-category limitation * Incorrect routing * Foreign card * Configuration issue

Authorization rate Approved authorization attempts ÷ eligible submitted authorization attempts × 100 Do not compare: * Domestic debit cards on one route * International credit cards on another and attribute the difference solely to acquiring. Control for: * Country * Issuer * Card type * Currency * Customer segment * Transaction value * Authentication * Fraud configuration * Time period

Cross-border fee incidence Transactions incurring the defined cross-border charge ÷ eligible processed transactions × 100 The definition of the fee must be fixed first. Do not combine: * Network cross-border assessment * Acquirer markup * FX * PSP international fee under one undefined label.

Cost per completed order Relevant payment, settlement and associated processing cost ÷ completed paid orders This is often more commercially useful than looking at interchange alone because it incorporates the outcome the merchant is actually trying to buy: a completed revenue-generating order.

Settlement timing Use a defined starting event. For example: Time from the contractually defined clearing or settlement event to merchant access to usable funds Do not call authorization-to-bank-receipt time “settlement time” unless that is the defined measurement.

Reconciliation-exception rate Transactions, refunds, fees or payouts requiring manual investigation ÷ records included in reconciliation × 100 A local route that saves basis points but creates a large finance-operations burden may not improve total economics.

How merchants should test a local-acquiring proposal A provider says: “Our local acquiring should improve your results.” Treat that as a hypothesis. Build comparable cohorts Match transactions on: * Country * Issuer * Card type * Currency * Customer cohort * Transaction value * Merchant category * Authentication * Fraud policy * Time period Then compare: Commercial * Completed orders * Retained revenue * Cost per completed order Authorization * Authorization rate * Soft decline rate * Hard decline rate * Authentication completion Financial * Acquirer fee * Network fees * Cross-border fees * FX * Refund fees * Chargeback fees Operational * Settlement timing * Reconciliation exceptions * Provider incidents * Support contacts Evidence that would disprove the hypothesis A local acquiring route may not justify its complexity if it produces no meaningful improvement in: * Market coverage * Authorization * Total payment cost * Settlement * Treasury * Reliability * Domestic payment access * Regulatory or operational control while adding: * New entity cost * Contract complexity * Reconciliation * Banking * reserves * Support * Engineering That is a valid result. The objective is not to maximize the number of local acquirers. The objective is to improve merchant economics or market access.

Where a global PSP can still be “local” The phrase global PSP describes provider scope. It does not necessarily describe every acquiring route. A global PSP may have: * Its own acquiring licences * Multiple acquiring subsidiaries * Sponsor-acquirer relationships * Payment-facilitator structures * Local partners * Different MID models by country Visa explicitly recognizes multiple acceptance entities beyond the direct acquirer and describes merchants as being able to connect to Visa through an acquirer or through approved third-party structures. (Visa) Therefore, these statements can all be true simultaneously: The merchant uses one global PSP. The merchant does not directly integrate the domestic acquirer. Eligible traffic uses a domestic acquiring route. Merchant payout occurs internationally. That is why the architecture—not the provider's headquarters—should drive the classification.

The useful questions are:

* Which merchant categories qualify? * Is the merchant direct, sponsored, aggregated, or otherwise structured? * Is a dedicated domestic MID used? * Does the merchant need a local entity? * Is domestic settlement available? * Can payout occur internationally? * Which currencies are supported? * What reporting exposes the acquiring route? * Can merchants compare local and cross-border performance?

A defensible positioning statement can remain capability-neutral: An experienced international payments partner should be able to explain the acquiring structure behind each market—not simply mark a country as “local.”

The terminology merchants should keep straight Term Practical meaning Acquirer Merchant-side card-network participant that provides or sponsors the acquiring relationship PSP Payment service provider that may combine gateway, acquiring connectivity, methods, fraud, settlement and other services Gateway Technical interface through which payment requests are transmitted Processor Technical system/entity processing transaction messages Payment facilitator Sponsored model that can onboard and serve merchants through an acquiring relationship Merchant account Merchant's broader acquiring/acceptance relationship MID Acquirer/provider-assigned merchant identifier used within the acceptance configuration Local MID Provider term that should be decomposed into acquirer, merchant country and transaction configuration Local entity Legal merchant establishment in the market Local acquiring Domestic-market acquiring arrangement for eligible merchant traffic Domestic transaction Individual transaction classified as domestic under applicable network/market rules Cross-border acquiring Acquiring arrangement in which relevant merchant/card transaction geography crosses network or market boundaries Local processing Ambiguous term; ask whether it refers to processor location, acquiring, routing or transaction classification Local settlement Merchant-side settlement or payout arrangement in the domestic market/currency Presentment currency Currency shown to and accepted by the customer Settlement currency

Currency used when funds are settled under the acquiring/provider arrangement Payout currency Currency ultimately received by the merchant The terms in the final column should be verified against the provider's contract and network implementation rather than inferred from marketing terminology.

Questions to ask any provider offering “local acquiring” The quickest way to uncover the real structure is to ask the following as one diligence sequence: 1. Who is the merchant of record for the card transaction? 2. Which merchant legal entity is associated with the acquiring arrangement? 3. Who is the actual card acquirer? 4. Does a payment facilitator or sponsor sit between us and that acquirer? 5. Which acquiring BIN or equivalent network configuration is used? 6. Which MID identifies our merchant activity? 7. Is that MID dedicated, sponsored, aggregated, or shared under the provider model? 8. How is merchant country represented to the network? 9. Under which conditions is a transaction considered domestic? 10. Which cards remain cross-border even on this route? 11. Does local currency change transaction classification, or only currency presentation? 12. Where do clearing and settlement occur? 13. Who actually pays us? 14. Where can we receive the payout? 15. Which payout currencies are available? 16. Is a local entity required? By whom and why? 17. Is a local bank account required? By whom and why? 18. Which merchant categories are excluded? 19. Which network, interchange, cross-border, and provider fees can still apply? 20. How will the domestic route appear in our reporting so we can measure it? A provider that cannot clearly answer those questions has not given the merchant enough information to evaluate its acquiring architecture.

Terminology FAQ Is local acquiring the same as domestic processing? Not necessarily. Local acquiring describes the merchant's acquiring arrangement. Domestic processing may be used to describe transaction classification, routing, or processor location depending on the provider. Ask what the provider specifically means.

Does local acquiring mean my company needs a subsidiary in that country? Not universally. Some direct acquiring arrangements may require domestic establishment, while provider-sponsored or payment-facilitator structures may create other access models for eligible merchants. The requirement must be verified by country, acquirer, provider, merchant category, and settlement model. Visa's payment-facilitator framework is one example of an industry structure in which the merchant can sit downstream from a sponsoring acquirer. (Visa)

Is a local MID proof that I have local acquiring? Not by itself. Ask: * Which acquirer allocated or sponsors it? * Which merchant country is associated with it? * Which acquiring BIN is used? * How eligible transactions are classified * How the provider routes the traffic

Is a MID the same as a merchant account? No. The merchant account is the broader acquiring relationship. The MID is an identifier allocated within the acquiring/acceptance configuration. Mastercard and Visa both identify merchant IDs as acquirer-assigned transaction attributes. (Anzegate)

If I charge customers in their local currency, am I locally acquiring? No. Local currency can be used with cross-border acquiring. Ask separately about: * Acquirer * MID * Merchant country * Transaction classification * Settlement

Does local acquiring eliminate cross-border fees? Not automatically. Fee treatment depends on the card network, card/issuer geography, merchant and acquirer configuration, transaction type, market, and provider pricing. Mastercard, for example, distinguishes interchange from the broader merchant discount rate and maintains separate cross-border assessment rules in applicable markets. (Mastercard)

Does local acquiring increase authorization rates? It may improve performance for some merchant populations and markets, but it does not guarantee higher authorization. The issuer still makes the approval decision. Test comparable issuer, card, customer, amount, currency, authentication, and fraud cohorts.

Does local acquiring mean I receive money locally? Not necessarily. Domestic acquiring and merchant payout are separate parts of the payment lifecycle. A PSP may use domestic acquiring and later pay the merchant internationally.

Final definition Local acquiring is easiest to understand by removing the word local and reconstructing the transaction. Ask: Who is the merchant? Which MID identifies the transaction? Which acquirer accepts it? Which acquiring configuration enters it into the card network? How does the network classify it? Which currency is used? Where does settlement occur? How does the merchant ultimately receive the money? Once those questions are answered, the phrase local acquiring becomes useful. Until then, it is only a label. For an international merchant, the decision should therefore be: Use local acquiring where a verifiable domestic acquiring structure creates enough value through market access, total payment economics, authorization performance, settlement, or operational control to justify the additional commercial and technical complexity. Not every market will pass that test. Not every merchant needs it. And not every provider offering “local acquiring” is offering the same thing.

Original practical asset: Local Acquiring Component Map The framework can be turned into an operational worksheet rather than remaining only an explanatory table. Merchant acquiring audit Component Current route Proposed local route Evidence required Owner Verified? Merchant establishment

Contract / legal entity Legal

Merchant ID

Acquirer/provider MID record Payments

Acquirer

Acquirer + acquiring BIN/network configuration Payments

Transaction classification

Network/acquirer documentation Payments/Finance

Presentment currency

Processor configuration Product

Processing currency

Provider confirmation Payments

Settlement currency

Settlement schedule/contract Treasury

Payout country

Provider agreement Treasury

Payout currency

Provider agreement Treasury

Local entity requirement

Source of requirement Legal

Local bank account

Acquirer/provider requirement Treasury

Local-acquiring share

Transaction routing data Analytics

Authorization

Matched-cohort data Payments

Cross-border charges

Network/provider billing Finance

Cost per completed order

Full cost model Finance

Settlement timing

Bank/provider records Treasury

Reconciliation exceptions

Finance operations Finance

This should be the primary reusable asset associated with the article. It converts: “Provider X has local acquiring” into: “These six components are local, these three remain international, and here is the evidence.”

Editorial-brief interpretation This article should own one foundational question: What does “local acquiring” actually mean when a payment provider says it offers it? The answer is more precise than “processing the payment in the customer’s country.” An acquiring arrangement can contain several independently configurable components: * The merchant’s legal establishment * The merchant ID used for the transaction * The institution acting as acquirer * The country or market attributes assigned to the merchant and transaction * The processing and transaction currency * The settlement and payout arrangement Those components often move together. They do not have to. The article should therefore teach the reader to decompose the provider claim “local acquiring” into its underlying acquiring structure. That approach follows the supplied editorial brief and keeps the article in its intended foundational role within the broader Local Acquiring cluster. Unique evidence anchor Official network documentation supports two especially important pieces of the model.

Visa defines an acquirer as a network member that signs a merchant and directly or indirectly introduces the resulting transaction into interchange. Visa also defines an acquiring BIN in relation to the country in which it is licensed for use. Mastercard documentation describes the acquirer merchant identifier as an identifier allocated by the acquirer to the merchant. These details show why acquiring is fundamentally about relationships, identifiers, licensed network participation, and transaction attributes, rather than the physical location of a server processing an API request. (Visa Developer) Editorial position Merchants should evaluate the mechanics behind the phrase “local acquiring” rather than accept the provider label at face value. Common assumption challenged “Local acquiring simply means the payment is processed inside the customer’s country.” That is too simplistic. Processor location, merchant location, acquirer location, MID configuration, network classification, transaction currency, and settlement can be different. Merchant decision supported After reading the article, a merchant should be able to ask a provider: Exactly what is local in the acquiring arrangement you are offering me? and interpret the answer. Selected format System map + transaction walkthrough Structural rationale Local acquiring is difficult to explain through a definition alone because the merchant interacts with a PSP while the issuer sees transaction attributes produced by a chain of participants.

Following one authorization from the merchant through the PSP, MID, acquirer, network, and issuer makes those control boundaries visible.

SEO and editorial package SEO title options 1. What Is Local Acquiring? How Domestic Card Processing Works 2. What Is Local Acquiring? A Guide for International Merchants 3. Local Acquiring Explained: Acquirers, MIDs, and Domestic Processing 4. How Local Acquiring Works for International Merchants 5. Local Card Acquiring: What Merchants Actually Need to Know Recommended SEO title What Is Local Acquiring? How Domestic Card Processing Works Recommended H1 What Is Local Acquiring? How Domestic Card Processing Works for International Merchants Meta description Learn what local acquiring actually means, how acquirers, MIDs, PSPs, networks, issuers, currency and settlement fit together, and what merchants should verify. URL slug /what-is-local-acquiring Primary keyword what is local acquiring Secondary keywords * local acquiring explained * local card acquiring * domestic acquiring * local card processing * international merchant acquiring * local payment processing * acquiring bank * local merchant acquiring * domestic card processing * cross-border acquiring Related entities and concepts * Merchant acquirer * Acquiring bank * Acquiring BIN * Merchant ID * MID * Card acceptor ID * PSP * Payment gateway * Processor * Payment facilitator * Merchant account * Card network * Issuer * Authorization * Clearing * Settlement * Interchange * Cross-border assessment * Visa * Mastercard Article excerpt

Local acquiring is often described as processing cards “in the customer's country,” but the real structure is more nuanced. This guide explains how the merchant entity, MID, acquirer, transaction classification, currency and settlement combine to determine what a merchant is actually receiving.

Internal-link recommendations Use the foundational definition article to hand off deeper questions rather than answering all of them here. Local Acquiring vs Cross-Border Acquiring Anchor ideas: * local vs cross-border acquiring * compare domestic and cross-border acquiring * transaction classification Use after introducing domestic transaction classification. Benefits of Local Card Processing Anchor ideas: * benefits of local card processing * why merchants use local acquiring Use in the merchant-motivation section. How Local Acquiring Reduces Payment Costs Anchor ideas: * local acquiring costs * cross-border payment fees * total payment cost Use immediately after the high-level economics discussion. When Does a Merchant Need a Local Entity? Anchor ideas: * local entity for acquiring * merchant incorporation requirements Use in Component 1. Can You Access Local Acquiring Without Incorporating? Anchor ideas: * local acquiring without a local entity * sponsored domestic acquiring Use in the payment-facilitator section. Domestic Merchant IDs Explained Anchor ideas: * domestic merchant ID * local MID * MID architecture Use in Component 2. Local Acquirers by Country Anchor ideas: * local acquiring availability by country * country acquiring requirements Use after the provider audit. Local Settlement vs International Settlement Anchor ideas: * local settlement * international payout * settlement currency Use in Component 6.

Recommended authoritative sources The published version should preferentially cite: * Visa Core Rules and Visa Product and Service Rules. The current public rules retrieved for this analysis are dated April 18, 2026. (Visa) * Visa Developer glossary for acquirer and acquiring-BIN terminology. (Visa Developer) * Visa Payment Facilitator Model for sponsored-merchant structures. (Visa) * Visa merchant and acceptance documentation for acquiring relationships. (Visa) * Mastercard official merchant-interchange documentation for the distinction between interchange and merchant discount pricing. (Mastercard) * Mastercard developer documentation for Acquirer Merchant Identifier terminology. (Anzegate) * PCI Security Standards Council glossary for the acquirer role. (PCI Security Standards Council) * BIS research on payment facilitators/sub-acquirers for an institution-neutral explanation of indirect acquiring access. (Bank for International Settlements) For country-specific versions of this analysis, add the relevant: * Central bank * Payment regulator * Competition authority * Acquirer documentation * Network regional rules * Tax authority

Supporting visual “What Exactly Is Local?” The hero/supporting diagram should not simply show: Merchant → Acquirer → Network → Issuer Instead, visually separate four boundaries: Merchant establishment * Domestic entity * Foreign entity Acquiring * MID * PSP * Acquirer * Acquiring BIN Issuing/customer * Card network * Domestic issuer * Foreign issuer Settlement * Local settlement * International payout * Currency conversion Use movable or contrasting boundary boxes to demonstrate that the boundaries do not have to align. Suggested caption Local acquiring describes the merchant's acquiring structure—not the physical location of every company, server, currency, and bank account involved. Alt text “Local acquiring diagram showing merchant entity, payment provider, merchant ID, domestic acquirer, card network, issuer, and settlement as separate configurable payment layers.”

Proposed author and reviewers These are roles to assign, not claims that review has occurred. Required before publication Author:

Acquiring specialist: Verify acquirer, MID, sponsored merchant, domestic classification, and card-network terminology. Payment architect: Review the merchant → PSP → MID → acquirer → network → issuer system map and ensure technical roles are not collapsed. Payments operations reviewer: Verify clearing, settlement, refund, dispute, reporting, and reconciliation descriptions. Strongly recommended Legal/compliance reviewer: Review statements about merchant establishment, network arrangements, sponsored models, local entities, and provider eligibility. Finance/treasury reviewer: Review the distinction among processing, settlement and payout currencies. Optional first-hand contribution Ask an approved acquiring specialist: “What is the most common thing merchants assume they are getting when a provider says ‘local acquiring’ that is not necessarily part of the actual arrangement?” A useful contribution would be a concise first-hand observation about confusion among: * Local entity * MID * domestic classification * settlement Do not fabricate the answer.

Acquiring fact-check items Verify before publication: 1. The final article definition against current Visa and Mastercard rules. 2. Current Visa definition of acquirer. 3. Current Visa treatment of acquiring BIN and licensed country. 4. Current Mastercard Acquirer Merchant Identifier terminology. 5. Whether “MID” is the preferred editorial shorthand across the networks being discussed. 6. Payment-facilitator and sponsored-merchant terminology. 7. Whether a provider-sponsored model can be described as domestic acquiring in each example market. 8. Network-specific domestic/cross-border definitions. 9. Merchant-location rules for ecommerce. 10. Treatment of foreign-issued cards under a domestic acquiring arrangement. 11. Whether any country examples require network-specific qualification. 12. Relationship among acquirer, processor and PSP in every factual example. 13. Clearing and settlement terminology.

Cost fact-check items Before adding any numerical cost claim to the published article, verify: 1. Network. 2. Country. 3. Issuer location. 4. Acquirer location. 5. Card type. 6. Consumer or commercial status. 7. Debit or credit. 8. Card-present or card-not-present. 9. Merchant category. 10. Domestic or cross-border classification. 11. Applicable interchange category. 12. Network assessment. 13. Cross-border assessment. 14. Acquirer markup. 15. PSP markup. 16. FX. 17. Settlement fee. 18. Effective date. Do not add a generic statement such as “local acquiring saves X%” without a comparable, approved dataset.

Country-specific fact-check items Any country example added beyond the hypothetical ones should verify: * Domestic acquiring definition * Merchant establishment rules * Merchant eligibility * Local MID structure * Acquiring licences * Domestic card schemes * Interchange regulation * Network country classification * Local bank-account requirements * Settlement currencies * Local entity requirements * Merchant-category restrictions * Tax registration * Data or payment regulation Country examples should clarify structure rather than imply that every market follows the same rule.

Entity and regulatory fact-check items For every statement that says a merchant “needs” something, identify the source of the requirement: * Statute * Regulation * Network rule * Acquirer policy * PSP policy * Bank requirement * Tax requirement * Settlement arrangement * Merchant-category underwriting condition Never turn: “Acquirer X requires a local company” into: “The country requires a local company.” 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 Require additional review before publication whenever the draft claims that local acquiring: * Produces domestic interchange * Avoids cross-border assessments * Improves authorization * Lowers cost * Requires incorporation * Does not require incorporation * Requires a domestic MID * Allows international settlement * Requires domestic settlement * Eliminates FX * Supports every locally issued card * Provides a domestic descriptor * Changes authentication * Is available from a named PSP * Is available in a named country * Is available for a particular merchant category The more useful formulation is usually: “Under this specific acquiring configuration, eligible transactions may receive X treatment, subject to network, acquirer, merchant, card, and market rules.”

* Countries with local acquiring * Acquirer relationships

* Sponsored-acquiring models * Payment-facilitator structures * Contracting entities * Local entity requirements * Dedicated versus sponsored/aggregated MID structures * Domestic merchant IDs * Acquiring BIN countries * Domestic transaction treatment * Supported card networks * Domestic card schemes * Merchant-category eligibility * Local currency processing * Settlement countries * Settlement currencies * International payout * Local bank-account requirements * FX * reserves * Refunds * Chargebacks * Reporting by MID/acquirer * Routing * Authorization analytics * Local-versus-cross-border comparison tools * Approved merchant results Until verified, do not claim them.

Provider-specific verification requirements For any provider mentioned in a future comparison, verify the difference among: * “Available in Country X” * “Accepts cards from Country X” * “Supports Country X currency” * “Offers a merchant account in Country X” * “Uses domestic acquiring in Country X” * “Provides a dedicated domestic MID” * “Provides sponsored domestic acquiring” * “Settles in Country X” * “Settles in Country X currency” * “Supports an international merchant on the local route” Those are nine different claims. A provider's public country list proves none of the others by itself.

Cluster sameness-audit fields * Article: What Is Local Acquiring? * Primary question owned: What constitutes a local acquiring arrangement? * Opening: Two merchants are both sold “local acquiring” but receive different structures. * Unique evidence anchor: Acquiring relationships, acquiring BIN geography and acquirer-assigned merchant identifiers demonstrate that acquiring is a network/relationship model rather than processor geography. * Editorial position: Inspect the mechanics behind the label. * Writer influence: Ed Yong's system-level precision without stylistic imitation. * Primary format: System map and transaction walkthrough. * Core distinction: Acquiring relationship and transaction classification versus geographic marketing language. * Main original framework: Local Acquiring Component Map. * Owned lifecycle: Merchant → PSP → MID → acquirer → network → issuer → clearing → settlement. * Primary examples: Direct domestic acquirer; sponsored local acquiring; domestic MID/international payout; local currency/cross-border acquiring; local entity/cross-border acquiring. * Primary metric: Local-acquiring share. * Secondary metrics: Authorization rate, cross-border fee incidence, cost per completed order, settlement timing, reconciliation exceptions. * Entity depth: Foundational only; detailed rules handed to When Does a Merchant Need a Local Entity? * No-incorporation depth: Introductory only; detailed models handed to Can You Access Local Acquiring Without Incorporating?

* Cost depth: Conceptual only; detailed economics handed to How Local Acquiring Reduces Payment Costs. * MID depth: Foundational distinction only; full architecture handed to Domestic Merchant IDs Explained. * Settlement depth: Foundational distinction only; treasury analysis handed to Local Settlement vs International Settlement. * Authorization position: Possible benefit, never a guaranteed part of local acquiring. * Final merchant decision: Implement local acquiring where the verified acquiring structure creates measurable market-access, economic, authorization, settlement or control value sufficient to justify the operational complexity.