End to End Payment Via Pre Authenticated Card Transaction
Description
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.
Capabilities Demonstrated
Seller Authenticates Payer
Preconditions
Airline supports "online" payment
Payment is carried out in an e-commerce context
Seller will authenticate payer
Must involve a card that supports authentication
Main flow
Step | Message | Description |
01 | AirShoppingRQ | Seller submits travel plan(s) on behalf of a customer. |
02 | AirShoppingRS | Airline responds with Offers and includes a catalogue of supported methods of payment and related payment fees. |
03 | OfferPriceRQ | Seller requests price for the selected Offer/OfferItem(s) |
04 | OfferPriceRS | Airline responds with a priced offer with a specific price and may provide additional information for card payment such as precise surcharge calculation and other payment catalogue options. |
05 | OrderCreateRQ | Seller requests to create the order with a preference to pay using a customer card. |
06 | OrderViewRS | Airline notifies seller that the order is created, and that payment is expected using customer card with associated card fees, if any. |
07 | OrderChangeRQ | Seller updates the order with card processing details, including authentication data. |
08 | OrderViewRS | Airline notifies seller that the payment is “SUCCESSFUL“ and the order is now paid. |
Post Condition
Airline has successfully processed a payment on the payer’s card based on the authentication data sent by the seller.
Seller is in receipt of an Order.
Data Elements
Shop
The table below is a non-exhaustive list of some of the functions used to illustrate this use case.
Message | Object | Details |
AirShoppingRS | PaymentSupportedMethod | Used to list the various payment methods supported by the Airline, optionally including additional data, such as surcharges, brand codes, etc. |
Price
Message | Object | Details |
OfferPriceRQ
| Payment type | Optionally indicates a payment method that the seller may provide at time of purchase |
OfferPriceRS | PaymentSupportedMethod | Used to list the various payment methods supported by the Airline, optionally including additional data, such as surcharges, brand codes, etc. |
Order
Message | Object | Details |
OrderCreateRQ
| Payment type | Optionally indicates a payment method that the seller may provide at time of purchase |
OrderViewRS | PaymentSupportedMethod | Used to list the various payment methods supported by the Airline, optionally including additional data, such as surcharges, brand codes, etc. |
Pay
Message | Object | Details |
OrderChangeRQ
| Payment Card | Contains a payment payload including all data relating to the customer card |
Secure Payment Version 2 | Contains additional information relating to customer authentication data, as defined by EMVCo standards. Seller should specify that the payment is in the context of an e-commerce transaction (“EC“). | |
Amount | Amount agreed to be paid by the Seller, including currency | |
OrderRefID | Reference to the Order being paid | |
OrderItemRefID | Reference to the OrderItem(s) being paid | |
OrderViewRS
| Payment ID | Provides a unique reference for a given payment transaction |
Payment Status | Indicates the status of the payment transaction |