EN 1545-2:2005

SLOVENSKI STANDARD
01-december-2005
6LVWHPL]LGHQWLILNDFLMVNLPLNDUWLFDPL±$SOLNDFLMH]DSUHYR]HSRNRSQHP±GHO
(OHPHQWLSRGDWNRYLQVH]QDPLSUDYLO]DSODþLODSUHYR]RYLQSRWRYDQM
Identification card systems - Surface transport applications - Part 2: Transport and travel
payment related data elements and code lists
Identifikationskartensysteme - Landgebundene Transportanwendungen - Teil 2:
Datenelemente und Codelisten für Zahlungsvorgänge in Transport- und
Reiseanwendungen
Systemes de cartes d'identification - Applications pour le transport terrestre - Partie 2:
Eléments de données et listes de codes relatifs au paiement du transport
Ta slovenski standard je istoveten z: EN 1545-2:2005
ICS:
35.240.15 Identifikacijske kartice in Identification cards and
sorodne naprave related devices
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 1545-2
NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2005
ICS 35.240.15 Supersedes ENV 1545-2:1998
English Version
Identification card systems - Surface transport applications -
Part 2: Transport and travel payment related data elements and
code lists
Systèmes de cartes d'identification - Applications pour le Identifikationskartensysteme - Landgebundene
transport terrestre - Partie 2: Eléments de données et listes Beförderungsanwendungen - Teil 2: Datenelemente und
de codes relatifs au paiement du transport Codelisten für Zahlungsvorgänge in Transport- und
Reiseanwendungen
This European Standard was approved by CEN on 19 May 2005.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the Central Secretariat or to any CEN member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the Central Secretariat has the same status as the official
versions.
CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36  B-1050 Brussels
© 2005 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 1545-2:2005: E
worldwide for CEN national Members.

Contents Page
Foreword .6
Introduction.7
1 Scope .9
2 Normative references .10
3 Terms and definitions.10
4 Abbreviations .12
5 Approach for definitions of data types.12
6 Transport and Travel Payment related Data Elements with Associated Code lists.12
6.1 AccommodationClassCode.12
6.2 AssistanceTypeCode.13
6.3 DiscountCode.13
6.4 ExtraServiceCode .14
6.5 FareBasisCode.14

