Card API (internal)

Latest version 3.0.0

As part of the Reader Layer, the Card API defines the internal elements shared by the reader layer with the card layers built on top of it, such as the Calypso card layer.

The complete, versioned reference — types, operations, behaviour, diagrams and constraints — is maintained in the Card API specification. This page is only a short overview.


What it provides

  • APDU exchanges — requests and responses are carried by data types (ApduRequest, ApduResponse, CardRequest, CardResponse) and transmitted through the ProxyReaderApi.

  • APDU construction rules — the constraints a card extension must respect when building its APDUs are normative.

  • Limitations and constraints — the commands the API never transmits, and the status words the reader layer handles itself, are listed in the specification.

  • Execution-time control — each exchange may carry a maximum duration and report its effective duration, which is the basis of the timing countermeasures against relay and card emulation.


Learn more

→ Read the full Card API specification

Previous