I 73 Extend after sales conditions with permitted payment methods

I-73: Extend after sales conditions with permitted reimbursement methods

Description

Show, in a structured way, whether a reimbursement resulting from a refund or exchange should be payed out to the original payment device or handled via voucher. This information should be provided on the fare as well as on the product layer.

Owner

• Ralf Bayer / Clemens Gantert (DB)

Business Value

For distributors who want to aggregate after sales conditions from several offers to show to their customers, exposing the details of these conditions in a structured way in the offer is a necessity which is already handled by providing the afterSalesConditions attribute within the common offer parts.

This improvement adds the information about the prescribed reimbursement method (voucher or payment to original device) to the existing structure, which allows for a more fine grained interpretation of this structure.

Nonfunctional Requirements

This improvement implies no additional non-functional requirements

Specification Effort

SMALL

Proposed API change

Create a new object type ReimbursementMethod which has the property reimbursementMethod, which is an enum with the possible values ORIGINAL_PAYMENT_DEVICE and VOUCHER.

Extend the existing structures AfterSaleCondition and RefundOffer with a new attribute named reimbursementMethod which is of type ReimbursementMethod.

Note

Currently the ExchangeOffer has no way of specifying a possible reimbursement due to the exchange. If we want to handle partial cancellations via exchange (e.g. removing a number of passengers from a group booking when collective ticketing is used), then this needs to be considered.