6.6 JourneyTypeCode.15
6.7 LoyaltyTypeCode .15
6.8 MultiProductTypeCode.15
6.9 PaymentMeansCode.16
6.10 PaymentModeCode.16
6.11 PaymentScopeCode .16
6.12 PaymentUnit .17
6.13 SeatPositionCode .17
6.14 STRLoadCode .18
6.15 UrbanAddOnCode.18
6.16 ValidationModelCode.18
7 Transport and Travel Payment related data elements .18
7.1 AccompaniedBy.18
7.2 AccountNumber .18
7.3 AmountPaid.19
7.4 AppDepositRefundableFlag .19
7.5 AutoloadEndDate.19
7.6 AutoloadStartDate.19
7.7 AutoRenewFlag.19
7.8 Balance .19
7.9 CompanionAllowedFlag .19
7.10 CountOfCharges .19
7.11 CountOfCoupons .20
7.12 CountOfJourneyLegs .20
7.13 CountOfJourneys.20
7.14 CountOfJourneysPerPeriod.20
7.15 CouponsAutoload.20
7.16 CouponsDeducted .20
7.17 CouponsLoaded.20
7.18 CumulativeFare .20
7.19 DebitingAmount .20
7.20 DecrementedCountOfJourneys .21
7.21 Deposit.21
7.22 DepositRefundableFlag .21
7.23 Destination .21
7.24 DiscountLevel .21
7.25 DossierId .21
7.26 DownPayment .21
7.27 DynamicDiscount.22
7.28 ExpiryDateOffset.22
7.29 FareDeducted.22
7.30 FareNotChargedFlag.22
7.31 InterchangesAllowed.22
7.32 JourneyDistance .22
7.33 JourneyRunId.22
7.34 LineId .23
7.35 LoadAmount.23
7.36 LoyaltyMembershipId .23
7.37 LoyaltyPoints .23
7.38 LoyaltySchemeId .23
7.39 ManualPricingFlag .23
7.40 MaxAmountLimit.24
7.41 MaxNumberOfCharges .24
7.42 MaxTripsPerDayOfWeek.24
7.43 MaxValidJourneys .24
7.44 MinAmountLimit.24
7.45 NotVia .24
7.46 NumberOfAdults .24
7.47 NumberOfChildren.24
7.48 NumberOfCompanions.25
7.49 NumberOfConcessionaryAdults.25
7.50 NumberOfConcessionaryChildren.25
7.51 NumberOfConcessionaryPassengers .25
7.52 NumberOfPassbacks .25
7.53 Origin .25
7.54 OverbookingIndicator.25
7.55 PartFareAmount.25
7.56 PassbackTime .25
7.57 PassengerTotal .26
7.58 PaymentMeansId.26
7.59 PaymentMeansPriorityFlag .26
7.60 PaymentProvider.26
7.61 PayMethod.26
7.62 PeriodJourneys.26
7.63 Price.26
7.64 PriceModificationLevel .27
7.65 PricingLevel.27
7.66 ProductId .27
7.67 ProductLoadDateStamp .27
7.68 ReceiptPrintedFlag .27
7.69 ReceiptToPrintFlag .27
7.70 ReservationReferenceId .28
7.71 RouteId .28
7.72 RouteVariantId .28
7.73 SeatAlphaId .28
7.74 SeatNumber.28
7.75 ServiceOperatorUsageIndicator .28
7.76 SmokingFlag .28
7.77 STRIdentifier.29
7.78 STRProvider .29
7.79 STRTransactionAmount .29
7.80 TariffNumber .29
7.81 ThresholdAmount .29
7.82 TicketToPrintFlag.29
7.83 TicketTransferFlag.29
7.84 TimeAllowed.30
7.85 TrainNumber.30
7.86 TransferTimeLimitFS .30
7.87 TransferTimeLimitSS .30
7.88 TravelServiceId .30
7.89 TripsPerDayOfWeek.30
7.90 VATAmount .31
7.91 VATPercentage .31
7.92 Via .31
7.93 Zone .31
7.94 ZoneCount.31
7.95 ZoneMap .31
8 Data elements for low memory capacity ICs.32
8.1 General .32
8.2 ChildFlag .32
8.3 ClassFlag.32
8.4 CurrencyFlag.32
8.5 ExpiryTimeIndicatorCode.32
8.6 LocationTypeFlag .32
8.7 OffPeakOnlyFlag .32
8.8 ValidityItem.33
8.9 WeekdayValidityFlag .33
9 Encoding rules .33
10 Backwards compatibility .33
11 Transport general module definition.33
Annex A (normative) Assignment of object identifiers.40
Annex B (normative) Tags .41
Annex C (informative) Index .46
Bibliography.49

Foreword
This European Standard (EN 1545-2:2005) has been prepared by Technical Committee CEN/TC 224
“Machine readable cards, related device interfaces and operations”, the secretariat of which is held by AFNOR.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by April 2006, and conflicting national standards shall be withdrawn at the
latest by April 2006.
This European Standard comprises the following parts, under the general title "Identification card systems -
Surface transport applications":
General part:
Part 1: Elementary data types, general code lists and general data elements.
Sector specific part:
Part 2: Transport and travel payment related data elements and codes.
This European Standard supersedes ENV 1545-2:1998.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Cyprus, Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland
and United Kingdom.
Introduction
ICs offer far greater opportunities for use in surface transport applications (STA) when compared to magnetic
stripe and barcoded cards. The standardisation of data elements, which is the purpose of this European
Standard, facilitates the use of ICs across multiple transport applications and operators, and in a variety of
transport related terminals. This European Standard also permits application builders to minimise data
duplication.
This European Standard contains definitions of data formats, data elements and specifies data elements with
associated codelists related to transport and travel payment. It is for use in the creation of surface transport
related data structures that may reside on a transport application. Abstract Syntax Notation One (ASN.1) has
been used in the definition of data types in this European Standard.
This European Standard provides a comprehensive toolbox of data elements and types as the basis for the
creation of data structures to be used in STAs. This European Standard alone does not ensure
interoperability; this is left to the application builders. The definition of data structures to be used in STAs is left
to applications.
This European Standard has a hierarchical approach:
1. basis for all definitions used in this European Standard is ASN.1 (ISO/IEC 8824);
2. EN1545-1 standardises its general elements, data types and data elements with associated code lists in
accordance with ASN.1;
3. The sectoral parts of this European Standard (EN 1545-2) define the sector specific elements and codes.
Apart from the sector specific codes that are directly based on ASN.1 all definitions of sector specific data
elements have to be based on EN 1545-1 definitions;
4. It is left to the applications to define the relevant data structures (data objects) strictly based on the
definitions of EN 1545:
4. Any transport application
data structures (sets)
sector specific data elements from EN 1545-sectoral
sector specific codes from EN 1545-sectoral
general data elements from EN 1545-1
elementary data types from EN 1545-1
general data elements with code lists from EN 1545-1

