FX Costs by Market - European Central Bank, Fuze Finance, IFX Payments

FX Costs by Market: How Merchants Should Prioritize Currency-Pair and Settlement Optimization

Put your revenue map next to your FX-cost map

A global merchant's sales dashboard might show its strongest regions in dark green.

North America dominates.

Western Europe follows.

Several Asian markets are growing quickly.

Now build a second map.

This one shows:

merchant FX expense.

The colors may not match at all.

A country responsible for 15% of sales might create only 3% of FX expense.

Another responsible for 5% of sales might create 18% of it.

A market with substantial customer volume might require almost no conversion because transaction and expense currencies already align.

A smaller market might convert nearly every unit of revenue through an expensive settlement path.

That is the first principle of analyzing FX costs by market:

Revenue share and FX-cost share are different portfolios.

Treasury should not automatically work down a list of countries sorted by sales.

It should work down a list of currency flows sorted by addressable economic cost.

A country is often the wrong unit for FX analysis

Consider what “the German market” could mean financially.

A merchant might have:

•customers in Germany;

•prices displayed in EUR;

•transactions presented in EUR;

•EUR card processing;

•settlement in EUR;

•EUR operating expenses;

•a parent company's reporting currency in USD.

Where is the FX cost?

Perhaps there is none at the payment stage.

There may be conversion only when excess EUR cash is moved to the group's USD treasury balance.

Now consider another merchant selling to the same German customers.

Its flow might be:

EUR transaction → USD settlement

The geographic customer market is identical.

The FX path is not.

Therefore:

country alone does not define merchant FX economics.

The better unit is market + currency pair + settlement structure

For market-level FX analysis, use a three-part unit.

•Transaction or commercial market

Where does the relevant customer/payment activity originate?

•Currency pair

Which source currency is actually being converted into which destination currency?

•Settlement structure

At what point does the conversion happen, and where do the proceeds ultimately go?

So instead of:

Germany

an analytical row might be:

**German customer market

•EUR → USD

•automatic USD settlement**

Another could be:

**German customer market

•EUR retained

•EUR bank settlement**

Those are economically different payment flows.

The brief explicitly recommends defining market FX analysis through market + currency pair + settlement structure, rather than ranking countries alone.

Start by mapping where currency actually changes

Before comparing countries, map the payment flow.

A merchant can have several currency layers:

Customer price

→ transaction/presentment currency

→ processing currency

→ settlement currency

→ merchant balance currency

→ payout currency

→ expense/reporting currency

Not every arrow creates FX.

Every arrow where the currency changes potentially does.

For market prioritization, the relevant question is:

How much economic value crosses each currency boundary during the year?

Measure conversion volume—not just market revenue

Suppose a merchant generates:

$200 million equivalent

of sales in one market.

Only 10% requires currency conversion.

Converted volume:

$20 million equivalent.

Another market generates:

$80 million

of sales.

Nearly all of it converts.

Converted volume:

$80 million.

The second market represents four times as much FX notional despite producing less than half the revenue.

That is why the first meaningful metric is:

Monthly or annual conversion volume

Value actually subjected to an FX event

rather than:

total sales in the country.

Track conversion volume by currency pair

Aggregate actual conversion notional into pairs such as:

•EUR → USD

•GBP → USD

•CAD → USD

•AUD → USD

•JPY → USD

•PLN → EUR

•CZK → EUR

•SGD → USD

These are examples, not recommendations about which currencies a merchant should convert.

Then determine:

•annual source-currency volume;

•actual destination currency;

•conversion stage;

•converting party;

•rate methodology;

•explicit fees;

•settlement path.

A market can produce several currency pairs.

A currency pair can also appear across several customer markets.

This is why country-level totals alone are insufficient.

Measure actual merchant FX cost

Do not use an advertised spread as the portfolio baseline unless it actually describes the merchant's commercial arrangement.

For every material conversion event capture:

•source currency;

•source amount;

•destination currency;

•actual destination amount;

•converter;

•conversion timestamp;

•applied rate;

•reference benchmark;

•explicit FX fee;

•other attributable conversion charge.

Then calculate the economic result.

Benchmark converted amount

For the relevant source amount:

source amount × appropriately normalized benchmark rate

subject to the correct quote direction.

Actual merchant converted amount

Use the amount actually received after the conversion and any FX charges intentionally included in the calculation.

Measured FX cost

Benchmark converted amount − actual converted amount

Effective FX cost %

Measured FX cost ÷ benchmark converted amount

× 100

State the benchmark and methodology.

Do not describe the result automatically as:

provider profit

or:

hidden markup.

It is a measured difference relative to the selected reference.

Use reference rates as benchmarks—not promises

Reference-rate discipline matters particularly in a market comparison.

Suppose the merchant measures:

EUR → USD

using one timestamp and:

PLN → EUR

using another.

That can be legitimate.

But the benchmark methodology must be consistent within each conversion.

The ECB currently publishes euro reference rates each working day and says they are intended for informational purposes rather than transaction execution.

So an ECB rate can help answer:

How did the merchant's actual result compare with an official reference at an aligned time?

It cannot prove:

This is the exact rate the PSP should have provided.

Time matters when comparing FX costs by market

Exchange rates move.

A market can look expensive simply because the benchmark was taken at the wrong time.

Compare:

•the same currency pair;

•the same direction;

•the same or closely aligned timestamp;

•the same conversion event;

•similar conversion size where commercial tiers matter.

Do not compare:

the provider's settlement conversion at 16:00

against:

a public benchmark from 09:00

and call the entire difference a spread.

If the provider's exact rate timestamp is unknown, record that as a data limitation.

Calculate FX cost by currency pair

For each pair:

Annual FX cost

Sum of measured FX cost across conversion events for that pair

Then calculate:

Share of total merchant FX expense

FX cost for pair ÷ total measured FX cost

This often produces a different priority ranking from revenue.

That is the ranking treasury needs.

Revenue share versus FX-cost share

A useful portfolio table is:

Market / currency path

Share of merchant revenue

Share of conversion volume

Share of FX expense

Market/currency path 1

Market/currency path 2

Market/currency path 3

Market/currency path 4

The most interesting rows are those where:

FX-cost share materially exceeds revenue share.

That does not automatically mean the market is inefficient.

It means the row deserves investigation.

High conversion volume does not automatically mean high optimization value

A currency path might represent enormous volume but have:

•efficient pricing;

