Ticketing Terminal APIs Specifications

Dedicated interfaces according to software layer

2 levels of APIs are offered to address the Reader or the Calypso layers, from the lowest to the highest:

• at the bottom the ‘reader layer’ generic interfaces:
  • the Reader API to control any reader solution and manage the application selection on a smart card,
  • the Card API for interfacing a card processing library specific to a smart card solution.
• Just below ‘smartcard solution layer’ specific interfaces:
  • several interfaces to integrate Calypso processing support:
    • Card and Legacy SAM APIs to perform secure transactions with Calypso cards or with Calypso security modules such as SAM-S1 or SAM-C1.
    • Symmetric Crypto and Asymmetric Crypto APIs to interface Calypso SAM or Calypso PKI processing libraries.

Dedicated interfaces according to development targets

The ticketing terminal APIs are differentiated according to development objectives:

• in “green” 🟢, high-level public reader and Calypso APIs dedicated to the design of applications on ticketing terminals.
• in “orange” 🔶, internal APIs dedicated to the design of middleware for smart card solutions (Calypso or others).