3. EN 1545-sectoral
Sector specific data elements
general data elements from EN 1545-1
elementary data types from EN 1545-1
sector specific code lists
codes expressed in ASN.1
2. EN 1545-1
general data elements
elementary data types from EN 1545-1
universal ASN.1 types from ISO/IEC 8824
general data elements with associated code lists
codes expressed in ASN.1
elementary data types
universal ASN.1 types from ISO/IEC 8824

1. ISO/IEC 8824
universal ASN.1 data types
This European Standard refers to existing ASN.1 encoding rules (transfer syntaxes), such as the basic and
packed encoding rules, for use within surface transport applications. However this European Standard does
not exclude the use of other encoding rules. The abstract syntax notation (ASN.1) has been used in the
definition of data types (i.e. ASN.1 types) in this European Standard.
The ASN.1 basic encoding rules (BER) includes significant redundancy in order to make transferred data fully
self-defining, which may result in data structures too large to be used in applications on ICs with restricted
data storage capacity. Therefore this European Standard allows the use of alternative encoding rules such as
the ones based upon the ASN.1 packed encoding rules (PER) (see Clause 9).
This European Standard does not pretend to identify and specify every possible ASN.1 type that may be used
in future applications by application builders. In addition, local systems may be defined in their own way.
This European Standard will be updated and added to over time as new surface transport applications are
created in the normal CEN practice.

1 Scope
This European Standard specifies data formats, data elements and data elements with associated code lists
for use within Surface Transport Applications on ICs. This European Standard defines those data elements
and code lists related to transport and travel payment and the specific data elements needed for low memory
capacity ICs.
The mechanism for how to establish the application context, including the decision of which encoding rules to
use, is outside the scope of this European Standard.

