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
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
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
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
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
Known gotchas
Fare currency and display currency mismatches are a leading cause of pricing complaints and chargebacks — always disclose the currency clearly and avoid presenting a converted price as the 'official' fare
Some airlines apply a surcharge for credit card payment or for ticketing outside their home market; these fees may not appear in the initial fare response and must be retrieved from a separate fees endpoint or surfaced during payment
BSP (Billing and Settlement Plan) settlement between the agent and airline always occurs in the BSP currency for that market; ensure your accounting layer reconciles in BSP currency not in user-display currency
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp