Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Payment statuses were simplified in a change request balloted for 21.3 release. The statuses support the following basic requirements:

Successful

Ensures that successful payments are communicated between parties involved in order payment, fulfilment and settlement processes across online and offline payment processes.

Card Payment

  • As an airline accepting payment via card, I need to communicate a successful payment transaction so that the payer is informed.

  • As a payer, I need to know that my card payment was successful

  • As a seller, I may need to inform the payer that a card payment was successful

BSP Payment

  • As an airline accepting payment via BSP, I need to communicate a successful payment transaction so that the payer is informed

  • As a seller, I need to know that BSP payment was successful.

EasyPay Payment

  • As an airline accepting payment via EasyPay, I need to communicate a successful payment transaction so that the payer is informed.

  • As a payer, I need to know that my EasyPay payment was successful

Other Payment

  • As an airline accepting other payments, I need to communicate a successful payment transaction so that the payer is informed

  • As a seller, I need to know that other payments were successful.

Failed

Ensures that unsuccessful payment transactions are communicated between parties involved in order payment, fulfilment and settlement processes across online and offline payment processes, optionally  allowing a payment recovery processes to be triggered.

Card Payment

  • As an airline accepting payment via card, I need to communicate an unsuccessful card payment status when a payment transaction fails.

  • As a payer, I need to know that my card payment was unsuccessful

  • As a seller, I may need to inform the payer that a card payment was unsuccessful

EasyPay Payment

  • As an airline accepting payment via EasyPay, I need to communicate an unsuccessful payment transaction so that the payer is informed.

  • As a payer, I need to know that my EasyPay payment was unsuccessful

Other Payment

  • As an airline accepting other payments, I need to communicate an unsuccessful payment transaction so that the payer is informed

  • As a seller, I need to know that other payments were unsuccessful.

Pending

Ensures that an offline payment transaction state can be communicated between parties involved in order payment, fulfilment and settlement processes.

Offline Payment

  • As an airline, I may need to communicate a pending payment status when a payment is processed outside NDC messages and the payment process is not complete.

  • As a seller, I need to know that payment is pending so that I can inform a payer.

  • As a payer, I need to know that payment is pending so that I can complete payment.