Results for area 10.6
payment schemed defined applications relying on EMV technology
NOTE 1 to entry As opposed to a payment scheme application relying on magstripe emulation.
NOTE 2 to entry This is the type of payment application.
offline transaction at the reader for a null amount
EXAMPLE Null amount, e.g. £0.00 or 0€ or 0USD.
NOTE 1 to entry This transaction may not be possible on all cards now.
a ticket for a product printed by the passenger as specified by the carrier(s) on plain paper or a mobile phone display with optional security devices in the design and with optional optically readable product data which the TCO(s) for the transport service are equipped to read
NOTE 1 to entry A print-at-home ticket provides autonomous and independent title to the transport contract and does not require further information such as from a sales or reservation database.
NOTE 2 to entry Each RU as carrier maintains its own specifications for print-at-home tickets and is eligible to participate in the maintenance of the specification for print-at-home tickets used for international rail passenger services.
holder of the payment application
NOTE 1 to entry The cardholder has a contract with the issuer of its payment application. The media hosting the payment application may not necessarily be a “card“.
abstract object performing a set of functions within the IFM
NOTE An entity can exist in the real world (e.g. a service operator), in which case it is called a “legal entity”. It can also be a model of this real world object (“abstract entity”). It covers the following sets of functions: Application Owner, Application Retailer, Product Owner, Product Retailer, Service Operator, Collection and Forwarding, Security Manager, Registrar and Customer.
the process of fulfilment where the customer purchases a ticket other than at a station or face to face at a ticket vendor
NOTE 1 to entry Indirect fulfilment methods are conventional ticket on departure, print-at-home ticket, e-ticket and smart ticket on departure.
rules defining the settlement and commission within the IFMS
entity having the necessary terminal equipment for handling payment transaction at validation points
NOTE 1 to entry In ISO TR 14806, merchants are Public Transport Operators (PTOs).
legal entity covering the functions and implied responsibilities of one or more of the following operational entities: Application Owner, Application Retailer, Product Owner, Product Retailer, Service Operator, and Collection and Forwarding
payment institution having a contract with the merchant for handling the remittance and settlement of transit fares charged to customers using the transport network
NOTE 1 to entry Merchant in ISO TR 14806 is Public Transport Operator (PTO).
NOTE 2 to entry The acquirer may accept payments using payment applications from one or more payment application issuers, and/or for one or more payment application schemes/brands.
application resident either in a conventional payment card or an application loaded into a multiapplication customer media
NOTE 1 to entry As described in ISO/TR 24014-3.
opportunity for customers to move between one part of an IFMS to any other part of the same or another IFMS with the minimum of inconvenience, according to their own journey plan using any combination of transport mode and Service Operator using a single Medium
anyone who wants to bring a Component to the IFMS
application Ooner requirements
set of Usage, Pricing and Commercial Rules defined by the Product Owner
<public transport> the unique combination of some or all of origin, destination, route, specific trains, date and time, tariff type, and discount category that uniquely defines what transport service can be/has been purchased by the customer
NOTE 1 to entry Product in the transport sense is identical to the use of the word in the retail industry, being the unambiguous description of things that can be bought.
NOTE 2 to entry See also Attributing System.
device with the necessary facilities (hardware and software) to communicate with a Customer Medium
a set of computer-to-computer messages between involved parties including carriers, issuers, retailers, distributors, attributors, station managers and TCOs that allow for the indirect fulfilment of all types of tickets excluding a conventional ticket
list of items related to IFM Applications or Products, downloaded to Medium Access Devices (MADs), actioned by the MAD if and when a specific IFM Application or Product referenced in the list is encountered by that MAD
specification of functions, data elements and security scheme according to the Application Rules
complete specification of functions, data elements and security scheme according to the Product Rules
set of specifications designed to Install, select, process and delete Applications in the SE
payment brands that establish industry operating regulations for acquirers and issuers to facilitate coordination with merchants and cardholders
NOTE 1 to entry Payment application schemes can have international scope (VISA, MasterCard, JCB Intl) or a domestic one (ZKA, GIE Carte Bancaire).
technical master of the Product Specification for creating Products
NOTE The Product Template is identified by a unique identifier.
payment transaction where neither the card nor its holder are present at the point of sale
EXAMPLE Orders by telephone, fax or the Internet.
standard logical data storage within the payment application available for transit ticketing operations, even if this storage is open to other merchants
NOTE 1 to entry Transit data storage can take two implementation forms that determine their life cycle: included in the payment transaction log; separate, and available for non-payment needs.
device that holds a Secure Element initialised with one or more Applications
payment institution having a contract with the cardholder and issuing the payment application on a
contactless media
NOTE 1 to entry The issuer issues payment applications such as credit or debit cards and guarantees payment for properly authorized transactions using the payment application.
physical component, whatever its form factor (embedded, removable or not) that can be installed in a media to host Applications in a secure environment for their execution