The short answer
Every card transaction is either domestic or cross-border. A charge is domestic when the card issuer's country and the merchant's acquirer country match. Otherwise it is cross-border, and both Visa and Mastercard assess: (1) an elevated interchange category (typically 70–150 bps above domestic equivalents), and (2) a flat cross-border assessment fee (about 0.40–1.20% depending on program). If your acquirer is in the US and you take a charge from a UK-issued card, that charge is cross-border both ways.
Fee stack on a cross-border charge
- Elevated interchange: 1.10% (intra-region EU) to 1.80% (intercontinental US / EU) vs. roughly 0.40–1.65% domestic.
- Cross-border assessment: 0.40% (intra-region) to 1.00% (intercontinental) — Visa calls this the International Service Assessment (ISA); Mastercard calls it the Cross-Border Fee.
- FX margin: if the acquirer settles in the merchant's local currency, the card network's FX margin is 1.00% on top. Dynamic Currency Conversion (DCC) at checkout time can shift this but is controversial.
- Elevated fraud liability: issuers exercise chargeback rights more aggressively on cross-border. Practical effect: higher chargeback ratios per transaction.
What operators need to know
- Know your inbound card geography. Check your processor's BIN-level reporting. If more than 15% of your charges are cross-border but your acquirer is US-only, you're paying a fee premium that local acquirers would compress.
- Multi-acquirer setups are justified above a threshold. If you do $500k+/year in European-issued cards, establishing an EU-based acquirer relationship (through Adyen, Checkout.com, or a multiflow-placed EU acquirer) captures the domestic interchange rates for those charges. Break-even is typically 10–15% cross-border volume.
- EMV 3DS matters more on cross-border. Authentication reduces not just fraud but regulated chargeback liability. Under EMV 3DS + PSD2 SCA in the EU, an authenticated transaction shifts liability to the issuer. Without it, the merchant carries liability.
- Visa and Mastercard have different definitions. Visa's "cross-border" is issuer-country vs. acquirer-country. Mastercard's program is similar but uses BIN + acquirer region. American Express has its own international assessment. Reporting from your processor should break these out separately.
- Currency matching matters. If the charge is in USD but the issuing country is UK, some issuers present the charge to the cardholder with a foreign-transaction-fee surcharge, driving "I didn't know this would be charged in dollars" disputes. Offering local-currency pricing (tied to an EU acquirer relationship) reduces this.
Mitigation strategies
- Route cross-border charges through a local acquirer. At multiflow-level this means a parent merchant account per major region. For US operators with European volume this compresses cross-border costs by 50–100 bps on those charges.
- Enable 3DS by default on cross-border BINs. Your gateway should be configurable to auto-challenge 3DS on non-domestic issuer cards. This is the single highest-ROI fraud/chargeback lever for cross-border.
- Avoid DCC unless you've done the math. Dynamic Currency Conversion lets you show the cardholder their local currency at checkout and capture FX margin, but adds friction and disputes.
- Correct MCC matters more internationally. Some regions (Brazil, India) require specific MCC declarations for cross-border acceptance. See our note on MCC codes.
How multiflow handles cross-border
For operators with meaningful international volume, we place a secondary regional acquirer alongside the primary. The multiflow orchestration layer routes inbound charges to the local acquirer based on issuer BIN, compressing cross-border fees on the affected slice of volume. See our pricing page for the volume-tier threshold at which this becomes worth the additional underwriting overhead.