•strong settlement availability;

•useful same-currency expenses;

•little realistic room for improvement.

Another path can have lower volume but a material spread and an easy settlement alternative.

So:

conversion volume identifies scale.

It does not identify addressable waste.

High spread does not automatically mean high optimization value either

Suppose a niche currency pair carries a relatively expensive effective conversion cost.

If annual converted volume is:

$50,000 equivalent,

the total economic opportunity might still be immaterial.

Meanwhile, a relatively efficient pair converting:

$500 million

could make a 10-basis-point commercial improvement economically significant.

This is why FX optimization needs both:

unit cost

and:

volume.

Weighted FX cost is better than a simple average of spreads

Do not average:

•0.4%

•0.8%

•1.6%

and call:

0.93%

the merchant's global FX cost unless the underlying volumes are identical.

Instead calculate:

Weighted effective FX cost

Total measured FX cost across included pairs

÷

total benchmark-converted economic value

This gives large currency flows the appropriate financial weight.

The brief explicitly requires weighting rather than taking unweighted averages across currency pairs.

Now identify what explains the market difference

Once the expensive currency pairs are visible, investigate why.

Potential drivers include:

•provider pricing;

•transaction size;

•currency pair;

•settlement availability;

•payout currency;

•banking conditions;

•automatic conversion;

•commercial contract tier;

•market liquidity;

•convertibility constraints;

•regulatory requirements;

•merchant account structure.

Do not attribute everything to “the FX market.”

Market liquidity can help explain conditions—but it does not tell you your PSP spread

Global FX activity is highly concentrated.

The BIS's 2025 Triennial Survey reported average global FX turnover of $9.6 trillion per day in April 2025. It found the U.S. dollar on one side of 89.2% of transactions, while the euro and yen represented substantially smaller shares.

That tells merchants something important:

currency markets differ dramatically in trading depth and structure.

But it does not tell a merchant:

•what its PSP charges;

•what spread its bank applies;

•what settlement structure is available;

•whether its negotiated rate is competitive.

Wholesale-market liquidity is an explanatory factor.

Merchant pricing is a commercial fact.

Keep those two statements separate.

Do not create a “liquid currencies are cheap” rule

It is tempting to infer:

major currency = low merchant FX cost

and:

less-traded currency = high merchant FX cost.

That can fail.

Merchant FX cost also depends on:

•PSP commercial pricing;

•volume tier;

•source/destination direction;

•conversion timing;

•settlement model;

•balance structure;

•banking route;

•explicit fees.

A large merchant can potentially negotiate favorable terms on a meaningful currency flow.

A small merchant can potentially pay a relatively wide commercial spread even on a globally liquid pair.

Measure the merchant result.

Settlement availability can matter more than the country itself

Suppose a market generates revenue in:

CAD.

If the merchant can settle CAD and has a CAD bank account, the currency may be retained.

If the current payment arrangement converts all CAD to USD automatically, there is a payment-stage FX event.

If another viable structure permits CAD settlement, the merchant can compare:

Current path

CAD → USD

versus:

Alternative path

CAD retained

The relevant market-cost opportunity is not:

“Canada has expensive FX.”

It is:

“Our current Canadian payment flow converts CAD even though a viable CAD settlement structure may exist.”

That is far more actionable.

Presentment support does not prove settlement support

A merchant may be able to charge customers in many currencies.

That does not necessarily mean it can receive merchant settlement in all of them.

The article should therefore separate:

customer-facing currency

from:

processing currency

from:

settlement currency.

That means market-level FX analysis must inspect the merchant's actual acquiring configuration rather than infer merchant settlement economics from the checkout currency.

Automatic conversion can create concentrated FX expense

A merchant may have dozens of transaction currencies but only one settlement currency.

That can simplify operations.

It can also mean certain high-volume transaction currencies are converted automatically every day or settlement cycle.

For each automatically converted currency, ask:

•What annual volume is converted?

•At what effective cost?

•Can the currency be retained?

•Is another settlement currency supported?

•Does the merchant have expenses in that currency?

•What would a different account structure cost?

This often identifies market-specific FX opportunities without requiring a global treasury redesign.

Same-currency expenses can change the ranking

Suppose the merchant receives substantial:

EUR revenue

and also pays:

•European staff;

•suppliers;

•marketing platforms;

•logistics providers;

in EUR.

If the merchant automatically converts all EUR into USD and later buys EUR again to meet those obligations, the true optimization opportunity may not be:

negotiate a slightly lower EUR/USD spread.

It may be:

reduce how much EUR is converted at all.

This is a payment-flow and treasury question.

Natural currency offsets can reduce conversion volume

Where legally and operationally appropriate:

same-currency revenue

can potentially fund:

same-currency costs.

This can reduce the notional that needs conversion.

It is sometimes described as a natural currency offset or natural hedge.

But merchants must account for:

•entity ownership;

•timing;

•banking structure;

•intercompany arrangements;

•regulation;

•tax;

•accounting policy;

•treasury controls.

This article identifies the potential conversion-cost effect.

It does not provide tax, accounting, investment, or legal advice.

Add same-currency expense offset to the market matrix

For every major currency:

Gross conversion volume

How much payment value enters the currency?

Then:

Potential same-currency use

How much could potentially fund legitimate same-currency expenses, subject to merchant structure and policy?

Then:

Net conversion requirement

Gross currency proceeds − approved same-currency use

This can materially change which currency deserves treasury attention.

A country can have high revenue and low FX exposure

Imagine the merchant sells extensively in a euro-area market.

Its customer transactions are EUR.

It settles EUR.

It also has large EUR operating expenses.

Very little economic value needs to leave EUR.

The market may be strategically huge but have modest payment-related FX cost.

Labeling it:

“high FX priority because Europe is our second-largest region”

would be poor treasury analysis.

A smaller market can create disproportionate FX expense

Now imagine another market:

•lower revenue;

•nearly all transactions convert;

•limited settlement choices;

•no same-currency expenses;

•a higher effective merchant spread.

The absolute FX expense can exceed that of the much larger market.

This is precisely why the article's core framework uses:

conversion volume + effective cost + settlement alternatives

rather than revenue rank.

Provider pricing can differ by currency pair

Do not assume:

our PSP FX spread is 70 bps

means:

every currency pair costs 70 bps.

Provider pricing can vary with:

•pair;

•volume;

•merchant size;

•contract;

•geography;

•conversion timing;

•settlement arrangement.

