EN 15320:2007

• Abstract:

  This European Standard specifies sets of data presented at an interface, the card sub-system interface, in a structured form as well as the rules for dealing with that data to enable products such as tickets to be written to a Machine Readable Card in a manner which will minimise the amount of data to be held on the card while allowing an authorised party to be able to access and interpret the data easily and efficiently.; This is the basis for practical interoperability and as such, this European Standard forms the foundation of interoperability across systems subject to commercial agreements and interchange of details concerning how this European Standard has been physically interpreted. As part of this capability, the design of the data environment allows for the addition of new sets of data to represent new or modified transport products without compromising the ability of existing terminals to continue to handle all sets of data held on the card, whether or not they are to be interpreted and possibly used.; Associated with the data is the set of processes which applies to the data within the application. The inclusion of process in the standard means that similar data will be treated in a similar way by all external services and terminals leading to true interoperability that can be achieved and maintained through this European Standard. In addition, acknowledgement that the application specifies both data and process also implies that it needs to consider security both at the level of access rights to data and the security of the overall environment in which it operates.

• Status: Published
• Publication Date: 04-Dec-2007
• Withdrawal Date: 29-Jun-2008
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: CEN/TC 224 - Machine-readable cards, related device interfaces and operations
• Drafting Committee: CEN/TC 224/WG 11 - Transport applications
• Current Stage: 9093 - Decision to confirm - Review Enquiry
• Start Date: 23-Nov-2022
• Completion Date: 17-Sep-2026
• Ref Project: SIST EN 15320:2011 - Identification card systems - Surface transport applications - Interoperable Public Transport Applications - Framework

• Refers: ISO/IEC 7816-4:2005 - Identification cards — Integrated circuit cards — Part 4: Organization, security and commands for interchange
• Effective Date: 25-Aug-2026
• Refers: EN 4160:2011 - Aerospace series - Paints and varnishes - Determination of the effect of thermal exposure
• Effective Date: 28-Jan-2026
• Refers: EN 1545-1:2005 - Identification card systems - Surface transport applications - Part 1: Elementary data types, general code lists and general data elements
• Effective Date: 28-Jan-2026
• Refers: EN 1545-2:2005 - Identification card systems - Surface transport applications - Part 2: Transport and travel payment related data elements and code lists
• Effective Date: 28-Jan-2026

Overview - EN 15320:2007 (Interoperable Public Transport Application)

EN 15320:2007 ("Identification card systems - Surface transport applications - Interoperable Public Transport Applications - Framework") is a CEN European Standard that defines a technology‑neutral framework for storing and exchanging public‑transport ticketing data on a Machine Readable Card. It specifies sets of data (data groups) and the rules for how terminals and external services should access and treat that data to achieve practical interoperability between different operators, systems and cards while minimizing data held on the card.

Key aims:

• Define a structured card sub‑system interface for ticket products and related data.
• Enable multiple operators/terminals to read, interpret and (subject to commercial agreements) write interoperable tickets.
• Allow extension with new product data without breaking support on existing terminals.
• Include process and security considerations so similar data is handled consistently.

Key topics and technical requirements

• Data groups and structures: Formal grouping of product, event log and control data to minimize on‑card storage and support extensibility.
• Abstract interfaces: Defined logical interfaces - the card data interface and the data group interface - that terminals use to access application data.
• Application security: Access rights, data protection and overall environment security requirements to control who can read/write data.
• Profiles and control data: Mechanisms to identify application profiles and manage capability/versioning so terminals can interoperate even when new data sets are added.
• Legacy support and migration: Guidance for interfacing legacy ticketing systems with the interoperable application.
• Normative mappings and tags: Use of standardized data elements (EN 1545) and ASN.1 tag allocations for consistent encoding.

Documents and annexes include data group definitions, mapping tables, example flows, event log formats and implementation notes.

Practical applications and users

Who uses EN 15320:2007:

• Public transport operators and transit authorities planning interoperable ticketing
• System integrators and back‑office vendors building fare management systems
• Smartcard manufacturers and card issuers implementing machine readable cards
• Terminal manufacturers (validators, gates, on‑board devices)
• Consultants, standards teams and procurement officers evaluating interoperability

Typical use cases:

• Contactless smart ticketing across multiple operators and regions
• Multi‑operator season tickets, carnets, stored travel rights
• Migration paths from legacy card systems to interoperable schemes
• Defining card/terminal interfaces to minimize card data while secure access is ensured

Related standards

• EN 1545‑1 / EN 1545‑2 (elementary data types, transport/payments data elements)
• ISO/IEC 14443 Parts 1–3 (contactless card physical and protocol layers) - adherence required for interoperability
• CEN/TC 224 publications and later amendments to EN 15320

