Direct payment carriers

IndiGo

IndiGo is supported in Smartpoint as a Direct Payment Carrier.

Airline Code

IndiGo (6E)

More Information

See IndiGo - 6E - General Information in the Travelport Knowledge Base.

Supported Currencies

IndiGo prices the itinerary in the currency of the city of origin. When looking at shopping results, the currency displayed is the equivalent price in the agent’s local currency to ease comparison between shopping options.

Note: Available forms of currency may vary by form of payment. See KB0024962: IndiGo - 6E - General Information for details.

Credential Requirements

As of 08 August 2017:

Agencies that do not have credentials specific to IndiGo can search and book IndiGo segments. However, Credit Cards are the only accepted form of payment.
Agencies that have credentials specific to IndiGo can book IndiGo segments using both Credit Cards and Agency Payment.

More Information

To use IndiGo credentials, your Agency Administrator must:

Register for a Corporate or Retail Agency ID at https://book.goindigo.in/Agency/Register?linkNav=Agency_Register. If your agency already has this ID, go to Step 2.

Enable your IndiGo credentials in Smartpoint or in the Universal Admin Portal.

To enable in Smartpoint, a user with second-level access rights must change the ZPROV table for Inigo (6E).

Enter ZPROV/6E/ACT-Y/ACC-AAA111/UID-BBB222/PSW-CCC333, where AAA111 is the Login ID, BBB222 is the Agency ID, and CCC333 is the agent password.

Booking Requirements

Required Customer Information for Direct Payment Carriers.

Required Customer Information for Direct Payment Carriers

Direct Payment Carriers have a different set of required Customer Information for PNR/Booking Files than Network (GDS) Carriers.

When booking with all Direct Payment Carriers, the following information is required in the PNR/Booking File.

Customer Information
Comments

Passenger Title

By default, the following titles are supported for Direct Payment Carriers. However, specific carriers may support a different list of titles.

MR

MRS

MISS

MS

MASTER

MSTR

Galileo and Apollo: Enter Z*NT to display a list of titles accepted by a specific carrier.

Passenger Names

Phone

A minimum of one Phone field is required.

Email

A minimum of one email address is required. If multiple email addresses exist, the first email address is sent to the Direct Payment Carrier.

Address

A minimum of one Customer Address or Delivery Address is required, including street address, city, state/province, ZIP/postal code, and country code.

Form of Payment

By default, the following forms of payment are supported for Direct Payment Carriers. However, specific carriers may support different forms of payment.

CREDIT CARD

DEBIT CARD

AGENCY PAYMENT

CASH

TRAVEL ACCOUNT CARD

PREPAID CARD

On the Payment tab, the Form of Payment drop-down only lists forms of payment accepted by the selected carrier. If a form of payment was added from a profile, changing the form of payment overrides the profile and changes for the form of payment for this PNR/Booking File only.

Galileo Terminal Equivalent: List of Accepted Forms of Payment

ZF* or ZF*Cxx (where xx is the two-letter airline code) to display a list of forms of payment accepted by a specific carrier.

Loyalty Membership (if applicable)

If applicable, ensure that the loyalty membership information is present before requesting a Fare Shopping search (FS) or Fare Quote (FQ).

Secure Flight Passenger Data (if applicable)

APIS/Secure Flight Passenger Data is required for all flights with an origin or destination in the United States, as well as for all flights that travel in US air space.

Some Direct Payment Carriers may also require additional Customer Information, such a birth date or citizenship, to complete a booking. If a PNR/Booking File is end transacted without all of the required Customer Information for the selected carrier, an error indicates the missing data that is required to complete the booking.

See information for individual Direct Payment Carriers for PNR/Booking File information required by each carrier.

