Within EASD Payment, there are two distinct Payment Transaction types and two distinct Payment Process types. Different forms of payment can be supported by each, but for the purpose of this implementation guide, the following methods are assumed to be supported in the following matrix
|Payment Transaction||Direct||- Customer Card|
- Value Store (Ticket/EMD/OrderItem)
- Loyalty Points
|Indirect||- Alternative Transfer Method (Agent card)|
|- BSP [Cash]|
- ARC [Cash]
- Bilateral [Other]
This concept is used to describe whether, from an airlines perspective, a payment is directly between them and the customer, or whether it is with a third party such as an agent. The two types of transactions can be illustrated in the following table:
Direct: In a “direct transaction”, there is “one step” in the payment flow: Customer → Airline
Indirect: In an “indirect transaction” there are “two steps” in the payment flow: Customer → Agent and Agent → Airline. These payment steps may be unrelated to each other in any way.
This concept is use to describe whether an NDC message is used to transport a payment payload or not. There are two types.
Online: Uses NDC for payment instrument data exchange. For example, payment via card where all elements required in order to authorize the payment are contained in the Payment Function "Payment Processing Details"
Offline: Does not use NDC for payment data exchange. For examples, payment via redirect where payment authorization will take place using a separate data exchange.