The relevant source is the merchant's:

•signed commercial terms;

•rate methodology;

•settlement statement;

•actual conversion result.

The brief specifically warns against assuming a single PSP spread applies across every currency.

Public pricing is not necessarily enterprise merchant pricing

When researching FX costs by country, merchants may encounter publicly advertised rates.

Treat them carefully.

The merchant's actual rate can be:

•individually negotiated;

•volume-tiered;

•method-specific;

•account-specific;

•settlement-specific.

Do not build an enterprise business case using a retail or generic public rate unless that rate genuinely applies to the merchant.

Use actual converted amounts whenever possible

Rate quotations are easy to mishandle because currency pairs can be expressed in opposite directions.

For example:

EUR/USD

and:

USD/EUR

are reciprocal representations.

Instead of relying only on displayed rates, reconstruct:

source amount → actual destination amount

That reduces quote-direction errors and incorporates explicit conversion charges where the calculation is designed to include them.

The closest nominal rate may not create the best final result

A conversion can include:

•quoted rate;

•embedded spread;

•explicit percentage fee;

•fixed fee;

•settlement charge;

•another conversion later.

So compare the merchant's:

All-in effective conversion rate

final destination amount after included FX charges ÷ source amount

against the defined benchmark.

Do not rank PSPs by one displayed exchange-rate number without holding the entire currency path constant.

The dedicated How to Compare PSP Exchange Rates article should own the full provider-comparison methodology.

Convertibility constraints can override spread optimization

Not every currency is freely interchangeable through every payment and banking structure.

Depending on jurisdiction, merchants can encounter:

•capital controls;

•conversion restrictions;

•local settlement requirements;

•documentation requirements;

•limits on offshore movement;

•bank-account rules.

These can create materially different settlement economics.

Do not treat such constraints as permanent universal facts.

Verify them for:

jurisdiction + currency + entity + transaction type + effective date.

A constrained market should not automatically be labeled “bad FX”

If a currency is operationally difficult to settle or convert, the observed cost can reflect more than provider markup.

Possible contributors can include:

•banking infrastructure;

•settlement restrictions;

•limited available routes;

•compliance requirements;

•currency accessibility.

The merchant can still evaluate the cost.

But the available lever may be smaller.

That could shift the opportunity from:

Optimize now

to:

Monitor

or:

No viable alternative currently.

Market constraints can make a higher-cost route economically rational

Suppose a merchant has two theoretical options.

One offers a lower apparent spread but requires:

•another legal entity;

•additional banking;

•local reporting;

•more reconciliation;

•new treasury operations.

The current higher FX cost may still be economically sensible at the merchant's volume.

That is why the matrix must include:

operational effort.

Do not optimize spread independently of settlement

A market can have:

attractive rate pricing

but:

poor settlement fit.

For example, the merchant may receive a currency it then immediately has to convert again.

Conversely, a provider with a slightly wider first-stage FX spread could offer settlement that eliminates an entire later conversion.

The merchant should compare the complete path.

This is where FX Costs by Market connects to:

•Multi-Currency Settlement;

•Avoiding Double Currency Conversion;

•Presentment vs Settlement Currency.

It should not duplicate those articles.

Build the FX Cost by Market Matrix

For every economically meaningful market/currency path, record:

Dimension

Merchant input

Customer / transaction market

[actual]

Transaction currency

[actual]

Processing currency

[where relevant]

Settlement currency

[actual]

Final required currency

[actual]

Monthly conversion volume

[actual]

Effective FX cost

[calculated]

Annual FX expense

[calculated]

Share of total FX expense

[calculated]

Settlement alternatives

[verified]

Same-currency expenses

[finance input]

Convertibility / regulatory constraint

[verified]

Provider flexibility

[verified]

Operational effort

[estimated]

Expected net savings

[modeled]

Optimization priority

[decision]

This is the article's central practical asset.

The matrix should rank opportunities, not countries

After completing the data, assign one of six actions.

Optimize now

Use when:

•FX expense is material;

•converted volume is material;

•an alternative exists;

•implementation complexity is manageable;

•evidence quality is high.

Examples could include:

•renegotiating a material pair;

•changing an unnecessary automatic conversion;

•switching settlement currency within an existing setup.

Negotiate

Use when the main problem is:

commercial FX pricing

rather than settlement architecture.

Evidence should show:

•substantial volume;

•measurable spread;

•otherwise acceptable currency path.

Change settlement structure

Use when:

•the existing settlement currency causes avoidable conversion;

•a viable alternative settlement currency is available;

•the net benefit exceeds the added operational cost.

Hold or use locally

Use when:

•revenue and expenses exist in the same currency;

•settlement can be retained;

•entity/banking rules permit it;

•the natural offset has meaningful economic value.

This is not a recommendation to accumulate speculative FX positions.

It is an operating-currency decision.

Monitor

Use when:

•the cost is real;

•current economic value is small;

•market or volume growth could change the answer later.

Low priority

Use when:

•absolute cost is immaterial;

•there is little actionable alternative;

•optimization complexity overwhelms likely savings.

Low priority is a valid outcome.

Add data confidence to every market

A matrix should never disguise uncertainty.

Classify evidence:

High confidence

Actual:

•settlement statements;

•timestamps;

•conversion amounts;

•merchant rates;

•annual volume.

Medium confidence

Reliable actual cost but incomplete benchmark or settlement-alternative information.

Low confidence

Quoted commercial estimates or assumed conversion behavior.

Do not approve structural FX changes on low-confidence evidence simply because the modeled savings look large.

Calculate the annual optimization opportunity

For each pair:

Baseline annual FX cost

Measured under the current structure.

Then:

Proposed annual FX cost

Using an evidence-supported alternative.

Then:

Gross FX savings

Baseline FX cost − proposed FX cost

Then subtract:

•new account fees;

•banking expense;

•provider expense;

•reconciliation;

•operating effort;

•implementation cost according to the merchant's chosen methodology.

Net FX benefit

Gross FX savings − incremental operational cost

This is the economic number that should drive market priority.

The brief explicitly requires net benefit rather than presenting benchmark improvement as pure merchant savings.

Consider implementation payback

Where meaningful:

Payback period

Implementation cost ÷ monthly net recurring FX saving

A market showing a large spread improvement may still deserve lower priority if:

•implementation is expensive;

•converted volume is small;

•payback is long.

A smaller spread change on a very large currency flow can produce a much stronger project.