Customer Information	Comments
Passenger Title	By default, the following titles are supported for Direct Payment Carriers. However, specific carriers may support a different list of titles. MR MRS MISS MS MASTER MSTR Galileo and Apollo: Enter Z*NT to display a list of titles accepted by a specific carrier.
Passenger Names
Phone	A minimum of one Phone field is required.
Email	A minimum of one email address is required. If multiple email addresses exist, the first email address is sent to the Direct Payment Carrier.
Address	A minimum of one Customer Address or Delivery Address is required, including street address, city, state/province, ZIP/postal code, and country code.
Form of Payment	By default, the following forms of payment are supported for Direct Payment Carriers. However, specific carriers may support different forms of payment. CREDIT CARD DEBIT CARD AGENCY PAYMENT CASH TRAVEL ACCOUNT CARD PREPAID CARD On the Payment tab, the Form of Payment drop-down only lists forms of payment accepted by the selected carrier. If a form of payment was added from a profile, changing the form of payment overrides the profile and changes for the form of payment for this PNR/Booking File only. Galileo Terminal Equivalent: List of Accepted Forms of Payment ZF* or ZF*Cxx (where xx is the two-letter airline code) to display a list of forms of payment accepted by a specific carrier.
Loyalty Membership (if applicable)	If applicable, ensure that the loyalty membership information is present before requesting a Fare Shopping search (FS) or Fare Quote (FQ).
Secure Flight Passenger Data (if applicable)	APIS/Secure Flight Passenger Data is required for all flights with an origin or destination in the United States, as well as for all flights that travel in US air space.

IndiGo also has the following specific requirements in the Primary Documentation Information (DOCS):
Gender
Date of Birth for Child (ages 2-11 inclusive) or Infant (ages 0-1) passengers.
Nationality

Equivalent Travelport+ (1G) Format

See KB0012355 in the Travelport Knowledge Base for Galileo Formats in SSR DOCS.

Equivalent Apollo (1V) Format

See KB0014440 in the Travelport Knowledge Base for Apollo Formats in SSR DOCS.

Optional Modifiers

Promotional Codes can be used, if available for the fare, route, and agency.

More Information

The Promotional (promo) Code must specified before end transacting the booking. The code can be added in either:

The Promotional Code field of a Fare Shopping request.

A cryptic entry in the pricing request.

Travelport+ (1G) : FQ-PC<promo code value>. For example: FQ-PCINDIGO83, where INDIGO83 is the Promo Code value.

Apollo (1V): $B-PC<promo code value>. For example: $B-PCINDIGO83, where INDIGO83 is the Promo Code value.

If discounted fares are available, the pricing response returns the discount as negative fee in the fare breakdown.

Frequent flyer (loyalty) memberships are not supported by IndiGo.
Both paid and free seats are available. The availability and price of seats varies depending on the passenger's selected fare brand. All seats are displayed as paid seats, with free seats identified by 0.00 price. The Free Seats filter is not available in seat maps for Indigo.

Note that IndiGo returns a record locator for the reservation, but does not return e-ticket numbers.

Supported Forms of Payment

See KB0024962: IndiGo - 6E - General Information in the Travelport Knowledge Base for details and instructions.

Credit Cards/Debit Cards.
Personal cards only, business cards are not supported. Supported cards vary by currency.
BSP Payment.
Availability varies by country and agency. Agencies interested in BSP Payment should contact their IndiGo Account Manager.
Agency Payment
For Form of Payment, the PCC used for Agency Payment is must be provisioned with the agency account code in the 'Access Code' field of the IndiGo (6E) ZPROV table.

Note: To book with Agency Payment, an agency must be provisioned for Indigo-specific credentials.

More Information

The PCC to be used for agency payment needs to be provisioned with the agency account code in the “Access Code” field of the IndiGo (6E) ZPROV table.

When Agency Payment is selected as the Form of Payment:

The 'Agency ID' and 'Password' fields need to be filled with the agency account code and User ID password, respectively.

The Agent ID value must be the same as the agency account code specified in the ZPROV table.

The Password field supports upper case (capital) letters only.

Confirmation

IndiGo automatically sends email notifications to the traveler for bookings created through Travelport Smartpoint.

Supported Functionality

Functionality	Supported by Travelport	Comments
Fare Shopping	Yes
Branded Fares	Yes
Ancillary Services	Yes
Price	Yes
Book	Yes
Retrieve	Yes
Modify	Yes	Modify segments and add ancillaries after booking.
Cancel	Yes	Cancel segments and PNRs/Booking Files.

This link does NOT provide Help Desk support. If you need immediate assistance with Travelport Smartpoint, please create a support request in MyTravelport or use your agency's normal method to contact the Help Desk.