The FX rate nobody locked between auth and capture
Ran into this on a cross-border order: card authorized in EUR, capture fires four days later once the item ships, settlement currency is USD. Between those two events the EUR/USD rate moved about 1.1%. The captured amount came back higher than the number shown at checkout, and the customer's statement didn't match the order confirmation. Turns out card networks only guarantee the authorization…
A cross-border order encountered a puzzling discrepancy: a card authorized in EUR, but captured four days later with settlement in USD. During this interlude, the EUR/USD exchange rate shifted by around 1.1%. The final captured amount exceeded the initial checkout total, and the customer's statement didn't align with the original order confirmation.
This anomaly stemmed from card networks only guaranteeing the authorization hold in the cardholder's currency for a limited window, typically 24 to 72 hours. Beyond this period, certain acquirers recalculated the conversion at capture using the prevailing rate instead of the one quoted at authorization. The API response didn't alert to this discrepancy, leading to a captured amount that was only a few cents or dollars off from the initial authorization.
The reconciliation process either overlooked the difference or flagged it as a false mismatch based on the organization's tolerance threshold. The team ultimately took control of the FX rate at authorization and manually compared it with the settlement report line by line, accepting minor drifts under a fixed cap and flagging any larger deviations for manual review.
For businesses handling delayed capture across currencies, the question arises: should one reprice at capture, refund the delta, or simply absorb it below a predetermined threshold?
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
