Pay API Guide

The Travelport Pay APIs allow online travel agencies to request credit card authorizations, card and address validations, and reversals against a specific merchant vendor. As with other Travelport JSON APIs, the Pay API requests are RESTful and support JSON.

Related Content: Pay API References

In this guide:

Basic Concepts

The Travelport JSON Pay APIs allow customers to request credit card authorizations, address validations, and reversals against a specific merchant vendor.

The credit card authorization request supports 3D Secure, which stands for 3-domain structure, also called 3DS. 3DS is a security protocol to help prevent fraud in online credit and debit card transactions. Travelport extends the full benefits of 3DS authentication by accepting agency generated 3DS verification data and passing that data to the required US authorization vendors. This enhances existing functionality currently used to format and send payment card authorization transactions. It is assumed that all current US payment card authorization vendors accept and process 3DS verification data in their existing messaging structures. The JSON APIs expect possible re-certification by each authorization vendor before returning authorization transaction results.

Supported Credit Cards

The Pay APIs process the following credit cards:

Card Vendor

Card Code

Notes

Visa

VI

 

MasterCard

CA

 

American Express

AX

 

Discover Card

DS

Not available in all countries.

Diners Club

DC

Not available in all countries.

ELO

EL

Brazil only

Japanese Card Bureau

JC

Japan only

Universal Air Travel Plan (UATP)

TP

 

EasyPay

EP

Payment product of IATA (International Air Transport Association, a trade group).

Pay API List

The Pay API includes the following requests:

  • Payment Card Authorization: Verifies whether a cardholder's payment card is authorized for sufficient funds and approved for future settlement. Optionally, you can include 3DS data in this transaction, and send address details to perform an address verification as part of the same transaction.
  • Address Verification: Verifies that a customer’s payment card address and/or postal code matches the address recorded in the card issuer's system. Standalone request for use when address verification is not performed in the payment card authorization request.
  • Authorization Reversal: Notifies the issuer that the sale has been voided or canceled and the authorization hold should be released.
  • Card Validation: Verifies the card number length, BIN range, and LUHN algorithm.

You can find a list of codes that responses may return in Pay API Response Codes.