2 Normative references
The following referenced documents are indispensable for the application of this European Standard.
For dated references, only the edition cited applies. For undated references, the latest edition of the
referenced document (including any amendments) applies.
EN 1545-1:2005, Identification card systems — Surface transport applications — Part 1: Elementary
data types, general codelists and general data elements
ISO 4217, Codes for the representation of currencies and funds
3 Terms and definitions
For the purposes of this European Standard, the following terms and definitions apply.
3.1
account
held in a central location, used for payment for services. When payment is made through the use of a card,
the card identifies the centrally held account
[EN 1545-1:2005]
3.2
contract
specific relationship between a transport service provider and a customer. The contract defines the conditions
under which the customer may use the services which are predefined by the service provider. The contract
may also indicate how the customer is charged. In public transport, a ticket represents a contract
3.3
coupon
ticket in a group of tickets sold as a group, where each ticket has the same nominal value valid for one journey
e.g. a carnet or multi-journey ticket
3.4
currency
unit in which a value is expressed. This may be conventional legal currency or proprietary tokens
3.5
customer
individual or organisation which receives a service in a commercial relationship with a service provider
3.6
event
circumstance which causes data to be written to a machine readable card. This may be an external event or a
card event. The card may already be available at the Interface device, or it may be presented, which action
may itself create an event
3.7
first event
first of a set of related events which are deemed to constitute a single journey
3.8
holder
person or organisation that is recognised as being the authorised user of the application
3.9
interchange
transfer of a passenger from one vehicle to another between two journey segments
3.10
interface device
device used to interface with the Integrated Circuit Card
3.11
journey
complete sequence of one or more journey legs 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
3.12
journey segment
part of a journey in which the customer uses one vehicle only. Some journeys consist of just one segment
3.13
machine readable card
ID-1 standard card containing information that may be read or written to by a machine or a card reading
device
3.14
network
all coordinated lines of road based, rail based, water based transport within a defined geographical area
and/or under a specified authority where a card is uniquely used
3.15
operator
organisation responsible for the operation of a surface transport service
3.16
point
when used as a location reference, the smallest addressable location in space (where smallest will depend on
the context in which the reference is used)
3.17
purse
electronic purse
generic name for all types of card based payment means where value is expressed electronically on the card.
Applications may range from an inter-sector electronic purse to a prepaid value card for one application within
one company. In this latter case, the term On-board Account is sometimes used
3.18
route
ordered sequence of points passed through by a transport service
3.19
service
facilities provided and/or actions performed by an operator/service provider
3.20
transport mode
means of transport characterised by the technology of the vehicle and infrastructure employed
3.21
zone
area in which all points are considered identical from the point of view of fare collection
4 Abbreviations
For the purposes of this European Standard, the following abbreviations apply.
AID Application Identifier [ISO/IEC 7816-5:2004]
ASN.1 Abstract Syntax Notation One, [ISO/IEC 8824-1:2002]
BCD Binary Coded Decimal
BER Basic Encoding Rules, [ISO/IEC 8825-1:2002]
BIBO Be-in, Be-out
CAD Card accepting device
CICO Check-in, Check-out
CIBO Check-in, Be-out
EAN European Article Numbering
IC Integrated Circuit
IEP Inter Sector Electronic Purse according to the EC e-Money Directive 2000/46
MII Major Industry Identifier, [EN ISO/IEC 7812-1:2000]
PER Packed Encoding Rules
RFU Reserved for Future Use
STA Surface Transport Application
STR Stored Travel Rights
VAT Value Added Tax
WIWO Walk-in, Walk-out
5 Approach for definitions of data types
See EN 1545-1:2005, Clause 5.
6 Transport and Travel Payment related Data Elements with Associated Code lists
6.1 AccommodationClassCode
Code representing an accommodation class.
AccommodationClassCode ::= ENUMERATED {
unknown   (0),
first    (1),
second-standard-traveller (2),
small   (3),
large   (4),
business   (5),
economy   (6),
club    (7),
enhanced-standard  (8),
premium   (9),
rfuCEN1   (10),
rfuCEN2   (11),
rfuCEN3   (12),
networkIdSpecific1  (13),
networkIdSpecific2  (14),
networkIdSpecific3  (15)
}
6.2 AssistanceTypeCode
Code defining the service provided by service provider staff.
AssistanceTypeCode ::= ENUMERATED {
unspecified    (0),
assist-wheelchair-user   (1),
assist-visually-impaired-person  (2),
assist-hearing-impaired-person  (3),
assist-mobility-impaired-person  (4), -- without wheelchair
assist-persons-accompanied-by-infants (5),
assist-unaccompanied-minor  (6),
assist-mentally-handicapped-person (7),
rfuCEN1     (8),
rfuCEN2     (9),
rfuCEN3     (10),
rfuCEN4     (11),
networkIdSpecific1   (12),
networkIdSpecific2   (13),
networkIdSpecific3   (14),
networkIdSpecific4   (15)
}
6.3 DiscountCode
A code specifying the validity criteria and percentage discount to which the holder is entitled. On the basis of
the defined element the fare reduction is calculated in the CAD or background system.
DiscountCode ::= INTM
--no-reduction     (0),
--Percentage-discount-level-1    (1),
--Percentage-discount-level-2    (2),
--Percentage-discount-level-3    (3),
--Percentage-discount-level-4    (4),
--Percentage-discount-level-5    (5),
--reduction-on-basis-of-a-kilometre-calculation  (6),
--reduction-dependant-on-the-used-mode-of-transport (7),
--reduction-dependant-on-the-vehicle-class  (8),
--for-short-distance-bus-and-train-travel-up-to-50 km (9),
--for-long-distance-train-travel    (10),
--for-long-distance-bus-travel    (11),
--rfuCEN      (12.45),
--networkIdSpecific     (46.63)