EN 15320:2007 provides a practical, standards‑based foundation for interoperable fare management and machine readable card applications in surface transport.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Sistemi z identifikacijskimi karticami - Aplikacije za prevoze po kopnem - Aplikacija za interoperabilni javni prevoz - OkvirIdentifikationskartensysteme - Landgebundene Transportanwendungen - Interoperable Anwendungen für den öffentlichen Verkehr - RahmenwerkSystèmes de cartes d'identification - Applications pour le transport terrestre - Applications de transport public interopérablesIdentification card systems - Surface transport applications - Interoperable Public Transport Applications - Framework35.240.60Uporabniške rešitve IT v transportu in trgoviniIT applications in transport and trade35.240.15Identifikacijske kartice in sorodne napraveIdentification cards and related devicesICS:Ta slovenski standard je istoveten z:EN 15320:2007SIST EN 15320:2011en01-maj-2011SIST EN 15320:2011SLOVENSKI
STANDARD
EUROPEAN STANDARDNORME EUROPÉENNEEUROPÄISCHE NORMEN 15320December 2007ICS 35.240.15 English VersionIdentification card systems - Surface transport applications -Interoperable Public Transport Applications - FrameworkSystèmes de cartes d'identification - Applications pour letransport terrestre - Applications de transport publicinteropérablesIdentifikationskartensysteme - LandgebundeneTransportanwendungen - Interoperable Anwendungen fürden öffentlichen Verkehr - RahmenwerkThis European Standard was approved by CEN on 8 September 2007.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this EuropeanStandard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such nationalstandards may be obtained on application to the CEN Management Centre or to any CEN member.This European Standard exists in three official versions (English, French, German). A version in any other language made by translationunder the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the same status as theofficial versions.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMITÉ EUROPÉEN DE NORMALISATIONEUROPÄISCHES KOMITEE FÜR NORMUNGManagement Centre: rue de Stassart, 36
B-1050 Brussels© 2007 CENAll rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 15320:2007: ESIST EN 15320:2011

Data group definitions.44 Annex B (normative)
Identification and mapping of data groups.48 Annex C (normative)
EN 1545 data elements enumerated for use in the application.72 Annex D (normative)
ASN.1 Tag allocations.86 Annex E (informative)
General requirements.95 Annex F (informative)
Examples.103 Annex G (informative)
Accessing the Interoperable Public Transport Application.140 Annex H (normative)
Relationship between legacy systems and the Interoperable Public Transport Application.143 Annex I (informative)
Supporting Legacy Systems.146 Bibliography.149
Figure 1 — Interoperable Fare Management system This European Standard describes the basis of an environment which aims to achieve the following objectives:  to provide a basis for offering machine readable interoperable tickets across the public transport network in Europe;  to satisfy the demand for securing a seamless journey for the passenger allowing them travel with all participating operators, possibly in different networks and countries, using a single card while in the context of not inhibiting commercial competition. This European Standard describes those components of the application necessary to support an interoperable environment including:  accessing the Interoperable Public Transport Application;  data structure and presentation;  sizing and enumeration of data;  data access methodology;  security and access considerations;  dealing with legacy systems. SIST EN 15320:2011

abstract syntax notation form of notation used to describe data elements and processes, standard for CEN documentation 3.2
account record of the current value and (truncated) transaction history of a product held on the ‘back office’ system of the ‘product owner’ 3.3
anonymous card card which is not linked to a named holder, but which will still bear a traceable serial number 3.4
anti-tear describes measures taken to ensure that any intentional alteration of data in the customer media during normal use does not lead to un-recoverable corruption of the customer media 3.5
application instance of the Interoperable Public Transport Application resident on a Machine Readable Card or other customer media 3.6
application owner entity which holds the application contract for the use of the application with the customer 3.7
application retailer entity which sells and terminates applications, collects and refunds value to a customer as authorised by the application owner 3.8
Card Accepting Device device which can interact with a card and exchange data with the card 3.9
card holder person who owns the right to use the card 3.10
Charge to Account facility/process for post-billing - rather than pre-payment or payment at the time of purchase (subtype of product) 3.11
check in – check out holders actively validate cards when entering and leaving defined areas specified by a transport provider 3.12
concession entitlement to a reduced (or zero cost) fare on the basis of age, condition or status SIST EN 15320:2011

contract expression of an agreement between two or more parties in the transport environment. It defines the conditions under which the user may use the services. Products such as tickets or entitlements represent a contract 3.14
customer media entity which at least supports the same functionality as a Machine Readable Card but may be in a different form factor 3.15
data element single store for an irreducible datum value (see EN 1545-1) 3.16
entitlement entitlement or qualification for a service expressed as a product (a type of product template) 3.17
hot list list of cards, applications, products or items of equipment where a transaction requires special attention 3.18
Interoperable Fare Management encompasses all systems designed to manage the acquisition and use of fare products data in an interoperable public transport environment 3.19
interoperability ability of systems to provide services to and accept services from other systems 3.20
journey complete sequence of one or more journey legs (rides) required to achieve a specific purpose at a specific destination. This sequence may include the use of more than one vehicle and using more than one transport mode (see EN 1545-1) 3.21
key binary string which is used to control access to an application or product, or which is used as the basis of encryption or during the calculation of Message Authentication Codes 3.22
loyalty rewards for use of transport services 3.23
Message Authentication Code computed field based on data in previous stated fields which allows a message to be verified as genuine SIST EN 15320:2011