Create a portfolio priority score

The merchant can score each market/currency path using its own thresholds.

Suggested dimensions:

Factor

Low priority

High priority

Conversion volume

Small

Large

Effective FX cost

Low

High

Annual FX expense

Small

Material

Addressable share

Low

High

Settlement alternative

None

Clear

Same-currency expense use

None

Material

Regulatory friction

High

Low

Provider flexibility

Low

High

Operating complexity

High

Low

Data confidence

Weak

Strong

Do not create arbitrary universal cutoffs.

A threshold that is material to a $50 million merchant may be irrelevant to a company processing billions.

Rank by net addressable FX expense

A particularly useful metric is:

Net addressable FX expense

Current annual FX expense

× estimated addressable proportion

− incremental operating cost

This is more useful than:

current spread

alone.

Why?

Because some portions of FX cost may not be economically removable.

A market with a 1.2% effective cost but no viable alternative can have less addressable value than a market costing 0.5% with substantial negotiable markup.

Separate “high FX cost” from “bad FX structure”

This distinction matters.

A merchant may have high absolute FX expense because:

•its international business is huge.

That does not prove pricing is poor.

Likewise a tiny market may have:

•an unattractive spread;

but still contribute negligible annual expense.

The optimization framework needs three questions:

•How much does it cost?

•Why does it cost that much?

•How much of that cost can realistically be changed?

Global FX optimization is often a Pareto-like portfolio problem—but measure before assuming

The merchant may discover that a few pairs create a large share of expense.

That would be consistent with the brief's concentration thesis.

But do not assert:

“80% of FX costs always come from 20% of markets.”

There is no universal merchant distribution.

Calculate:

Pair share of total FX expense

and sort descending.

Then observe the actual concentration.

Build a cumulative FX-cost curve

A useful treasury visual is:

x-axis: currency pairs ranked by annual FX cost

y-axis: cumulative share of merchant FX expense

This answers:

How many currency paths account for 50%, 75%, or 90% of measured FX expense?

It can also show whether the merchant has:

Concentrated FX economics

A few pairs dominate.

or:

Distributed FX economics

Many pairs each contribute meaningful expense.

The optimization strategy should differ.

Concentrated portfolios deserve targeted optimization

If five pairs create most expense, treasury can deeply analyze:

•rate;

•settlement;

•balance;

•local expenses;

•provider terms;

for those five.

There is little need to redesign 60 low-volume currencies simultaneously.

Distributed portfolios may favor platform-level improvements

If dozens of currencies contribute similar amounts of cost, pair-by-pair negotiation becomes operationally inefficient.

That may make broader changes more attractive, such as:

•improved global FX commercial terms;

•different settlement architecture;

•a more flexible multi-currency structure;

•reporting improvements.

The portfolio shape should inform the intervention.

PSP negotiation should use currency-pair economics

Do not go to a provider with:

“We process $2 billion globally, reduce our FX rate.”

Bring:

•annual conversion volume by pair;

•average transaction/settlement size;

•current effective cost;

•current rate methodology;

•same-currency settlement alternatives;

•growth forecast;

•priority pairs.

This can focus a pricing discussion on the economically meaningful flows.

Do not guarantee negotiability.

Those Terms establish that FX can be an identifiable component of merchant economics.

They do not publicly establish a universal:

•FX spread;

•rate methodology;

•currency-pair price;

•settlement structure;

•market ranking.

Those should remain account- and contract-specific.

Its credit-card documentation says processing currencies depend on acquiring banks.

These are examples of payment-method processing currencies.

They are not enough to infer:

•final merchant settlement currency;

•FX spread;

•payout currency;

•merchant-specific conversion cost.

Those require separate verification.

Reporting is part of FX optimization

A merchant cannot manage market-level FX cost without reliable transaction data.

That can be relevant to the measurement layer of an FX-cost program.

•transaction currency;

•converted amount;

•settlement currency;

•exchange rate;

•FX fee;

•payout currency;

•method;

•market;

•acquirer.

Do not infer those fields merely from general reporting availability.

Refund FX should influence market priority only where economically material

Markets with high refund activity can generate another currency flow.

The original sale may:

convert Currency X → Currency Y

while the refund later requires:

Currency Y → Currency X

or another settlement adjustment.

That can increase total currency conversion cost.

However, the detailed mechanics belong in Currency Conversion for Refunds.

For this article, add one market-level metric where relevant:

Refund-related FX cost

Then include it only if it materially changes the market's prioritization.

Double conversion should also be a flag—not the whole article

If one market follows:

BRL → USD → EUR

while the merchant ultimately needs EUR, that path may contain unnecessary sequential conversion.

Flag:

Double-conversion risk: yes

in the matrix.

Then link to Avoiding Double Currency Conversion for the diagnostic.

This article should only ask whether the extra conversion materially increases that market's total FX-cost ranking.

FX exposure is not the same as FX conversion cost

A merchant can hold foreign currency without converting it.

While held, the economic value can change relative to the merchant's reporting currency.

That is:

currency exposure.

The spread paid at actual conversion is:

conversion cost.

Do not add market movement automatically to the PSP's FX fee.

Where holding currency is proposed as an optimization, treasury should separately evaluate exposure.

The dedicated Managing Payment FX Exposure article owns that decision in depth.

Operational simplicity deserves an explicit price

Suppose converting everything to USD creates:

•one settlement currency;

•one reconciliation model;

•fewer accounts;

•simple treasury reporting.

It may cost more in FX than maintaining several currencies.

The merchant should quantify both sides.

FX benefit of additional currency balances

versus:

Operational cost of maintaining them

This prevents the organization from saving 15 basis points while creating a much more expensive finance operation.

Smaller merchants may rationally accept wider FX economics

For a smaller international merchant:

•one settlement currency;

•automatic conversion;

•simple finance processes;

can be valuable even if the spread is somewhat higher.

The fixed operational cost of sophisticated treasury infrastructure may overwhelm the possible FX saving.

Larger merchants can justify more pair-level optimization

At greater conversion volumes, merchants may justify:

•negotiated pair-specific pricing;

•multiple currency balances;

•multi-currency settlement;

•local banking;

•treasury coordination;

•direct bank relationships.

Small basis-point differences can become financially meaningful.

But the same rule applies:

complexity needs to earn its keep.

The FX Cost by Market Matrix

A practical completed version should look conceptually like this:

Market / path

Conversion volume

