How to Identify Hidden FX Markups
A merchant records €1,000,000 of sales. Later, its settlement report shows $1,075,000. Someone opens a public EUR/USD chart, multiplies €1 million by a rate on the screen and concludes: “We should have received more. The PSP must be hiding an FX markup.” Maybe. But the evidence i
How to Identify Hidden FX Markups in PSP Statements and Settlement Reports
A merchant records €1,000,000 of sales.
Later, its settlement report shows $1,075,000.
Someone opens a public EUR/USD chart, multiplies €1 million by a rate on the screen and concludes:
“We should have received more. The PSP must be hiding an FX markup.”
Maybe.
But the evidence is not there yet.
Before calling the difference a markup, finance needs to know:
When did the conversion happen?
Which euros were actually converted?
Who performed the conversion?
Was it one conversion or several?
Which exchange rate applied?
Was a separate fee deducted?
Is the public rate being compared from the same timestamp and in the same direction?
Until those questions are answered, the difference between a public chart and a settlement total is not a measured FX markup.
It is an unexplained variance.
That distinction is the basis of a credible merchant FX audit.
“No FX fee” does not mean “no FX cost”
A PSP can make currency conversion economically visible in several ways.
A merchant might see:
a separately itemized percentage fee;
a fixed conversion charge;
an FX spread embedded in the conversion rate;
a settlement conversion adjustment;
another conversion when funds are paid out;
or commercial pricing that combines several elements.
The assignment therefore requires merchants to distinguish explicit fees from rate-embedded economics rather than treating them as interchangeable.
Consider a purely illustrative conversion:
Source: €100,000
Benchmark: 1 EUR = 1.0800 USD
Provider conversion: 1 EUR = 1.0740 USD
Explicit FX fee: none
Benchmark destination amount:
€100,000 × 1.0800 = $108,000
Actual destination amount:
€100,000 × 1.0740 = $107,400
Difference:
$600
All-in variance relative to the benchmark result:
$600 ÷ $108,000 = approximately 0.556%
There is clearly an economic difference.
But the merchant still should not automatically call that 0.556% an undisclosed provider markup.
It needs to establish whether:
the two rates are timestamp-aligned;
the chosen benchmark is appropriate;
the provider contract defines a spread or conversion methodology;
the transaction was actually converted at that stage;
another amount was deducted separately;
the full €100,000 was eligible for conversion.
The calculation identifies the question.
The evidence determines the answer.
Start with the currency path, not the FX rate
Before reviewing pricing, draw the payment flow.
A payment can move through several currency layers:
Customer price
→ transaction/presentment currency
→ processing currency, where relevant
→ settlement currency
→ merchant balance currency
→ payout currency
→ merchant reporting or expense currency
Every arrow where the currency changes is a potential conversion event.
Suppose customers pay in EUR, but the merchant ultimately reports in GBP.
There are several possible structures.
Path A: direct conversion
EUR
→ GBP
One visible conversion event.
Path B: conversion at settlement
EUR
→ USD merchant balance
→ merchant retains USD
One conversion, even though GBP is the merchant's reporting currency. The later accounting translation is not necessarily another cash conversion.
Path C: settlement plus payout conversion
EUR
→ USD balance
→ GBP bank account
Two actual currency conversions.
Path D: no immediate conversion
EUR
→ EUR balance
→ EUR bank account
No merchant-side cash conversion at those stages, even though the merchant may later translate EUR into GBP for financial reporting.
Those four structures cannot be audited with the same equation.
First identify where money actually changes currency.
Then analyze the rate.
For every conversion, establish eleven facts
A conversion-event record should contain:
Source currency
Source amount
Destination currency
Destination amount
Party performing or pricing the conversion
Applied rate, if provided
Rate timestamp
Benchmark source
Benchmark timestamp
Explicit fee
Other deductions associated with the event
If one is unknown, record:
Unknown — verification required
Do not estimate it silently.
The core audit principle from the brief is that effective FX economics become measurable only when the actual conversion event can be reconstructed.
Reconstruct the implied exchange rate
You do not always need the PSP to print an FX rate to infer what happened economically.
If the source and destination amounts are known, calculate the implied rate.
For a EUR → USD conversion:
Implied USD-per-EUR rate
Destination USD
÷ source EUR
Example:
Source amount: €1,000,000
Destination amount: $1,075,000
Implied conversion rate:
$1,075,000 ÷ €1,000,000 = 1.0750 USD per EUR
That does not yet tell the merchant whether 1.0750 was competitive.
It creates a rate that can be compared.
When an explicit fee is deducted separately
Suppose the provider converts at 1.0780 but also deducts a separate $2,000 fee.
If finance simply divides the final bank receipt by the gross EUR amount, it produces an all-in effective rate, not the provider's pure conversion rate.
Both metrics can be useful.
Keep them separate:
Rate-only implied conversion rate
Destination value before separately itemized FX fee
÷ source amount actually converted
All-in effective conversion rate
Final destination amount after explicit FX charges
÷ gross source amount
The first helps examine the spread.
The second answers the more commercially important question:
What amount did the merchant actually receive for each unit of source currency?
Normalize the rate direction
Exchange rates can be quoted in either direction.
EUR/USD might be shown as:
1 EUR = 1.08 USD
while another system may express the inverse:
1 USD = 0.9259 EUR
Those rates describe approximately the same relationship.
Comparing 1.08 against 0.9259 as if both use the same convention will produce nonsense.
For every audit:
define the pair;
define the base currency;
define the quote currency;
convert all observations into the same direction.
When there is any ambiguity, reconstruct the rate from source and destination amounts.
That is harder to misinterpret than a quotation label.
The benchmark is a comparison tool—not automatically “the rate the merchant should have received”
One of the most common FX-audit mistakes is calling a public reference rate the “real rate.”
There is no single universal exchange rate at which every merchant could have executed a conversion.
The European Central Bank's euro reference rates illustrate the problem. The ECB publishes them around 16:00 CET on working days based on an earlier daily concertation procedure, and explicitly says they are published for information purposes and discourages their use for transaction purposes.
The Bank of England makes a similar caution about its published spot-rate statistics: they are statistical data and do not constitute official transaction rates or carry special authority simply because the Bank publishes them.
These can still be useful audit references.
But the correct conclusion is:
“The provider result differed from benchmark X at time Y by Z.”
Not:
“Benchmark X proves the merchant was entitled to that exact executable rate.”
Select the benchmark before looking at the answer
A defensible FX audit should document benchmark selection in advance.
Possible benchmarks include:
a central-bank/reference rate;
independent institutional market data;
another authorized market-data benchmark;
a provider-defined base/reference rate where the contract explicitly uses it.
For each benchmark record:
Source
Who publishes or supplies it?
Currency pair
EUR/USD, GBP/USD, etc.
Direction
USD per EUR or EUR per USD?
Timestamp
When was the observation taken?
Type
Daily reference, spot observation, fixing or another defined rate.
Purpose
Why is this benchmark appropriate for this conversion?
A benchmark chosen retrospectively because it creates the largest apparent provider markup is not a credible audit methodology.
Timestamp alignment can change the conclusion
FX rates move over time.
That means these comparisons are analytically weak:
Provider conversion at 15:04 UTC
versus
morning benchmark
or:
Settlement on Tuesday
versus
checkout rate from Monday
or:
month-end provider payout
versus
today's exchange-rate chart
The audit needs the rate timing defined by the conversion event.
Possible conversion points can include:
authorization;
capture;
clearing;
settlement;
periodic balance conversion;
payout.
The relevant stage must be verified rather than inferred.
If the timestamp is missing
Do not invent one.
Classify the result:
Benchmark comparison limited by missing conversion timestamp.
Then ask the provider for:
exact rate timestamp;
rate-lock event;
time zone;
whether conversion happens transaction-by-transaction or in batches.
A missing timestamp is itself an audit finding.
Example: why the timestamp matters
Assume a hypothetical €1 million settlement.
The merchant receives:
$1,075,000
The implied rate is:
1.0750 USD/EUR
Finance finds a public benchmark showing:
1.0850
At that rate the conversion would have produced:
$1,085,000
The apparent difference is:
$10,000
That looks significant.
But suppose finance later learns:
1.0850 was the benchmark at 09:00;
the conversion occurred at 16:30;
an independently selected comparable benchmark at 16:30 was 1.0770.
The event-level benchmark result is then:
€1,000,000 × 1.0770 = $1,077,000
The unexplained difference has fallen from:
$10,000
to:
$2,000
Nothing about the provider rate changed.
The audit methodology changed.
That is why “the chart says…” is not enough.
Embedded does not necessarily mean undisclosed
“Hidden FX markup” is a useful search term but a dangerous accusation.
The assignment requires four distinct classifications.
Undisclosed
The merchant has evidence that a material pricing element was not disclosed where disclosure was required under the applicable commercial arrangement or law.
This characterization requires careful contractual or legal review.
Embedded
The provider's commercial terms explain that the exchange rate contains a spread or specified adjustment, but the markup is incorporated into the rate rather than appearing as a separate invoice line.
It can be difficult to observe without being undisclosed.
Difficult to observe
The merchant cannot calculate the economic difference because rate timestamps, reference methodology or conversion details are unavailable.
That is a transparency/data problem.
It is not automatically evidence of misconduct.
Unexplained
The merchant has reconstructed the event, reconciled known explicit fees and aligned the benchmark, but a residual variance remains.
This should trigger provider clarification.
Only evidence should determine what label follows.
Contract language is part of the rate reconstruction
The PSP agreement, fee schedule and product-specific terms should answer questions such as:
Is FX priced as a fixed spread from a defined base rate?
Is a percentage conversion charge listed separately?
Can the provider choose a settlement rate methodology?
When is the rate determined?
Are FX terms different by currency pair?
Are they volume-tiered?
Does settlement conversion use the same methodology as payout conversion?
Does the merchant have the right to hold certain balances without conversion?
What happens when the payout bank account uses another currency?
How are refunds treated?
A rate difference that corresponds exactly to a contractual 50-basis-point adjustment is not an unexplained mystery.
It may still be commercially expensive.
But it is analytically different from an unexplained 50-basis-point gap.
Reconcile explicit FX charges before measuring residual markup
Suppose:
Benchmark destination result: $500,000
Provider destination amount before fee: $498,000
Explicit FX fee: $1,000
Final merchant amount: $497,000
There are two cost questions.
Embedded rate variance
$500,000 − $498,000 = $2,000
Explicit fee
$1,000
All-in conversion cost versus benchmark
$500,000 − $497,000 = $3,000
This decomposition prevents the merchant from calling the full $3,000 a “spread.”
It also prevents the opposite mistake: comparing the quoted provider rate with a benchmark and forgetting a separately deducted FX fee.
The Hidden FX Markup Audit
For each conversion event, complete the following sequence.
Step 1 — Locate the source transaction or balance
Identify the exact value that was available immediately before conversion.
Do not begin with the monthly bank payout if several currencies or adjustments were aggregated into it.
Step 2 — Identify source currency
Example:
EUR
Step 3 — Identify destination currency
Example:
USD
Step 4 — Record the converted source amount
Example:
€250,000
Distinguish this from gross sales if only part of the sales balance was converted.
Step 5 — Record the actual destination amount
Use the amount immediately after the conversion where possible—not after unrelated deductions.
Step 6 — Determine conversion timestamp
Record:
date;
time;
time zone;
event that fixed the rate.
Step 7 — Record provider rate if available
If absent, calculate the implied rate.
Step 8 — Select a comparable benchmark
Same:
pair;
direction;
comparable timestamp;
amount context where relevant.
Step 9 — Normalize rate direction
Convert both rates to one consistent quote.
Step 10 — Calculate benchmark destination amount
Source amount × benchmark rate
subject to correct rate direction.
Step 11 — Calculate the all-in economic variance
FX conversion variance
Benchmark destination amount
− actual destination amount
Step 12 — Calculate effective variance %
FX conversion variance
÷ benchmark destination amount
× 100
Step 13 — Reconcile explicit fees
Identify how much of the difference is explained by separately itemized FX charges.
Step 14 — Reconcile contractual markup
Compare the remaining difference with the contractual spread/rate methodology.
Step 15 — Check for another conversion
Follow the funds through settlement, balance and payout.
One conversion that looks reasonable can still be followed by another expensive one.
Classify the audit result
Every audited conversion should finish in one of four categories.
Explained
The economic difference is adequately reconciled to:
agreed rate methodology;
explicit fee;
timestamp;
rounding;
documented conversion path;
other verified factors.
No unresolved material difference remains.
Contractually embedded
The markup is incorporated into the provider's rate and is consistent with disclosed commercial terms.
The merchant may still decide the price is uncompetitive.
But the audit has identified its source.
Unclear — provider clarification required
Examples:
no precise timestamp;
rate methodology unavailable;
converted source amount unclear;
provider rate absent;
several adjustments bundled together;
transaction and payout currencies cannot be reconciled.
This category is especially important.
Do not convert missing data into an accusation.
Potential discrepancy requiring review
The merchant has:
reconstructed the conversion;
aligned currencies;
aligned timestamps;
reconciled explicit fees;
considered the agreed methodology;
and still finds a material unexplained difference.
Escalate with the evidence chain.
Do not begin with the allegation.
Begin with the numbers.
Monthly settlement totals can hide the conversion event
Suppose a merchant processes EUR sales throughout a month.
Conversions occur on 20 different days.
FX rates differ across those dates.
The provider may also:
convert some transactions individually;
convert others in batches;
deduct refunds;
deduct processing fees;
carry balances across reporting periods.
Comparing:
monthly EUR gross sales
with:
monthly USD bank receipt
is therefore a weak way to estimate FX markup.
The denominator may not even represent the amount converted.
Better period calculation
For each conversion i:
Benchmark destination amountᵢ
= source amountᵢ × benchmark rateᵢ
Then:
Period benchmark destination value
Σ benchmark destination amountᵢ
Compare with:
Period actual converted value
Σ actual destination amountᵢ
The period result is built from event-level evidence rather than one average monthly rate.
The assignment specifically requires distinguishing monthly aggregate analysis from conversion-event analysis.
Measure audit-data completeness
A merchant cannot manage FX economics reliably if only a fraction of conversions can be reconstructed.
Add:
Complete-rate-data ratio
Conversion events with source amount, destination amount, pair and usable timestamp
÷ total conversion events
A low ratio tells finance that its first FX problem is not necessarily price.
It is observability.
A procurement team cannot meaningfully negotiate a 30-basis-point spread improvement if treasury cannot identify when or where current conversions happen.
Detect the second conversion
A settlement statement may make the first conversion visible and the second nearly invisible.
Example:
Customer pays EUR
→ PSP converts EUR to USD balance
→ merchant requests payout into GBP bank account
Audit both arrows:
EUR → USD
and:
USD → GBP
For each, identify:
source amount;
destination amount;
rate;
timestamp;
converting participant;
fee;
benchmark.
The total economic effect is not simply “the EUR/USD spread.”
It includes the second conversion too.
The brief calls out double conversion as a separate dedicated article, so this piece should detect the second event without turning into a full redesign guide.
Diagnostic question
After every FX event ask:
Is this now the currency the merchant ultimately needs?
If not:
What happens next?
That simple question catches many multi-step conversion paths.
Cross-border processing cost is not FX markup
Another common reconciliation mistake is attributing every cost on an international transaction to currency conversion.
A payment can be:
cross-border without merchant-side currency conversion;
currency-converted without carrying the same cross-border card fee structure;
both.
The Foreign Exchange brief explicitly separates currency-driven conversion economics from geography-driven processing premiums.
Therefore do not include in the FX variance merely because the transaction was international:
cross-border card surcharge;
international interchange difference;
network cross-border assessment;
acquiring geography premium.
Those belong in the Cross-Border Costs analysis.
FX audit:
What did changing currency cost?
Cross-border fee audit:
What did international transaction geography cost?
They can coexist.
They should not be double-counted.
Settlement conversion and payout conversion are different events
An FX audit should distinguish:
Settlement conversion
Currency changes when transaction proceeds are posted or credited to the relevant merchant/provider balance.
Payout conversion
Currency changes again when funds move from that balance into a differently denominated merchant bank account.
The brief explicitly requires those events to remain separate because a merchant can incur either or both.
That means a merchant should not ask only:
“What currencies can customers pay in?”
It should ask:
“Which currencies can remain unconverted through settlement and payout?”
Those are different capabilities.
A smaller spread is not automatically a cheaper FX setup
Suppose Provider A has a tighter quoted FX spread.
But Provider A converts EUR revenue automatically into USD and the merchant later needs GBP.
Provider B has a slightly wider first conversion but can settle the merchant directly in GBP.
The correct comparison is not:
Provider A spread versus Provider B spread
It is:
final amount in the currency the merchant actually needs, after all conversions and explicit fees.
This is the logic behind the all-in effective conversion rate:
All-in effective conversion rate
Final destination amount after included FX charges
÷ original source amount
Then compare providers using:
same source amount;
same source/destination pair;
same direction;
aligned timestamp;
same settlement structure;
same payout assumptions;
same contract tier.
The assignment expressly requires those controls in provider comparisons.
Those public terms support the existence of FX-related commercial and settlement effects.
They do not establish:
one reference-rate methodology;
one rate timestamp;
one spread for every currency pair;
one settlement conversion path for every merchant.
Those items require the merchant's current fee schedule, product terms and actual settlement/reconciliation data.
Questions to ask the PSP
When an FX variance cannot be explained internally, send a structured request rather than:
“Why is your exchange rate so bad?”
Ask:
What exact conversion event produced this destination amount?
What was the source amount?
What was the source currency?
What was the destination currency?
At what timestamp was the rate determined?
What time zone does that timestamp use?
Was the rate locked at transaction, capture, settlement, batch conversion or payout?
What provider/reference rate was used?
What contractual spread or adjustment was applied?
Was an explicit conversion fee also charged?
Was the conversion performed transaction-by-transaction or on an aggregated balance?
Did another participant perform part of the conversion?
Was the balance converted again before payout?
Can the original currency be retained?
Which settlement currencies are available for this merchant?
Which payout currencies are available?
Can FX rate, timestamp and converted amounts be exported for reconciliation?
How are refunds converted?
Does pricing vary by pair or volume tier?
Which version of the fee schedule governs this transaction?
The purpose is to produce a reproducible evidence chain.
How to interpret a benchmark variance
Suppose an audit produces:
Benchmark result: $10,000,000
Actual result: $9,940,000
Difference:
$60,000
Effective variance:
0.60%
Do not stop there.
Scenario A: contract specifies approximately the observed adjustment
Classification:
Contractually embedded
Next commercial question:
Is that pricing competitive at the merchant's conversion volume?
Scenario B: $40,000 is an explicit disclosed fee and $20,000 is rate variance
Classification:
Explained in part
Separate fee from spread before comparing providers.
Scenario C: provider used a materially different conversion timestamp
Classification:
Potentially explained by timing once an aligned benchmark is used.
Scenario D: the merchant discovers a second conversion
Classification:
Part of the apparent “PSP rate problem” was actually multi-stage FX.
Link to Avoiding Double Currency Conversion.
Scenario E: no contractual or operational explanation remains
Classification:
Potential discrepancy requiring review
Provide transaction IDs, amounts, timestamps, implied rates and benchmark methodology to the provider.
Benchmark variance versus unexplained variance
These should be separate metrics.
Benchmark variance
Benchmark destination value
− actual destination value
This is the total economic difference between the selected reference conversion and actual merchant outcome.
Explained variance
Amounts attributable to verified:
explicit fees;
contractual spread;
known rounding;
other documented conversion adjustments.
Unexplained variance
Benchmark variance
− explained variance
This is the figure that should drive provider clarification.
Not every benchmark variance is unexplained.
That distinction prevents the phrase “hidden markup” from being used as a synonym for “conversion cost.”
Measure total FX cost by period
Once the event audit works, aggregate it.
For period P:
Total modeled FX cost
Σ benchmark destination value
− Σ actual destination value
where actual destination values are defined consistently and the metric's fee scope is documented.
Then calculate:
Weighted effective FX cost %
Total modeled FX cost
÷ total benchmark-converted value
Do not average individual percentage spreads without weighting by converted economic value.
A 2% variance on a $500 conversion should not receive the same weight as a 0.4% variance on a $5 million conversion.
Segment the result by currency pair
At minimum report:
source currency;
destination currency;
conversion volume;
conversion count;
benchmark variance;
explained explicit fees;
unexplained variance;
effective FX cost;
provider;
conversion stage.
That makes the investigation commercially actionable.
Finance can determine whether the problem is concentrated in:
one currency pair;
one settlement path;
one provider;
one market;
one payout structure.
The brief explicitly warns against assuming a single provider spread applies equally to every currency pair or market.
Do not confuse conversion cost with FX exposure
A merchant can incur a conversion cost at the moment money changes currency.
It can also experience currency-value movement while holding foreign-currency balances before conversion.
Those are different economics.
Conversion cost
EUR changes into USD.
The merchant can measure the rate and any fee relative to its selected benchmark.
FX exposure
The merchant continues to hold EUR.
EUR's value relative to the merchant's base or expense currencies changes before the merchant later uses or converts it.
A favorable movement can benefit the merchant.
An unfavorable movement can hurt it.
Do not automatically call either movement an “FX fee” or “loss.”
The dedicated Managing Payment FX Exposure article owns that treasury problem in depth.
Refunds require a second rate investigation
A transaction can be converted when sold and converted again when refunded.
For an FX audit, preserve:
original transaction currency;
original conversion amount;
original conversion rate/time;
settlement currency;
refund amount;
refund currency;
refund conversion rate/time;
settlement adjustment.
Do not assume the original exchange rate is reused.
Do not assume today's rate is used either.
Verify the provider/payment-method treatment.
Detailed refund FX belongs in Currency Conversion for Refunds, but a markup audit should at least flag refunds as separate conversion events rather than mixing them into original-sale FX.
A strong FX audit ends with evidence, not suspicion
The audit is complete when finance can produce a record such as:
Source amount: €250,000
Destination amount: $268,250
Implied rate: 1.0730 USD/EUR
Conversion stage: settlement
Conversion timestamp: verified
Benchmark source: documented
Benchmark rate: timestamp-aligned
Explicit fee: reconciled
Contractual spread: reconciled
Second conversion: none
Residual unexplained variance: calculated
Status: explained / contractually embedded / clarification required / potential discrepancy
That is a commercial artifact procurement can negotiate from.
“The internet says EUR/USD was higher” is not.
Final recommendation: audit the conversion event, not the chart
The merchant trying to find an FX markup should work backward from the money it actually received.
First:
Map every point where currency changes.
Second:
Reconstruct the source and destination amounts for each event.
Third:
Determine when the rate was fixed.
Fourth:
Compare it with a defensible, timestamp-aligned benchmark in the same direction.
Fifth:
Reconcile explicit fees and contractual rate adjustments.
Sixth:
Follow the funds forward to make sure another conversion does not occur later.
Only then classify the result.
An embedded spread may be expensive without being undisclosed.
A public-rate difference may be large without being a markup if the timestamps do not match.
A zero-dollar explicit FX fee may coexist with meaningful conversion cost.
And an apparently competitive first conversion can still produce poor all-in economics when settlement or payout creates a second one.
The commercial question is therefore not:
“Does this PSP hide FX fees?”
It is:
“For each conversion event, how much destination currency did we receive relative to a defensible benchmark, how much of the difference is explained by our commercial terms, and how much remains unexplained after every fee, timestamp and conversion stage has been reconciled?”
That is the evidence chain a merchant can measure, compare and negotiate.
How to Identify Hidden FX Markups in PSP Statements and Settlement Reports
Editorial brief interpretation
This article owns forensic detection of embedded FX economics. Its central discipline is evidentiary: a settlement amount that looks worse than a public exchange-rate chart does not, by itself, prove a hidden markup. The merchant first has to reconstruct the actual conversion—source amount, destination amount, currencies, conversion stage, timestamp, provider rate, comparable benchmark, explicit charges, and any second conversion.
Field
Editorial decision
Merchant FX-cost problem
The merchant suspects expensive FX but cannot separate market movement, timing, embedded spread, explicit fees and multiple conversions.
Currency path
Map transaction/presentment → processing where relevant → settlement → merchant balance → payout before calculating anything.
Source currency
The currency immediately before each conversion event. There may be several source currencies across one payment lifecycle.
Destination currency
The currency received immediately after that conversion—not automatically the merchant's final reporting currency.
Conversion stage
Transaction, settlement, balance conversion, payout or refund.
Converting party
PSP, payment partner, acquiring participant, bank or another participant; verify rather than assume.
Benchmark methodology
Use an independently sourced rate for the same pair, direction and closely aligned timestamp. Treat central-bank daily reference rates as analytical references, not executable merchant rates.
Unique evidence anchor
An invoice may contain no separate “FX fee” while the conversion result still embeds measurable rate economics.
Editorial position
Audit FX at conversion-event level before describing a difference as hidden, excessive or unexplained.
Common assumption challenged
“The settlement amount is below today's public exchange rate, so the PSP must have added a hidden markup.”
Merchant decision
Determine whether the variance is explained, contractually embedded, unclear, or a potential discrepancy requiring escalation.
Selected format
FX markup forensic audit.
Primary asset
Hidden FX Markup Audit.
Primary metrics
Implied rate, benchmark variance, unexplained variance, total FX cost and percentage of conversion events with complete rate data.
The assignment specifically requires separating embedded from undisclosed pricing, spread from market movement, transaction date from settlement date, monthly aggregation from conversion events, contractual markup from unexplained variance, and FX cost from cross-border processing fees.
Proposed architecture
No FX fee on the invoice—so what happened?
Map the currency path before looking at the rate
What evidence an FX audit actually needs
Reconstruct the implied conversion rate
Choose a defensible benchmark
Timestamp errors that create false “markups”
Explicit fees versus embedded spread
The Hidden FX Markup Audit
Monthly totals: why aggregation can mislead
Detecting a second conversion
How to interpret the evidence
Questions to ask the PSP
Final recommendation: audit the event, not the chart
Original practical asset: Hidden FX Markup Audit
Conversion-event record
For every conversion capture:
Field
Value
Transaction/balance ID
Provider
Conversion stage
Source currency
Source amount
Destination currency
Destination amount
Conversion timestamp
Time zone
Provider rate
Implied rate
Benchmark source
Benchmark rate
Benchmark timestamp
Explicit fee
Contractual spread/markup
Second conversion?
Final destination currency
Evidence source
Audit classification
Core calculations
Implied rate
Destination amount
÷ source amount
assuming that rate direction is defined as destination currency per unit of source currency.
Benchmark destination amount
Source amount × benchmark rate
Benchmark variance
Benchmark destination amount
− actual destination amount
Effective benchmark variance %
Benchmark variance
÷ benchmark destination amount
× 100
Unexplained variance
Benchmark variance
− reconciled explicit costs
− reconciled contractual/operational differences
Use only where each deducted component has defensible evidence.
Classification
Explained
Contractually embedded
Unclear / provider clarification required
Potential discrepancy requiring review
FX audit evidence hierarchy
Use evidence in roughly this order:
Merchant-specific PSP agreement
Merchant fee schedule
FX/conversion product terms
Settlement report
Payout report
Transaction-level payment data
Provider rate/timestamp export
Merchant bank statement
Independently selected benchmark data
Treasury reconciliation analysis
A public exchange-rate website should not outrank the merchant's actual conversion records.
SEO metadata
H1: How to Identify Hidden FX Markups in PSP Statements and Settlement Reports
Meta description: Learn how to reconstruct payment FX conversions, calculate implied exchange rates, align timestamps and benchmarks, and separate embedded PSP markup from explicit fees and market movement.
URL slug: /identify-hidden-fx-markups
Secondary keywords:
hidden FX markup
PSP exchange rate markup
detect FX fees
payment FX markup
hidden currency conversion fees
merchant FX audit
PSP settlement exchange rate
payment provider FX spread
Related entities:
foreign exchange
FX spread
exchange-rate benchmark
settlement currency
payout currency
PSP
merchant settlement
treasury
currency conversion
FX markup
reference rate
implied exchange rate
multi-currency settlement
Article excerpt: A settlement amount below a public exchange-rate benchmark does not automatically prove a hidden PSP markup. Merchants need to reconstruct the actual conversion event—amount, currencies, timestamp, benchmark, fees and settlement path—to determine what the difference really represents.
Suggested structured data: Article and BreadcrumbList.
Internal links
FX Spread
Link when explaining rate-embedded pricing and spread calculations rather than duplicating detailed spread mechanics.
Compare PSP Exchange Rates
Link from provider-comparison methodology; that article should own full competitive rate benchmarking.
Double Currency Conversion
Link when the forensic audit identifies a second conversion between settlement and payout.
Hidden & Ancillary Fees
Link when distinguishing embedded FX economics from other ancillary provider charges.
Presentment vs Settlement Currency
Optional link when the audit cannot establish where the first currency conversion occurs.
Currency Conversion for Refunds
Optional link when refund events create separate FX economics.
Authoritative source recommendations
Merchant-specific PSP agreement and fee schedule — primary evidence for contractual FX pricing.
Merchant settlement and payout reports — primary evidence for the actual source/destination amounts.
Provider conversion-rate/timestamp reporting — where available, primary evidence for rate reconstruction.
European Central Bank euro foreign-exchange reference rates and methodology — useful independent analytical reference, with the important caveat that the ECB says its reference rates are for information purposes and discourages their use for transaction purposes.
Bank of England spot-rate statistics and methodology — another useful illustration that official-sector published rates should not automatically be interpreted as the uniquely authoritative executable rate.
Merchant treasury/finance analysis — required to connect conversion-event results with total period economics.
Supporting visual: Hidden FX Markup Audit
Visual flow
SOURCE
€250,000
Source currency: EUR
↓
CONVERSION EVENT
Who converts?
When?
Which rate?
Explicit fee?
↓
ACTUAL RESULT
$X received
Implied EUR/USD rate calculated
↓
BENCHMARK
Independent source
Same pair
Same direction
Aligned timestamp
↓
RECONCILIATION
Benchmark difference
− explicit fee
− contractual spread
− explained timing/rounding
↓
RESULT
Explained
or
Contractually embedded
or
Clarification required
or
Potential discrepancy
Then one final arrow:
Does another currency conversion occur before the merchant can use the funds?
Visual takeaway
A rate difference becomes evidence only after the conversion event is reconstructed.
Suggested image alt text: Hidden FX Markup Audit showing source currency, conversion timestamp and provider rate, benchmark comparison, explicit fee reconciliation, second-conversion check and final audit classification.
Proposed author and review structure
Do not invent completed review.
Audit reviewer: [Named Payment Operations Analyst]
FX methodology reviewer: [Named Treasury Specialist]
Financial reviewer: [Named Merchant Finance Lead]
Recommended first-hand contribution: An anonymized merchant FX reconciliation containing several real conversion events, showing source/destination values, timestamp completeness, benchmark variance and how much of the initial “hidden markup” suspicion was ultimately explained, embedded or unresolved.
The brief specifically recommends payment operations, treasury and merchant-finance participation.
FX-rate fact-check items
For every numerical FX example intended as factual rather than hypothetical, verify:
source currency;
destination currency;
source amount;
destination amount;
pair direction;
provider rate;
implied rate;
benchmark source;
benchmark methodology;
provider timestamp;
benchmark timestamp;
time zone;
conversion stage;
explicit fee;
effective date;
rounding treatment.
Never copy a current rate into the article without its timestamp and purpose.
Provider-pricing fact-check items
Verify:
provider;
merchant/product;
public versus negotiated pricing;
explicit FX fee;
embedded spread methodology;
reference/base rate methodology;
currency-pair differences;
volume tiers;
conversion timing;
whether rates are locked;
settlement conversion terms;
payout conversion terms;
ability to hold balances;
waiver/promotional treatment;
contractual effective date.
Do not infer a provider's spread from a single conversion event if the commercial methodology is unknown.
Settlement and payout fact-check items
For each merchant setup confirm:
transaction currency;
settlement currency;
merchant balance currency;
payout currency;
bank-account currency;
whether settlement conversion occurs;
who performs it;
when its rate is fixed;
whether payout generates another conversion;
whether the merchant can select another settlement currency;
whether the original currency can remain unconverted.
Double-conversion fact-check items
Where a second conversion is suspected, verify both independently:
Conversion 1
source;
destination;
amount;
party;
rate;
timestamp;
fee.
Conversion 2
source;
destination;
amount;
party;
rate;
timestamp;
fee.
Then determine:
why the intermediate currency exists;
whether a direct path is technically/commercially available;
what a direct path would cost;
whether eliminating the conversion creates another provider, banking, account or operational cost.
Do not describe every multi-step currency path as avoidable.
Refund FX fact-check items
For relevant merchant scenarios verify:
original transaction currency;
original settlement currency;
original conversion rate/time;
refund amount;
refund currency;
refund-date conversion rate/time;
whether original rate is reused;
whether current rate applies;
merchant settlement adjustment;
partial-refund treatment;
explicit refund/FX fees.
Do not infer customer home-currency outcome from merchant-side refund accounting.
Market and currency fact-check items
For market-specific FX claims identify:
currency pair;
geographic market;
settlement arrangement;
payment method;
provider;
convertibility or regulatory restriction, if any;
effective date.
Do not infer merchant PSP pricing directly from general statements about wholesale currency liquidity.
Treasury and regulatory flags
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 and accounting treatment with qualified advisers, banks, payment providers and relevant authorities.
Additional qualified review may be required for:
capital controls;
exchange controls;
restricted currencies;
local settlement rules;
entity ownership of foreign-currency balances;
repatriation requirements;
accounting treatment of FX differences;
treasury hedging.
This article should not recommend speculative currency positions or financial trading strategies.
Amber-flag claims
“The mid-market rate is the real rate.”
Avoid. Define the benchmark precisely. The ECB itself says its euro reference rates are information-only and discourages transaction use.
“The PSP charged a hidden 1% markup.”
Requires conversion-event reconstruction, timestamp alignment and contractual review.
“No FX fee means free conversion.”
Incorrect methodology; rate-embedded cost can exist even with no separately itemized fee.
“Any difference from an ECB rate is PSP profit.”
Unsupported. Reference-rate purpose, timestamp, executable market conditions and provider commercial terms all matter.
“The settlement-date rate is the relevant benchmark.”
Only if that is when the rate was actually determined.
“The transaction-date rate is the relevant benchmark.”
Same issue.
“This is double conversion.”
Verify that two actual changes of currency occurred rather than one cash conversion plus accounting translation.
Requires internal/current verification.
Requires product-specific verification.
The public Reporting API page establishes transaction-report access but does not, from the documentation reviewed, establish complete FX-rate/timestamp coverage.
Before publication:
Identify the current commercial definition of any currency exchange fees referenced by the Terms.
Verify whether FX pricing is explicit, rate-embedded or can use both approaches by merchant/product.
Confirm the provider/reference-rate methodology, if one is contractually defined.
Confirm precisely when conversion rates are determined for each relevant flow.
Verify whether transaction, settlement and payout conversions can use different methodologies.
Confirm which settlement currencies are currently available by product/merchant structure.
Confirm which payout currencies are currently available and whether same-currency bank-account requirements apply to the target merchant arrangement.
Verify whether merchants can retain balances in transaction currencies rather than convert automatically.
Confirm whether conversion event ID, source amount, destination amount, rate and timestamp are available in Merchant Area, settlement reports or APIs.
Confirm exactly which relevant fields are accessible through the Reporting API.
Verify how refunds involving multiple currencies are converted.
Verify any pair-specific or volume-tiered commercial terms.
Cluster sameness-audit fields
Title: How to Identify Hidden FX Markups in PSP Statements and Settlement Reports
First two sentences: A merchant records €1,000,000 of sales. Later, its settlement report shows $1,075,000.
Opening device: Forensic investigation of a suspicious settlement result rather than a generic FX explanation.
Source currency: EUR in the opening example; event-specific throughout the methodology.
Destination currency: USD in the opening example; event-specific elsewhere.
Conversion stage: Unknown at the opening and deliberately reconstructed by the audit.
Converting party: Unknown until evidence identifies PSP/payment partner/bank or another participant.
Benchmark: Independently selected and timestamp-aligned rather than a generic “mid-market” number.
Primary format: FX markup forensic audit.
Unique evidence anchor: A settlement can contain embedded FX economics even when no explicit conversion charge appears, but a benchmark difference is not proof until the conversion event is reconstructed.
Editorial position: Audit at event level before characterizing a markup as hidden or excessive.
Common assumption challenged: A settlement below today's public market rate proves provider markup.
Merchant decision: Classify each variance as explained, contractually embedded, unclear or a potential discrepancy.
Original framework: Hidden FX Markup Audit.
Primary metric: Event-level benchmark variance.
Secondary metrics: Implied rate, unexplained variance, weighted FX cost and conversion-event data completeness.
Conclusion: Evidence requires source/destination values, pair, timing, rate methodology, explicit fees and full currency path.
CTA: Reconstruct a representative sample of the merchant's largest FX conversion events before the next PSP pricing or treasury review.
Closing element: Forensic evidence chain rather than a generic FX rate comparison.
Differentiation: This article owns markup detection. It does not own basic FX-spread mechanics, the full multi-currency settlement architecture, double-conversion redesign, provider-wide exchange-rate comparison, merchant FX exposure, refund FX or market-by-market FX intelligence.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