Handle multi-currency pricing and point-of-sale configuration correctly in airline booking APIs

Steps

1. Understand that airline fares are filed in specific POS (point of sale) markets defined by country of sale and ticketing carrier; the same itinerary can have materially different prices depending on POS
2. Configure your API requests with the correct POS country code and sales currency to retrieve fares applicable to your market; use the currency and country parameters explicitly rather than relying on defaults
3. When displaying prices, distinguish between the fare currency (in which the fare is filed), the ticketing currency (in which the ticket is issued), and the display currency (what the user sees); apply exchange rates only at the display layer
4. For multi-currency storefronts, retrieve prices in the fare currency and perform FX conversion using a near-real-time exchange rate service; store the fare currency amount in the booking record alongside the converted display amount
5. At payment, charge in the ticketing currency unless your payment processor and airline agreement explicitly support multi-currency settlement; mismatches between charged and ticketing currency create reconciliation and chargeback risks