Version 26.1
This use case illustrates a servicing flow where the customer changes their contact details, specifically updates existing email and phone number details, adds the residence country code and deletes the identity document.
This use case illustrates the flow where the customer wants to view an existing Order through a seller.
This use case illustrates an end-to-end flow whereby a customer shops at a travel seller’s website. During the shopping and pricing phases, the airline provides the seller with a series of payment options and the seller determines that they will pass through the customer's payment card. The seller proceeds to create and pay for an order using customer card, having authenticated the card holder and provides authentication data in the payment payload. The payment is accepted, and the order is confirmed.
This use case illustrates the flow whereby a customer shops with a Seller. During the shopping and pricing phases, the airline provides the seller with a series of payment options and the seller determines that payment for the specific order will be by way of a pre-existing settlement plan. The seller proceeds to create and pay for an order using the settlement plan. The payment is accepted and the order is confirmed.
This use case illustrates the flow whereby a customer pays an order which falls under the scope of Reserve Bank of India mandate for a transaction for which both the merchant and card issuer are located in India. The mandate requires that no entity in the card transaction chain, other than the card issuers (banks) and/or networks (Visa, Mastercard, etc.), shall store the actual card data. Solution is to use an alternative token called AlternateCardNumberText which has same format as the Credit Card Primary Account Number (CC PAN) and which is issued by a third-party system authorized by the Reserve Bank of India. Note that for the time being it is not clear if the Seller can authenticate autonomously. This is under discussion with Payment Council of India.
This use case illustrates the flow whereby a customer shops with a Seller. During the shopping and pricing phases, the Airline provides the Seller with a series of payment options and the Seller determines that the customer will pay using redirection. The Seller accepts to create the Order with a commitment to pay using the payment method subject to redirection. The payment confirmation is marked as pending and the redirection URL is returned by the Airline. The customer is redirected to this URL and the customer makes the payment. The Airline later notifies the Seller about the final payment status.
This use case illustrates a prime booking flow for one single adult passenger, including the steps between flight shopping by origin/destination and order creation without payment.
NDC Clearance is an independent tool and is not affiliated with, endorsed by, or connected to the International Air Transport Association (IATA).