Effective FX cost

Annual FX cost

Cost share

Alternative

Same-currency use

Constraint

Operational effort

Action

Market path 1

High

Medium

High

High

Clear

Medium

Low

Low

Optimize now

Market path 2

High

High

High

High

Current provider pricing

Low

Low

Low

Negotiate

Market path 3

Medium

Medium

Medium

Medium

Retain currency

High

Low

Medium

Hold/use locally

Market path 4

Medium

High

Medium

Medium

New settlement structure

Low

Medium

High

Validate structure

Market path 5

Low

High

Low

Low

Limited

Low

High

High

Monitor

Market path 6

Low

Low

Low

Low

Irrelevant

Low

—

—

Low priority

Do not populate this matrix with generic global spread assumptions.

Use merchant data.

Add expected net savings

For each actionable row:

Current annual conversion cost

−

Expected alternative annual conversion cost

=

Gross FX savings

Then:

Gross FX savings

− new provider costs

− banking

− account cost

− reconciliation

− incremental treasury/operations

=

Expected net savings

Rank the rows again.

The second ranking can differ substantially from the first.

Re-rank after implementation cost

Suppose Market X has:

$1 million gross annual FX opportunity

but needs:

$800,000 of additional annual infrastructure and operating cost.

Net:

$200,000.

Market Y has:

$500,000 gross opportunity

and:

$50,000 incremental cost.

Net:

$450,000.

Market Y should probably receive treasury attention first, all else equal.

That is exactly why:

high FX cost

and:

high optimization priority

are not synonyms.

Re-measure after every change

When pricing or settlement changes, remeasure:

•actual conversion volume;

•actual destination amount;

•effective FX cost;

•annualized cost;

•settlement currency;

•number of conversion events;

•same-currency usage;

•operational expense.

Do not declare a project successful because:

the contractual spread fell.

Verify:

the merchant's total FX expense fell on comparable currency flows.

Use the same methodology before and after

If the pre-change benchmark uses:

ECB 14:10-related reference methodology

while the post-change analysis uses:

a different intraday market snapshot,

the calculated savings can be distorted.

Use a consistent method.

Where market data differs, document it.

The ECB itself makes clear that its published reference rates are informational averages and not transaction prices, reinforcing why methodological consistency matters more than pretending one public number is a universal executable rate.

Market portfolio scenario 1: Huge sales, little FX work to do

The revenue map shows one region dominating sales.

Treasury maps the flow and discovers:

•transactions occur in a major operating currency;

•proceeds settle in that currency;

•local costs consume a substantial amount;

•only residual balances are converted;

•effective FX pricing on that residual is acceptable.

Portfolio classification: Monitor.

The biggest market is not automatically the biggest FX project.

Market portfolio scenario 2: Moderate sales, expensive automatic conversion

A smaller region contributes modest revenue.

But:

•nearly every transaction is converted;

•the settlement currency differs from the operating requirement;

•no meaningful local expenses offset the currency;

•annual conversion notional is still material;

•the provider spread is measurable;

•another settlement structure appears viable.

Portfolio classification: Validate settlement change / optimize.

The smaller country can outrank the larger revenue market.

Market portfolio scenario 3: The spread looks expensive, but there is no economical alternative

A currency flow has:

•relatively high measured FX cost;

•limited settlement availability;

•material regulatory or banking constraints;

•small annual volume;

•high complexity for an alternative setup.

Portfolio classification: Monitor or low priority.

A high percentage does not force action.

Market portfolio scenario 4: The best FX project is to stop converting so much

The merchant receives substantial proceeds in one currency.

It also pays major suppliers in the same currency.

Yet treasury automatically converts all proceeds into the group base currency, then buys the operating currency again later.

The key project is not:

find the lowest spread.

It is:

reduce unnecessary gross conversion volume, subject to entity, treasury, accounting, tax, legal, and banking feasibility.

Portfolio classification: Hold/use locally or redesign settlement.

Market portfolio scenario 5: The PSP spread is not the biggest problem

A market appears expensive.

The diagnostic finds:

transaction currency → settlement currency → payout currency

with two conversion events.

Negotiating 10 basis points from the first spread leaves the second conversion intact.

Portfolio classification: Investigate double conversion.

The right lever is payment-flow design, not merely pricing.

Market portfolio scenario 6: The pair is efficient, but the volume makes small savings material

The merchant's largest conversion pair already has relatively efficient pricing.

But annual notional is enormous.

Even a small verified reduction can produce significant absolute savings.

Portfolio classification: Negotiate.

A low spread can still deserve attention at sufficient scale.

Merchant market-research checklist

Use this checklist before assigning an FX optimization project to a country.

Market definition

•What customer/transaction market are we studying?

•What transaction currency is used?

•Is customer country actually relevant to the FX event?

•What legal entity owns the transaction?

•What PSP/acquirer handles it?

Currency path

•What is the processing currency?

•What is the settlement currency?

•What is the merchant balance currency?

•What is the payout currency?

•What currency does the merchant ultimately need?

•How many currency boundaries does the value cross?

Conversion volume

•What monthly volume is actually converted?

•What annual volume is converted?

•What percentage of market revenue undergoes FX?

•Which currency pairs represent the most notional?

FX cost

•What actual source amount was converted?

•What actual destination amount was received?

•What rate was applied?

•At what timestamp?

•What benchmark is being used?

•Is there an explicit FX fee?

•Is pricing embedded in the rate?

•What is the effective FX cost?

•What is total annual FX expense?

Portfolio concentration

•What share of global FX expense comes from this pair?

•How does FX-cost share compare with revenue share?

•Where does the pair rank by annual FX cost?

•Where does it rank by addressable FX cost?

Settlement alternatives

•Can the transaction currency be retained?

•Is same-currency settlement supported?

•Can another settlement currency be selected?

•Would the alternative create another payout conversion?

•Does the merchant already maintain an appropriate bank account?

•Is another entity required?

Same-currency use

•Does the merchant have material expenses in this currency?

•Could proceeds legally and operationally fund those expenses?

•Does timing allow the offset?

•Would retaining the balance create unwanted exposure?

Market constraints

•Is the currency freely convertible for the required structure?

•Are there capital or exchange controls?

•Are local settlement requirements relevant?

•Are there banking/documentation requirements?

•Has current jurisdiction-specific guidance been checked?

PSP/provider pricing

•Is the FX pricing public or merchant-specific?

