Travel Bank Service

Digital Connect introduces the Travel Bank service to allow passengers to retrieve a list of transactions for a particular travel bank account along with a second service that allows retrieving additional information related to particular transactions (e.g. VCR/EMD), without the need for a double login to Customer Insight and Travel Bank separately. Instead, all transaction details are displayed to the logged-in passenger. By exposing this service, airlines gain the ability to control the type and format of data displayed to the customer.

Travel Bank service endpoints include:

• Travel Bank Statement API [/travelBank/getStatement]
• Travel Bank Transaction Details API [/travelBank/getTransactionDetails]

There are the following transaction types available in Travel Bank services:

• Ticket purchase / void ticket purchase
• Ancillary purchase / void ancillary purchase
• Ticket refund / void ticket refund
• Ancillary refund / void ancillary refund
• Administrative details
• Credit expiry extension
• Transfer service credit
• Transfer service credit fees

Prerequisites

• The passenger's login credentials must be passed using POST /login to authenticate the profile.

Request examples

• ​ POST /v4/dc/travelBank/getStatement​

{​
  "startDate": "2021-07-09",​
  "endDate": "2021-12-09",​
  "transactionsRange": "1-20"​
}

• ​POST /v4/dc/travelBank/getTransactionDetails

{​
  "transactionId": "12345"​
}

CST time is used for the transaction range dates used in travelBank/getStatement.

The default value for start and end dates is 6 months, and the default transaction number is 50 (based on configuration).

​User flow diagram

Activation

To consume either of the endpoints, there is activation required. Please contact your Delivery Manager for further details.

Error Handling

The Travel Bank service is the first fully Lingo compliant service, including error handling. The Lingo standard provides a different error structure compared to the legacy DC solution. The Travel Bank service is identified as an RPC API. Therefore, we always return an HTTP 200 code as HTTP is only a transportation layer in RPC. Errors are returned in payload and the customer must check the error list instead of the HTTP code.

Examples:

• Sending incorrect request - missing field

{​
  "startDate": "2021-07-09",​
  "endDate": "2021-12-10",​
  "transactionsRange": "1-20"​
}

{​
  "timestamp": "2022-03-01T16:08:21.395Z",​
  "errors": [​
    {​
      "category": "BAD_REQUEST",​
      "type": "INVALID_VALUE",​
      "description": "Validation Failed: must not be null",​
      "fieldName": "transactionsRange",​
      "fieldPath": "TravelBankStatementRequest"​
    }​
  ]​
}​

• Login not executed before call getStatement

{​
  "startDate": "2021-07-09",​
  "endDate": "2021-12-10",​
  "transactionsRange": "1-20"​
}

{​
  "timestamp": "2022-03-01T16:24:41.533Z",​
  "errors": [​
    {​
      "category": "APPLICATION_ERROR",​
      "type": "LOGGED_USER_REQUIRED",​
      "description": "User needs to be logged in."​
    }​
  ]​
}

Error Structure

Field	Type	Description
category	String	Indicates error category.
description	String	Provides detailed description.
fieldName	String	Requests field name if the error is caused by a bad request.
fieldPath	String	Requests field path if the error is caused by a bad request.
fieldValue	String	Requests field value if the error is caused by a bad request.
type	String	Indicates error type.

Error List

Error Type	Error Category	Description
INVALID_VALUE	BAD_REQUEST	Invalid request has been sent - validation error.
ATH_TOKEN_FAILURE	APPLICATION_ERROR	Problem with authentication to core system.
DOWNLINE_SERVICE_FAILURE	APPLICATION_ERROR	Problem with response from core system.
LOGGED_USER_REQUIRED	APPLICATION_ERROR	Service has been executed without user being logged with login service.
UNABLE_TO_RETRIEVE_CONFIGURATION	APPLICATION_ERROR	Unable to communicate with configuration service.
UNABLE_TO_STORE_SESSION_DATA	APPLICATION_ERROR	Unable to communicate with session service.
INTERNAL_SERVER_ERROR	APPLICATION_ERROR	Unexpected and unknown error.
TRAVEL_BANK_LOGGED_USER_REQUIRED	APPLICATION_ERROR	User is logged in into account with profile without profile associated.