Local Settlement vs International Settlement
Two merchants charge the same customer 100 units of local currency. The payment succeeds. Merchant A receives the proceeds in that same currency into a bank account in the customer’s market. Merchant B receives the proceeds later in its headquarters currency through an internatio
Local Settlement vs International Settlement: Currency, Treasury, and Merchant Cash Flow
Two merchants charge the same customer 100 units of local currency.
The payment succeeds.
Merchant A receives the proceeds in that same currency into a bank account in the customer’s market.
Merchant B receives the proceeds later in its headquarters currency through an international payout from its PSP.
Which merchant paid less?
At first glance, Merchant A appears to have the advantage. No obvious international payout. No immediate currency conversion. Money stays close to the transaction.
But suppose Merchant A has almost no expenses in that market.
It now has local cash it does not need. Eventually it must convert and repatriate the funds, maintain another bank account, reconcile another balance, manage local liquidity, and potentially navigate local banking or foreign-exchange rules.
Merchant B, meanwhile, receives slightly less after provider FX and payout fees—but the money arrives directly in the account where its treasury team needs it.
Now reverse the situation.
Suppose Merchant A operates warehouses, pays employees, funds refunds, pays tax, and buys advertising in the local currency.
Merchant B converts every customer payment into USD or EUR and later sends money back into the country to pay those same expenses.
The centralized settlement model can now create two currency events where Merchant A requires none.
The question is therefore not:
Is local settlement better than international settlement?
It is:
Where does this merchant need the cash, in which currency, at what time, and what does it cost to get it there?
That is the treasury question payment teams should answer before declaring one settlement model superior.
The Payment Is Approved—but Where Does the Money Go?
Authorization tells the merchant that the issuer has approved the transaction.
It does not mean the merchant has received spendable cash.
After authorization and capture, payment information moves into clearing and settlement. Card-network settlement connects financial obligations between issuing and acquiring participants; the acquirer then has responsibility for paying the merchant according to the merchant agreement or provider arrangement. Visa’s current acquirer standards explicitly describe settlement of merchant funds as a fundamental acquiring responsibility. (Visa)
The broad sequence may look like:
Customer
→ issuer
→ card network
→ acquirer
→ PSP or payment facilitator
→ merchant
But the financial sequence can contain several distinct stages:
Authorization
Capture
Clearing
Network settlement
Acquirer funding
PSP settlement
Merchant payout
Treasury conversion
Internal cash allocation
Repatriation where applicable
Calling all of that simply “settlement” hides economically important differences.
Clearing, Settlement, and Payout Are Not the Same Thing
Clearing
Clearing determines the financial obligations arising from payment transactions.
It can include:
Transaction records
Adjustments
Fees
Refund information
Net obligations between participants
The ECB defines clearing broadly as the process by which financial institutions exchange and process payment data before final settlement. (European Central Bank)
Network settlement
The payment network facilitates settlement of obligations between participating institutions according to its rules and settlement arrangements.
Visa describes its treasury and settlement infrastructure as moving the appropriate settlement amount between issuing and acquiring participants in the required settlement currency. (Visa)
This is not necessarily the moment the merchant receives cash.
Acquirer settlement
The acquirer accounts for the merchant transaction and becomes responsible for funding the merchant under the acquiring agreement.
The amount may reflect:
Gross transaction value
Processing fees
Refunds
Chargebacks
Reserves
Other contractual deductions
PSP settlement
If the merchant contracts through a PSP, payment facilitator, aggregator, or other intermediary, the provider may receive or account for settlement before paying the merchant.
That creates another layer between network settlement and merchant cash.
Merchant payout
Payout is the movement of funds from the acquirer or PSP into the merchant’s designated bank or treasury account.
That payout can differ from the underlying settlement in:
Currency
Country
Timing
Frequency
Net amount
FX method
This distinction matters.
A provider may legitimately advertise support for settlement in a market while the merchant actually receives a cross-border payout in another currency.
Follow 100 Units Through the System
Consider a deliberately simplified hypothetical transaction.
The customer pays:
100 LCU
where LCU means the local currency unit.
No real pricing or fee level is implied.
Flow A: Local Settlement
Customer pays
100 LCU
↓
Issuer processes customer obligation
↓
Card network clears transaction
↓
Acquirer receives or accounts for network settlement
↓
Acquirer or PSP deducts applicable payment costs
↓
Merchant receives:
LCU balance or LCU bank-account credit
↓
Merchant uses local funds for:
Payroll
Suppliers
Tax
Logistics
Advertising
Refunds
Local operating costs
In this configuration, FX may be minimal or absent at the merchant treasury layer if the merchant also spends the money in LCU.
That last condition matters.
Flow B: International Settlement
Customer pays
100 LCU
↓
Issuer processes transaction
↓
Network clearing and settlement
↓
Acquirer or PSP receives local or network-settlement funds
↓
Provider converts:
LCU → merchant payout currency
↓
Provider applies any applicable:
FX spread
Conversion fee
Payout fee
Processing deductions
Reserve deductions
↓
Merchant receives:
USD, EUR, GBP, or another treasury currency
↓
Cash enters centralized treasury account
This may create a cleaner treasury structure when the merchant has few local-currency obligations.
Flow C: Local Settlement Followed by Repatriation
Customer pays
100 LCU
↓
Merchant receives local LCU settlement
↓
Merchant pays some local obligations
↓
Remaining LCU is converted through:
Local bank
Treasury bank
FX provider
Internal treasury arrangement
↓
Funds transferred internationally
↓
Merchant headquarters receives functional currency
This model can provide more control over:
Timing
FX counterparties
Local liquidity
Repatriation schedule
It also creates additional treasury work.
Flow D: International Payout Followed by Local Re-Funding
Customer pays
100 LCU
↓
Provider converts to headquarters currency
↓
Merchant receives centralized payout
↓
Merchant later needs funds locally
↓
Treasury converts headquarters currency back into LCU
↓
Cash is sent to local subsidiary or operating account
This is where an apparently simple international settlement structure can become expensive.
The merchant may effectively experience:
LCU → central currency → LCU
instead of retaining the original local-currency cash.
The economic cost depends on the actual FX pricing, banking structure, timing, and amounts involved.
Local Settlement: What It Actually Means
The phrase local settlement should be defined carefully.
It can mean different things in different provider arrangements.
Possible interpretations include:
Local settlement currency
The merchant receives the customer-market currency.
Local settlement country
The merchant receives funds into an account located in that country.
Domestic bank settlement
The acquiring or PSP arrangement pays a local merchant bank account.
Domestic legal-entity settlement
Funds are paid to the merchant’s locally incorporated entity.
These characteristics often occur together.
They do not have to.
A merchant could potentially receive:
Local currency outside the country
Local currency through a multicurrency account
Domestic payment into a local PSP-controlled structure followed by foreign payout
Local acquiring with centralized settlement
The provider agreement should identify the actual flow.
Local Acquiring Is Not Local Settlement
This is one of the most important distinctions in the entire local-acquiring cluster.
A transaction may be domestically acquired while the merchant receives payout internationally.
Possible structure:
Customer
→ domestic issuer
→ domestic acquiring route
→ local acquirer
→ global PSP
→ international merchant payout
The authorization route may be local.
The merchant cash destination is not.
Conversely, a merchant may receive local-currency payout without having a fully domestic acquiring arrangement.
Therefore:
Acquiring architecture describes how the transaction enters the payment system. Settlement architecture describes how the merchant receives the money.
Do not treat the two decisions as one.
Settlement Currency Is Not Processing Currency
Suppose a customer is charged:
1,000 MXN
The transaction could theoretically involve:
Presentment currency: MXN
Authorization currency: MXN
Processing currency: MXN
Network settlement currency: another supported settlement currency under the participants’ arrangement
PSP accounting currency: USD
Merchant payout currency: EUR
Merchant functional currency: GBP
Not every payment will contain this many conversions.
The point is that the customer seeing MXN proves almost nothing about what the merchant ultimately receives.
Before launch, map every currency stage.
Payout Currency Is Not the Merchant's Functional Currency
A merchant’s functional currency is an accounting concept reflecting the primary economic environment in which an entity operates.
Its payout currency can be different.
For example:
Merchant receives:
EUR payout
while its parent company reports primarily in:
USD
That creates another treasury conversion or accounting exposure.
Or:
Merchant receives:
BRL locally
and uses most of it for Brazilian operations.
In that case, converting all funds immediately into USD merely because USD is the group's reporting currency may not make economic sense.
Payments architecture and accounting currency should inform one another without being confused.
Where FX Actually Appears
Merchants often ask:
“Does local settlement eliminate FX?”
Not necessarily.
FX can occur at several points.
Cardholder FX
If the merchant charges in a currency different from the cardholder’s account currency, the issuer or network may perform conversion.
That is primarily a cardholder-side currency event.
Dynamic currency conversion
A merchant may offer the customer a choice to pay in the cardholder’s home currency.
Visa notes that DCC involves a currency conversion and additional disclosed pricing information. (Visa)
That should not be confused with merchant settlement FX.
Network settlement FX
Network participants can settle across supported currencies depending on the network arrangement and participant configuration.
Acquirer FX
The acquirer may convert funds before merchant funding.
PSP FX
A PSP may aggregate local revenues and convert them into a merchant-selected payout currency.
Bank FX
A merchant may receive local settlement and later convert through its bank.
Treasury FX
Large merchants may execute conversion through a dedicated treasury bank, hedging program, or internal treasury operation.
The merchant should therefore ask:
Who converts, when, at what reference rate, with what explicit fee, and with what spread?
FX Fee Versus Embedded Spread
An explicit FX fee is visible.
An embedded spread is less obvious.
Suppose the interbank or reference market rate at the relevant time is:
1 LCU = 0.1000 treasury currency
The provider converts at:
1 LCU = 0.0970
The difference may represent:
Provider spread
Market movement
Timing difference
Liquidity cost
Other pricing components
A merchant should not evaluate FX only by asking:
“What is the currency conversion fee?”
Instead ask for:
Reference rate
Rate source
Rate timestamp
Applied rate
Explicit fee
Spread
Conversion timing
This is particularly important for high-volume merchants.
A Simple FX-Cost Model
For a settlement period:
Reference value
Local currency settlement amount
× reference FX rate
Actual converted value
Amount actually received in payout currency
Implied FX cost
Reference converted value
− actual converted value
This calculation should be adjusted for known:
Payout fees
Bank fees
Taxes
Other non-FX deductions
The goal is to isolate the currency-conversion component rather than attributing every deduction to FX.
Merchant Profile 1: The Merchant With Local Operating Expenses
Consider a marketplace or ecommerce merchant operating materially in Brazil.
It collects BRL and pays:
Employees
Local suppliers
Warehousing
Advertising
Refunds
Taxes
Logistics
in BRL.
The treasury question is simple:
Why convert all BRL revenue into another currency only to buy BRL again later?
Local settlement may provide value through natural hedging.
Revenue and expenses occur in the same currency.
This can reduce the amount of currency the merchant must actively trade.
Potential benefits
Less unnecessary FX
Faster access to operating liquidity
Easier local refunds
Reduced need for intercompany funding
Better matching of revenue and expense currencies
Potential costs
Additional bank account
Additional treasury operations
Local cash management
Repatriation of surplus cash
More reconciliation
Local compliance requirements
Local settlement is attractive when the natural hedge outweighs those costs.
Merchant Profile 2: The Merchant Centralizing Treasury
Now consider a digital SaaS company.
It sells in 40 countries.
Employees are concentrated in the United States and Europe.
Hosting, payroll, financing, and corporate expenses are primarily paid in USD and EUR.
Local-market expenses are minimal.
Holding:
BRL
MXN
COP
JPY
KRW
PLN
CZK
SGD
in separate local accounts may not help.
The treasury team may prefer:
Local customer payment
→ provider conversion
→ centralized USD/EUR payout
even if this means accepting an FX spread.
Why?
Because centralization can reduce:
Bank accounts
Idle cash
Internal transfers
Local liquidity forecasting
Repatriation work
Treasury staffing
Intercompany funding complexity
Payments teams may dislike the visible FX cost.
Treasury teams may prefer the lower organizational cost.
Both can be correct.
Merchant Profile 3: Settle Locally, Repatriate Surplus
Many international merchants need neither extreme.
They can use a hybrid model:
Collect locally.
Maintain enough local currency for expected costs.
Keep a liquidity buffer.
Repatriate excess funds periodically.
Convert through the treasury channel offering the best risk-adjusted economics.
This separates:
operating cash
from:
surplus cash
The merchant might retain local funds for:
30 days of payroll
Expected refunds
Supplier invoices
Taxes
Marketing commitments
and sweep the excess to headquarters.
The exact buffer is a treasury policy decision.
Merchant Profile 4: International Payout With Provider FX
This is often attractive for merchants that value operational simplicity.
Flow:
Customer local currency
→ PSP
→ PSP FX
→ centralized settlement account
The merchant should evaluate:
FX rate quality
Conversion timing
Payout fee
Settlement delay
Minimum payout
Weekend/holiday treatment
Refund funding
Chargeback funding
The model can be economically rational even if the FX spread is not the absolute lowest available.
The merchant is purchasing:
Conversion
Cash concentration
Banking simplification
Operational outsourcing
That service has value.
The relevant comparison is total treasury cost—not FX spread alone.
Merchant Profile 5: The Multi-Market Merchant That Can Net Currencies
Large merchants may generate revenue and expenses in several currencies.
Suppose the merchant:
Collects EUR in Europe
Pays European suppliers in EUR
Collects GBP in the UK
Pays UK payroll in GBP
Collects USD globally
Pays cloud infrastructure in USD
A treasury system can avoid unnecessary conversion by matching inflows and outflows.
This is sometimes described as natural netting or currency matching.
The objective is to minimize gross currency turnover.
Instead of converting:
EUR revenue → USD
then
USD → EUR expenses
the merchant uses EUR revenue to pay EUR obligations.
Only the net surplus or deficit needs conversion.
Why Cross-Border Settlement Can Consume Liquidity
Cross-border payment arrangements can involve additional:
Intermediaries
Operating-hour differences
Currency markets
correspondent relationships
prefunding
timing mismatches
The BIS has repeatedly identified operating-hour mismatches, liquidity requirements, and settlement timing as sources of friction in cross-border payments. (Bank for International Settlements)
The issue for a merchant is not wholesale payment-system design itself.
It is the downstream effect:
When can treasury actually use the cash?
If funds are delayed by an extra settlement or payout cycle, the merchant may need:
More cash reserves
Short-term borrowing
Larger operating buffers
Intercompany funding
This creates a working-capital cost even when the nominal payment fee is unchanged.
Settlement Timing Is a Financial Variable
Compare two settlement models.
Model A
Customer pays Monday.
Merchant can use cash Tuesday.
Model B
Customer pays Monday.
Provider settles Thursday.
At small scale, the difference may be irrelevant.
At large scale, three days of sales can represent significant working capital.
The merchant should track:
Settlement delay
Date/time funds become merchant-accessible
− date/time payment reaches the defined completed-payment state
Do not rely solely on labels such as:
T+1
T+2
Weekly
Those labels require operational definitions.
Ask:
Business days or calendar days?
Which timezone?
Before which cutoff?
Does weekend traffic settle Monday?
Are reserves withheld?
Does payout processing add another day?
How long does the receiving bank take to credit?
Working-Capital Days
One useful metric is:
Working-capital settlement days
Average elapsed days between payment completion and usable merchant cash.
The financial impact can be approximated using:
Average unsettled balance
× merchant's annual cost of capital
× settlement-delay days / 365
This does not capture every liquidity effect.
It creates a common language between payments and finance.
Reserves Change the Cash Flow
An acquiring relationship may hold:
Rolling reserves
Fixed reserves
Security deposits
Fraud reserves
Chargeback reserves
Suppose the transaction succeeds today but 5% of proceeds remain unavailable under a reserve.
From a payment-conversion perspective:
Success.
From a treasury perspective:
95 units accessible; 5 units restricted.
That distinction should appear in settlement analysis.
Measure:
Cash availability rate
Immediately usable merchant cash
÷ expected merchant settlement amount
× 100
and separately:
Reserve balance
Restricted payment-related funds held under acquiring/provider terms.
Gross Settlement Versus Net Settlement
Gross settlement
The merchant receives transaction proceeds separately from some fees or adjustments.
Conceptually:
Sales = 100
Merchant receives = 100
Fees billed separately
Net settlement
Fees or adjustments are deducted before payout.
Conceptually:
Sales = 100
Processing fee = 2
Refund adjustment = 3
Reserve = 5
Payout = 90
Net settlement is common and can simplify provider collection.
It can make reconciliation harder if deductions are not itemized clearly.
Why Net Settlement Creates Reconciliation Problems
Finance may see:
Bank deposit: 90,000
while the ecommerce platform records:
Gross sales: 105,000
The difference might contain:
Processing fees
Refunds
Chargebacks
Reserves
FX
Payout fees
Prior-period adjustments
Without transaction- and settlement-level reporting, finance may be unable to explain the gap.
The settlement model should therefore support:
Order
→ transaction
→ capture
→ gross processed value
→ fee
→ refund
→ dispute
→ reserve
→ FX
→ settlement batch
→ payout
→ bank receipt
Reconciliation Is Part of Settlement Economics
Manual reconciliation is a cost.
If one provider offers:
Slightly cheaper processing
but produces:
Poor settlement files
Unmatched adjustments
Manual bank reconciliation
Unclear FX
Delayed reporting
the theoretical savings may disappear in finance operations.
Track:
Reconciliation exception rate
Settlement records requiring manual investigation
÷ settlement records expected to reconcile
× 100
and:
Manual reconciliation cost
Finance and payment-operations cost attributable to investigating settlement exceptions.
Customer Payment Success Is Not Merchant Cash Success
A useful payment dashboard can show:
Authorization: approved
Capture: complete
Payment: successful
while treasury still sees:
Funds: unavailable
Possible causes include:
Settlement cycle
Reserve
Minimum payout threshold
Compliance review
Bank holiday
FX conversion cycle
International transfer
Payout failure
Receiving-bank delay
The payment lifecycle and cash lifecycle overlap.
They are not identical.
Local Bank Account Versus Local Entity
Another common assumption is:
If local settlement requires a local account, we must create a local company.
Sometimes.
Not universally.
Possible structures include:
Local entity + local bank account
Traditional domestic operating model.
Local entity + international settlement
Merchant contracts locally but centralizes payout elsewhere where permitted by the provider and applicable rules.
Foreign entity + provider-supported local-currency payout
Possible under certain provider or banking structures.
Provider-controlled collection + international payout
Merchant does not directly hold the domestic acquiring settlement account.
The correct question is:
Who requires the local bank account, and whose name must it be in?
Possible sources of the requirement include:
Acquirer
PSP
Bank
Local law
Foreign-exchange rules
Tax structure
Merchant underwriting
The separate When Does a Merchant Need a Local Entity? article should own the complete entity analysis.
Local Bank Accounts Have Operational Costs
The benefit of avoiding FX should be compared against:
Account opening
KYC
Bank fees
Minimum balances
Local treasury operations
Cash forecasting
Signatory management
Audit
Compliance
Reconciliation
Intercompany transfers
Closure risk
A zero-FX local settlement path is not economically free.
Repatriation Changes the Calculation
In some markets, a merchant can freely convert and move surplus local funds.
In others, foreign-exchange, documentation, tax, capital-control, or banking rules can affect repatriation.
Do not assume:
Local settlement → cash can immediately move offshore.
The merchant should confirm:
Whether repatriation is permitted
Required documentation
Taxes or withholding
FX approval
Conversion channels
Timing
Dividend versus service-payment treatment where relevant
Intercompany transaction requirements
These are jurisdiction-specific legal and treasury questions.
Example: Market With Settlement Restrictions
Consider a hypothetical market where:
Merchant can receive local currency domestically
FX conversion is regulated
Offshore remittance requires documentation
Provider cannot automatically pay all proceeds internationally
Local settlement may be technically available.
But excess cash could become difficult to centralize.
For a merchant with large local operating costs, that may be manageable.
For a digital merchant with nearly all costs outside the country, it may be a major disadvantage.
The question is not:
“Can we settle locally?”
It is:
“Can we use or move the cash after we settle locally?”
Settlement Frequency and Treasury Design
Provider settlement schedules may include:
Daily
Several times per week
Weekly
Threshold-based
Rolling
Delayed by merchant-risk classification
Merchants should model:
Sales volatility
Refund volume
Payroll cycle
Supplier cycle
Tax dates
Marketing spend
Local cash buffer
Debt-service schedule
A weekly payout may be operationally acceptable for a low-volume digital merchant.
It may create significant liquidity pressure for a marketplace funding sellers every day.
Marketplaces Have a Different Settlement Problem
A marketplace receives customer payment but may owe most of the funds to a seller.
For example:
Customer payment: 100
Marketplace commission: 10
Seller payable: 90
The marketplace’s settlement strategy must account for:
Seller payout timing
Currency
Customer refund
Chargebacks
Reserve
Seller-country bank account
FX
regulatory treatment of held funds
Centralizing the entire 100 units internationally before sending 90 back into the same country may be inefficient.
But retaining seller funds locally can raise legal or safeguarding questions depending on the jurisdiction.
Marketplaces therefore require a separate funds-flow review.
Refunds Create Reverse Settlement
A refund moves value in the opposite direction.
Merchant cash
→ PSP/acquirer
→ network/payment rail
→ issuer/customer
This raises several questions:
Must refunds be funded locally?
Can refunds be deducted from future settlement?
What if the local account lacks funds?
Which FX rate applies?
Does the customer receive the original currency?
Who bears currency movement between purchase and refund?
Can refunds create a negative merchant balance?
Refund design should be included in treasury planning.
FX on Refunds
Suppose:
Customer pays 1,000 LCU.
Provider converts the merchant proceeds into USD.
One month later the merchant refunds the customer 1,000 LCU.
The LCU/USD rate has moved.
Even when the customer receives exactly 1,000 LCU back, the merchant’s USD economic result may differ from the original transaction.
This is refund FX exposure.
At sufficient scale, treasury should measure it separately.
The Settlement Destination Decision Model
Use ten questions.
Where is revenue generated?
Measure by:
Country
Currency
Channel
Payment provider
Do not assume customer geography and payment-settlement geography are identical.
Where are expenses paid?
Map:
Payroll
Suppliers
Logistics
Tax
Marketing
Refunds
Marketplace seller payouts
Offices
Which currency is actually needed?
Separate:
Customer presentment currency
Local expense currency
Treasury currency
Functional currency
What is the total FX cost?
Include:
Explicit provider conversion fee
Embedded spread
Bank conversion
Re-conversion
Hedging
Transfer fee
When does cash become usable?
Measure:
Settlement delay
Payout delay
Bank-credit delay
Weekend effects
Reserve
What banking infrastructure is required?
Confirm:
Local account
Multicurrency account
Local entity
Banking partner
Signatories
Can funds be repatriated?
Confirm:
Legal rules
FX rules
Documentation
Tax
Timing
How much liquidity is needed locally?
Calculate:
Operating expenses
Refunds
Seller payouts
Tax
Buffer
How difficult is reconciliation?
Measure:
Batch detail
FX visibility
Fee detail
Exception rate
Manual effort
Are there regulatory constraints?
Check:
Foreign exchange
safeguarding
payment regulation
tax
capital movement
marketplace funds
Model Output 1: Settle Locally
Best candidate when:
Local expenses are substantial
Revenue and costs naturally match
Local refunds are common
Merchant needs working capital locally
Local currency conversion elsewhere would be unnecessary
Local settlement is legally and operationally practical
Model Output 2: Settle Internationally
Best candidate when:
Local expenses are limited
Central treasury dominates cash use
Merchant wants fewer bank accounts
Provider FX is acceptable
Repatriation would otherwise add complexity
Local banking overhead exceeds its value
Model Output 3: Hybrid Treasury Model
Best candidate when:
Merchant has meaningful local expenses
Merchant also wants global cash concentration
Revenue materially exceeds local costs
Local liquidity can be forecast
Possible structure:
Keep:
expected operating cash + buffer
Convert and repatriate:
surplus
This is often the most economically balanced model for scaled international merchants.
Model Output 4: Market-Specific Specialist Review
Required when:
FX restrictions exist
Repatriation is constrained
Local settlement is mandatory
Local bank requirements are unclear
Funds may become trapped
Marketplace safeguarding applies
Material tax consequences depend on the funds flow
A Settlement Comparison Table
Question
Local settlement
International settlement
Customer pays local currency
Yes
Yes
Merchant receives local currency
Usually, depending on model
Not necessarily
Merchant receives funds domestically
Often
Usually no
FX may occur
Yes
Yes
Natural hedge possible
Strong when local expenses exist
Weaker if currency converted immediately
Treasury centralization
Lower unless cash swept
Strong
Local bank account
May be required
Often avoidable, provider dependent
Repatriation required
For surplus funds
Usually handled before merchant payout
FX control
Potentially greater
Often delegated to provider
Operational simplicity
Lower in multicountry model
Potentially higher
Local liquidity
Strong
May require re-funding
Bank-account count
Higher
Lower
Settlement/reconciliation complexity
Country dependent
Provider dependent
Working-capital impact
Can be favorable locally
Depends on international payout cycle
Best for
Merchants with local expenses and operations
Merchants centralizing cash with little local spend
This table describes common operating patterns—not universal provider configurations.
The Net Usable Revenue Metric
Settlement decisions should ultimately be compared using usable cash.
Define:
Net usable revenue
Gross settled customer revenue
− payment fees
− refunds
− chargebacks
− reserves
− FX cost
− payout fees
− banking costs
− directly attributable treasury costs
The metric should reflect the cash the merchant can actually deploy.
Two providers can show identical processing rates while producing very different net usable revenue.
Settlement Efficiency Rate
One possible internal treasury metric is:
Net usable merchant cash
÷ gross eligible settled revenue
× 100
Use identical cost definitions across providers.
Do not compare one provider before refunds and another after refunds.
FX Cost Rate
Measured FX and conversion cost
÷ relevant converted volume
× 100
Track by:
Country
Currency pair
Provider
Settlement model
Payout Fee Rate
Payout fees
÷ payout volume
× 100
This helps distinguish transaction processing cost from moving the resulting cash.
Trapped Cash
Define:
Cash legally or operationally unavailable for the merchant’s intended treasury use
Possible causes:
Reserve
Regulatory restriction
Minimum payout
Banking restriction
Repatriation constraint
Compliance hold
Provider hold
Measure both:
Amount
Days unavailable
Reconciliation Exception Rate
Settlement or payout records requiring manual investigation
÷ settlement or payout records expected to reconcile
× 100
High exception rates create hidden operational cost.
Working-Capital Days
Average time from payment completion to merchant-accessible cash
Track separately for:
Acquirer settlement
PSP payout
Bank credit
This allows finance to identify where delay is introduced.
A Hypothetical Treasury Comparison
Assume a merchant processes:
10 million LCU per month
Two settlement models are available.
Option A: Local settlement
Merchant receives LCU.
It spends:
6 million LCU locally
and has:
4 million LCU surplus
Only the 4 million surplus requires conversion.
Option B: International settlement
Provider converts all:
10 million LCU → headquarters currency
But the merchant still needs 6 million LCU locally.
Treasury must later buy LCU again.
In this simplified scenario:
Option A exposes:
4 million LCU
to outward conversion.
Option B can expose:
10 million LCU to provider conversion + equivalent local re-funding requirements for 6 million LCU
The actual economic difference depends on:
FX rates
spreads
banking
timing
transfer costs
hedging
tax
provider pricing
The purpose of the example is not to claim local settlement is cheaper.
It shows why local expense matching changes the denominator of the FX problem.
The Opposite Hypothetical
Now assume the same merchant has:
10 million LCU of revenue
but only:
200,000 LCU of local expenses
Maintaining local banking, treasury, compliance, reconciliation, and repatriation operations merely to preserve 200,000 LCU of natural hedging may be uneconomic.
Central international settlement can be rational.
The transaction country has not changed.
The cash-use destination has.
Settlement and Local Acquiring
Local acquiring may create access to:
Local currency settlement
Domestic bank funding
Local payment products
Different treasury options
But those outcomes require verification.
A merchant should document separately:
Acquiring route:
Who acquires?
MID:
Which merchant configuration processes the transaction?
Settlement route:
Who receives network/acquirer settlement?
Merchant payout:
Who gets paid?
Currency:
What currency arrives?
Bank location:
Where does it arrive?
The word “local” should never replace those six fields.
When International Payout May Be Better
International settlement can be attractive when:
Merchant has low local operating expenses
Treasury is highly centralized
Provider conversion is competitive
Currency risk is intentionally centralized
Local banking setup is expensive
Cash concentration matters
Merchant does not want idle balances
Local repatriation would be burdensome
The merchant is effectively paying the provider to solve part of the treasury problem.
That can be economically sensible.
When Local Settlement May Be Better
Local settlement can be attractive when:
Merchant spends substantial amounts locally
Refunds need local funding
Marketplace seller payouts are local
Domestic suppliers are paid locally
Local payroll exists
Local tax is substantial
Merchant wants direct FX control
Provider FX is expensive
Settlement speed is better domestically
Local banking is already required for other reasons
Again, the correct answer depends on net economics.
Settlement Architecture for a Multi-Country Merchant
A scalable treasury architecture can divide markets into three groups.
Group A: Natural local-currency markets
Revenue and expenses materially match.
Strategy:
Retain sufficient local currency.
Group B: Collection markets
Merchant has customer revenue but little local expense.
Strategy:
Centralize settlement where practical.
Group C: Restricted or specialist markets
Currency or regulatory conditions make settlement and repatriation unusually complex.
Strategy:
Separate treasury and legal review before scale.
This classification may be more useful than simply labeling countries “local acquiring” or “cross-border acquiring.”
What a Treasury Team Should Ask a PSP or Acquirer
Currency
What is the transaction currency?
What is the network settlement currency?
What currency does the provider settle internally?
What currencies can we receive?
Can we hold balances?
Can we select conversion timing?
FX
Who performs FX?
What reference rate is used?
At what timestamp?
What spread is added?
Is there a separate conversion fee?
What happens on weekends?
What happens on refunds?
Settlement
What is the contractual settlement cycle?
What is the actual historical payout time?
Are weekends included?
Are minimum thresholds applied?
Are payouts net or gross?
Reserves
Is there a rolling reserve?
How is it calculated?
Which currency is reserved?
When is it released?
Banking
Is a local bank account required?
Can funds be sent to a multicurrency account?
Which countries can receive payout?
Which banking fees apply?
Repatriation
Does the provider send funds offshore?
Who handles the conversion?
What documentation is required?
Are there jurisdictional restrictions?
Reconciliation
What settlement ID appears in reporting?
Can every bank deposit be matched to a settlement batch?
Are FX and fees itemized?
Are reserves itemized?
Are refunds and chargebacks traceable?
Settlement Terminology Glossary
Authorization
Issuer decision approving or declining the payment request.
Capture
Merchant or provider action confirming that an authorized card transaction should proceed into clearing, subject to the payment configuration.
Clearing
Exchange and processing of transaction information used to determine financial obligations before settlement. (European Central Bank)
Network settlement
Settlement of financial obligations between payment-network participants.
Acquirer settlement
Funding/accounting process through which the acquiring side recognizes the merchant proceeds according to the acquiring arrangement.
PSP settlement
Provider accounting or funding stage that may occur between acquirer settlement and merchant payout.
Merchant payout
Transfer of money to the merchant's designated bank or treasury account.
Settlement currency
Currency used for the relevant settlement obligation.
Payout currency
Currency the merchant actually receives.
Functional currency
Primary currency used by an entity for accounting purposes based on its economic environment.
Local settlement
A configuration in which some or all merchant proceeds settle in the local market and/or local currency. The exact meaning should be defined contractually.
International settlement
A merchant funding model in which payment proceeds are paid outside the customer market and commonly into a centralized treasury currency or account.
Gross settlement
Funding before specified fees or adjustments are netted.
Net settlement
Funding after specified fees, refunds, reserves, chargebacks, or other adjustments are deducted.
Reserve
Merchant funds withheld temporarily under acquiring or provider risk terms.
Repatriation
Moving merchant funds from a local country or currency environment to another jurisdiction.
FX spread
Difference between a reference exchange rate and the effective conversion rate used by the merchant's provider, bank, or counterparty.
Working-capital delay
Period during which economically earned payment revenue is not yet available for the merchant to use.
The Settlement Destination Decision Model: Worksheet
Question
Merchant answer
Effect
Where is revenue generated?
Where are operating costs paid?
What local currency must be retained?
What is provider FX cost?
What is bank/treasury FX cost?
What is settlement delay?
Is a local account required?
Is a local entity required?
Can surplus cash be repatriated?
What local liquidity buffer is required?
What reserves apply?
How difficult is reconciliation?
Are funds ever trapped?
What is net usable revenue?
Output
Settle locally
Settle internationally
Use a hybrid treasury model
Perform specialist market review
Merchant Recommendation
A merchant should not select local settlement simply because it uses local acquiring.
Nor should it accept international settlement simply because a global PSP makes centralized payout easier.
Start with the destination of the cash.
Ask:
In what currency did the customer pay?
In what currency does the merchant actually need the money?
How much of the revenue will be spent locally?
How much will ultimately be repatriated?
Where does FX occur?
Who sets the exchange rate?
How quickly does the merchant gain usable cash?
What reserves or payout delays apply?
What bank accounts and entities are required?
Can finance reconcile the result without excessive manual work?
Merchants with substantial local operating costs should strongly evaluate local-currency settlement because matching local revenues with local expenses can reduce unnecessary conversion and improve access to operating liquidity.
Merchants with little local expenditure and highly centralized treasury may rationally accept an international payout if its FX, payout, liquidity, and operating costs are lower than maintaining local banking and cash-management infrastructure.
Scaled multinational merchants will often benefit from a hybrid model:
retain what the local business needs; centralize the surplus.
The correct settlement architecture is therefore not determined by where the payment began.
It is determined by where the cash becomes economically useful.
Original Practical Asset: Side-by-Side Flow-of-Funds Diagram
Purpose
Make the difference between local settlement and international payout visible.
Local Settlement Flow
Customer pays 100 LCU
↓
Issuer
↓
Network clearing/settlement
↓
Local acquirer
↓
PSP where applicable
↓
Merchant receives LCU
↓
Local payroll / suppliers / refunds / tax
↓
Surplus converted and repatriated
International Settlement Flow
Customer pays 100 LCU
↓
Issuer
↓
Network clearing/settlement
↓
Acquirer / PSP
↓
Provider FX
↓
International payout
↓
Central treasury account
↓
Local currency repurchased if local expenses exist
Callouts
Display at each stage:
Currency
Fee
Hold/reserve
Settlement time
FX
Reconciliation ID
Decision supported
Whether FX and liquidity are better managed locally, centrally, or through a hybrid model.
The uploaded brief makes this article the cluster’s treasury and flow-of-funds piece, not another acquiring-performance comparison. Its central question is: after the customer pays, where should the merchant’s money actually end up, in what currency, and how quickly?
Editorial Interpretation
Unique evidence anchor
Two merchants sell the same product in the same market.
A customer pays 100 units of local currency.
Merchant A receives the proceeds into a domestic local-currency settlement account.
Merchant B receives a provider-converted payout into a centralized international treasury account.
Which merchant has the better settlement model?
There is no answer until we know what each merchant intends to do with the money next.
If Merchant A needs the local currency for payroll, suppliers, refunds, tax, logistics, or marketing, converting it into another currency only to buy it back later may create unnecessary FX and liquidity friction.
If Merchant B has almost no local expenses and centralizes cash globally, accumulating local balances in dozens of bank accounts may create more operational cost than the FX saved.
The transaction is identical.
The treasury problem is not.
Editorial position
Settlement should be designed around the merchant’s cash-use destination, not simply the country where the customer paid.
Local settlement is most valuable when the merchant needs local currency for local operating expenses, regulatory requirements, liquidity management, or FX control.
International settlement can be preferable when centralized liquidity is more valuable and the incremental conversion, payout, and timing costs remain acceptable.
Common assumption challenged
“Local settlement is automatically cheaper and better.”
Merchant decision supported
This article helps a merchant decide:
Where payment proceeds should settle
Which currency should be received
Whether a local bank account provides real treasury value
Whether proceeds should remain local or be repatriated
Whether provider FX is economically competitive
How payout timing changes working capital
When net settlement complicates reconciliation
When a hybrid local-and-central treasury structure is justified
Selected format
Flow-of-funds and treasury comparison
Structural rationale
This article follows money rather than the authorization message.
The sequence is:
Customer pays
→ issuer funds the transaction
→ network clearing and settlement
→ acquirer receives funds
→ PSP or acquiring platform applies its settlement model
→ merchant settlement or payout occurs
→ treasury decides whether to hold, spend, convert, or repatriate the cash
That keeps this article distinct from:
What Is Local Acquiring?
Local Acquiring vs Cross-Border Acquiring
How Local Acquiring Improves Approval Rates
How Local Acquiring Reduces Payment Costs
When Does a Merchant Need a Local Entity?
SEO Metadata
Local Settlement vs International Settlement for Merchants
H1
Local Settlement vs International Settlement: Currency, Treasury, and Merchant Cash Flow
Alternative titles
Local vs International Payment Settlement Explained
Local Payment Settlement, FX, and Merchant Treasury
Should Merchants Settle Payments Locally or Internationally?
Local Currency Settlement vs International Merchant Payouts
Payment Settlement Strategy for Global Merchants
Meta description
Compare local and international payment settlement, including settlement currency, FX, treasury, bank accounts, working capital, repatriation and merchant payouts.
URL slug
/local-settlement-vs-international-settlement
local settlement vs international settlement
Secondary keywords
local payment settlement
international payment settlement
domestic settlement payments
cross-border settlement
local acquiring settlement
merchant settlement currency
international merchant payouts
local currency settlement
payment treasury
Related entities
Settlement
Clearing
Payout
Acquirer
PSP
Merchant account
Foreign exchange
FX spread
Repatriation
Treasury
Working capital
Liquidity
Reserve
Net settlement
Gross settlement
Functional currency
Local acquiring
Article excerpt
A locally acquired payment does not necessarily settle locally, and local settlement does not automatically reduce FX costs. This guide follows merchant funds from customer payment through clearing, settlement, conversion and treasury to show when local, international or hybrid settlement makes economic sense.
Internal-Link Recommendations
What Is Local Acquiring?
Anchor suggestions:
how local acquiring works
the acquiring lifecycle
Use when readers need the upstream acquiring context.
How Local Acquiring Reduces Payment Costs
Anchor suggestions:
total local acquiring cost
payment-cost economics
Use for detailed interchange, network, processing and FX cost decomposition.
When Does a Merchant Need a Local Entity?
Anchor suggestions:
local entity requirements
when domestic settlement requires local establishment
Use for legal and contracting depth.
Domestic Merchant IDs Explained
Anchor suggestions:
domestic merchant IDs
MID and settlement configuration
Use when discussing how merchant accounts and settlement structures connect.
Additional useful links
Local Acquiring vs Cross-Border Acquiring
Can You Access Local Acquiring Without Incorporating?
Local Acquirers by Country
Payment Reconciliation Explained
Payment Orchestration for International Expansion
Authoritative Source Recommendations
Maintain current versions of:
Visa Core Rules
Visa Global Acquirer Risk Standards
Mastercard Rules
Mastercard Transaction Processing Rules
BIS Committee on Payments and Market Infrastructures cross-border payment work
IMF cross-border payment and FX research
National central-bank settlement-system documentation
National FX authorities where repatriation is material
Acquirer merchant-funding agreements
Approved PSP settlement documentation
Merchant treasury-bank FX documentation
The BIS is particularly useful for background on the relationship between payment-system operating hours, cross-border settlement, liquidity, and settlement risk. (Bank for International Settlements)
Proposed Author and Human Review
Author
Payments finance or payment-strategy lead
Should have experience in:
Acquiring
Settlement
Merchant finance
Payment economics
Do not invent a credential.
Required reviewer: Treasury specialist
Review:
Cash-use assumptions
Natural hedging
FX
Repatriation
Liquidity
Working capital
Required reviewer: Payments finance analyst
Review:
Settlement calculations
Net usable revenue
Fee treatment
Cost attribution
Required reviewer: Reconciliation specialist
Review:
Batch model
Net settlement
Bank matching
Exception metrics
Required reviewer: Acquiring specialist
Review:
Clearing
Network settlement
Acquirer settlement
PSP payout terminology
Conditional reviewers
Legal/compliance
When:
Repatriation
Local-account requirements
Restricted markets
Marketplace funds
are discussed specifically.
Tax
When entity, withholding, intercompany funding, or repatriation tax consequences materially affect the example.
Acquiring Fact-Check Items
Verify:
Acquirer
Merchant entity
Merchant account
MID
Capturing entity
Network settlement structure
Settlement terms
Reserve
Refund funding
Chargeback deductions
Merchant payout path
Settlement Fact-Check Items
Verify:
Settlement country
Network settlement currency
Acquirer settlement currency
PSP balance currency
Merchant payout currency
Payout country
Settlement cycle
Bank-credit timing
Minimum payout
Holiday treatment
Gross/net settlement
Reserve timing
Negative balance handling
FX Fact-Check Items
Verify:
FX provider
Conversion stage
Reference rate
Rate source
Rate timestamp
Spread
Explicit fee
Weekend pricing
Refund FX
Chargeback FX
Treasury conversion alternative
Country-Specific Fact-Check Items
For any country example added before publication, confirm:
Currency controls
Local settlement availability
Local bank requirements
Merchant entity
Foreign ownership rules where relevant
Repatriation
Settlement restrictions
Tax
Withholding
Local-currency account structure
Provider eligibility
Do not infer one market’s rules from another.
Entity and Regulatory Fact-Check Items
Before stating that local settlement requires an entity, determine whether the requirement comes from:
Law
Regulator
Acquirer
PSP
Bank
FX regime
Tax
Commercial policy
Similarly, before stating that offshore payout is allowed, verify:
Provider contract
Currency
Country
Merchant category
Bank destination
Current legal rules
This article provides general information and does not constitute legal, regulatory, tax, accounting, or treasury advice. Merchants should confirm applicable obligations and operating requirements with qualified advisers, acquiring partners, banks, and relevant authorities.
Amber-Flag Claims
Require direct evidence before publishing claims such as:
“Local settlement eliminates FX.”
“Local settlement is cheaper.”
“International settlement costs X% more.”
“A local bank account is required.”
“A local entity is required.”
“Funds can be freely repatriated.”
“This provider settles in local currency.”
“This market supports offshore settlement.”
“Funds settle in T+1.”
“Domestic acquiring automatically creates domestic settlement.”
“Local MID means local settlement.”
“International payout creates two FX events.”
“Local settlement improves working capital.”
All can be true under particular structures.
None should be treated as universal.
Local acquiring
Settlement currency
Local-currency balances
Merchant payout currencies
Payout countries
Settlement frequency
Settlement timing
FX methodology
FX spread or pricing framework
Multicurrency support
Local bank-account requirements
Local entity requirements
Reserves
Net/gross settlement
Refund funding
Chargeback deductions
Reconciliation files
Settlement APIs
Marketplace settlement
Seller payouts
Repatriation support
Any treasury-management features
Any quantified FX savings
Any quantified settlement improvement
Do not convert:
into:
without verification.
Provider-Specific Verification Template
Provider:
Country:
Merchant entity:
Acquirer:
MID:
Transaction currency:
Processing currency:
Network settlement currency:
Provider ledger currency:
Merchant settlement currency:
Payout currency:
Payout country:
Bank-account requirement:
Local-entity requirement:
Settlement schedule:
Reserve:
FX provider:
FX reference rate:
FX spread:
Payout fee:
Refund funding model:
Chargeback treatment:
Repatriation responsibility:
Settlement report:
Bank reconciliation key:
Production verified:
Last reviewed:
Cluster Sameness-Audit Fields
Title
Local Settlement vs International Settlement: Currency, Treasury, and Merchant Cash Flow
Opening
Two merchants process the same 100-unit local-currency payment but receive the money in different places and currencies.
Primary format
Flow-of-funds and treasury comparison.
Unique evidence anchor
The same successful transaction can produce different merchant economics depending on where the cash ultimately needs to be used.
Editorial position
Settlement destination should follow cash-use destination rather than customer country.
Merchant decision
Whether to keep payment proceeds locally, centralize them internationally, or operate a hybrid treasury model.
Main analytical unit
Movement of 100 local-currency units from customer payment to usable merchant cash.
Original framework
The Settlement Destination Decision Model.
Original visual
Local Settlement vs International Payout flow-of-funds diagram.
Primary metrics
Net usable revenue
Settlement delay
FX cost
Working-capital days
Trapped cash
Reconciliation exception rate
Conclusion
Retain currency where it is economically useful; centralize cash where the benefits of concentration exceed the cost of conversion and local liquidity loss.
Closing element
Settlement terminology glossary and treasury worksheet rather than a generic FAQ.
Topics intentionally owned elsewhere
Full local-acquiring definition
Local vs cross-border authorization
Acquirer availability by country
Detailed local-entity requirements
Domestic MID architecture
Full acquiring-fee decomposition
The uploaded brief’s most important discipline is worth preserving in publication: a flow should never be described simply as “local settlement” without separately documenting the settlement country, settlement currency, payout country, payout currency, FX stage, and merchant cash destination. That six-field description makes the economics much harder to misinterpret.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