Request-Level Fields

The tables in this section describe the airline request fields to use with a capture or credit request.

When you send a capture or credit request with airline data, you must include the basic fields required for every capture or credit request. For information about the non-airline-data fields required for capture and credit requests, see Credit Card Services Using the SCMP API.

 

Table 48

General Request Fields

CyberSource Field Name	UATP Field Name	Description	Required / Optional	Data Type & Length
airline_invoice_date	Invoice Date (INVD)	Invoice date. The format is YYYYMMDD. If this value is included in the request, it is used in the creation of the invoice number. See Invoice Number.	Optional	Integer (8)
airline_passenger_name	Passenger Name (PXNM)	Name of the passenger to whom the ticket was issued. Do not include special characters such as commas, hyphens, or apostrophes. Only ASCII characters are supported.	Required	String (49)
bill_trans_ref_no	Ticket/Document Number (TDNR)	Reference number or identifier for the ticket. Use this field only with captures. You must include this number because CyberSource does not generate it. This value must consist of 15 alphanumeric characters. The first 3 digits must be the airline code. The rest of the value can contain the booking reference or a unique numbering sequence followed by underscore padding. This value must be padded out to 15 characters using the underscore (_) character.	Required	String (15)
credit_trans_ref_no	Ticket/Document Number (TDNR)	Reference number or identifier for the ticket. Use this field only with credits. You must include this number because CyberSource does not generate it. This value must consist of 15 alphanumeric characters. The first 3 digits must be the airline code. The rest of the value can contain the booking reference or a unique numbering sequence followed by underscore padding. This value must be padded out to 15 characters using the underscore (_) character.	Required	String (15)

You must include information for at least the first leg of the trip (leg 0). You must use consecutive numbers for the legs; do not skip a number. If you skip a number, CyberSource ignores the legs that follow the skipped number.

Table 49

Request Fields for Travel Legs

CyberSource Field Name	UATP Field Name	Description	Required / Optional	Data Type & Length
airline_leg#_carrier_code	Carrier (CARR)	IATA1 code for the carrier for this leg of the trip.	Optional	String (4)
airline_leg#_leg_departure_date	Flight Date (FTDA)	Departure date for the first leg of the trip. The format is YYYYMMDD.	Optional	Integer (8)
airline_leg#_destination	Destination Airport/City Code (DSTC)	IATA1 code for the destination airport for this leg of the trip.	Optional	String (5)
airline_leg#_fare_basis	Fare Basis/Ticket Designator (FBTD)	Code for the fare basis for this leg of the trip. The fare basis is assigned by the carriers and indicates a particular ticket type, such as business class or discounted/nonrefundable.	Optional	String (15)
airline_leg#_originating_airport_code	Origin Airport/City Code (ORAC)	IATA1 code for the originating airport for this leg of the trip.	Optional	String (5)
airline_leg#_stopover_code	Stopover Code (STPO)	Code that indicates whether a stopover is allowed on this leg of the trip. Possible values: ■ O (capital letter “O”) (default): Stopover allowed ■ X (capital letter “X”): Stopover not allowed	Optional	String (1)
1 IATA=International Air Transport Association