03.060 - Finances. Banking. Monetary systems. Insurance
ICS 03.060 Details
Finances. Banking. Monetary systems. Insurance
Finanzen. Bankwesen. Wahrungssysteme. Versicherungswesen
Finances. Banque. Systemes monétaires. Assurance
Finance. Bančništvo. Monetarni sistemi. Zavarovanje
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 03.060 - Finances. Banking. Monetary systems. Insurance
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document specifies the security framework for using biometrics for authentication of customers in financial services, focusing exclusively on retail payments. It introduces the most common types of biometric technologies and addresses issues concerning their application. This document also describes representative architectures for the implementation of biometric authentication and associated minimum control objectives. The following are within the scope of this document: — use of biometrics for the purpose of: — verification of a claimed identity; — identification of an individual; — biometric authentication threats, vulnerabilities and controls; — validation of credentials presented at enrolment to support authentication; — management of biometric information across its life cycle, comprising enrolment, transmission and storage, verification, identification and termination processes; — security requirements for hardware used in conjunction with biometric capture and biometric data processing; — biometric authentication architectures and associated security requirements. The following are not within the scope of this document: — detailed specifications for data collection, feature extraction and comparison of biometric data and the biometric decision-making process; — use of biometric technology for non-financial transaction applications, such as physical or logical system access control.
- Standard65 pagesEnglish languagesale 15% off
- Draft67 pagesEnglish languagesale 15% off
This document specifies a concrete REST webservice API description of the processes and data (see
EN 17419-1:2020 for more information) as an OpenAPI definition specified by the OpenAPI specification.
- Technical report102 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft102 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines code values used to enable the classification of merchants into specific categories based on the type of business, trade or services supplied. Values are specified only for those merchant categories that are generally expected to originate retail financial transactions. It is not within the scope of this document to mandate the use of merchant category codes in any given situation.
- Standard2 pagesEnglish languagesale 15% off
This document specifies a concrete REST webservice API description of the processes and data (see
EN 17419-1:2020 for more information) as an OpenAPI definition specified by the OpenAPI specification.
- Technical report102 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft102 pagesEnglish languagesale 10% offe-Library read for1 day
This document examines semantic enrichment to support the maintenance of the ISO 20022 conceptual model. It reports on existing and proposed practices to enrich a model: — in a repository, annotating repository concepts with metadata using semantic markup or constraints; — outside a repository, using references to repository concepts, such as the provenance of changes.
- Technical report12 pagesEnglish languagesale 15% off
This document discusses the modes, related mainstream technologies, logical models, physical implementation models, data management (data storage and data security) and service quality control used in the reference data distribution in financial services. This document applies to the reference data distribution and transmission processes in financial services.
- Technical report15 pagesEnglish languagesale 15% off
- Draft15 pagesEnglish languagesale 15% off
- Draft15 pagesEnglish languagesale 15% off
This document provides guidelines for customer identification in mobile financial services (MFS), including: — a general framework of customer identification for MFS; — the multi-dimensional overall identity assurance level (AL) of an MFS customer and its evaluation criteria; — security and privacy considerations. This document also contains annexes which demonstrate how to apply the ALs in practice, through (e)KYC use cases in different regions, for example. This document is applicable to various kinds of MFS providers, including but not limited to commercial banks and third-party payment service providers. This document is applicable to identifying natural persons. Identifying legal entities, known as (e)KYB, is out of the scope of this document.
- Standard23 pagesEnglish languagesale 15% off
This document provides best practices for writing a banking products or services (BPoS) handbook. It is applicable to any providers of banking products or services (BPoSP) that issue and operate BPoS. NOTE 1 A BPoS handbook is edited by either product managers or personnel in charge of key elements mentioned in this document, based on their role and responsibility within the BPoSP. NOTE 2 Whether ISO 21586 has been formally introduced, this document is useful as existing BPoS contain the key elements listed in ISO 21586.
- Technical report15 pagesEnglish languagesale 15% off
- Draft15 pagesEnglish languagesale 15% off
- Draft15 pagesEnglish languagesale 15% off
This document gives guidance to organizations on the application of overarching sustainability principles, practices and terminology for financing activities. It addresses what is material from the perspective of the organization and of its stakeholders. This document is applicable to all organizations active in the financial sector, including, but not limited to, direct lenders and investors, asset managers and service providers. Beyond financial institutions and intermediaries, this document can be used by other parties in the financial sector such as providers or recipients of sustainable finance, governmental organizations, public and private sector institutions, business entities, industry associations, financial market regulators, and supervisory and control bodies.
- Standard26 pagesEnglish languagesale 15% off
This document reports on a study to map messages defined using FIX Orchestra into the ISO 20022 model.
- Technical report6 pagesEnglish languagesale 15% off
This document establishes a framework and outlines a process to identify criteria for environmental impacts and performance to take into account when considering projects, assets and activities seeking finance. This document also gives guidance on assessing the risks and opportunities that can arise in applying environmental criteria to projects, assets and activities. It is applicable to parties seeking finance, providing finance or other interested parties.
- Standard39 pagesEnglish languagesale 15% off
- Standard44 pagesFrench languagesale 15% off
This document defines a taxonomy of eligible investment categories for designation as green debt instruments, including bonds and loans. This document categorizes economic sectors and establishes criteria for determining the eligibility of projects, assets and supporting expenditures. It provides guidance on adaptation by sector in Annex A. It provides examples of thresholds and exclusions in Annex B.
- Standard128 pagesEnglish languagesale 15% off
- Standard151 pagesFrench languagesale 15% off
This document provides the normative specification of the FIX session layer standard and its session profiles.
- Standard79 pagesEnglish languagesale 15% off
This document specifies the elements and structure of a universal identifier code, the business identifier code (BIC), for financial and non-financial institutions, for which such an international identifier is required to facilitate automated processing of information for financial services. The BIC is used for addressing messages, routing business transactions and identifying business parties. This document applies to organizations and excludes individual persons.
- Standard5 pagesEnglish languagesale 15% off
This document provides a set of mandatory and optional conformity tests applicable to all versions of the FIX session layer standard.
- Standard15 pagesEnglish languagesale 15% off
This document provides the normative specification of the FIX tagvalue encoding, which is one of the possible syntaxes for FIX messages.
- Standard17 pagesEnglish languagesale 15% off
This document specifies an unambiguous scheme to list official organizational roles by jurisdiction in a standard way. It is not the purpose of this document to compare or align official organizational roles across different countries or jurisdictions, so as not to limit the usage or relevance of this document. To understand the powers associated with each official organizational role, users of this document can consult applicable regulation or legislation, documents of the legal entity in which the official organizational role exists and procedures specific to each organizational entity.
- Standard4 pagesEnglish languagesale 15% off
- Draft4 pagesEnglish languagesale 15% off
This document specifies the elements of an unambiguous scheme to identify over-the-counter (OTC) derivative products that are reportable to trade repositories, in particular: — the structure and format of the unique product identifier (UPI) code; — the minimum data elements of the UPI reference data library, together with their allowable values. At a minimum, the UPI code is applicable to OTC derivative instruments falling under the following categories of the classification of financial instruments (see ISO 10962): — swaps (S); — forwards (J); — non-listed and complex listed options (H); — others (miscellaneous) (M).
- Standard8 pagesEnglish languagesale 15% off
This document specifies a machine-readable, unambiguous natural person identifier (NPI) and the relevant reference data to uniquely identify the natural person relevant to any financial transaction rather than the personal identifying information.
- Standard13 pagesEnglish languagesale 15% off
- Draft13 pagesEnglish languagesale 15% off
This document defines the data elements included in the registry record and used to establish the 1:1 relationship between a digital token and the identifier assigned according to the method in ISO 24165-1.
- Standard16 pagesEnglish languagesale 15% off
- Draft16 pagesEnglish languagesale 15% off
This document defines the assignment and generation of a random, unique, fixed-length identifier for digital tokens in response to a request for registration that conforms to specified application guidelines (see also ISO 24165-2).
- Standard8 pagesEnglish languagesale 15% off
- Draft9 pagesEnglish languagesale 15% off
This document specifies requirements for verification bodies performing verification of claims of conformity to ISO 14030-1 or ISO 14030-2 and to ISO 14030-3 or a suitable substitute taxonomy. Conformity to the requirements of this document is mandatory for the verification of statements made by green debt issuers, borrowers and lenders that claim that their products conform to the ISO 14030 series. This document specifies requirements for the validation of claims of eligibility made in conformity to ISO 14030-1:2021, 5.4, ISO 14030-2:2021, 6.3, and ISO 14030-2:2021, 7.3. This document also establishes requirements for the optional use of third-party marks of conformity.
- Standard12 pagesEnglish languagesale 15% off
- Standard12 pagesFrench languagesale 15% off
- Draft11 pagesEnglish languagesale 15% off
- Draft14 pagesFrench languagesale 15% off
This document establishes principles, specifies requirements and gives guidelines: for designating as “green” loans which finance eligible projects, assets and supporting expenditures; for managing and reporting on the use of proceeds; for defining, monitoring and reporting on the environmental impacts; for reporting to interested parties; for validation and verification. This document is applicable to any borrower seeking financing by way of a green loan for eligible green projects, assets and supporting expenditures. It is also applicable to lenders.
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesFrench languagesale 15% off
- Draft14 pagesEnglish languagesale 15% off
- Draft16 pagesFrench languagesale 15% off
This document establishes principles, specifies requirements and gives guidelines: for designating bonds which finance eligible projects, assets and supporting expenditures as “green”; for managing and reporting on the use of proceeds; for defining, monitoring and reporting on their environmental impacts; for reporting to interested parties; for validation and verification. This document is applicable to any issuer of bonds.
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesFrench languagesale 15% off
- Draft14 pagesEnglish languagesale 15% off
- Draft18 pagesFrench languagesale 15% off
This document provides a non-exhaustive list of relevant basic concepts, key initiatives and terms that are in common use in the global community of sustainable finance, and have been identified by ISO/TC 322 as helpful to facilitate a greater understanding of the topics suggested by sustainable finance practitioners, including but not limited to: financial regulators, development and commercial banks, asset managers, investors, international initiatives and researchers. The terms included in this document have been selected because they are: widely accepted and used in financial markets; sourced from supranational organization(s) or initiative(s), or national regulatory authorities; NOTE With priority given to the source with the larger geographic coverage. likely to be used in documents from ISO/TC 322 and other related International Standards; of international prevalence and interest.
- Technical report35 pagesEnglish languagesale 15% off
- Technical report33 pagesFrench languagesale 15% off
- Draft31 pagesEnglish languagesale 15% off
This document aims to provide an introduction to the topic of creating a conceptual model for storing multidimensional data which is received as XBRL instances that follow the rules defined by European taxonomies published by the European Banking Authority (EBA) or by the European Insurance and Occupational Pensions Authority (EIOPA).
- Standard52 pagesEnglish languagesale 15% off
- Draft52 pagesEnglish languagesale 15% off
This document defines the Data Point Methodology for the creation of Data Point Models in the context of European supervisory reporting. Data Point Models are published by a European supervisory authority. To reflect the defined structures in a machine-readable form, they can be accompanied by an XBRL taxonomy. It is also possible to extend the described methodology to other environments.
- Standard18 pagesEnglish languagesale 15% off
- Draft18 pagesEnglish languagesale 15% off
This document provides guidelines for data point modelling for supervising experts. The main body consists of four sections. The interrogative form helps in choosing which section may best answer your question and lead you to a good understanding of the subject matter. After this first introductory section and the section containing terms and definitions, the main part starts to provide basic knowledge about different types of data models and data modelling approaches. The first and the second sections provide an overview of data models in general, in contrast to the third section that highlights the necessity of data modelling for supervisory data. This third section draws on the objectives and background information of the preceding sections. Furthermore, a paragraph classifies the Data Point Model introduced by the Eurofiling Initiative and elaborated by EIOPA and EBA, where many new terms related to DPM are introduced. Another paragraph explains the areas of application for the DPM. The third section concludes with a paragraph introducing a subset of the technical constrains that need to be considered in the creation process of the DPM. The fourth section gives step-by-step instructions on how to create a DPM. The paper concludes with remarks on the progress achieved so far, and provides an outlook on the software that is being developed at the moment to support you during the creation process.
- Standard36 pagesEnglish languagesale 15% off
- Draft36 pagesEnglish languagesale 15% off
This document defines a common terminology to be used in the context of third-party payment (TPP). Next, it establishes two logical structural models in which the assets to be protected are clarified. Finally, it specifies security objectives based on the analysis of the logical structural models and the interaction of the assets affected by threats, organizational security policies and assumptions. These security objectives are set out in order to counter the threats resulting from the intermediary nature of TPPSPs offering payment services compared with simpler payment models where the payer and the payee directly interact with their respective account servicing payment service provider (ASPSP). This document assumes that TPP-centric payments rely on the use of TPPSP credentials and the corresponding certified processes for issuance, distribution and renewal purposes. However, security objectives for such processes are out of the scope of this document. NOTE This document is based on the methodology specified in the ISO/IEC 15408 series. Therefore, the security matters that do not belong to the TOE are dealt with as assumptions, such as the security required by an information system that provides TPP services and the security of communication channels between the entities participating in a TPP business.
- Standard40 pagesEnglish languagesale 15% off
- Draft40 pagesEnglish languagesale 15% off
This document defines the process and the structure of the transfer of electronic documents, and facilitates the transfer of electronic documents between stakeholders in the insurance industry.
- Standard65 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft58 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines and describes the structure for the codes for an internationally valid system to classify financial instruments. The classification system applies to financial instruments negotiated internationally as well as to domestic instruments. The term “financial instruments” refers not only to classical securities and derivatives but also covers the innovative financial products that have emerged in different markets (a trend that is expected to continue in the future). This document is intended for use in any application in the trading and administration of financial instruments in the international securities business. Insofar as the trading and administration of securities do not affect other countries, the application of this document remains at the discretion of the responsible national bodies, such as stock exchanges, banks, brokers, regulatory bodies and other institutions active in the securities field. In principle, the CFI code reflects characteristics that are defined when a financial instrument is issued and that remain unchanged during its entire lifetime. However, a few events that can lead to a new CFI code for the same instrument are anticipated, such as the changing of voting rights or ownership restrictions by a stockholders' meeting.
- Standard9 pagesEnglish languagesale 15% off
- Standard9 pagesEnglish languagesale 15% off
- Draft9 pagesEnglish languagesale 15% off
This document specifies a general framework, including principles, requirements and guidance for assessing, measuring, monitoring and reporting on investments and financing activities in relation to climate change and the transition into a low-carbon economy. The assessment includes the following items: — the alignment (or lack thereof) of investment and financing decisions taken by the financier with low-carbon transition pathways, adaptation pathways, and climate goals; — the impact of actions through the financier’s investment and lending decisions towards the achievement of climate goals in the real economy, i.e. mitigation (greenhouse gas emissions) and adaptation (resilience); — the risks to owners of financial assets (e.g. private equities, listed stocks, bonds, loans) arising from climate change. To support the financier’s assessment of the impact of investment and lending decisions, this document provides guidance for the financier on how to: — set targets and determine metrics to be used for tracking progress related to the low-carbon transition pathways of investees; — determine low-carbon transition and adaptation trajectories of investees; — document the causality or linkage between its climate action and its outputs, outcomes and impacts. This document is applicable to financiers, i.e. investors and lenders. It guides their reporting activities to the following third parties: shareholders, clients, policymakers, financial supervisory authorities and non-governmental organizations.
- Standard43 pagesEnglish languagesale 15% off
- Standard47 pagesFrench languagesale 15% off
- Draft43 pagesEnglish languagesale 15% off
- Draft52 pagesFrench languagesale 15% off
This document provides a uniform structure for the identification of financial instruments as well as referential instruments (see Annex A) using a unique identification code and associated minimum descriptive data (see Annex B).
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesEnglish languagesale 15% off
- Draft15 pagesEnglish languagesale 15% off
The standard defines the transfer of electronic documents between stakeholders in the insurance industry (for
example between insurer and intermediary).
The standard specifies:
the semantic process for the transfer of documents (for example insurance policy, claim notification,
correspondence) that may be transferred as an attached file and
a limited number of meta data describing the document (for example type of document, identification of
insurer, intermediary and client, policy number, claim number).
- Standard65 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft58 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes the Registration Authority (RA) responsible for the registry of IBAN formats that conform with ISO 13616-1, the procedures for registering IBAN formats that conform with the ISO 13616 series and the structure of the registry.
- Standard3 pagesEnglish languagesale 15% off
- Draft3 pagesEnglish languagesale 15% off
This document specifies the elements of an international bank account number (IBAN) used to facilitate the processing of data internationally in data interchange, in financial environments as well as within and between other industries. The IBAN is designed for automated processing but can also be used conveniently in other media interchange when appropriate (e.g. paper document exchange). This document does not specify internal procedures, file organization techniques, storage media or languages to be used in its implementation, nor is it designed to facilitate the routing of messages within a network. It is applicable to the textual data which might be conveyed through a system (network).
- Standard8 pagesEnglish languagesale 15% off
- Draft8 pagesEnglish languagesale 15% off
This document specifies how to describe the characteristics of banking products or services (BPoS) from a customer's perspective. Characteristics of a BPoS can be observed from different facets, called key elements, which are divided into three groups: required, optional or voluntary elements. This document elaborates on the purpose, content and description approach for the required and optional key elements. Six levels of conformity are described in this document which are intended to allow a customer to assess the coverage of key elements in a BPoS. The logical and physical formats to express key elements are also defined. This document excludes requirements of a BPoS itself and specific value ranges of any key element are out of the scope. This document guides the provider of BPoS in describing their products or services with the intent to help customers understand or compare specific BPoS. It is not applicable to describing securities or insurance-related products or services. BPoS can be issued by banks and other institutions.
- Standard51 pagesEnglish languagesale 15% off
This document specifies the minimum elements of an unambiguous legal entity identifier (LEI) scheme to identify the legal entities relevant to any financial transaction. It is applicable to "legal entities", which include, but are not limited to, unique parties that are legally or financially responsible for the performance of financial transactions or have the legal right in their jurisdiction to enter independently into legal contracts, regardless of whether they are incorporated or constituted in some other way (e.g. trust, partnership, contractual). It includes governmental organizations, supranationals and individuals when acting in a business capacity[1], but excludes natural persons. It also includes international branches as defined in 3.5. The LEI is designed for automated processing. It can also be conveniently used in other media interchange when appropriate (e.g. paper document exchange). NOTE Examples of eligible legal entities include, without limitation: — all financial intermediaries; — banks and finance companies; — international branches; — all entities that issue equity, debt or other securities for other capital structures; — all entities listed on an exchange; — all entities that trade financial instruments or are otherwise parties to financial transactions, including business entities, pension funds and investment vehicles such as collective investment funds (at umbrella and sub-fund level) and other special purpose vehicles that have a legal form; — all entities under the purview of a financial regulator and their affiliates, subsidiaries and holding companies; — sole traders (as an example of individuals acting in a business capacity); — counterparties to financial transactions. [1] As stated by the LEI Regulatory Oversight Committee on 30 September 2015.
- Standard8 pagesEnglish languagesale 15% off
This document specifies a standardised way of embedding the legal entity identifier (LEI) code, as represented in ISO 17442-1, in digital certificates, represented by the International Telecommunications Union (ITU) Recommendation X.509 and its ISO equivalent standard, ISO/IEC 9594-8. This document specifies the structure of a public key certificate conforming with ISO/IEC 9594-8 in which the LEI is embedded.
- Standard5 pagesEnglish languagesale 15% off
This document specifies the elements of an unambiguous scheme to identify a financial transaction uniquely whenever useful and agreed by the parties or community involved in the transaction. It does not specify the timing of assignment of who should be responsible for its generation, so as not to limit its usage or relevance, nor does it consider a need to establish a data record for the unique transaction identifier (UTI) itself.
- Standard3 pagesEnglish languagesale 15% off
This International Standard specifies the elements and structure of a universal identifier code, the business identifier code (BIC), for financial and non-financial institutions, for which such an international identifier is required to facilitate automated processing of information for financial services. The BIC is used for addressing messages, routing business transactions and identifying business parties. This International Standard applies to organizations and excludes individual persons.
- Standard6 pagesEnglish languagesale 15% off
- Standard9 pagesEnglish languagesale 10% offe-Library read for1 day
This document gives an overview of existing and currently used financial instrument identifiers. It shows which instrument identifiers, ticker symbols and proprietary codes are assigned via a standardized scheme to instruments of all asset classes. It focuses on providing an overview of the landscape and not on evaluating the schemes. Several aspects of the detailed trade cycle (a few examples being book building/primary, order entry management, execution management and trade confirmation matching) are excluded as their complexity would reduce the readability of the overview. Similarly, the level of complexity involved in properly representing the shifting perspectives of what is considered a financial instrument, based on a particular function being performed, is excluded.
- Technical report4 pagesEnglish languagesale 15% off
This International Standard provides a uniform structure for the identification of fungible and nonfungible
securities and financial instruments (see Annex A) using a unique identification number and
associated minimum descriptive data (see Annex B).
- Standard11 pagesEnglish languagesale 15% off
- Standard16 pagesEnglish languagesale 10% offe-Library read for1 day
ISO/TR 21941:2017 reports the findings of research into the interface between third-party payment service providers (TPPs) and account servicing payment service providers (ASPSPs).
- Technical report19 pagesEnglish languagesale 15% off
ISO 20275:2017 specifies the elements of an unambiguous scheme to identify the distinct entity legal forms in a jurisdiction. Its aim is to enable legal forms within jurisdictions to be codified and thus facilitate the classification of legal entities according to their legal form. It is not the purpose of the document to give the comparison or alignment of entity legal forms across different jurisdictions, so as not to limit its usage and relevance.
- Standard4 pagesEnglish languagesale 15% off
ISO 12812-1:2017 defines the general framework of mobile financial services (payment and banking services involving a mobile device), with a focus on: a) a set of definitions commonly agreed by the international financial industry; b) the opportunities offered by mobile devices for the development of such services; c) the promotion of an environment that reduces or minimizes obstacles for mobile financial service providers who wish to provide a sustainable and reliable service to a wide range of customers (persons and businesses), while ensuring that customers' interests are protected; d) the different types of mobile financial services accessed through a mobile device including mobile proximate payments, mobile remote payments and mobile banking, which are detailed in other parts of ISO 12812; e) the mobile financial services supporting technologies; f) the stakeholders involved in the mobile payment ecosystems. ISO 12812-1:2017 includes the following informative annexes: - an overview of other standardization initiatives in mobile financial services (Annex A); - a description of possible mobile payment business models (Annex B); - a description of typical payment instruments which may be used (Annex C).
- Standard33 pagesEnglish languagesale 15% off
ISO/TS 12812-4:2017 provides comprehensive requirements and recommendations, as well as specific use cases for implementation of interoperable mobile payments-to-persons. The emphasis is placed on the principles governing the operational functioning of mobile payments-to-persons systems and processes, as well as the presentation of the underlying technical, organizational, business, legal and policy issues, leveraging legacy infrastructures of existing payment instruments (see ISO 12812‑1:2017, Annex C). ISO/TS 12812-4:2017 includes the following items: a) requirements applicable to mobile payments-to-persons; b) recommendations regarding mechanisms involved in the operation of interoperable mobile payments-to-persons; c) a description of the different use cases for mobile payments-to-persons; d) a generic interoperability model for the provision of different mobile payments-to-persons; e) recommendations for the technical implementation of the generic architectures for the mobile payments-to-persons program; f) recommendations for mobile remittances; g) use cases with the corresponding transaction flows; h) discussion of the financial inclusion of unbanked and underbanked persons (Annex A); i) some legal aspects to consider for mobile payments-to-persons (Annex B). ISO/TS 12812-4:2017 is structured as follows: - Clause 6 sets forth the requirements that a mobile payments-to-persons program must comply with. - Clauses 7, 8 and 9 provide the different levels of implementation for the interoperability of mobile payments-to-persons. - Clause 7 describes the interoperability principles for mobiles payments-to-persons. - Clause 8 describes: a three-layer high-level architecture for mobile payments-to-persons programs; payments instruments sustained by these programs; processing details for a series of significant use cases of mobile payments-to-persons using these payment instruments. - Clause 9 provides a step-by-step data flow description for different mobile payments-to-persons implementations: bank-centric, non-bank centric and card-centric. They can be mapped into the processing use cases of Clause 8, where abstraction is made in the nature of the payment service providers.
- Technical specification36 pagesEnglish languagesale 15% off
ISO/TS 12812-5:2017 focuses on mechanisms by which a person ("consumer", "payer" or "business") uses a mobile device to initiate a payment to a business entity ("merchant" or "payee"). Such a payment may use the traditional merchant point of interaction (POI) system, where the manner of settling the payment follows well-established merchant services paradigms. Additionally, there are other ways for a consumer to make a payment to a merchant, using the mobile device to initiate, authorize and process transactions outside of traditional payment networks using secure payment instruments. Accordingly, this document supports both "push" and "pull" payments (i.e. transactions that are pushed or transmitted from a mobile device into a POI or pulled or received into a mobile device or POI), which are initiated and/or confirmed by a consumer to purchase goods and or services, including proximate payments, remote secure server payments, as well as mobile payments that leverage other technologies [e.g. cloud computing, quick response ("QR") codes, biometrics, geo-location and other methods to authenticate and authorize the transaction]. One of the most important aspects of the MFS environment is mobile payments to businesses. There are many ways a consumer, or a business as a consumer, can make a payment to a merchant. ISO 12812 provides a comprehensive standard for using the mechanisms involved in mobilizing the transfer of funds regardless of who is involved in the process. This document is intended to be used by potential implementers of mobile retail payment solutions, while ISO 12812-4 is intended for potential implementers of solutions for mobile payments to persons. NOTE ISO 12812‑1:2017, 5.4 explains the differences in the use of these terms. As such, the ISO 12812 (all parts) seeks to support all possible technologies and is not designed to highlight or endorse specific technologies in the competitive marketplace. Although this document deals with mobile payments made by a consumer or a business acting as a consumer, which transactions are subject to a variety of consumer protection requirements, in terms of the relationship to the MFSP, the consumer (or business) is the customer of the MFSP. Nevertheless, this document will use the term "consumer."
- Technical specification55 pagesEnglish languagesale 15% off
ISO 12812-2:2017 describes and specifies a framework for the management of the security of MFS. It includes - a generic model for the design of the security policy, - a minimum set of security requirements, - recommended cryptographic protocols and mechanisms for mobile device authentication, financial message secure exchange and external authentication, including the following: point-to-point aspects to consider for MFS; end-to-end aspects to consider; security certification aspects; generation of mobile digital signatures; - interoperability issues for the secure certification of MFS, - recommendations for the protection of sensitive data, - guidelines for the implementation of national laws and regulations (e.g. anti-money laundering and combating the funding of terrorism (AML/CFT), and - security management considerations. In order to avoid the duplication of standardization work already performed by other organizations, this document will reference other International Standards as required. In this respect, users of this document are directed to materials developed and published by ISO/TC 68/SC 2 and ISO/IEC JTC 1/SC 27.
- Technical specification56 pagesEnglish languagesale 15% off
ISO/TS 12812-3:2017 specifies the interoperable lifecycle management of applications used in mobile financial services. As defined in ISO 12812‑1, an application is a set of software modules and/or data needed to provide functionality for a mobile financial service. This document deals with different types of applications which is the term used to cover authentication, banking and payment applications, as well as credentials. Clause 5 describes the basic principles required, or to be considered, for the application lifecycle management. Because several implementations are possible with impacts on the lifecycle, this document describes the different architectures for the location of the application and the impacts of the different scenarios regarding the issuance of the secure element when present (see Clause 6), the different roles for the management of the application lifecycle and the domains of responsibilities (see Clause 7). It also specifies functions and processes in the application lifecycle management (see Clause 8) and describes scenarios of service models and roles of actors (see Clause 9).
- Technical specification12 pagesEnglish languagesale 15% off