idaCUPPS

Introduction

This file provides information specific to idaCUPPS emulator, which includes CUPPS support. idaCUPPS meets the IATA Common Use Passenger Processing System (CUPPS) standard by providing a CUPPS compliant library.

For additional information about idaCUPPS, visit the support site at https://www.ida-as.com/Support/

Important Notices

  • You can run idaCUPPS interface standalone.
  • This version includes support for CUPPS versions through 1.0, 1.01, 1.03 and 1.04.
  • Check the ReadMe folder for any instructions specific to using CUPPS

MSR / FOID Features

Additional Payment Card Industry (PCI) protection

When the airleine/DCS application type is set to MSR/FOID, sensitive data is obfuscated in accordance with the IATA FOID rules. What this means is, credit card information that appears in the MSR tracks is partially or wholly concealed by X characters, depending on the data type. (Credit card numbers are partially concealed; CVV codes are wholly concealed.)

Device Initialization

Initialization files for AEA devices are stored on the local drive with the permanent idaCUPPS files. The initialization files are small ASCII text files that contain the string pairs (outputs and expected responses on alternate lines) to initialize, set the mode and parameters, load logos, etc). The following three initialization files are included:

  • Setup for device communication settings
  • Initialisation commands for AEA devices.
  • Cupps specs

Locking

When airline app logged in, all configured CUPPS readers (i.e. MS, OC, and/or BC devices) on the system are locked, and are kept in a locked state until quit. The text document printer (PR device) is only locked when there is data to print. The PR device is left unlocked at other times.

CUPPS Modes

Boarding pass printers (BP), baggage tag printers (BT) and boarding gate readers (BG) are opened in AEA mode. All other devices, such as document printers and readers (OC, BC, MS) , are opened in Standard mode. Raw mode devices are not used.

Environmental Variables

The following CUPPS environment variables are referenced during startup:

CUPPSCN, CUPPSDSP, CUPPSPLT, CUPPSPN, CUPPSPP, CUPPSXSDD, CUPPSXSDL, CUPPSXSDU

The following CUPPS user specific environment variables are referenced during user login:

CUPPSACN, CUPPSAL2, CUPPSAL3, CUPPSALA, CUPPSAPD, CUPPSAPL, CUPPSAPU, CUPPSPGSD, CUPPSPGSL, CUPPSPGSU, CUPPSPLSD, CUPPSPLSL, CUPPSPLSU, CUPPSTSD, CUPPSTSL, CUPPSTSU, CUPPSUN

Supported Interface Levels

The following IATA CUPPS interface levels are supported:

  • 1.00
  • 1.01
  • 1.03
  • 1.04

The highest interface level is default. Airline/DCS applications may select lower versions at authentication. The same interface level is used for the platform connection and all device connections.

CUPPS XML Messages

The platform may respone any of following CUPPS XML message names:

  • “interfaceLevelsAvailableRequest”
  • “interfaceLevelRequest”
  • “authenticateRequest”
  • “deviceAcquireRequest”
  • “interfaceModeRequest”
  • “aeaRequest”
  • “aeaResponse”
  • “printRequest”
  • “deviceLockRequest”
  • “deviceUnlockRequest”
  • “readerReadRequest”
  • “deviceReleaseRequest”
  • “byeRequest”
  • “applicationStopCommandResponse”
  • “notify”
  • “messageIDErrorRequest ( v 01.00 only)”
  • “illogicalMessageErrorRequest ( v 01.00 only)”
  • “xmlParseFailureRequest ( v 01.00 only)”
  • “streamErrorBodyRequest ( v 01.00 only)”
  • “streamErrorHeaderRequest ( v 01.00 only)”
  • “readerOpenRequest ( v 01.00 only)”
  • “readerCloseRequest ( v 01.00 only)”

The platform may generate following CUPPS XML message names:

  • “interfaceLevelsAvailableResponse”
  • “interfaceLevelResponse”
  • “authenticateResponse”
  • “deviceAcquireResponse”
  • “interfaceModeResponse”
  • “aeaRequest”
  • “aeaResponse”
  • “printResponse”
  • “notify”
  • “deviceLockResponse”
  • “deviceUnlockResponse”
  • “readerReadResponse”
  • “deviceReleaseResponse”
  • “byeResponse”
  • “applicationStopCommandRequest”
  • “messageIDErrorRequest ( v 01.00 only)”
  • “illogicalMessageErrorRequest ( v 01.00 only)”
  • “xmlParseFailureRequest ( v 01.00 only)”
  • “streamErrorBodyRequest ( v 01.00 only)”
  • “streamErrorHeaderRequest ( v 01.00 only)”
  • “readerOpenResponse ( v 01.00 only)”
  • “readerCloseResponse ( v 01.00 only)”

Custom Configuration

Certain features of idaCUPPS are controllable via a idaCUPPS.dat file. (The options in the idaCUPPS.dat may vary according to the airline’s needs.). To enable an optional XML trace, disable pop-ups, or make other changes to the idaCUPPS interface, you can specify values in the idaCUPPS.dat file and save the modified file to the same directory as the local copy of the idaas app files on local hard disk. The modified local idaCUPPS.dat file will replace the original idaCUPPS.dat file located on the local disk. However, platform must be restarted for the new settings to take effect. These files will replaced with original configuration files when you logged out.

User Files

All permanent files for the platform are stored on the local drive. When you logged in the platform, temporary files (such as configuration and log files), are stored in the transient storage. These files are deleted when you quit the application.