Correctly apply Visa ISA and Mastercard cross-border assessment fees when presentment currency differs from settlement currency
domain: payments · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the transaction's presentment currency (what the cardholder was shown/charged in) versus your settlement currency, since a mismatch is what triggers cross-border/currency-conversion assessments.
For Visa, expect the International Service Assessment to apply at a lower rate when the transaction settles in USD without conversion and a higher rate when currency conversion is required; confirm current rates with your acquirer since network-set percentages can change.
For Mastercard, expect an analogous Cross-Border Assessment Fee that is likewise higher when currency conversion occurs versus same-currency cross-border settlement.
Reconcile these assessment line items separately from interchange and your processor's markup on your monthly statement, since they're pass-through network fees, not acquirer margin.
If you operate a dynamic currency conversion (DCC) program, understand it doesn't eliminate the network cross-border fee — it's a separate merchant/acquirer mechanism layered on top of the underlying transaction.
Disclose the applicable fee structure in merchant pricing/statements so cross-border-heavy merchants aren't surprised by the higher currency-conversion tier.
Known gotchas
The lower same-currency-settlement tier still applies to a cross-border transaction if no currency conversion happens, so don't assume all international transactions get the higher rate.
Rates are set by the card networks and revised periodically — treat them as configurable values, not fixed constants, in any fee-estimation logic.
These fees are separate from your acquirer's own cross-border markup, so reconciling them requires isolating network-assessed lines from processor-added lines on settlement reports.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?