•Does pricing differ by currency pair?

•Does it differ by volume?

•Is the spread negotiable?

•Does the provider offer another settlement route?

•Are actual conversion fields available in reporting?

Economics of change

•What is current annual FX expense?

•What portion is realistically addressable?

•What is projected gross FX saving?

•What new provider/account costs arise?

•What banking cost arises?

•What reconciliation work is added?

•What treasury effort is added?

•What is expected net annual benefit?

•What is implementation payback?

•Is the data confidence sufficient to proceed?

Decision

Assign exactly one:

•Optimize now

•Negotiate

•Change settlement structure

•Hold/use locally

•Monitor

•Low priority

The key question is not:

“Which countries have expensive FX?”

It is:

“Which market + currency pair + settlement paths consume the most merchant value, and which of those costs can be removed economically?”

That is the distinction that turns a global FX-rate review into a treasury prioritization system.

Original framework: FX Cost by Market Matrix

Required fields

Market layer

•Customer/transaction market

•Merchant entity

•PSP/acquirer

•Payment method

Currency layer

•Transaction currency

•Settlement currency

•Final required currency

•Currency pair or sequence

Volume layer

•Monthly conversion volume

•Annual conversion volume

•Share of global converted volume

Cost layer

•Effective FX cost %

•Annual FX expense

•Share of global FX expense

•Explicit conversion charges where relevant

Alternative layer

•Settlement alternatives

•Same-currency expenses

•Potential retained balance

•Alternative provider/account structure

Constraint layer

•Convertibility constraints

•Regulatory/banking constraints

•Entity requirements

•Provider flexibility

Implementation layer

•Engineering effort

•Treasury effort

•Reconciliation effort

•Ongoing account/provider cost

Decision layer

•Gross FX savings

•Net FX benefit

•Data confidence

•Optimization priority

Measurement plan

Primary financial metrics

FX cost by currency pair

Actual measured FX expense for each material conversion pair.

FX cost by market

FX expense grouped by the defined market + pair + settlement structure.

Share of total FX expense

Market/pair FX cost ÷ total measured merchant FX expense

Weighted effective FX cost

Total measured FX cost ÷ total benchmark-converted value

Conversion volume

Value actually subjected to currency conversion.

Avoidable conversion volume

Converted value for which a viable lower-cost conversion or settlement path exists.

Gross FX savings

Current conversion cost minus proposed conversion cost.

Net FX benefit

Gross FX saving minus incremental operating/infrastructure cost.

Implementation payback

Where meaningful:

Implementation cost ÷ monthly recurring net saving

I’ve treated the new brief as the controlling assignment for Article 10: FX Costs by Market, the final market-intelligence piece in the Foreign Exchange cluster. I also incorporated the explicit cluster-wide instruction to vary openings and endings: this version opens with a revenue-map-versus-FX-cost-map problem and closes with portfolio scenarios plus a market-research checklist rather than another generic recommendation or FAQ.

Editorial package

Concise interpretation of the brief

Merchant FX-cost problem:

International merchants often organize FX decisions around countries or revenue size:

•biggest sales market;

•fastest-growing country;

•largest customer base;

•largest local entity.

But sales geography is not the same thing as FX economics.

A high-revenue country can create little merchant FX cost if:

•transactions already settle in a useful currency;

•the merchant has same-currency expenses;

•conversion pricing is relatively efficient;

•little value actually needs to cross a currency boundary.

A smaller market can generate disproportionately high FX expense if:

•most proceeds are converted;

•its currency pair carries a high effective merchant spread;

•settlement choices are limited;

•proceeds are converted more than once;

•the PSP applies different commercial pricing;

•the merchant has no natural use for the currency.

Article-owned cost:

The concentration of merchant FX expense across market + currency pair + settlement path.

Currency path:

This article does not assume one universal path. Each market should be reduced to:

transaction currency → processing/settlement currency → merchant-required currency

with every actual conversion measured.

Source currency:

Varies by transaction market.

Destination currency:

Varies by merchant settlement, payout, or treasury requirement.

Conversion stage:

Primarily transaction-to-settlement and settlement/payout conversion where those stages create market-specific cost.

Converting party:

PSP, acquirer, bank, payment-method operator, settlement provider, or another financial intermediary depending on the flow.

Rate/benchmark methodology:

Measure actual converted value against a defined, timestamp-aligned benchmark for the same pair, direction, and conversion event. Public central-bank rates can provide analytical reference points where appropriate, but should not be represented as rates commercially available to the merchant. The ECB, for example, states that its euro reference rates are informational and discourages their use as transaction rates.

Unique evidence anchor:

A merchant's FX expense is usually better understood as a portfolio than as a country ranking:

a relatively small number of high-volume or high-cost currency paths can account for a disproportionate share of total conversion expense.

Editorial position:

FX optimization should be prioritized by currency-pair economics and settlement path, not country revenue alone.

Common assumption challenged:

“The markets where we sell the most are automatically where FX optimization matters most.”

Merchant decision:

Identify which market/currency paths combine:

•material conversion volume;

•high effective FX cost;

•an actionable alternative;

•manageable operating complexity.

Optimize those first.

Selected format:

FX market prioritization matrix.

Structural principle:

Move from:

sales geography

to:

currency-flow economics

to:

measured cost concentration

to:

actionable settlement or pricing change.

The brief gives this article ownership of market/currency-pair prioritization rather than generic country FX tables.

Proposed architecture

•Put the revenue map next to the FX-cost map

•Why a country is the wrong analytical unit

•Define market + pair + settlement path

•Measure conversion volume

•Measure effective FX cost

•Calculate FX-cost share

•Understand what liquidity can—and cannot—tell you

•Identify settlement alternatives

•Account for same-currency expenses

•Identify convertibility and regulatory constraints

•Separate PSP pricing from market conditions

•Build the FX Cost by Market Matrix

•Rank markets by addressable economic value

•Calculate net savings

•Re-measure after change

•Market portfolio scenarios

•Merchant market-research checklist

SEO package

FX Costs by Market: How to Prioritize Currency Optimization

Alternative SEO title:

FX Costs by Country and Currency: Merchant Optimization Guide

H1:

FX Costs by Market: How Merchants Should Prioritize Currency-Pair and Settlement Optimization

Meta description:

Learn how to compare FX costs by market, currency pair, conversion volume, settlement path, effective spread, and net savings—and identify which international currency flows deserve optimization first.