Machine Readable Card token or entity that conforms to ISO/IEC 14443 Parts 1 to 3 3.25
profile
means to achieve interoperability between different card platforms 3.26
product enables a customer to benefit from a transport service. It is an instance of a product template in the application. It is identified by a unique identifier. The Interoperable Public Transport Application distinguishes between four subtypes of a Product: CTA, STR, ticket and entitlement 3.27
product owner entity which performs the functions of ownership (specifies pricing, usage rules and commercial rules), clearing and reporting 3.28
product retailer entity which sells and terminates products, collects and refunds value to a customer as authorised by a product owner 3.29
product rules product owner requirements (set of usage, pricing and commercial rules) 3.30
product specification specification of function, data elements and security schema according to product rules 3.31
product template technical master of the product specification for implementation. A unique identification (product template ID) is given to each product template by the registrar, triggered by the product owner 3.32
retailer see: product retailer, application retailer 3.33
ride component of a journey 3.34
route reference to a single path through a transport network 3.35
seal guarantee of authenticity SIST EN 15320:2011

service operator entity which provides the service to the customer against the use of a product 3.37
Stored Travel Rights specialised form of closed e-purse for travel. (subtype of product template which uses transport tokens in place of currency) 3.38
ticket entitlement for a journey (subtype of product) 4 Symbols and abbreviated terms 3DES Triple DES AFI
Application Family Identifier AID
Application Identifier AM-DO Access Mode Data Object ASN.1 Abstract Syntax Notation One ATQ Answer to Request ATS Answer To Selection BER Basic Encoding Rules CAD Card Accepting Device
CDS Control Data Structure CEN European Committee for Standardisation CICO Check in – Check out CRC Cyclic Redundancy Check CTA Charge to Account DES Data Encryption Standard FCP File Control
ID
Identity IEC
International Electrotechnical Commission IFM
Interoperable Fare Management ISO
International Organisation for Standardisation MAC Message Authentication Code SIST EN 15320:2011

Tag Length Value 5 Basic structure of application components1) 5.1 Data element A data element in this European Standard is one of the data element entities described in the EN 1545. It is the lowest hierarchical entity of data discussed in this European Standard. Each element shall be associated with a tag and length descriptor to form a TLV data object according to ASN.1 conventions.
Figure 2 — Data element within a data object Most of the data elements used in this European Standard are specified as ASN.1 primitive data elements and are originally defined in EN 1545 and enumerated in Annex C. In a few specific cases, the data elements used in this European Standard are formed as constructed data objects based on their definition in EN 1545.
1) The subclauses below describe the terminology used in this European Standard to refer to data. SIST EN 15320:2011

Figure 3 — Data structure Data structures are classified for the purpose of convenience by type as follows: M Mandatory (data structures that shall be present within a specific data group [see 5.3]); A Additional (additional data structures that are normally created when the data group [see 5.3] or product is created. Data in these structures is normally not altered during the life of the data group which should be reflected in the security subsystem access rights applying to the data structure within the data group containing the data structure); L Logging (additional data structures that are normally created during the lifetime of the data group [see 5.3] or product. Data in these structures may be fixed and not alterable once created or it may be updateable from time to time dependent upon requirement and the access rights applying to the access structure as controlled by the security subsystem). 5.3 Data group A top level grouping of data structures concatenated together as ASN.1 a constructed TLV object to identify major groupings of data accessible as a coherent set through the Tag.
Figure 4 — Data group The M data structure will always appear first in a data group, while A and L type data structures may appear in any order, however, A type structures will normally be created when the data group is created while L type structures will usually (but not always) be added after the data group has been created. It is usual therefore, but not mandatory, for the data group to be constructed in the sequence M, A…, L…
Figure 5 — Relationships between the data groups SIST EN 15320:2011

- for the life of the application on the card holder
- until explicitly released product Stored Travel Rights - until no longer required and explicitly released Charge to Account
- until no longer required and explicitly released customer entitlement - until no longer required and the space is required ticket
- until no longer required and the space is required (wrapper
- until no longer required and the space is required) event - for the life of the Application on the card, space re-used on a cyclic record basis 6.9 Data group mandatory structures 6.9.1 General Annex B details the mandatory data elements in the mandatory data structures (Type M) for each different type of data group. While there are some data element
...