Open

In some LATAM markets, we offer passengers the ability, when paying by credit card, to pay for the Order in installments. The interest rates and number of installments allowed vary depending upon the country, the credit card used and the issuing bank.

Payment in Installments impacts the following messages:

• OfferPriceRS - where we return the acceptable payment methods and installment information when applicable.

• OrderCreateRQ - where the payment information is sent to us with the installment information when applicable for instant purchase bookings.

• OrderChangeRQ - Payment - where the payment information is sent to us with the installment information when applicable to pay for bookings on hold (not permitted to pay for changes and additions to Orders). For further information about Unpaid or on hold Orders in NDC, please visit our OrderChange 17.2 page.

• OrderViewRS - where we will return the installment payment applied.

The following are the Countries and Credit Cards, issued in those countries, where installment payment can be used as of October 2024:

*Number of quotas and interest rates are dynamic and may not be returned in the OfferPriceRS, and only be returned in the OrderViewRS for the OrderCreate and OrderChange-Payment.

Within an OfferPriceRS, in addition to the usual information, we also include the Payments and PaymentFormMetadata containing the information necessary for Installment payments, when they are applicable.

In addition to the usual form of payment information, when payment in Installments is available, the following will also appear in the OfferPriceRS message:

• PaymentCard refs links the payment type to the applicable Installment information in the PaymentFormMetadata.

• PaymentFormMetadata indicates the number of Installments and the interest rate applied.

• Amount is mandatory for the schema and will always have a value of '0' (zero).

In case this payment method is allowed for a specific card type, all Information will be stored in OtherMetadata.

For installments payment info, the MetadataKeyneeds to match the installments' reference in PaymentCard refs, as well as inPaymentFormMetadata refs.

For this market, PaymentCard1, which we know is the Visa, allows up to ten Installments.

In the example below, we can see <Text>installments/10/30.00</Text>, where ‘10’ is the number of installments and ‘30.00’ is the interest rate in % applied by card issuer:

Both the OrderCreateRQ and the OrderChangeRQ (Payment) contain the following elements:

• PaymentCard refs, where the element for the applicable Installment information is KEY_QUOTAS.

• PaymentFormMetadata with attribute MetadataKey which can be referenced from the Credit Card payment type, and contains the KEY_QUOTAS element.

• Text, where only the number of Installments is indicated.

In the following example, the CC used is EL ('ELO', specific to Brazil market):

PaymentFormMetadata contains the number of installments along with the interest rate in % applied by card issuer. TheMetadataKey element contains KEY_QUOTAS.

This is also used to reference the associated 3DS info in PaymentCardSecureInfo ObjectKey.

Note: If both 3DS and payment in Installments are being used for the same Order, then the two references are included here together separated by a space (e.g. <PaymentCard refs="KEY_3DS KEY_QUOTAS">.

The following are the errors that could be returned:

Open