URL slug:

/fx-costs-by-market

FX costs by market

Secondary keywords:

•FX costs by country

•payment FX costs by market

•currency conversion costs countries

•merchant FX rates by currency

•international payment FX costs

•PSP FX cost by country

•settlement currency cost

•cross border FX markets

Related entities and semantic terms:

•foreign exchange

•FX spread

•currency pair

•merchant FX fees

•settlement currency

•multi-currency settlement

•conversion volume

•PSP FX pricing

•weighted FX cost

•currency liquidity

•convertibility

•exchange controls

•natural currency offset

•international payments

•merchant treasury

Article excerpt:

The countries generating the most sales are not necessarily the markets generating the most foreign-exchange cost. Merchants should prioritize FX optimization by currency-pair conversion volume, effective FX cost, settlement path, actionable alternatives, and net economic benefit.

Suggested structured data:

Article + BreadcrumbList

No generic FAQ is recommended. The FX Cost by Market Matrix, portfolio scenarios, and market-research checklist better match the article's intelligence and prioritization intent.

Internal-link architecture

The brief prioritizes links to rate comparison, settlement, exposure, cross-border costs, and country payment intelligence.

How to Compare PSP Exchange Rates

Suggested anchor:

compare PSP exchange rates on a like-for-like basis

Link from benchmark and provider-pricing sections.

Multi-Currency Settlement and FX Costs

Suggested anchor:

multi-currency settlement and automatic-conversion economics

Link from settlement alternatives.

Managing Payment FX Exposure

Suggested anchor:

manage the exposure created by retained foreign-currency balances

Link from same-currency holding discussion.

Cross-Border Costs

Suggested anchor:

separate geographic cross-border processing cost from FX

Link where currency and international processing are distinguished.

Country Payment Guides

Suggested anchor:

market-specific payment and currency conditions

Use where local payment infrastructure materially affects currency flow.

Also link:

How PSP Foreign-Exchange Fees Work

for the high-level FX fee stack.

What Is an FX Spread?

for spread mechanics.

How to Identify Hidden FX Markups

for invoice/rate reconstruction.

Avoiding Double Currency Conversion

when a market path contains multiple sequential FX events.

Presentment vs Settlement Currency

when customer-facing and merchant settlement currencies diverge.

Currency Conversion for Refunds

when refund FX materially changes market economics.

Supporting visual

FX Cost by Market Matrix

Create a portfolio-style visual rather than a world map showing generic FX prices.

Horizontal axis

Ease / feasibility of optimization

Low → High

Include:

•alternative settlement availability;

•provider flexibility;

•regulatory feasibility;

•banking feasibility;

•implementation effort.

Vertical axis

Annual addressable FX cost

Low → High

Derived from:

•conversion volume;

•measured effective FX cost;

•addressable portion.

Bubble size

Annual conversion volume

Bubble label

Currency pair / market path

Examples:

EUR → USD | EU card flows

CAD → USD | Canada

rather than just:

Germany

or:

Canada

Bubble indicator

Same-currency expense potential:

•none;

•moderate;

•high.

Quadrants

OPTIMIZE NOW

High value

High feasibility

STRUCTURAL PROJECT

High value

Lower feasibility

QUICK / NEGOTIATE

Lower value

High feasibility

MONITOR

Lower value

Low feasibility

Visual callout

Rank currency flows—not countries.

Image alt text

FX Cost by Market Matrix ranking merchant currency-pair and settlement paths by annual addressable foreign-exchange cost, conversion volume, settlement flexibility, same-currency expenses, operational effort, and optimization feasibility.

Authoritative source recommendations

Merchant-specific evidence — highest priority

Use:

•signed PSP/acquirer agreements;

•commercial FX schedule;

•merchant settlement statements;

•conversion reports;

•payout reports;

•merchant bank statements;

•transaction data;

•treasury cash-flow records.

These are the strongest evidence for actual merchant FX cost.

Central-bank/reference data

For euro pairs, ECB reference-rate data can provide an authoritative analytical benchmark when pair, direction, and timestamp are defined. The ECB explicitly states that these rates are informational and not transaction rates.

For other currencies, use relevant official central-bank/reference sources where suitable.

Bank for International Settlements

The BIS 2025 Triennial Survey is a current authoritative source for the structure and concentration of global wholesale FX activity. Its results can explain why currency-market liquidity differs, but should not be used as evidence of merchant PSP pricing.

Use to support the limited current claim that foreign-exchange services can carry additional fees and that currency exchange rate fluctuations/fees can affect Total Net Revenue.

Use for verified payment-method processing currencies and the current statement that credit-card processing currencies depend on acquiring banks.

Use only for the verified claim that transaction reports can be pulled from a Merchant Account when the API is activated.

Proposed author and reviewer model

Author:

Treasury specialist:

[Named reviewer]

Regional payments expert:

[Named reviewer]

Merchant finance analyst:

[Named reviewer]

Payments pricing reviewer:

[Named reviewer]

Settlement specialist:

[Named reviewer where settlement-market claims remain]

Last reviewed:

[Publication date]

Recommended first-hand contribution

The strongest proprietary asset would be an approved anonymized analysis showing:

•merchant revenue share by market;

•conversion volume by currency pair;

•measured FX expense by pair;

•settlement structure;

•share of total FX cost;

•identified alternative;

•gross savings;

•implementation cost;

•realized net benefit.

An especially compelling contribution would show a case where:

the largest sales market was not the highest-priority FX market.

Do not invent this evidence.

FX-rate fact-check items

For every consequential currency-pair claim verify:

•Source currency.

•Source amount.

•Destination currency.

•Actual destination amount.

•Currency-pair direction.

•Conversion stage.

•Converting participant.

•Applied rate.

•Applied-rate timestamp.

•Benchmark source.

•Benchmark timestamp.

•Explicit fee.

•Effective cost methodology.

•Merchant contract tier.

•Effective date.

Provider-pricing fact-check items

Verify:

•PSP FX fee;

•embedded spread methodology;

•pair-specific pricing;

•public versus negotiated rate;

•volume tier;

•settlement conversion;

•payout conversion;

•rate-lock timing;

•automatic conversion;

•balance holding;

•settlement options;

•reporting transparency.

Settlement/payout fact-check items

For each priority market verify:

•processing currency;

•settlement currency;

•balance currency;

•payout currency;

•receiving-bank currency;

•automatic-conversion rules;

•who performs conversion;

