IATA EasyPay integration API
home
Introduction
This page describes the high level and common content for the IATA EasyPay integration API
API Summary
The purpose of this API is to support integrations between external systems and the IATA EasyPay platform, to perform a certain set of operations:
- Generate IEPN
- View Wallet Balances
Glossary
| Term | Description |
|---|---|
| Agency | An Agency is a travel agent which is a customer of IATA and is identified by unique 8 digit IATA Code. An Agency has a type ('Head Entity' or 'Associate Entity') and a state |
| IEP Account | An IEP Account a collection of related Agencies (e.g. branches of the same organisation). An IEP Account has at most one Agency of type 'Head Entity' and the IEP Account is uniquely identified by the IATA Code of that Agency. IEP Accounts also have states |
| Wallet | EasyPay Wallets have a currency and a balance and are used to store funds that will be used to pay for purchases. Each EasyPay wallet has a state (Open or Closed) and a funding method (Directly funded, or Indirectly funded). Every EasyPay Wallet belongs to an Agency, and Agencies may have multiple Wallets, but only in currencies available in the Agency's BSP. Additionally, An Agency is allowed only one Open, Directly funded wallet at any one time (but can have any number of Indirectly funded wallets or closed wallets) |
| IEPN | IATA EasyPay Numbers (IEPNs) are payment cards that can be generated on demand and used to pay for purchases in GDSs. IEPNs can only be issued from wallets which have a positive balance, an Open state, belong to an Agency in an Approved state, and belong to an IEP Account in an Open state |