Local Acquiring Licensing Requirements
“Local acquiring” sounds like a routing decision. For merchants, it often is. For the company providing the acquiring service, it can also be a regulatory and card-network question. That distinction matters because merchants sometimes hear that entering a new market requires a “l
Local Acquiring Licensing Requirements: What Businesses Need to Know
“Local acquiring” sounds like a routing decision.
For merchants, it often is.
For the company providing the acquiring service, it can also be a regulatory and card-network question.
That distinction matters because merchants sometimes hear that entering a new market requires a “local acquiring licence” and assume their ecommerce business must become a licensed acquirer before it can process cards locally.
Usually, those are two different issues.
A merchant generally does not need to become a licensed acquirer simply to accept card payments for its own goods or services. The acquiring bank, payment institution, PSP, or other entity providing the acquiring service is the participant that typically needs the regulatory authority and card-scheme permissions required for that activity.
The merchant can still face significant requirements before it can use a local acquiring route. Depending on the country, scheme, provider, and business model, those can include:
an eligible local merchant entity;
an appropriate merchant location;
a local or supported settlement account;
merchant underwriting;
KYC/KYB;
tax or registration information;
scheme requirements;
prohibited-business restrictions;
local contracts;
reporting and operational obligations.
Those are important requirements.
They are not the same thing as the merchant obtaining an acquiring licence.
The distinction is especially important for businesses entering several countries. Otherwise a commercial decision about local processing can turn into a much larger—and potentially unnecessary—licensing project.
What is local acquiring?
There is no single globally standardized legal definition called local acquiring.
In commercial payments usage, local acquiring generally describes an arrangement in which card transactions are acquired through an acquiring setup associated with the merchant's target market rather than being processed entirely through a foreign or cross-border acquiring relationship.
What qualifies as sufficiently “local” can depend on several facts:
Where is the merchant established?
What country is recorded as the merchant location?
Where is the acquirer established or permitted to provide acquiring?
Which merchant ID or acquiring configuration is used?
Where does settlement occur?
Which card-scheme regional rules apply?
That is why two PSPs can both advertise local acquiring while using different legal entities, banking partners, merchant-account structures, settlement arrangements, or scheme memberships.
The phrase describes an operating model.
It is not the name of one universal licence.
Who is the acquirer in a card payment?
The acquirer sits on the merchant side of the card-payment chain.
A simplified flow is:
CARDHOLDER
|
v
MERCHANT
|
v
ACQUIRER / MERCHANT ACQUIRER
|
v
CARD NETWORK
|
v
ISSUER
The merchant sells the product or service.
The acquirer provides the merchant-facing payment service that enables eligible card transactions to be accepted and processed.
Current UK FCA guidance defines acquiring of payment transactions as a payment service in which a PSP contracts with a payee to accept and process payment transactions resulting in funds being transferred to that payee. The FCA expressly says this includes traditional merchant acquiring.
The same FCA guidance makes the merchant/acquirer distinction particularly clear: simply accepting a card payment for the merchant's own goods or services does not generally make the merchant the provider of the payment service. The firm enabling the merchant to process the card transaction and receive payment is providing the merchant-acquiring service.
That is the basic answer to one of the article's most important questions:
The merchant accepting cards is normally not the merchant acquirer.
Who needs an acquiring licence?
The business providing acquiring as a payment service is the one that needs to determine which regulatory authorization applies.
The licence/category differs by jurisdiction.
There is no universal credential named:
Global Local Acquiring Licence
For example:
in the UK, acquiring payment transactions is regulated under the Payment Services Regulations framework;
in the EU, acquiring of payment transactions is one of the payment services governed under the current PSD2 framework;
in Singapore, merchant acquisition service is expressly listed as a regulated payment service under the Payment Services Act.
A provider can also operate under another regulatory status that permits the relevant activity, such as a bank or other appropriately authorized financial institution, depending on the market.
The merchant, meanwhile, is normally the user of the acquiring service.
When could a merchant itself become an acquiring provider?
The distinction changes if the business stops merely accepting payments for itself and starts contracting with other merchants to provide acquiring.
Suppose a software platform tells third-party merchants:
“Use our service to accept card transactions. We will contract with you for that payment acceptance and processing.”
That should not automatically be treated as ordinary merchant acceptance.
In UK perimeter guidance, the FCA specifically says the acquiring definition can capture master merchants or payment facilitators where they contract with payees for acquiring services. Merely providing technical services such as data processing, storage, terminals, or an online gateway does not, by itself, constitute acquiring.
So the relevant question is not:
Do we have a payments API?
It is:
Are we merely using or technically supporting acquiring—or are we actually contracting with merchants to provide the acquiring service?
That question belongs in the licensing analysis before a platform launches embedded or marketplace payment acceptance.
Merchant requirements and acquirer licensing are two different layers
A useful launch model separates them.
Layer 1 — Acquirer regulatory authorization
This answers:
Is the provider legally permitted to provide acquiring in the relevant market?
The answer can involve:
banking authorization;
payment-institution authorization;
another applicable payment-services licence;
exemptions or other permitted regulatory status;
local versus cross-border permissions.
Layer 2 — Card-scheme participation
This answers:
Can the provider participate in Visa, Mastercard, or another applicable network in the acquiring role required for the transaction?
Visa, for example, operates a separate licensing program for institutions that want to become licensed Visa merchant acquirers. Visa states that prospective acquiring clients are vetted against regional regulatory requirements.
That is a scheme relationship.
It is not the same thing as a government regulatory licence.
Layer 3 — Merchant eligibility
This answers:
Can this particular merchant use the acquiring arrangement?
The acquirer can require:
corporate documentation;
ownership information;
business-model information;
transaction forecasts;
merchant category;
website/product review;
risk information;
settlement-account information;
local registration information where relevant.
Card-scheme and acquirer merchant-underwriting rules can add requirements even when the merchant itself needs no acquiring authorization.
Visa, for example, requires acquirers to conduct compliance checks before accepting merchants and maintains acquirer due-diligence requirements through its network rules and screening infrastructure.
Layer 4 — Local operating requirements
Finally:
Does this local route require a merchant entity, merchant location, bank account, currency, tax identifier, or other country-specific setup?
That answer is provider- and jurisdiction-specific.
This fourth layer is frequently what commercial teams mean when they say:
“You need a local setup for local acquiring.”
It should not automatically be translated into:
“The merchant needs an acquiring licence.”
Local acquiring vs cross-border acquiring
The distinction is partly legal and partly operational.
A simplified model is:
Local acquiring
MERCHANT / MARKET A
|
v
ACQUIRING SETUP
FOR MARKET A
|
v
CARD NETWORK
|
v
LOCAL / FOREIGN ISSUERS
Cross-border acquiring
MERCHANT / MARKET A
|
v
ACQUIRER / SETUP
IN MARKET B
|
v
CARD NETWORK
|
v
ISSUERS IN MARKET A / OTHERS
Actual payment architecture can be more complicated than these diagrams.
The central point is that merchant location, acquiring country, provider authorization, and scheme treatment can differ.
Visa's current materials, for example, maintain distinct acquirer-country and merchant-location data and state that regional or country-specific Visa rules can apply to merchants and acquirers according to their region or country.
Therefore:
“The PSP can process transactions from customers in that country” does not necessarily mean “the PSP offers local acquiring for that merchant in that country.”
Global card acceptance and local acquiring coverage are different capabilities.
Local acquiring regulation is jurisdiction-specific
A comparison of three current frameworks illustrates why merchants should not search for one worldwide acquiring licence.
Market
Regulator / framework
Acquiring treatment
Merchant implication
UK
FCA / Payment Services Regulations 2017
Acquiring payment transactions is a regulated payment service; providers may need FCA authorization/registration or another qualifying status
Ordinary merchant card acceptance is distinguished from providing acquiring
EU/EEA
National competent authorities / PSD2
Acquiring payment transactions is a payment service under PSD2
Merchant normally obtains acquiring from an eligible PSP rather than becoming a PI solely to accept cards
Singapore
MAS / Payment Services Act
Merchant acquisition service is explicitly regulated; provider generally needs a Standard or Major Payment Institution licence unless another provision applies
Merchant uses the licensed acquiring service; local nexus also appears in the statutory definition
The UK FCA currently lists non-bank merchant acquirers among the firms affected by the payment-services regime and states that firms providing payment services as a regular occupation or business activity generally require an applicable authorization or registration unless another permitted status or exemption applies.
In the EU, PSD2 defines acquiring of payment transactions as a service under which a PSP contracts with a payee to accept and process payment transactions resulting in transfer of funds to the payee. Acquiring is included among regulated payment services.
As of August 2026, PSD2 remains the operative framework reflected in current EU materials, while its replacement package has advanced substantially: the Council and European Parliament reached political agreement in November 2025, and the Council confirmed final compromise text in April 2026. Businesses planning future EU acquiring models should therefore recheck the applicable framework and transition dates before launch.
Singapore offers another useful model. Its Payment Services Act expressly defines merchant acquisition service and includes it among regulated payment services. The Act generally requires a Standard Payment Institution or Major Payment Institution licence to carry on that service, subject to the Act's provisions.
The point is not that these regimes are equivalent.
It is precisely the opposite:
“Acquiring licence” means different things in different regulatory systems.
Singapore also shows why the merchant's local nexus can matter
Singapore's statutory definition of merchant acquisition service is instructive.
It covers the relevant acquiring service where, among other conditions, the merchant carries on business in Singapore, is incorporated, formed, or registered there, or the merchant-acquirer contract is entered into in Singapore.
That does not create a universal rule that merchants everywhere must incorporate locally.
It demonstrates a more useful principle:
The merchant's location, establishment, contract, and acquiring relationship can be legally significant—not merely commercial details.
A market-entry team should therefore determine what “local merchant” means for the particular acquiring route rather than assuming that incorporation, website availability, customer geography, and card-scheme merchant location are interchangeable concepts.
Does a merchant need a local legal entity for local acquiring?
Sometimes.
Not universally.
This is one of the most common sources of confusion around local acquirer requirements.
An acquiring setup can potentially require a particular relationship among:
merchant legal entity;
merchant location;
acquiring entity;
settlement bank account;
settlement currency;
tax registration;
card-scheme configuration.
Other acquiring arrangements may support merchants without a separately incorporated entity in every market.
Visa itself maintains country- and region-specific rules and requires merchants and acquirers to represent appropriate merchant-location information in the network.
Therefore, do not ask only:
“Do we need a local entity?”
Ask:
“For this acquiring route, which merchant legal entity will contract with the acquirer, what country will be represented as the merchant location, where can settlement occur, and what evidence supports that setup?”
That produces a much more useful answer.
A local bank account is also not the same thing as an acquiring licence
The acquiring provider may support settlement:
to a local account;
to an account elsewhere;
in local currency;
in another supported settlement currency.
The options depend on the provider and market.
A local bank account may be:
mandatory for a specific setup;
commercially useful;
optional;
unavailable.
But opening a local settlement account does not turn the merchant into the acquirer.
Similarly:
merchant has local company
does not mean:
merchant has an acquiring licence.
Keep each layer distinct.
Card-scheme licensing and regulatory licensing are not interchangeable
An acquiring business can need to satisfy several separate systems.
Consider:
REGULATOR
"Are you legally permitted to provide acquiring?"
|
v
CARD SCHEME
"Are you permitted to participate as an acquirer?"
|
v
ACQUIRER
"Will we onboard this merchant?"
|
v
MERCHANT
"Can this legal entity use this local acquiring route?"
Visa's own current documentation makes this separation visible.
Visa has a formal licensing program for institutions seeking status as Visa issuers or merchant acquirers. Separately, Visa publishes Core Rules and Product and Service Rules governing participating financial institutions and notes that country- and region-specific rules can apply.
A provider therefore should not say:
“We are Visa licensed, so all regulatory acquiring requirements are automatically satisfied everywhere.”
Nor should a merchant say:
“Our PSP is regulated, therefore every card-network requirement is irrelevant to us.”
Regulation and scheme participation are complementary layers.
A merchant can still have card-scheme obligations
The merchant usually does not become a Visa or Mastercard acquiring institution simply by accepting the cards.
It nevertheless participates in the network under its acceptance agreement with the acquirer and must comply with applicable merchant requirements.
Visa's current public rule materials expressly tell merchants that additional requirements can be contained in their Visa acceptance agreement with the acquirer and that regional/country rules can apply.
Examples of merchant-facing areas can include:
transaction acceptance;
merchant identification/location;
card-data security;
disputes;
prohibited or restricted activity;
transaction processing requirements.
The acquiring provider is responsible for enforcing many network requirements within its merchant portfolio, but that does not make the merchant's own obligations disappear.
Why do merchants pursue local acquiring?
The regulatory work is worthwhile only if the operating model serves a commercial purpose.
Potential reasons identified in the brief include:
authorization performance;
local payment acceptance;
settlement;
less cross-border complexity;
potentially different cost structures.
Those should be treated as potential advantages, not guaranteed outcomes.
Authorization performance can be one reason
Card issuers make authorization decisions using many inputs.
The acquiring route can be one element of the transaction context.
A local acquiring arrangement may therefore be evaluated as part of an authorization-performance strategy.
But merchants should not assume:
local = higher authorization rate
without measurement.
A fair comparison should control for variables such as:
issuer;
country;
card type;
authentication;
customer cohort;
transaction value;
risk treatment;
routing eligibility;
time period.
The decision should come from merchant performance data rather than the label attached to the acquiring route.
Local payment acceptance can be broader than card acquiring
A merchant expanding internationally may need:
local card acquiring
and:
local payment methods.
They are related but not identical.
Local bank transfers, wallets, cash-based methods, and other alternative payment methods can use completely different regulatory and settlement models from card acquiring.
Do not use:
local acquiring
as a synonym for:
every local payment method.
The page should remain focused on acquiring regulation.
Settlement can be another reason
Local acquiring can affect how the merchant's acquiring and settlement relationships are structured.
Possible design questions include:
settlement entity;
settlement currency;
settlement bank;
payout schedule;
FX/conversion;
reconciliation.
Again, the exact outcome is provider-specific.
A local acquiring route is not automatically:
local-currency settlement
and local-currency settlement is not necessarily:
local acquiring.
Those are separate configuration decisions that can sometimes be combined.
Cost structure can change without necessarily becoming cheaper
Moving from cross-border to local acquiring can change:
acquirer pricing;
scheme treatment;
FX exposure;
settlement costs;
operational costs.
That does not mean:
local acquiring is always cheaper.
A merchant might reduce one cross-border cost and simultaneously add:
local-entity costs;
banking costs;
compliance costs;
additional PSP fees;
reporting overhead.
The proper comparison is:
total economics of the acquiring model
rather than one processing-rate line.
Cross-border complexity may be reduced—but operating complexity can increase
This is an important trade-off.
Local acquiring can simplify parts of the transaction path.
It can make the merchant's corporate and financial architecture more complex.
For example:
ONE CROSS-BORDER ACQUIRER
|
v
Single contract
Single settlement structure
Simpler finance model
MULTIPLE LOCAL ACQUIRERS
|
v
Multiple merchant entities?
Multiple MIDs
Multiple contracts
Multiple currencies
Multiple bank accounts
Multiple regulatory contexts
Multiple settlement reports
Neither is inherently superior.
The merchant should determine which complexity produces enough value to justify maintaining it.
Local contracts multiply quickly
Suppose the merchant operates local acquiring in ten countries.
The resulting operating estate can potentially involve:
ten merchant entities;
several acquirers;
multiple merchant contracts;
country-specific underwriting;
different settlement currencies;
separate bank accounts;
different reporting files;
different tax/compliance processes.
This can materially affect launch speed even though the merchant itself has not become an acquirer.
The regulatory burden has been placed primarily on the provider side, but the merchant still needs to satisfy the conditions that allow the provider to onboard and operate it.
Reconciliation becomes part of the regulatory operating model
A merchant adding local acquiring should know whether finance can identify:
transaction
→ merchant entity
→ acquirer/MID
→ currency
→ fee
→ settlement
→ bank receipt.
If not, a payment-performance improvement can create a finance-operations problem.
The acquiring architecture should therefore be planned with:
Payment Operations;
Treasury;
Accounting/Finance;
Legal/Compliance;
Engineering;
Tax
before market launch.
Local acquiring is not only a routing configuration.
Local acquiring can slow a launch even when the merchant needs no licence
This is where the topic connects directly to Compliance Slows Launches.
Suppose the merchant decides:
“We want domestic acquiring in six new countries.”
The compliance question may quickly become:
Which provider entity is licensed?
Can it acquire our merchant entity?
Do we need a local establishment?
Which entity signs the contract?
Which KYC/KYB documents are required?
Where does settlement occur?
Which scheme requirements apply?
Does our product category need additional approval?
Do tax registrations or bank accounts need to exist first?
How will transactions be reported and reconciled?
Those questions can delay a launch if they are discovered after the technical integration is finished.
The brief correctly treats local entities, bank/acquiring relationships, compliance, reporting, and country-specific operating processes as potential sources of launch complexity.
The better sequence is:
TARGET MARKET
|
v
TARGET ACQUIRING MODEL
|
v
PROVIDER REGULATORY COVERAGE
|
v
CARD-SCHEME ELIGIBILITY
|
v
MERCHANT ENTITY / LOCATION
|
v
SETTLEMENT + BANKING
|
v
KYC / CONTRACT / RISK
|
v
TECHNICAL ENABLEMENT
|
v
TEST + LAUNCH
Technical implementation belongs near the end of that decision chain, not the beginning.
A global acquirer or PSP can reduce the number of direct relationships
Merchants do not necessarily need to negotiate a completely separate acquiring contract with a different bank every time they enter a country.
A global acquiring or payment partner can potentially provide access to several markets through:
its own regulated entities;
local acquiring relationships;
appropriately structured bank/acquirer partners;
regional payment infrastructure.
That can centralize:
integration;
provider management;
reporting;
risk processes;
commercial relationships.
It does not necessarily eliminate:
local merchant-entity requirements;
local bank-account requirements;
KYC/KYB;
tax obligations;
card-scheme requirements;
local regulatory restrictions.
The useful question is therefore:
How much of the acquiring infrastructure can this provider centralize without requiring us to reproduce the provider's regulatory role ourselves?
One API is not the same as one regulatory relationship
This distinction matters when evaluating PSPs.
A provider may offer:
one API
while operating behind that API through:
different regulated entities;
different acquiring banks;
different MIDs;
different countries;
different settlement arrangements.
From engineering's perspective:
one integration.
From legal and treasury's perspective:
multiple acquiring relationships or regulatory contexts.
Both statements can be true.
A merchant should therefore evaluate the commercial and legal architecture underneath the API rather than assuming integration simplicity equals regulatory simplicity.
Questions to ask before launching local acquiring
A merchant can avoid considerable rework by answering these questions first.
About the provider
Which legal entity provides acquiring in this country?
What regulatory status permits that entity to provide the acquiring service?
Does the provider acquire directly or through another acquirer/bank?
Which card-scheme status or sponsorship structure applies?
Is the proposed route actually local acquiring under the provider's definition?
About the merchant
Which merchant legal entity will sign the acquiring agreement?
Does that entity need to be incorporated, registered, or operating in the target country?
What merchant location will be represented to the card network?
Which KYC/KYB and underwriting requirements apply?
Does the merchant's industry require additional scheme/provider review?
About settlement
Which entity receives settlement?
Is a local bank account required?
Which settlement currencies are supported?
Where does FX occur?
How do settlement and fees appear in reporting?
About operations
Which MID/acquiring route identifies the market?
How will refunds and disputes work?
How are transactions reconciled across local entities?
What changes if the merchant later switches acquirers?
Which regulatory or scheme changes can affect the route after launch?
If these questions do not have clear answers, the merchant has not finished designing its local acquiring model.
A Local Acquiring Regulatory Stack
The most useful way to analyze a new market is layer by layer:
LOCAL ACQUIRING
|
v
REGULATORY AUTHORIZATION
Can the provider legally acquire here?
|
v
CARD-SCHEME STATUS
Can it participate in the required role?
|
v
MERCHANT ELIGIBILITY
Can this merchant/entity be onboarded?
|
v
LOCAL CONFIGURATION
Entity / location / MID / currency / bank
|
v
SETTLEMENT MODEL
Funds / FX / timing / reporting
|
v
OPERATING MODEL
Reconciliation / disputes / support / tax
The stack prevents one of the most common conceptual mistakes:
Provider licensing and merchant eligibility are related—but they are not the same requirement.
Key takeaways
Local acquiring contains two questions that merchants should never confuse.
The first is:
Who is legally permitted to provide the acquiring service?
That is primarily a question about the acquirer or PSP and the relevant regulatory framework.
The second is:
What must our merchant business satisfy to use that local acquiring setup?
That can involve:
merchant entity;
country;
merchant location;
KYC/KYB;
underwriting;
scheme rules;
bank account;
settlement currency;
contracts;
reporting.
For an ordinary merchant accepting cards for its own goods and services, the objective is normally not to become the licensed acquirer.
It is to choose an acquiring structure in which an appropriately authorized provider can legally and operationally serve the merchant.
For payment companies, payment facilitators, or other businesses that themselves contract with merchants to accept and process transactions, the analysis is different: the business may be entering the acquiring perimeter and should determine the exact authorization and scheme status required in each jurisdiction.
And for international merchants, the biggest launch risk is often not misunderstanding card processing technically.
It is discovering too late that:
provider licence
scheme status
merchant entity
merchant location
settlement
and:
local operating requirements
do not line up.
Solve those questions before the acquiring route is built into the market-launch plan.
This article provides general information and does not constitute legal, regulatory, tax, financial, or compliance advice. Acquiring regulation, card-scheme rules, authorization categories, exemptions, and merchant eligibility requirements vary by jurisdiction and payment model and can change over time. Businesses should confirm the current position with qualified counsel, the relevant regulator, card schemes where appropriate, and the payment providers or acquiring banks involved before launch.
🙂 🙂 🙂 🙂 🙂 🙂 🙂
Those sources support a limited commercial statement:
They do not establish from the public materials reviewed here:
the regulatory licence relied on for every route;
the Visa/Mastercard membership or sponsorship structure for every market;
every local-entity requirement;
every settlement-bank requirement;
universal local acquiring coverage;
guaranteed authorization improvement;
a universal cost advantage.
Those items should be verified for the actual merchant, market, acquiring route, and contract before publication of stronger claims or before launch.
Recommended SEO title
Local Acquiring Licensing Requirements: Merchant vs Acquirer Rules
Meta title
Meta description
Learn how local acquiring licensing works, who needs the regulatory authorization, what merchants must satisfy to access local acquiring, and how regulatory licences differ from card-scheme requirements, local entities, settlement accounts, and cross-border acquiring.
Suggested URL
/solve/compliance-slows-launches/licensing-regulatory-requirements/local-acquiring-licensing-requirements/
local acquiring licensing requirements
Secondary keywords
local acquiring
acquiring licence
merchant acquiring regulation
local acquirer requirements
cross-border acquiring
The article brief specifically requires the page to distinguish the authorization needed to provide acquiring services from the conditions a merchant must meet to access local acquiring.
ARTICLE — PUBLICATION COPY
SEO / EDITORIAL GUIDANCE — NOT PART OF THE ARTICLE
Recommended featured-answer block
Place within the first 150 words:
A merchant generally does not need its own acquiring licence simply to accept card payments for its goods or services. The bank, payment institution, PSP, or other provider that supplies merchant acquiring normally needs the regulatory authorization and card-scheme permissions required for that service. The merchant may still need to satisfy local entity, merchant-location, KYC/KYB, settlement, banking, and scheme conditions to access local acquiring.
This directly answers both sides of the target search intent.
Recommended excerpt
Local acquiring is both a commercial payment strategy and a regulated service. Merchants normally access acquiring through appropriately authorized providers rather than becoming licensed acquirers themselves, but local entity, merchant-location, underwriting, card-scheme, bank-account, settlement, and reporting requirements can still determine whether a particular local acquiring route is available.
Semantic entities to reinforce
merchant acquiring
local acquiring
cross-border acquiring
acquirer
acquiring bank
merchant acquirer
PSP
payment institution
merchant ID
MID
merchant location
merchant entity
settlement account
settlement currency
acquiring country
merchant acceptance
card scheme
Visa acquiring
merchant underwriting
KYC
KYB
acquiring agreement
payment authorization
authorization rate
cross-border processing
local settlement
regulatory authorization
scheme licence
merchant eligibility
PSD2
Payment Services Regulations 2017
Payment Services Act Singapore
FCA
MAS
High-value long-tail SEO opportunities
The article naturally answers:
does a merchant need an acquiring licence
what is a local acquiring licence
local acquiring requirements
local acquiring vs cross border acquiring
does local acquiring require a local entity
do I need a local bank account for local acquiring
merchant acquiring regulation
who needs an acquiring licence
payment institution merchant acquiring
local acquirer requirements
Visa acquiring licence
card scheme licence vs payment licence
local merchant ID requirements
local acquiring for international merchants
local acquiring compliance
how to set up local acquiring
can a PSP provide local acquiring
cross-border acquirer vs local acquirer
local acquiring settlement
does local acquiring improve authorization rates
Suggested internal links
The brief specifies four primary destinations.
Suggested anchor
Internal destination
checking whether a PSP is authorized in a particular market
PSP Licensing by Country
the broader rules around international payment flows
Cross-Border Payment Regulations
country-specific payment and compliance requirements
Regulatory Requirements by Market
why ordinary merchant acceptance differs from providing payment services
Does a Merchant Need a Payments Licence?
Additional useful link:
Payment Licensing Explained when introducing acquiring as one regulated payment-service category.
Do not substantially reproduce PSP Licensing by Country here. This page should remain focused on acquiring.
Suggested visual 1 — Local Acquiring Regulatory Stack
LOCAL ACQUIRING
↓
REGULATORY AUTHORIZATION
Provider may need banking / PI / other authority
↓
CARD-SCHEME PERMISSION
Visa / Mastercard / relevant network relationship
↓
MERCHANT ELIGIBILITY
Business / category / underwriting / KYC
↓
LOCAL CONFIGURATION
Entity / merchant location / MID / currency
↓
SETTLEMENT
Bank / FX / reports
↓
OPERATIONS
Reconciliation / disputes / compliance
Headline:
Six layers can determine local acquiring. Only one is the provider's regulatory licence.
Alt text:
Local acquiring regulatory stack showing provider authorization, card-scheme permission, merchant eligibility, local entity and MID configuration, settlement, and ongoing payment operations.
Suggested visual 2 — Merchant vs Acquirer Requirements
Merchant
Acquirer / PSP
Sell own goods/services
Provide merchant acquiring
Pass underwriting/KYC
Hold relevant authorization
Meet merchant scheme rules
Hold scheme acquiring status/sponsorship
Supply entity/location data
Contract with merchant
Maintain settlement setup
Accept/process payment transactions
Reconcile settlement
Operate acquiring infrastructure
Does not become acquirer merely by accepting cards
May be inside acquiring regulatory perimeter
Headline:
Accessing local acquiring is not the same as providing it.
Suggested visual 3 — Local vs Cross-Border Acquiring
LOCAL
Merchant A
↓
Acquiring route in Market A
↓
Network
↓
Issuer
CROSS-BORDER
Merchant / customers in Market A
↓
Acquiring route in Market B
↓
Network
↓
Issuer
Underneath:
Actual classification depends on merchant location, acquiring country, scheme rules, provider structure, and jurisdiction.
Suggested visual 4 — Launch Readiness Decision Tree
TARGET MARKET
↓
DOES PROVIDER HAVE AN ELIGIBLE
ACQUIRING ROUTE?
|
NO ├──→ Find another provider/model
|
YES
↓
WHICH REGULATED ENTITY PROVIDES IT?
↓
DOES OUR MERCHANT ENTITY QUALIFY?
|
NO ├──→ Entity / structure decision
|
YES
↓
SCHEME + UNDERWRITING APPROVED?
|
NO ├──→ Resolve requirements
|
YES
↓
SETTLEMENT + BANKING READY?
|
NO ├──→ Complete treasury setup
|
YES
↓
TECHNICAL ENABLEMENT + TEST
↓
LAUNCH
Headline:
Do regulatory and merchant-eligibility work before the integration becomes the launch plan.
Authoritative source recommendations
Use primary sources for every jurisdiction-specific licensing statement.
United Kingdom — FCA
The FCA's current Payment Services Regulations and PERG guidance should be the main source for UK acquiring claims. It expressly lists merchant acquiring within payment services and distinguishes the merchant accepting its own cards from the provider supplying merchant-acquiring services.
EU/EEA — EUR-Lex and European Commission
PSD2 Article 4 defines acquiring of payment transactions, and the Directive includes acquiring among payment services. The European Commission and Council should be monitored for transition to the PSD3/PSR replacement framework.
Singapore — Singapore Statutes Online / MAS
The Payment Services Act expressly regulates merchant acquisition service, while MAS's Financial Institutions Directory can confirm whether a particular institution currently holds an SPI/MPI licence covering Merchant Acquisition Service.
Visa
Visa's current rules and licensing materials are appropriate sources for the separate card-scheme layer, including Visa licensing for merchant acquirers and regional/country-specific network rules.
Regulatory fact-check list before publication
UK
Recheck:
PSRs 2017 status;
FCA authorization categories;
acquiring definition;
merchant-acquirer versus technical-provider perimeter;
any UK payment-services reform affecting acquiring.
EU/EEA
Recheck:
PSD2 status;
whether PSD3/PSR has formally entered into force;
transition dates;
amended acquiring definition, if any;
national implementation or competent-authority requirements in the target state.
This is particularly time-sensitive because the replacement package was politically agreed in November 2025 and final compromise text was confirmed by the Council in April 2026.
Singapore
Recheck:
current Payment Services Act;
merchant acquisition definition;
SPI/MPI thresholds and requirements;
applicable exemptions;
MAS licence status of the proposed provider.
Do not reuse old payment-volume thresholds from memory.
Card-scheme fact-check list
Before publishing a market-specific claim, verify:
actual acquiring member/sponsor;
merchant country/location;
acquiring country;
relevant Visa rules;
relevant Mastercard rules;
merchant category;
merchant registration requirements;
high-risk/special-category requirements;
scheme data fields;
applicable cross-border scheme treatment.
Do not state that a regulator licence automatically provides direct Visa or Mastercard acquiring membership.
Do not state that card-scheme membership substitutes for regulatory authorization.
Merchant-entity fact-check list
For each market, verify:
which legal entity signs the merchant agreement;
where that entity is incorporated;
whether a branch/registration is required;
actual merchant location under scheme rules;
tax registrations;
local establishment requirements;
supported settlement bank location;
settlement currency;
beneficial ownership/KYB requirements.
Avoid:
“Local acquiring always requires a local entity.”
Also avoid:
“A global PSP means you never need local entities.”
Both are too broad.
Benefits fact-check list
Do not publish universal claims such as:
“Local acquiring increases authorization by X%.”
“Local acquiring always has lower fees.”
“Local acquiring eliminates cross-border fees.”
“Local acquiring guarantees local settlement.”
For a merchant case study, verify:
comparable transaction population;
issuer/geography mix;
card type;
authentication;
risk treatment;
route;
exact cost components;
settlement currency;
observation period.
Use measured merchant evidence rather than provider marketing generalizations.
Amber-flag claims
Avoid:
“Merchants need a local acquiring licence.”
Usually confuses merchant access with provider authorization.
“A local acquiring licence exists in every country.”
There is no standardized global licence category.
“The merchant is the acquirer because it accepts cards.”
FCA guidance expressly distinguishes these roles.
“Any PSP can acquire transactions worldwide from one licence.”
Licensing and scheme coverage are jurisdiction-specific.
“Visa licensing means regulatory licensing.”
Different layers.
“Regulatory authorization guarantees card-scheme membership.”
Different layers.
“Local acquiring always requires local incorporation.”
Provider/market specific.
“Local acquiring never requires local incorporation.”
Also too broad.
“A local bank account is an acquiring licence requirement everywhere.”
Unsupported.
“Local acquiring always means local-currency settlement.”
Not necessarily.
“Local acquiring always improves authorization.”
Needs merchant-specific evidence.
“Local acquiring is always cheaper.”
Needs total-cost analysis.
“Cross-border acquiring is unregulated.”
False framing; the provider's authorization and cross-border permissions still matter.
“One API means one acquiring entity.”
Not necessarily.
Not established by current public material.
exact countries with current local acquiring;
whether each route is direct or partner acquiring;
acquiring-bank entity;
applicable regulatory authorization;
Visa/Mastercard licence or sponsorship model;
merchant-entity requirements;
merchant-location treatment;
MID structure;
high-risk merchant restrictions;
settlement countries;
settlement currencies;
local bank-account requirements;
FX treatment;
dispute ownership;
chargeback reporting;
applicable scheme fees;
local/cross-border classification;
current authorization-performance evidence;
product availability by merchant segment.
Do not publish an authorization uplift percentage unless approved merchant evidence supports the exact population and methodology.
Cluster differentiation audit
Field
Local Acquiring Licensing Requirements
Primary question
What regulation applies to local acquiring, and does the merchant need the licence?
Core answer
Acquirer authorization ≠ merchant eligibility
Primary audience
International merchants, PSPs, acquiring/payment companies
Primary object
Acquiring relationship
Core distinction
Merchant accepting cards ≠ provider of acquiring
Second distinction
Regulatory licence ≠ scheme licence
Third distinction
Local acquiring ≠ every local payment method
International principle
No universal local acquiring licence
Market examples
UK / EU / Singapore
Merchant issue
Entity/location/bank/KYB can determine access
Provider issue
Authorization + scheme participation
Commercial angle
Authorization, acceptance, settlement, economics
Operational angle
Contracts, entities, bank accounts, reporting
Primary framework
Local Acquiring Regulatory Stack
Launch insight
Verify the acquiring model before technical enablement
Global-provider angle
Centralize relationships without assuming regulation disappears
Conclusion
Provider licence and merchant setup must align market by market
This keeps the article inside the Licensing and Regulatory Requirements cluster and avoids duplicating PSP Licensing by Country, Cross-Border Payment Regulations, or the general Does a Merchant Need a Payments Licence? article.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