•whether merchant controls currency choice;

•whether another conversion occurs after settlement;

•bank-side conversion.

Double-conversion fact-check items

Where the market matrix flags sequential conversion, verify:

source → intermediate → final

and identify:

•each converter;

•each rate;

•each timestamp;

•each fee/spread;

•reason for intermediate currency;

•direct alternative.

Do not call an intermediate conversion unnecessary until the alternative is verified.

Refund FX fact-check items

Only where material to market priority, verify:

•original transaction currency;

•original settlement currency;

•refund currency;

•refund conversion;

•rate timing;

•merchant versus customer FX outcome.

Link to the dedicated refund article for deeper mechanics.

Market/currency fact-check items

For any country or currency-specific statement verify current:

•convertibility;

•capital controls;

•local settlement requirements;

•banking requirements;

•payment-method currency support;

•PSP settlement capability;

•offshore/onshore restrictions where applicable;

•effective date.

Do not describe broad categories such as “emerging markets” as uniformly expensive or constrained.

Treasury/regulatory flags

Market FX strategies may intersect with:

•currency controls;

•capital controls;

•settlement regulation;

•banking regulation;

•entity ownership;

•intercompany funding;

•tax;

•accounting;

•treasury policy.

Identify the jurisdiction.

Do not provide speculative trading advice.

Disclaimer:

This article provides general information and does not constitute legal, tax, accounting, investment, treasury, or financial advice. Merchants should verify current currency rules, provider terms, settlement restrictions, banking requirements, and accounting treatment with qualified advisers, banks, payment providers, and relevant authorities.

Amber-flag claims

“Country X has expensive FX.”

Too imprecise.

Specify:

•currency pair;

•merchant setup;

•settlement path;

•provider;

•period.

“FX costs in Country X are X%.”

Requires merchant- or provider-specific current data and methodology.

“Less-liquid currencies always have higher PSP spreads.”

Do not use.

Market liquidity can influence conditions but does not establish merchant pricing.

“Major currency pairs are always cheap.”

Unsupported.

Commercial merchant pricing still matters.

“The market with the most sales should receive the most treasury attention.”

The article specifically challenges this assumption.

“Settling locally will eliminate FX.”

Unsupported.

Merchant treasury may still need conversion.

“Multi-currency balances lower cost.”

They can reduce conversion but also add operational cost and exposure.

“Holding local currency is always better.”

No.

Depends on use, exposure, banking, and operations.

Do not use.

No current public evidence supports such a claim.

Requires current merchant/product verification unless directly supported by applicable current documentation.

Requires approved current merchant-specific evidence.

Current public documentation establishes a Reporting API, not every FX field required for this model.

Current public evidence safely supports only a limited set of claims:

Current card documentation states that credit-card processing currencies depend on acquiring banks.

Current individual payment-method documentation demonstrates that payment methods can operate with different processing currencies.

Current API documentation establishes transaction-report export capability for Merchant Accounts when activated.

Before publication, internally verify:

•Current FX pricing model.

•Reference/base-rate methodology.

•Rate timing.

•Spread/markup treatment.

•Explicit FX fees.

•Pair-specific pricing.

•Volume tiers.

•Current processing currencies by product.

•Current settlement currencies.

•Current payout currencies.

•Merchant balance currencies.

•Automatic-conversion rules.

•Merchant selection of settlement currency.

•Local-settlement availability.

•Currency availability by acquiring bank.

•Currency availability by payment method.

•Multi-currency balance capability.

•Direct conversion-pair capability.

•Refund FX behavior.

•Rate treatment on refunds.

•Reporting fields for transaction currency.

•Reporting fields for settlement currency.

•Reporting fields for applied FX rate.

•Reporting fields for converted amount.

•Reporting fields for payout currency.

•Reporting fields for geography.

•Approved market-level FX analyses.

•Approved merchant savings cases.

•Named treasury/FX reviewer.

•Effective dates for all market-specific claims.

A restrained publishable paragraph could read:

Suggested CTA

Cluster sameness-audit fields

Field

This article

Title

FX Costs by Market: How Merchants Should Prioritize Currency-Pair and Settlement Optimization

First two sentences

A global merchant's sales dashboard and its FX-cost dashboard do not necessarily highlight the same markets. The markets generating the most revenue can be very different from those generating the most currency-conversion expense.

Opening device

Revenue heat map versus FX-cost heat map

Source currency

Variable by market

Destination currency

Variable by settlement/treasury requirement

Conversion stage

Market-specific settlement/payment conversion

Converting party

PSP/acquirer/bank/payment method as applicable

Benchmark

Defined and timestamp-aligned by currency pair

Primary format

FX market prioritization matrix

Unique evidence anchor

FX expense can be concentrated in a subset of currency paths

Editorial position

Rank pair + settlement economics, not countries by sales

Assumption challenged

Largest market = highest FX priority

Merchant decision

Identify high-volume, high-cost, actionable currency flows

Original framework

FX Cost by Market Matrix

Primary metric

Annual FX cost by currency pair

Secondary metric

Share of total merchant FX expense

Optimization metric

Expected net FX benefit

Conclusion style

Portfolio scenarios + research checklist

CTA

Map highest-cost flows and review available configurations

FAQ

None

Cannibalization safeguards

How PSP Foreign-Exchange Fees Work owns overall PSP FX mechanics.

What Is an FX Spread? owns spread mechanics.

How to Identify Hidden FX Markups owns detection methodology.

Multi-Currency Settlement and FX Costs owns settlement architecture.

Avoiding Double Currency Conversion owns sequential conversion.

Presentment vs Settlement Currency owns currency-layer distinction.

How to Compare PSP Exchange Rates owns provider rate comparison.

Managing Payment FX Exposure owns currency risk.

Currency Conversion for Refunds owns refund FX.

This article alone owns market/currency-pair prioritization.

Publication standard — August 15, 2026

The brief's central insight should remain visible from the first section to the matrix:

FX optimization should be prioritized by currency-pair economics and settlement path, not by country ranking alone.

The article should not become a table purporting to rank “cheap” and “expensive” countries.

The better SEO and merchant asset is a repeatable process for finding:

where conversion occurs

× how much volume crosses it

× what it costs

× what alternative exists

× what that alternative costs to operate

=

where treasury should act first.

The research checklist—not a generic FAQ or repeated “final recommendation”—should be the publication's final decision asset, consistent with the brief's requested ending.