6.4 ExtraServiceCode
Code identifying the extra service offered in a contract.
ExtraServiceCode ::= INTM
--none  (0),
--breakfast  (1),
--lunch  (2),
--dinner  (3),
--cold-buffet  (4),
--snack  (5),
--hot-drink  (6),
--child-extras  (7),
--infant-facilities (8),
--hot-buffet  (9),
--meal  (10),
--rfuCEN  (11.31),
--networkIdSpecific (32.64)
6.5 FareBasisCode
Code indicating the basis on which the price of a fare is calculated.
FareBasisCode ::= INTP
--undefined  (0),
--fare-code  (1),
--distance  (2),
--zones   (3),
--stops   (4),
--rides   (5),
--station-count  (6),
--rfuCEN   (7.15),
--networkIdSpecific (16.31)
6.6 JourneyTypeCode
A code indicating the type of journey defined in a travel contract.
JourneyTypeCode ::= ENUMERATED {
unspecified  (0),
single   (1),
return   (2),
circular   (3),
rfuCEN1   (4),
rfuCEN2   (5),
networkIdSpecific1 (6),
networkIdSpecific2 (7)
}
6.7 LoyaltyTypeCode
Indicates whether loyalty is held locally (on card) or on central account.
LoyaltyTypeCode ::= ENUMERATED {
undefined  (0),
oncard  (1),
centralAccount (2)
}
6.8 MultiProductTypeCode
Indicates the type of a multiple contract.
MultiProductTypeCode ::= ENUMERATED{
stored-single-journey-legs (0),
stored-multi-leg-journeys (1),
rfuCEN1   (2),
rfuCEN2   (3),
rfuCEN3   (4),
rfuCEN4   (5),
networkSpecific1  (6),
networkSpecific2  (7)
}
6.9 PaymentMeansCode
The means by which the payment is effected.
PaymentMeansCode ::= BIT STRING (SIZE(5))
mmmm Payment means (5 bits) :
'00000'  Unspecified
'00001'  Cash
'00010'  Cheque
'00011'  Credit-Debit-card
'00100'  IEP
'00101'  CTA
'00110'  Direct-Debit-offline
'00111'  Invoicing
'01000'  Stored-Travel-Rights
'01001'  Loyalty-redemption
'01010'  Token
'01011'  Membership-benefit
'01100'  Auto-Renew
'01101'  Warrant
'01110'  Voucher
‘11111’  Traveller-cheque
‘10000’  Cheque-Vacances
‘10001’  Direct-Debit-Online
‘10011’ - ‘10111’ rfuCEN
‘11000’ - ‘11111’ networkIDSpecific

6.10 PaymentModeCode
The payment mode identifies the timing of actual money transfer (e.g. ahead of or after the event).
PaymentModeCode ::= BIT STRING (SIZE(2))
pp Payment mode (2 bits) :
‘00’B : unspecified,
‘01’B : prepayment, (payment is affected in advance of travel)
‘10’B : postpayment, (payment is affected after travel, possibly in back office)
‘11’B : trippayment (payment is affected at the end of a trip, i.e. at check out)

6.11 PaymentScopeCode
The payment scope refers to the application extent of the payment method.
PaymentScopeCode ::= BIT STRING (SIZE(4))
ssss Payment Scope (4 bits) :
‘0000’B : Not further specified,
‘0001’B : Inter-Sector (Multi-purpose) International,
‘0010’B : Inter-Sector (Multi-purpose) National,
‘0011’B : Financial (banking) International specific,
‘0100’B : Financial (banking) National specific,
‘0101’B : Company (provider) specific,
‘0110’B : Inter-Company specific,
‘0111’B : Transport National specific,
‘1000’B : Transport International specific,
‘1001’B : Locally (regionally) specific,
‘1111’B : Proprietary, unspecified.

