Payment Via Redirection with Airline Notification of Payment Success
Description
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.
Capabilities
https://standards.atlassian.net/wiki/spaces/EASD/pages/574881833
https://standards.atlassian.net/wiki/spaces/EASD/pages/574226556
https://standards.atlassian.net/wiki/spaces/EASDedit/pages/607486706
Preconditions
Airline supports payment using redirection.
Main Flow
Step | Message | Description |
01.1 | AirShoppingRQ | Seller submits travel plan(s) on behalf of a customer. |
01.2 | AirShoppingRS | Airline responds with Offers and includes a catalogue of supported payment methods. |
02.1 | OfferPriceRQ | Seller requests price for Offer/OfferItem(s) and expresses an intent to use a form of payment method subject to redirection. |
02.2 | OfferPriceRS | Airline responds with a priced Offer with a specific price and additional instructions for the payment method subject to redirection. |
03.1 | OrderCreateRQ | Seller requests to create the order with the preference to pay using the payment method subject to redirection by using the payment criteria. |
03.2 | OrderViewRS | Airline responds to the seller that the order is created, and the payment is expected using the payment method subject to redirection. Payment time limit is applied at this point. Any applicable surcharge amounts are also precisely calculated and returned. |
04.1 | OrderChangeRQ | Seller accepts to pay for the order with the selected payment method subject to redirection. |
04.2 | OrderViewRS | Airline responds to the seller that the payment is in a “PENDING” state and returns the redirection URL for the Payer to proceed to the payment transaction. |
05.1 | OrderChangeNotifRQ | Airline notifies the seller that the payment is approved (with a status of “SUCCESSFUL“), time limits are removed, and all OrderItems are considered as paid. |
05.2 | Acknowledgement | Seller acknowledges reception of notification. |
06.1 | OrderRetrieveRQ | Seller optionally retrieves the Order to confirm changes are reflected, as provided by the previous OrderChangeNotifRQ. |
06.2 | OrderViewRS | Airline returns the latest version of the Order. |
Postconditions
Airline has successfully processed a payment using redirection.
Seller is in receipt of an Order.
Payment is confirmed as successful.
Data Elements
3.2 OrderViewRS
…/PaymentFunctions/PaymentSupportedMethod/PaymentRedirectionInd | Current Method of Payment is subject to redirection |
…/PaymentFunctions/PaymentSupportedMethod/PaymentTypeCode | CC - Customer Card |
.../PaymentFunctions/PaymentSupportedMethod/PaymentBrandCode | VI - VISA |
…/Order/OrderItem/Service/DeliveryStatusCode | CONFIRMED |
4.1 OrderChangeRQ
…/PaymentProcessingDetails/PaymentMethod/OfflinePayment/PaymentBrandCode | VI for this kind of payment |
…/PaymentProcessingDetails/PaymentMethod/OfflinePayment/PaymentTypeCode | CC - Customer Card |
…/PaymentProcessingDetails/PaymentMethod/OfflinePayment/PayerReturnURI | Success URL |
…/PaymentProcessingDetails/PaymentMethod/OfflinePayment/RedirectionAcceptanceInd | Set to True as seller accepts redirection |
4.2 OrderViewRS
…/PaymentFunctions/ PaymentProcessingSummary/ PaymentProcessingSummaryPaymentMethod/ PaymentGatewayURI | Redirection URL |
.../PaymentFunctions/ PaymentProcessingSummary/PaymentID | ID for the payment transaction |
.../PaymentFunctions/ PaymentProcessingSummary/ PaymentStatusCode | PENDING |
…/Order/OrderItem/Service/DeliveryStatusCode | CONFIRMED |
5.1 OrderChangeNotifRQ
.../Notification/ChangeGroup/ChangeOperationGroup/ChangeOperation/Old/PaymentFunctions/ PaymentProcessingSummary/PaymentStatusCode | PENDING |
…/Notification/ChangeGroup/ChangeOperationGroup/ChangeOperation/New/PaymentFunctions/PaymentProcessingSummary/PaymentStatusCode | SUCCESSFUL |
../Notification/ChangeGroup/ChangeOperationGroup/ChangeOperation/Old/Order/OrderItem/PaymentTimeLimitDateTime | Removed payment time limit against the paid order items. |
…/Notification/ChangeGroup/ChangeOperationGroup/ChangeOperation/Old/Order/OrderItem/Service/DeliveryStatusCode | CONFIRMED |
…/Notification/ChangeGroup/ChangeOperationGroup/ChangeOperation/New/Order/OrderItem/Service/DeliveryStatusCode | READY TO PROCEED |
Ensure resolution to missing DeliveryStatusCode (OCN/OrderHistoryRS) is in effect in schemas prior to publishing document.