| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO 12812-1:2017 |
Core banking — Mobile financial services — Part 1: General framework |
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).
|
Published |
2017-03 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TS 12812-2:2017 |
Core banking — Mobile financial services — Part 2: Security and data protection for mobile financial services |
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.
|
Published |
2017-03 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TS 12812-3:2017 |
Core banking — Mobile financial services — Part 3: Financial application lifecycle management |
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).
|
Published |
2017-03 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TS 12812-4:2017 |
Core banking — Mobile financial services — Part 4: Mobile payments-to-persons |
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.
|
Published |
2017-03 |
Edition : 1 |
Number of pages : 36 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 31-8:1980/Amd 1:1985 |
Quantities and units of physical chemistry and molecular physics — Amendment 1 |
|
Withdrawn |
1985-08 |
Edition : 2 |
Number of pages : 1 |
Technical Committee |
01.060
Quantities and units
|
| ISO/TS 12812-5:2017 |
Core banking — Mobile financial services — Part 5: Mobile payments to businesses |
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."
|
Published |
2017-03 |
Edition : 1 |
Number of pages : 55 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 13569:1996 |
Banking, securities and other financial services — Information security guidelines |
|
Withdrawn |
1996-11 |
Edition : 1 |
Number of pages : 57 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 13569:1997 |
Banking and related financial services — Information security guidelines |
|
Withdrawn |
1997-10 |
Edition : 2 |
Number of pages : 96 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 13569:1997/Amd 1:1998 |
Banking and related financial services — Information security guidelines — Amendment 1 |
|
Withdrawn |
1998-12 |
Edition : 2 |
Number of pages : 3 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 13569:2005 |
Financial services — Information security guidelines |
ISO TR 13569:2005 provides guidelines on the development of an information security programme for institutions in the financial services industry. It includes discussion of the policies, organization and the structural, legal and regulatory components of such a programme. Considerations for the selection and implementation of security controls, and the elements required to manage information security risk within a modern financial services institution are discussed. Recommendations are given that are based on consideration of the institutions' business environment, practices and procedures. Included in this guidance is a discussion of legal and regulatory compliance issues, which should be considered in the design and implementation of the programme.
|
Withdrawn |
2005-11 |
Edition : 3 |
Number of pages : 72 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 13616-1:2007 |
Financial services - International bank account number (IBAN) — Part 1: Structure of the IBAN |
ISO 13616-1:2007 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, etc.).
ISO 13616-1:2007 does not specify internal procedures, file organization techniques, storage media, languages, etc. 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).
|
Withdrawn |
2007-03 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 13616-1:2020 |
Financial services — International bank account number (IBAN) — Part 1: Structure of the IBAN |
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).
|
Published |
2020-09 |
Edition : 2 |
Number of pages : 8 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 13616-2:2007 |
Financial services - International bank account number (IBAN) — Part 2: Role and responsibilities of the Registration Authority |
ISO 13616-2:2007 describes the Registration Authority (RA) responsible for the registry of IBAN formats that are compliant with ISO 13616-1, the procedures for registering ISO 13616-compliant IBAN formats and the structure of the registry.
|
Withdrawn |
2007-03 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/CD 16677-1 |
Biobanking — Biobanking of germplasm for conservation of genetic resources and biodiversity — Part 1: Agricultural animal species |
This new work item will address the requirements for biodiversity and addressing conservation of genetic resources for agricultural animal species
|
Under development |
|
Edition : 1 |
|
Technical Committee |
07.080
Biology. Botany. Zoology
|
| ISO 13616-2:2020 |
Financial services — International bank account number (IBAN) — Part 2: Role and responsibilities of the Registration Authority |
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.
|
Published |
2020-09 |
Edition : 2 |
Number of pages : 3 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 13616:1997 |
Banking and related financial services — International Bank Account Number (IBAN) |
|
Withdrawn |
1997-09 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 13616:2003 |
Banking and related financial services — International bank account number (IBAN) |
ISO 13616:2003 specifies the elements of an international bank account number (IBAN), used to facilitate the processing of data in data interchange internationally -- in financial environments as well as within and between other industries. The IBAN is designed for automated processing, but can also be conveniently used in other media interchange when appropriate (paper document exchange, etc.). ISO 13616 does not specify internal procedures, file organization techniques, storage media, languages, etc. 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).
|
Withdrawn |
2003-08 |
Edition : 2 |
Number of pages : 7 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 14030-1:2021 |
Environmental performance evaluation — Green debt instruments — Part 1: Process for green bonds |
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.
|
Published |
2021-09 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
13.020.20
Environmental economics. Sustainability
|
| ISO 14030-2:2021 |
Environmental performance evaluation — Green debt instruments — Part 2: Process for green loans |
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.
|
Published |
2021-09 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
13.020.20
Environmental economics. Sustainability
|
| ISO 14030-3:2022 |
Environmental performance evaluation — Green debt instruments — Part 3: Taxonomy |
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.
|
Published |
2022-07 |
Edition : 1 |
Number of pages : 128 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
13.020.20
Environmental economics. Sustainability
|
| ISO 14030-4:2021 |
Environmental performance evaluation — Green debt instruments — Part 4: Verification programme requirements |
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.
|
Published |
2021-09 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
13.020.20
Environmental economics. Sustainability
|
| ISO 18245:2003 |
Retail financial services — Merchant category codes |
ISO 18245:2003 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.
ISO 18245:2003 also establishes the procedures for a Registration and Maintenance Management Group (RMMG), which considers requests for new code values, and a Maintenance Agency (MA), which provides the administrative procedures required to maintain an up-to-date list of codes.
It is not within the scope of ISO 18245:2003 to mandate the use of merchant category codes in any given situation.
|
Withdrawn |
2003-04 |
Edition : 1 |
Number of pages : 29 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 14097:2021 |
Greenhouse gas management and related activities — Framework including principles and requirements for assessing and reporting investments and financing activities related to climate change |
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.
|
Published |
2021-05 |
Edition : 1 |
Number of pages : 43 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
13.020.20
Environmental economics. Sustainability
|
| ISO 14100:2022 |
Guidance on environmental criteria for projects, assets and activities to support the development of green finance |
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.
|
Published |
2022-08 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
13.020.20
Environmental economics. Sustainability
|
| ISO/TR 14742:2010 |
Financial services — Recommendations on cryptographic algorithms and their use |
ISO/TR 14742:2010 provides a list of recommended cryptographic algorithms for use within applicable financial services standards prepared by ISO/TC 68. It also provides strategic guidance on key lengths and associated parameters and usage dates.
The focus is on algorithms rather than protocols, and protocols are in general not included in ISO/TR 14742:2010.
ISO/TR 14742:2010 deals primarily with recommendations regarding algorithms and key lengths.
The categories of algorithms covered in ISO/TR 14742:2010 are:
block ciphers;
stream ciphers;
hash functions;
message authentication codes (MACs);
asymmetric algorithms;
digital signature schemes giving message recovery,
digital signatures with appendix,
asymmetric ciphers;
authentication mechanisms;
key establishment and agreement mechanisms;
key transport mechanisms.
ISO/TR 14742:2010 does not define any cryptographic algorithms; however, the standards to which ISO/TR 14742:2010 refers may contain necessary implementation information as well as more detailed guidance regarding choice of security parameters, security analysis, and other implementation considerations.
|
Published |
2010-07 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 15022-1:1999 |
Securities — Scheme for messages (Data Field Dictionary) — Part 1: Data field and message design rules and guidelines |
This part of ISO 15022 consists of:- the description of the Enhanced ISO 7775 syntax and message design rules;- the contents and organization of the dictionary of Enhanced ISO 7775 and EDIFACT fields for securities messages; and- the contents and organization of the catalogue of securities messages built in the Enhanced ISO 7775 and EDIFACT syntaxes.
It refers to the EDIFACT syntax when necessary to ensure an easy cross-reference between Enhanced ISO 7775 concepts and EDIFACT concepts. The EDIFACT syntax is not described in this part of ISO 15022; it is defined in ISO 9735 which is incorporated by reference.
This part of ISO 15022 is used for electronic data interchange between securities industry participants, independently of the communication network. Network dependent rules, for example, on how to specify where and when the message is to be sent, message acknowledgement and message protection are outside the scope of this part of ISO 15022.
The maintenance of this part of ISO 15022 is described in part 2 of ISO 15022.
|
Published |
1999-03 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 15022-1:1999/Cor 1:1999 |
Securities — Scheme for messages (Data Field Dictionary) — Part 1: Data field and message design rules and guidelines — Technical Corrigendum 1 |
|
Published |
1999-12 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 15022-2:1999 |
Securities — Scheme for messages (Data Field Dictionary) — Part 2: Maintenance of the Data Field Dictionary and Catalogue of Messages |
This part of ISO 15022 describes the responsibilities of the parties involved in the maintenance of the Data Field
Dictionary (DD) and the Catalogue of Messages (CM). There is a Registration Authority (RA) which is the operating
authority responsible for maintaining the Data Field Dictionary and the Catalogue of Messages, and a Registration
Management Group (RMG). The RMG is the governing body of the RA, and monitors its performance.
|
Published |
1999-03 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 15022-2:1999/Cor 1:1999 |
Securities — Scheme for messages (Data Field Dictionary) — Part 2: Maintenance of the Data Field Dictionary and Catalogue of Messages — Technical Corrigendum 1 |
|
Published |
1999-12 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 17442-1:2020 |
Financial services — Legal entity identifier (LEI) — Part 1: Assignment |
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.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 17442-2:2020 |
Financial services — Legal entity identifier (LEI) — Part 2: Application in digital certificates |
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.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/CD 17442-3 |
Financial services — Legal entity identifier (LEI) — Part 3: Part 3: verifiable LEIs (vLEIs) |
This document specifies the use of the Legal Entity Identifier (LEI) code, represented in ISO 17442-1:2020 Financial services - Legal entity identifier (LEI) – Part 1 Assignment, in Authentic Chained Data Container credentials (ACDC credentials), represented by [reference to ACDC specification at the time of submission of this form 4, at a minimum to the IETF draft specification]. Leveraging standard cryptography combined with the chaining feature and strong authentication protocol, the Global Legal Entity Identifier Foundation (GLEIF) has designed and developed specific ACDC credentials containing LEIs and refers to these credentials as verifiable LEIs, or vLEIs. The goal of integrating LEIs in vLEI ACDC credentials is to combine the advantages of both. LEIs can provide unique identification of businesses (legal entities) and the cryptographic verification of identification associated with digital credentials. vLEIs provide automated remote verification of legal entities owning LEIs, i.e., cryptographically prove that an LEI is owned by the organization signing with or presenting the credential. vLEIs have been created both for the LEI legal entity level as well as for Role Credentials, vLEI credentials which in addition to containing the LEI, identify persons acting on behalf of a legal entity and the official or functional roles in which these persons represent the legal entity. Users can view the lists of entity level vLEIs as well as vLEI Role Credentials issued for legal entities to persons acting in official roles for the legal entity, which are called Legal Entity Official Organizational Role vLEI Credentials (OOR Credentials). Look up of this information is accessible in addition to the look up of each LEI code and its entity and relationship reference data provided in the Global LEI System for which GLEIF provides a GLEIF Application Programming Interface (API). OOR Credentials further leverage the ISO/TC 68 Subcommittee 8 ISO 5009:2022 Financial services – Official Organizational Roles – Scheme for Official Organizational Roles standard. This standard specifies an unambiguous scheme to list official organizational roles by jurisdiction in a standard way, providing codes and their associated data records.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 17442:2012 |
Financial services — Legal Entity Identifier (LEI) |
ISO 17442:2012 specifies the elements of an unambiguous legal entity identifier (LEI) scheme to identify the legal entities relevant to any financial transaction.
|
Withdrawn |
2012-06 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 17442:2019 |
Financial services — Legal entity identifier (LEI) |
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.
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;
— all entities that issue equity, debt or other securities for other capital structures;
— all entities listed on an exchange;
— all entities that trade stock or debt; investment vehicles, including mutual funds, pension funds and alternative investment vehicles constituted as corporate entities or collective investment agreements (including umbrella funds as well as funds under an umbrella structure, hedge funds, private equity funds);
— 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.
|
Withdrawn |
2019-04 |
Edition : 2 |
Number of pages : 6 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 17944:2002 |
Banking — Security and other financial services — Framework for security in financial systems |
ISO/TR 17944:2002 provides a framework for standards dealing with security that are deemed necessary for the financial industry. It consists of an inventory of the key security issues which arise in the financial industry and, for each of these issues, the titles of the relevant existing standards are given.
|
Withdrawn |
2002-08 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 24165-2:2021 |
Digital token identifier (DTI) — Registration, assignment and structure — Part 2: Data elements for registration |
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.
|
Published |
2021-09 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 18245:2023 |
Retail financial services — Merchant category codes |
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.
|
Published |
2023-02 |
Edition : 2 |
Number of pages : 2 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 18774:2015 |
Securities and related financial instruments — Financial Instrument Short Name (FISN) |
ISO 18774:2015 defines and describes rules for an internationally valid system for building short names of any kind of financial instrument within a defined structure.
This International Standard is intended for use in any application in the trading and administration of securities globally.
The FISN has been developed after taking into account the need of human-readability as well as interoperability with existing standards and systems.
|
Published |
2015-11 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 19092-1:2006 |
Financial services — Biometrics — Part 1: Security framework |
ISO 19092-1:2006 describes the security framework for using biometrics for authentication of individuals in financial services. It introduces the types of biometric technologies and addresses issues concerning their application. ISO 19092-1:2006 also describes the architectures for implementation, specifies the minimum security requirements for effective management, and provides control objectives and recommendations suitable for use by a professional practitioner.
The following are within the scope of ISO 19092-1:2006:
usage of biometrics for the authentication of employees and persons seeking financial services by:verification of a claimed identity;identification of an individual;validation of credentials presented at enrolment to support authentication as required by risk management;management of biometric information across its life cycle comprised of the enrolment, transmission and storage, verification, identification and termination processes;security of biometric information during its life cycle, encompassing data integrity, origin authentication and confidentiality;application of biometrics for logical and physical access control;surveillance to protect the financial institution and its customers;security of the physical hardware used throughout the biometric information life cycle.
ISO 19092-1:2006 provides the mandatory means whereby biometric information may be encrypted for data confidentiality or other reasons.
|
Withdrawn |
2006-12 |
Edition : 1 |
Number of pages : 81 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 19092:2008 |
Financial services — Biometrics — Security framework |
ISO 19092:2008 describes the security framework for using biometrics for authentication of individuals in financial services. It introduces the types of biometric technologies and addresses issues concerning their application. ISO 19092:2008 also describes the architectures for implementation, specifies the minimum security requirements for effective management, and provides control objectives and recommendations suitable for use by a professional practitioner.
The following are within the scope of ISO 19092:2008:
usage of biometrics for the authentication of employees and persons seeking financial services by:
verification of a claimed identity;
identification of an individual;
validation of credentials presented at enrolment to support authentication as required by risk management;
management of biometric information across its life cycle comprised of the enrolment, transmission and storage, verification, identification and termination processes;
security of biometric information during its life cycle, encompassing data integrity, origin authentication and confidentiality;
application of biometrics for logical and physical access control;
surveillance to protect the financial institution and its customers;
security of the physical hardware used throughout the biometric information life cycle.
ISO 19092:2008 provides the mandatory means whereby biometric information may be encrypted for data confidentiality or other reasons.
|
Withdrawn |
2008-01 |
Edition : 1 |
Number of pages : 77 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 19092:2023 |
Financial services — Biometrics — Security framework |
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.
|
Published |
2023-03 |
Edition : 2 |
Number of pages : 65 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 20022-1:2004 |
Financial services — UNIversal Financial Industry message scheme — Part 1: Overall methodology and format specifications for inputs to and outputs from the ISO 20022 Repository |
ISO 20022-1:2005 consists of the overall description of the modelling approach; the overall description of the ISO 20022 Repository contents; a high-level description of the input to be accepted by the Registration Authority to feed/modify the Repository's Data Dictionary and Business Process Catalogue; a high-level description of the Repository output to be made publicly available by the Registration Authority.
|
Withdrawn |
2004-12 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-1:2013 |
Financial services — Universal financial industry message scheme — Part 1: Metamodel |
ISO 20022-1:2013 consists of:
the overall description of the modelling approach;
the overall description of the ISO 20022 Repository contents;
a high-level description of the input to be accepted by the Registration Authority to feed/modify the Repository's DataDictionary and BusinessProcessCatalogue;
a high-level description of the Repository output to be made publicly available by the Registration Authority.
BusinessTransactions and Message Sets complying with ISO 20022 can be used for electronic data interchange among any industry participants (financial and others), independently of any specific communication network. Network-dependent rules, such as message acknowledgement and message protection, are outside the scope of ISO 20022.
|
Published |
2013-05 |
Edition : 2 |
Number of pages : 152 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-2:2004 |
Financial services — UNIversal Financial Industry message scheme — Part 2: Roles and responsibilities of the registration bodies |
ISO 20022-2:2004 specifies the responsibilities of the bodies involved in the registration and maintenance of the Data Dictionary and Business Process Catalogue items in the ISO 20022 Repository. The Registration Authority (RA) is the operating authority responsible for the above-mentioned tasks, and is assisted by different Standards Management Groups (SMG), i.e. groups of industry experts responsible for specific Business Areas of the Repository. The Registration Management Group (RMG) is the governing body of the overall registration process and the appeal body for the communities of users, the RA and the SMGs, and monitors the registration process performance.
|
Withdrawn |
2004-12 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-2:2007 |
Financial services — UNIversal Financial Industry message scheme — Part 2: Roles and responsibilities of the registration bodies |
ISO 20022-2:2007 specifies the responsibilities of the bodies involved in the registration and maintenance of the ISO 20022 Repository. The Registration Authority (RA) is the operating authority responsible for the above-mentioned tasks and is assisted by different Standards Evaluation Groups (SEGs), i.e. groups of industry experts responsible for specific Business Areas of the Repository. The Registration Management Group (RMG) is the governing body of the overall registration process and the appeal body for the communities of users, the RA, the SEGs and the Submitting Organizations, and monitors the registration process performance.
|
Withdrawn |
2007-04 |
Edition : 2 |
Number of pages : 16 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-2:2013 |
Financial services — Universal financial industry message scheme — Part 2: UML profile |
ISO 20022-2:2013 defines the UML Profile for ISO 20022. In essence, it defines how to use UML to create models that conform to the ISO 20022 Metamodel, which is defined in ISO 20022-1:2013. In so doing, it defines a UML-based concrete syntax for the Metamodel. It does not preclude the specification of additional concrete syntaxes for the Metamodel, such as a textual concrete syntax.
The Profile defines how to represent in UML each of the Metamodel's Scope Level Elements (Level 1), Business Level Elements (Level 2) and Message Level Elements (Level 3), as well as Metamodel Elements that are scoped across the levels.
Therefore, the Profile covers all of the Metamodel's Packages, except for the following:
· ISO20022::Metamodel::ConceptualLevel::MessageTransport
· ISO20022::Metamodel::LogicalLevel::Reversing
· ISO20022::Metamodel::LogicalToPhysicalTransformation
· ISO20022::Metamodel::PhysicalLevel
The Profile also covers the ISO20022::TypeLibrary Package, upon which the Metamodel has some dependencies.
ISO 20022-2:2013 is only applicable when UML is used.
|
Published |
2013-05 |
Edition : 3 |
Number of pages : 71 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-3:2013 |
Financial services — Universal financial industry message scheme — Part 3: Modelling |
ISO 20022-3:2013 describes the modelling workflow, complementing ISO 20022-1:2013 and ISO 20022-2:2013. The modelling workflow describes the required steps a modeller follows in order to develop and maintain standardized BusinessTransactions and MessageSets.
ISO 20022-3:2013 is not intended to describe what will be the permissible artefacts and/or documents to be submitted to the Registration Authority (this information is contained in ISO 20022-7).
Examples are provided only to illustrate the modelling methodology and are not normative.
|
Published |
2013-05 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TS 20022-3:2004 |
Financial services — UNIversal Financial Industry message scheme — Part 3: ISO 20022 modelling guidelines |
ISO/TS 20022-3:2004 explains the different steps a modeller should follow to ensure that ISO 20022 Business Components / Elements, Message Components / Elements, Business Transactions and Messages are defined in a consistent way.
The ISO 20022 methodology is composed of a set of activities. These activities are grouped into the following phases:
business analysis,requirements analysis,logical analysis,logical design (message design),technical design.
For each of these activities, ISO/TS 20022-3:2004 describes
the artefacts needed to start this activity (required input),the artefacts that should be the result of this activity (expected output)an example - where useful,any modelling and other guidelines that should be followed or taken into account.
|
Withdrawn |
2004-12 |
Edition : 1 |
Number of pages : 43 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 24366:2021 |
Financial services — Natural person identifier (NPI) |
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.
|
Published |
2021-10 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-4:2013 |
Financial services — Universal financial industry message scheme — Part 4: XML Schema generation |
ISO 20022-4:2013 was prepared to complement the ISO 20022 Metamodel, as specified in ISO 20022-1:2013, with the XML syntax transformation rules to be applied by the ISO 20022 Registration Authority in order to translate an ISO 20022 compliant MessageDefinition into an XML Schema for the description and validation of XML Messages.
It specifies the transformation rules from level 3 to level 4. It is a deterministic transformation, meaning that the resulting XML Schema is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation.
|
Published |
2013-05 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TS 20022-4:2004 |
Financial services — UNIversal Financial Industry message scheme — Part 4: ISO 20022 XML design rules |
XML is a technical standard defined by the World Wide Web Consortium (W3C) that can be used for the physical representation (i.e. the syntax) of standardized ISO 20022 Messages. XML leaves a lot of freedom for the exact way it is used in a particular application. Therefore, merely stating that XML is used is not sufficient to guarantee predictability; one must also explain how it will be used.
ISO/TS 20022-4:2004 contains a set of XML design rules, called ISO 20022 XML. These design rules define how a standardized Message - described by a Message Definition in UML according to the Modelling Guidelines of ISO/TS 20022-3 - must be represented as a valid ISO 20022 compliant XML document.
A valid XML document (referred to as an "XML instance") as defined by W3C is any XML document that has an associated description and that complies with the constraints expressed in that description. The associated description in this case is derived from the Message Definition, which is originally described in UML.
ISO/TS 20022-4:2004 also describes how (a part of) the UML Message Definition can be converted into a W3C XML Schema. This XML schema will then make it possible to use a validating XML schema parser to automatically verify that a given XML instance complies with (a subset of) the constraints described in the Message Definition.
|
Withdrawn |
2004-12 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-5:2013 |
Financial services — Universal financial industry message scheme — Part 5: Reverse engineering |
ISO 20022-5:2013 was prepared to complement ISO 20022-1:2013. The reverse engineering guidelines explain how to extract relevant information from existing IndustryMessageSets in order to prepare the submission to the ISO 20022 Registration Authority of equivalent, ISO 20022 compliant BusinessTransactions and MessageSets.
The ISO 20022 Repository will contain all ISO 20022 compliant BusinessTransactions and MessageSets, as outlined in ISO 20022-1:2013.
|
Published |
2013-05 |
Edition : 1 |
Number of pages : 36 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TS 20022-5:2004 |
Financial services — UNIversal Financial Industry message scheme — Part 5: ISO 20022 reverse engineering |
ISO/TS 20022-5:2004 describes the activities of "ISO 20022 reverse engineering" from the point of view of the user who wants to verify that the business functionality, covered by his own Industry Message Set, is covered by ISO 20022 compliant Business Transactions and Message Sets. It is not an attempt to define a"methodology" for reverse engineering.
ISO/TS 20022-5:2004 describes the following set of required activities:
extract relevant information from existing Industry Message Sets and compare it to the related information in the ISO 20022 Repository;use the results of this comparison for the development of ISO 20022 compliant Business Transactions and Message Sets;submit the resulting update requests to the Registration Authority;prepare the migration to the ISO 20022 compliant Business Transactions and Message Sets.
The main objectives of the "ISO 20022 reverse engineering" are as follows:
capture the industry knowledge covered by existing Industry Message Sets;build upon former standardization efforts in the industry when building ISO 20022 compliant Business Transactions and Message Sets;ensure that the resulting ISO 20022 compliant Business Transactions and Message Sets fully cover the business scope of existing Industry Message Sets;maximize interoperability between existing Industry Message Sets and ISO 20022 compliant Business Transactions and Message Sets;support the migration from existing Industry Message Sets to ISO 20022 compliant Business Transactions and Message Sets.
ISO/TS 20022-5:2004 gives some specific terms that are used in the document. It then describes the major activities that will be conducted during reverse engineering and also describes at a high level the resulting deliverables. A detailed workflow is presented, explaining all activities, inputs and outputs. Finally, a detailed description of the Convergence Documentation is given in an appendix.
|
Withdrawn |
2004-12 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-6:2009 |
Financial services — UNIversal Financial Industry message scheme — Part 6: Message Transport Characteristics |
ISO 20022-6:2009 specifies the characteristics of the Message Transport System required for an ISO 20022 Business Transaction and Message Definition. Changes to the value of the Message Transport Characteristics can affect the Business Transaction and Message Definition.
Each Business Transaction in the ISO 20022 Repository is associated with a Message Transport Mode. The Message Transport Mode specifies the values for the Message Transport Characteristics.
ISO 20022-6:2009 specifically does not define the wire-level interoperability of message transports. The overall structure is of a layered specification, in order that ISO 20022 can be implemented over many message transports. ISO 20022-6:2009 defines only those characteristics required for interoperability at the business process and message level.
|
Withdrawn |
2009-10 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-6:2013 |
Financial services — Universal financial industry message scheme — Part 6: Message transport characteristics |
ISO 20022-6:2013 specifies the characteristics of the MessageTransportSystem required for an ISO 20022 BusinessTransaction and MessageDefinition. Changes to the value of the MessageTransport Characteristics can affect the BusinessTransaction and MessageDefinition.
Each BusinessTransaction in the ISO 20022 Repository is associated with a MessageTransportMode. The MessageTransportMode specifies the values for the MessageTransportCharacteristics.
|
Published |
2013-05 |
Edition : 2 |
Number of pages : 7 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 5982:2001 |
Mechanical vibration and shock — Range of idealized values to characterize seated-body biodynamic response under vertical vibration |
|
Withdrawn |
2001-11 |
Edition : 2 |
Number of pages : 28 |
Technical Committee |
13.160
Vibration and shock with respect to human beings
|
| ISO 20022-7:2013 |
Financial services — Universal financial industry message scheme — Part 7: Registration |
ISO 20022-7:2013 specifies the responsibilities of the following bodies, which are involved in the registration and maintenance of the ISO 20022 Repository.
The Registration Authority (RA) is the operating authority responsible for the registration and maintenance of the ISO 20022 Repository and for providing access to the information described in ISO 20022-1:2013. The RA is assisted by different Standards Evaluation Groups (SEG), i.e. groups of industry experts responsible for specific Business Areas of the Repository.
A Technical Support Group (TSG) advises the SEGs, the RA, developers and communities of users on the technical implementation of ISO 20022.
The Registration Management Group (RMG) is the governing body of the overall registration process and the appeal body for the communities of users, Submitting Organisations, the RA, the SEGs and the TSG. It monitors the registration process performance.
|
Published |
2013-05 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20022-8:2013 |
Financial services — Universal financial industry message scheme — Part 8: ASN.1 generation |
ISO 20022-8:2013 describes the transformation rules to generate ASN.1 abstract syntax from an ISO 20022 compliant MessageDefinition. The generated abstract syntax is for the description and validation of Messages.
The transformation rules are a transformation from Level 3 to Level 4. It is a deterministic transformation, meaning that the resulting ASN.1 is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation.
ISO 20022-8:2013 is the ASN.1 equivalent of ISO 20022-4:2013. In ISO 20022-4:2013 the abstract syntax generated is XML Schema; in ISO 20022-8:2013 it is ASN.1. In ISO 20022-4:2013 the only encoding supported is UTF-8 XML; in ISO 20022-8:2013 there are multiple encodings supported for ASN.1. These include all the standard encodings, but in addition the ability to register custom encodings in ECN.
|
Published |
2013-05 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 20275:2017 |
Financial services — Entity legal forms (ELF) |
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.
|
Published |
2017-07 |
Edition : 1 |
Number of pages : 4 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/DIS 20937 |
Financial services — Specification of QR-codes for mobile (instant) credit transfers |
|
Under development |
|
Edition : 1 |
Number of pages : 29 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.040.50
Automatic identification and data capture techniques
|
| ISO 21586:2020 |
Reference data for financial services — Specification for the description of banking products or services (BPoS) |
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.
|
Published |
2020-09 |
Edition : 1 |
Number of pages : 51 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 21797:2019 |
Reference data for financial services — Overview of identification of financial instruments |
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.
|
Published |
2019-04 |
Edition : 1 |
Number of pages : 4 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/TR 21941:2017 |
Financial services — Third-party payment service providers |
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).
|
Published |
2017-07 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 389:1985 |
Acoustics — Standard reference zero for the calibration of pure tone air conduction audiometers |
|
Withdrawn |
1985-03 |
Edition : 2 |
|
Technical Committee |
13.140
Noise with respect to human beings
|
| ISO/TR 22126-3:2023 |
Financial services — Semantic technology — Part 3: Semantic enrichment of the ISO 20022 conceptual model |
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.
|
Published |
2023-01 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO/TR 22126-5:2022 |
Financial services — Semantic technology — Part 5: Mapping from FIX Orchestra to the common model |
This document reports on a study to map messages defined using FIX Orchestra into the ISO 20022 model.
|
Published |
2022-08 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 22222:2005 |
Personal financial planning — Requirements for personal financial planners |
ISO 22222:2005 defines the personal financial planning process and specifies ethical behaviour, competences and experience requirements for personal financial planners.
ISO 22222:2005 is applicable to all personal financial planners regardless of their employment status.
ISO 22222:2005 describes and addresses the various methods of conformity assessment and specifies requirements applying to each of them.
|
Published |
2005-12 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 22307:2008 |
Financial services — Privacy impact assessment |
ISO 22307:2008 recognizes that a privacy impact assessment (PIA) is an important financial services and banking management tool to be used within an organization, or by “contracted” third parties, to identify and mitigate privacy issues and risks associated with processing consumer data using automated, networked information systems.
ISO 22307:2008
describes the privacy impact assessment activity in general,
defines the common and required components of a privacy impact assessment, regardless of business systems affecting financial institutions, and
provides informative guidance to educate the reader on privacy impact assessments.
A privacy compliance audit differs from a privacy impact assessment in that the compliance audit determines an institution's current level of compliance with the law and identifies steps to avoid future non-compliance with the law. While there are similarities between privacy impact assessments and privacy compliance audits in that they use some of the same skills and that they are tools used to avoid breaches of privacy, the primary concern of a compliance audit is simply to meet the requirements of the law, whereas a privacy impact assessment is intended to investigate further in order to identify ways to safeguard privacy optimally.
ISO 22307:2008 recognizes that the choices of financial and banking system development and risk management procedures are business decisions and, as such, the business decision makers need to be informed in order to be able to make informed decisions for their financial institutions. ISO 22307:2008 provides a privacy impact assessment structure (common PIA components, definitions and informative annexes) for institutions handling financial information that wish to use a privacy impact assessment as a tool to plan for, and manage, privacy issues within business systems that they consider to be vulnerable.
|
Published |
2008-05 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 23195:2021 |
Security objectives of information systems of third-party payment services |
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.
|
Published |
2021-06 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO/PRF TS 23526 |
Security aspects for digital currencies |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO 23897:2020 |
Financial services — Unique transaction identifier (UTI) |
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.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO 24165-1:2021 |
Digital token identifier (DTI) — Registration, assignment and structure — Part 1: Method for registration and assignment |
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).
|
Published |
2021-09 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
|
| ISO/IEC TR 27015:2012 |
Information technology — Security techniques — Information security management guidelines for financial services |
ISO/IEC TR 27015:2012 provides information security guidance complementing and in addition to information security controls defined in ISO/IEC 27002:2005 for initiating, implementing, maintaining, and improving information security within organizations providing financial services.
|
Withdrawn |
2012-12 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.030
IT Security
;
03.100.70
Management systems
|
| ISO/IEC CD 27562 |
Privacy guidelines for fintech services |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.030
IT Security
;
35.240.40
IT applications in banking
|
| ISO 32210:2022 |
Sustainable finance — Guidance on the application of sustainability principles for organizations in the financial sector |
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.
|
Published |
2022-10 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
01.040.03
Services. Company organization, management and quality. Administration. Transport. Sociology. (Vocabularies)
;
01.040.13
Environment. Health protection. Safety (Vocabularies)
;
13.020.20
Environmental economics. Sustainability
|
| ISO/TR 32220:2021 |
Sustainable finance — Basic concepts and key initiatives |
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.
|
Published |
2021-08 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
01.040.03
Services. Company organization, management and quality. Administration. Transport. Sociology. (Vocabularies)
;
01.040.13
Environment. Health protection. Safety (Vocabularies)
;
13.020.20
Environmental economics. Sustainability
|
| ISO 1004-1:2013 |
Information processing — Magnetic ink character recognition — Part 1: Print specifications for E13B |
ISO 1004-1:2013 specifies the shape, dimensions, magnetic signal level, and tolerances for the E-13B characters which include 10 numerals and four special symbols printed in magnetic ink and used for the purpose of character recognition. It describes the various known types of printing defects and other printing considerations, together with the tolerances permitted.
|
Published |
2013-06 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 1004-2:2013 |
Information processing — Magnetic ink character recognition — Part 2: Print specifications for CMC7 |
ISO 1004-2:2013 specifies the shapes, dimensions and tolerances for the 10 digits 0 to 9, five symbols, and 26 letters, to be printed with magnetic ink for the purpose of character recognition. It describes the various types of printing defects and other printing considerations, together with the tolerances permitted, and also contains specifications to signal level measurement.
|
Published |
2013-06 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 1004:1995 |
Information processing — Magnetic ink character recognition — Print specifications |
Cancels and replaces the second edition (1977). Specifies the shapes, dimensions and tolerances for the ten digits and four special symbols to be printed in magnetic ink and used für the purposes of character recognition. Describes the various types of printing defects and other printing considerations, together with the tolerances permitted, and also contains specifications for signal level measurement and references to Optical Character Recognition (OCR), a technology now often used in conjunction with E 13 B MICR reading.
|
Withdrawn |
1995-06 |
Edition : 3 |
Number of pages : 55 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 2953:1985 |
Balancing machines — Description and evaluation |
|
Withdrawn |
1985-10 |
Edition : 2 |
Number of pages : 34 |
Technical Committee |
21.120.40
Balancing and balancing machines
|
| ISO/TR 3242:2022 |
Blockchain and distributed ledger technologies – Use cases |
This document lists use cases that summarise common capabilities and usage patterns for attributes of distributed ledger technologies including the blockchain in order to help standards and technology development. This document includes use cases reflecting a range of industry sectors, processes and specific applications.
This document can inform decision-makers considering or involved in applying these new technologies, including business, academia, government, technical and standards bodies.
|
Published |
2022-10 |
Edition : 1 |
Number of pages : 190 |
Technical Committee |
35.030
IT Security
;
35.240.40
IT applications in banking
;
35.240.99
IT applications in other fields
|
| ISO/DIS 5201 |
Financial services — Code-scanning payment security |
|
Under development |
|
Edition : 1 |
Number of pages : 31 |
Technical Committee |
03.060
Finances. Banking. Monetary systems. Insurance
;
35.240.40
IT applications in banking
|
| ISO/PRF TR 6039 |
Blockchain and distributed ledger technologies — Identifiers of subjects and objects for the design of blockchain systems |
|
Under development |
2023-06 |
Edition : 1 |
|
Technical Committee |
35.030
IT Security
;
35.240.40
IT applications in banking
;
35.240.99
IT applications in other fields
|
| ISO/IEC 7501-1:1991 |
Identification cards — Machine readable travel documents — Part 1: Machine readable passport |
|
Withdrawn |
1991-11 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7580:1987 |
Identification cards — Card originated messages — Content for financial transactions |
|
Withdrawn |
1987-12 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7810:1985 |
Identification cards — Physical characteristics |
|
Withdrawn |
1985-12 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7811-2:1985 |
Identification cards — Recording technique — Part 2: Magnetic stripe |
|
Withdrawn |
1985-12 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7811-3:1985 |
Identification cards — Recording technique — Part 3: Location of embossed characters on ID-1 cards |
|
Withdrawn |
1985-12 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7811-4:1985 |
Identification cards — Recording technique — Part 4: Location of read-only magnetic tracks — Tracks 1 and 2 |
|
Withdrawn |
1985-12 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7811-5:1985 |
Identification cards — Recording technique — Part 5: Location of read-write magnetic track — Track 3 |
|
Withdrawn |
1985-12 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7812:1987 |
Identification cards — Numbering system and registration procedure for issuer identifiers |
|
Withdrawn |
1987-05 |
Edition : 2 |
Number of pages : 6 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 7812:1987/Cor 1:1988 |
Identification cards — Numbering system and registration procedure for issuer identifiers — Technical Corrigendum 1 |
|
Withdrawn |
1988-12 |
Edition : 2 |
Number of pages : 1 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO/IEC 7813:1990 |
Identification cards — Financial transaction cards |
|
Withdrawn |
1990-05 |
Edition : 3 |
Number of pages : 4 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 8484:1987 |
Magnetic stripes on savingsbooks |
Specifies the location, dimensions, electromanetic properties, recording characteristics, character coding and character set of magnetic stripes on savingsbooks used in interchange. Describes features of the savingsbook cover i.e. stiffness, minimum dimensions, surface irregularities, roughness as well as the interaction between cover material and magnetic stripe. References: ISO 7811-2 and -5, TAPPI T489 os-76.
|
Withdrawn |
1987-07 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 8732:1988 |
Banking — Key management (wholesale) |
Describes the process whereby cryptographic keys and initialisation vectors (keying material) are provided for use by two parties and continue to be subject to secure handling procedures until they have been destroyed. Has been divided into sections as follows: One: General, Two: Manual distributionof keying material, Three: Automatic distribution of keying material. Annex A gives an example of the implementation of the requirements for manual distribution of keying material.
|
Withdrawn |
1988-11 |
Edition : 1 |
Number of pages : 82 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO/IEC 8484:2007 |
Information technology — Magnetic stripes on savingsbooks |
ISO/IEC 8484:2007 specifies the characteristics and location of a magnetic stripe on a savingsbook and the use of such savingsbooks for international interchange. Compatibility with international interchange systems is provided through the requirements of ISO/IEC 8484:2007, enabling a savingsbook with a magnetic stripe to be read and possibly encoded in a device that is compatible with reading identification cards used in international interchange. It takes into consideration both human and machine aspects and states minimum requirements.
ISO/IEC 8484:2007 specifies requirements for a magnetic stripe (including any protective overlay) on a savingsbook, the encoding technique and coded character sets. It also specifies the characteristics of the savingsbook cover such as stiffness, minimum size, surface irregularities, roughness and interaction between the cover material and the magnetic stripe. Most of the magnetic characteristics are based on ISO/IEC 7811-2. The major changes from ISO 8484:1987 include the following.
ISO/IEC 8484:2007 uses the same definitions, criteria and test methods as in ISO/IEC 7811-2. The reference material has changed from SRM 3200 to RM 7811/2. More complete requirements have been added for signal amplitude, flux transition spacing variation, magnetic stripe area surface profile and warpage. Classifications have been added for unused and returned savingsbooks. An optional high coercivity magnetic stripe has been added based on ISO/IEC 7811-6 and RM 7811/6.
Because savingsbooks are generally paper-based documents, some criteria and test methods have been taken from ISO/IEC 15457-2.
ISO/IEC 8484:2007 specifies
the conditions for conformance;physical characteristics for the savingsbook (warpage, surface distortions, and stiffness) and the magnetic stripe area (location, height and surface profile, roughness, adhesion, wear, and resistance to environment),the signal amplitude performance characteristics of the magnetic stripe;the encoding specification, including technique, angle of recording, bit density, flux transition spacing variation, and signal amplitude;the data structure, including track format, coded character sets and use of error correction;the location of the encoded track.
ISO/IEC 8484:2007, together with a standard for test methods, provides for interchange between various types of savingsbook processing devices and systems.
|
Withdrawn |
2007-07 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO/IEC 8484:2014 |
Information technology — Magnetic stripes on savingsbooks |
ISO/IEC 8484:2014 specifies the characteristics and location of a magnetic stripe on a savingsbook and the use of such savingsbooks for international interchange. Compatibility with international interchange systems is provided through the requirements of ISO/IEC 8484:2014, enabling a savingsbook with a magnetic stripe to be read and possibly encoded in a device that is compatible with reading identification cards used in international interchange.
ISO/IEC 8484:2014 specifies requirements for a magnetic stripe (including any protective overlay) on a savingsbook, the encoding technique, and coded character sets. It also specifies the characteristics of the savingsbook cover such as stiffness, minimum size, surface irregularities, roughness, and interaction between the cover material and the magnetic stripe. It takes into consideration both human and machine aspects and states minimum requirements.
Coercivity influences many of the quantities specified in ISO/IEC 8484:2014 but is not itself specified. Exposure of the savingsbook to a magnetic field is likely to destroy the recorded data.
ISO/IEC 8484:2014 defines performance criteria for savingsbooks. No consideration is given within ISO/IEC 8484:2014 to the amount of use, if any, experienced by the savingsbook prior to test.
|
Published |
2014-08 |
Edition : 2 |
Number of pages : 16 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 8583:1987 |
Bank card originated messages — Interchange message specifications — Content for financial transactions |
|
Withdrawn |
1987-08 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 8730:1986 |
Banking — Requirements for message authentication (wholesale) |
|
Withdrawn |
1986-11 |
Edition : 1 |
|
Technical Committee |
35.240.40
IT applications in banking
|
| ISO 8730:1990 |
Banking — Requirements for message authentication (wholesale) |
Operation implies acceptance of the responsibility for their MAC (message authentication code) by the correspondent financial institutions. Specifies the method by which authentication algorithms are to be approved for inclusion in ISO 8731. It specifies a technique for protecting either the whole of the message or specified elements within it. The authentication of messages is independent of the transmission process used. This IS is designated for use with symmetric algorithms where sender and receiver use the same key.
|
Withdrawn |
1990-05 |
Edition : 2 |
Number of pages : 25 |
Technical Committee |
35.240.40
IT applications in banking
|