6.12 PaymentUnit
The unique designation of a currency shall be as defined in ISO 4217 using the ISO numeric representation.
The code can also express a company specific token or a 'charging unit code' as used in freight.
PaymentUnit ::= OCTET STRING (SIZE(2))
Value Assignment :
'0xxx’H Currency in main units,
'1xxx’H Currency in minor units of 10 :1
'2xxx’H Currency in minor units of 100 :1 ('cents'),
'3xxx’H Currency in minor units of 1000 :1,
'4xxx’H Currency in 'major' units / 10,
'5xxx’H Currency in 'major' units / 100,
'6xxx’H Currency in 'major' units / 1000,
'7xxx’H Currency in 'major' units / 10000,
'8xxx’H Currency in 'major' units / 100000
xxx BCD representation of Currency as defined in ISO 4217.
(928 for EURO)
'9xxx’H Tokens :
xxx Purse Provider specific coding.
'Axxx’H Charging Unit Codes denoting quantification of the service provided
(e.g. man-hours)
‘Bxxx’H Fare code
6.13 SeatPositionCode
To identify the position of the passenger seat with respect to the direction of travel.
SeatPositionCode ::= ENUMERATED {
unspecified   (0),
facing-direction-of-travel (1),
back-to-direction-of-travel (2),
airline   (3), --(fixed position)
facing-right   (4), --relative to direction of travel
facing-left   (5), --relative to direction of travel
rfuCEN   (6),
networkIdSpecific  (7)
}
6.14 STRLoadCode
Indicates how the STR is loaded.
STRLoadCode ::= ENUMERATED {
unspecified   (0),
threshold-autoload  (1),
internal-autoload  (2), --load from another value source
loaded-by-user  (3),
pre-selected-autoload (4),
periodic-autoload  (5),
rfuCEN2   (6),
rfuCEN3   (7)
}
6.15 UrbanAddOnCode
Indicates if a contract can be used for an urban journey in addition to the principle journey.
UrbanAddOnCode ::= ENUMERATED {
unspecified   (0),
urban-at-origin  (1),
urban-at-destination  (2),
urban-at-both  (3),
interchange   (4)
}
6.16 ValidationModelCode
Defines the validation model i.e. CICO, CI-Destination, BIBO.
ValidationModelCode ::= ENUMERATED {
unspecified    (0),
manual-preselection-immediately-validated (1),
manual-preselection-validation-required (2),
cico     (3),
bibo     (4),
cibo     (5),
wiwo     (6),
rfuCEN1     (7)
}
7 Transport and Travel Payment related data elements
7.1 AccompaniedBy
Defines the accompanying persons, objects or animals under the contract.
AccompaniedBy::= SEQUENCE {
accompaniedByType  ProfileCodeNetwork,
accompaniedByNumber  NumberOfCompanions
}
7.2 AccountNumber
The reference for a central account.
AccountNumber ::= IAI
7.3 AmountPaid
The amount of a transaction.
AmountPaid ::= Amount
7.4 AppDepositRefundableFlag
It indicates whether a deposit taken when the application was loaded is refundable without reference to the
product owner.
AppDepositRefundableFlag ::= Flag
0 = non refundable without referral, 1 = refundable
7.5 AutoloadEndDate
The last date upon which an autoload facility may be used.
AutoloadEndDate ::= DateStamp
7.6 AutoloadStartDate
The first date upon which an autoload facility may be used.
AutoloadStartDate ::= DateStamp
7.7 AutoRenewFlag
A flag indicating whether auto-renew is enabled.
AutoRenewFlag ::= Flag
0 = not enabled, 1 = enabled
7.8 Balance
Amount remaining e.g. in a purse or a stored travel rights accumulator.
Balance ::= SignedAmount
7.9 CompanionAllowedFlag
A flag indicating that, under the contract, a companion is allowed to travel at the same fare as the person
entitled to travel. No other evidence is required for the companion.
Co
...