The Billing and Settlement Plan is IATA’s global system for settling money between travel agencies and airlines, with ARC performing the equivalent role in the United States. It is not a technical specification but it functions as one: BSP/ARC accreditation determines who may issue tickets at all, and its documents — traffic documents, EMDs, agency numbers, ADMs — are the portable record layer of air travel commerce.
IATA BSP
BSP is how money moves between the agency that sold a ticket and the airline that must fly it, and in the United States ARC does the same job. Neither is a technical standard in the OpenAPI sense. Both behave like one, because accreditation under them is the precondition for issuing a ticket at all — which makes them the real access-control layer of air travel, sitting underneath every API the sector publishes.
- Accreditation is the gate - an IATA, ARC, TIDS or equivalent number is what permits ticketing. No amount of API access substitutes for it.
- The documents are portable - traffic documents under IATA Resolution 649, EMDs (Electronic Miscellaneous Documents), ticket numbers and agency numbers survive a change of system.
- Enforcement runs through ADMs - Agency Debit Memos, governed by IATA Resolution 850m, are how airlines claw back against agencies for policy breaches, and how distribution policy is actually enforced.
- BSP Link is the operational surface - the interface agencies actually work in, and it predates and outlives most airline API programmes.
What the evidence shows
The travel quartet found that the binding constraint on machine access in this sector is almost never technical. An agent can parse a specification, follow a discovery document and invoke an MCP tool. It cannot obtain BSP or ARC accreditation.
The State of Australian Travel APIs records the mechanism explicitly. Virgin Australia’s Travel Agent Main Agreement requires current IATA or ATIS accreditation and states “You must have GDS access for BSP Sales”, with refusal at Virgin’s absolute discretion, third-party credit assessment, and removal of ticketing authority after sixty days of inactivity. Rex ties commission to logged-in portal sessions and fixes the accreditation number permanently at registration. Jetstar restricts registered agents to its API, GDS and Agent Hub, making commercial booking through its own website an express breach.
Across the four markets, thirteen of forty newly researched organizations gate access behind a commercial agreement and seven more behind accreditation or a licence — only seven of forty are self-serve. That distribution, not any facet of API design, is what keeps travel the lowest-scoring sector this research programme has measured.
The State of Canadian Travel APIs adds the institutional irony: IATA operates this machinery from Montreal and scores 21.5 on its own published surface — tied with a tour operator and below a Crown-corporation railway — while the volunteer OpenTravel Alliance scores 55.1.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Canadian Travel APIs
The settlement machinery every airline in the quartet depends on — authored and operated by an organization whose own published surface scores 21.5.
The State of Australian Travel APIs
Virgin Australia's agency terms mandate GDS access for BSP sales outright — accreditation is the gate, not an API key.
Governed by these regulations
A standard is the machine-readable contract; a regulation is the law that requires it. These are the regulations that mandate or drive this standard, catalogued at regulations.apievangelist.com.
IATA Resolution 824
The Passenger Sales Agency Agreement — accreditation under it is the precondition for issuing a ticket and settling through BSP or ARC.
IATA Resolution 850m
Agency Debit Memos: how distribution policy is enforced, through a debit raised inside the settlement rail itself.
