Definition
What is FX slippage in payments?
FX slippage is the gap between the exchange rate you expected and the rate actually applied when a payment crossed currencies — conversion spread made concrete. On Connect platforms it appears wherever settlement, transfer and payout currencies differ, and each crossing carries spread that no API error, webhook or dashboard ever surfaces. Individually unremarkable; across thousands of cross-border payouts, a negotiable line item hiding inside "market conditions".
Where crossings happen
Charge currency into platform balance currency: one crossing. Transfer crossing currencies: another. Payout into seller currency: potentially a third. Multi-currency marketplaces stack these invisibly — the arithmetic exists only across balance transactions, readable via exchange_rate fields nobody aggregates.
Measuring without external feeds
Comparing against mid-market rates mostly restates that spreads exist. The useful measurement is relative: each transfer’s realised rate versus same-day baseline for the identical pair — isolating genuine outliers (misconfigured currencies, timing anomalies) from constant known cost. Losses-only flagging prevents noise; ~0.8% deviation thresholds separate signal from spread.
Monitoring, not recovery
Honest framing: converted-at-rate money is gone; nothing reverses spread. Value arrives through outlier detection catching live misconfigurations, and negotiation armed with documented annual cost figures. Measurement turns invisible drag into procurement leverage — that is the entire play.
Common questions
Typical spread size?
Varies by pair and volume — which is precisely why measuring beats quoting folklore. Baselines make your number undeniable.
Is slippage a fee we can negotiate?
Effectively yes at scale — documented annualised cost is the only artifact that makes conversion-pricing conversations productive.