TABLE OF CONTENTS



Overview & Capability Scope


In GDN API v1.x, shopping quotations were strictly limited to a single fixed currency (typically the default settlement currency configured between the Seller and the supplier/airline).

In GDN API v2.0, GDN introduces multi-currency quotation logic across the pre-booking flow. This allows Sellers to receive pricing in multiple valid settlement currencies (including Point of Origin/POO currencies) and explicitly select the final settlement currency at order creation.


Supplier Capability Dependency

GDN operates as a global distribution network. Multi-currency quotation capabilities are dependent on whether the underlying airline connection / supplier supports multi-currency pricing.

  • If the connected supplier returns multi-currency options, GDN standardizes and passes these currencies through the API.
  • If the supplier only supports a single base currency, GDN will return the offers strictly in that supplier's default currency.



Order Lifecycle & Currency Rules


To ensure price integrity and avoid foreign exchange discrepancies across booking steps, multi-currency flows follow strict lifecycle boundaries:

  1. Pre-Booking Phase Only: Multi-currency quotation options are strictly offered during pre-booking search and ancillary APIs (airShopping, serviceList, seatAvailability, bundleAvailability).
  2. OfferPrice Currency Behavior: In the verification step (offerPrice), passing a requested currency parameter does NOT trigger dynamic currency conversion. offerPrice strictly re-evaluates prices using the exact currency structure returned in the upstream AirShopping response.
  3. Mandatory Currency Locking at Order Creation:Split-currency payments are not supported. Buyers MUST explicitly specify a single valid settlement currency in the OrderCreate request (selected from the supported currencies offered during pre-booking). Once the order is created:
    • The order currency is locked permanently.
    • The payment currency cannot be changed or switched post-creation.
    • All subsequent settlement and invoicing must strictly use this locked currency.
  4. Post-Booking Servicing Single Currency Limit: For created orders, all post-booking servicing workflows (including orderRetrieve, orderReshop, orderReshopReprice, and ancillary search) will ONLY quote and settle in the locked original order currency. Multi-currency response arrays are unavailable during servicing.



Schema Structure: The settlementPrices Array


The settlementPrices node is a standardized array object introduced across all pre-booking pricing payloads. It serves as an explicit catalog of all currencies eligible for final order settlement between the buyer and the supplier for a specific offer.



Pre-Booking Currency Resolution Logic


When querying pre-booking APIs (AirShopping, ServiceList, SeatAvailability, BundleAvailability), GDN resolves currency outputs based on supplier capabilities, route restrictions, and user search inputs:


Important Notice on Wallet & Settlement Eligibility

Not all registered agency wallet currencies or supplier connection currencies are eligible for every route. GDN evaluates route-level restrictions to return only valid, payable settlement options.


Response Scenarios

Scenario 1: Specific Currency Provided in Request

  • Match Found (Direct Payable): If the requested currency is supported for settlement on that route, GDN returns the price directly in the root price node using the requested currency. The settlement array is omitted.
  • No Match: If the requested currency cannot be directly settled for the route, the root price returns in the POO currency, and the settlement array is attached containing all eligible settlement currencies.

Scenario 2: No Specific Currency Provided in Request

When no specific currency is passed in the search request, GDN standardizes the pricing output as follows:

  • Root price Node: Always returns the pricing in the flight's native Point of Origin (POO) currency.
  • settlement Array Node: Populated with all available and eligible settlement currencies supported for that route.



Explicit Currency Specification at orderCreate


To finalize the reservation, Buyers must pass the selected settlement currency code in the OrderCreate request payload. This code must match one of the currency options provided inside the settlementPrices array during pre-booking.