35.240.40 - IT applications in banking
ICS 35.240.40 Details
IT applications in banking
IT-Anwendungen im Bankwesen
Applications des TI dans le domaine bancaire
Uporabniške rešitve IT v bančništvu
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.40 - IT applications in banking
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
- 1 (current)
- 2
- 3
- 4
- 5
This document provides a specification for QR codes for mobile (instant) credit transfers (MCTs) whereby the payer uses a mobile device to initiate the payment transaction. The QR code is used to exchange data between the payer and the payee to enable the initiation of the (instant) credit transfer by the payer.
This document is applicable to both cases where the QR code is presented by the payee or by the payer.
This document excludes the following from its scope:
— The details of technical requirements and the supporting infrastructure to achieve interoperability amongst mobile (instant) credit transfer (MCT) service providers;
— The detailed implementation specification of the payload included in the QR code.
- Draft36 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides a list of recommended ISO cryptographic algorithms for use within applicable ISO TC 68, Financial services, standards. It also provides strategic guidance on key lengths and associated parameters and usage dates. This document focuses on core algorithms, key lengths and frequently used mechanisms. The included algorithms are considered to be fit for purpose for financial service use. For additional algorithms, see the body of standards produced by ISO/IEC JTC 1 SC 27, Information security, cybersecurity and privacy protection. For standards on key management, see ISO 11568. The categories of algorithms covered are: a) block ciphers and modes of operation; b) stream ciphers; c) message authentication codes (MACs); d) authenticated encryption algorithms; e) format preserving encryption; f) hash functions; g) asymmetric algorithms: 1) digital signature schemes giving message recovery; 2) digital signatures with appendix; 3) asymmetric ciphers. h) authentication mechanisms; i) key derivation, establishment and agreement mechanisms; j) key transport mechanisms: 1) key wrapping. This document does not define any cryptographic algorithms. However, the standards to which this document refers contain necessary implementation information as well as more detailed guidance regarding choice of security parameters, security analysis and other implementation considerations.
- Technical specification36 pagesEnglish languagesale 15% off
This document specifies cryptographic methods for: — PIN generation; — reference PIN change; — transaction PIN verification. These PIN management functions can be implemented using: — encryption using an approved algorithm (see REF Table_tab_1 \r \h Table 1 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000C0000005400610062006C0065005F007400610062005F0031000000 ); — CMAC using an approved block cipher (see REF Table_tab_1 \r \h Table 1 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000C0000005400610062006C0065005F007400610062005F0031000000 ); — HMAC using an approved hash algorithm (see REF Table_tab_1 \r \h Table 1 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000C0000005400610062006C0065005F007400610062005F0031000000 ). Refer to ISO 9564-1 for basic principles & requirements regarding PIN establishment.
- Standard21 pagesEnglish languagesale 15% off
This document gives requirements and guidance on security controls and implementation for third-party payment service providers (TPPSPs). This document deals with the overall security controls of TPPSPs from developing and testing to installing, operating and auditing the system. These security controls consist of: — security governance controls; — cross-functional controls; — function-specific controls.
- Standard24 pagesEnglish languagesale 15% off
This document specifies approved algorithms for the encipherment of personal identification numbers (PINs).
- Standard13 pagesEnglish languagesale 15% off
This document defines fundamental terminology for blockchain and distributed ledger technologies.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines fundamental terminology for blockchain and distributed ledger technologies.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides the normative specification of Simple Binary Encoding (SBE), which is one of the possible syntaxes for FIX messages, but not limited to FIX messages. The scope comprises the encoding (wire format) and the message schema for SBE.
- Standard55 pagesEnglish languagesale 15% off
This document is concerned with the representation of the ISO 20022 e-Repository contents in RDF and OWL by developing a case study around the ISO 20022 auth.016 sample message (hereafter simply referred to as “auth.016”). This includes: a) transformation of the sample message into an RDF instance graph; b) demonstrating a set of SPARQL rules that transform the auth.016 message into a FIX TradeCaptureReport(35=AE) message (hereafter simply referred to as “FIX AE”); c) expressing the metamodel, business components and message components exactly with a custom RDF vocabulary; d) representing those schemas as OWL schemas using OWL vocabulary when possible and annotation properties otherwise; e) creating instance graphs for the auth.016 sample messaging using the vocabulary of the business components and message components. This document also discusses the choices that arise in structuring RDF documents equivalent to documents in XML, and FIX Tag-Value format balancing considerations such as preserving the order of parts of the message versus creating graphs that are suitable for RDFS and OWL inference.
- Technical report45 pagesEnglish languagesale 15% off
This document provides guidelines for a security framework to address the implementation of security mechanisms in technical infrastructures designed for the provision of third-party payment (TPP) services in order to achieve the security objectives defined in ISO 23195. The security framework is intended to protect critical systems and objects within the TPP system environment, either under the direct control of the third-party payment service provider (TPPSP) or by another entity (e.g. a bank). This document is applicable to the provision of any TPP service, including: — the TPP logical structural model; — the definition of the security framework; — the design principles, responsibilities and functional recommendations to support the security mechanism; — guidelines for applying the security framework defined in this document.
- Technical specification24 pagesEnglish languagesale 15% off
This document provides guidelines on privacy for fintech services. It identifies all relevant business models and roles in consumer-to-business relations and business-to-business relations, as well as privacy risks and privacy requirements, which are related to fintech services. It provides specific privacy controls for fintech services to address privacy risks. This document is based on the principles from ISO/IEC 29100, ISO/IEC 27701, and ISO/IEC 29184, the privacy impact assessment framework described in ISO/IEC 29134, and the risk management guideline described in ISO 31000. It also provides guidelines focusing on a set of privacy requirements for each stakeholder. This document can be applicable to all kinds of organizations such as regulators, institutions, service providers and product providers in the fintech service environment.
- Standard30 pagesEnglish languagesale 15% off
Common security requirements for internet connected radio equipment that equipment enables the holder or user to transfer money, monetary value or virtual currency. This document provides technical specifications for radio equipment processing virtual money or monetary value, which apply to electrical or electronic products that are capable to communicate over the internet, regardless of whether these products communicate directly or via any other equipment.
- Standard185 pagesEnglish languagesale 10% offe-Library read for1 day
Common security requirements for internet connected radio equipment that equipment enables the holder or user to transfer money, monetary value or virtual currency. This document provides technical specifications for radio equipment processing virtual money or monetary value, which apply to electrical or electronic products that are capable to communicate over the internet, regardless of whether these products communicate directly or via any other equipment.
- Standard185 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the security characteristics for secure cryptographic devices (SCDs) based on the cryptographic processes defined in the ISO 9564 series, ISO 16609 and ISO 11568. This document states the security characteristics concerning both the operational characteristics of SCDs and the management of such devices throughout all stages of their life cycle. This document does not address issues arising from the denial of service of an SCD. This document does not address software services that use multi-party computation (MPC) to achieve some security objectives and, relying on these, offer cryptographic services. NOTE These are sometimes called “soft” or software hardware security modules (HSMs) in common language, which is misleading and does not correspond to the definition of HSM in this document.
- Standard27 pagesEnglish languagesale 15% off
This document provides an overview, risk assessment, minimum security requirements and extended security guidelines for code-scanning payment in which the payer uses a mobile device to operate the payment transaction. This document is applicable to cases where the payment code is used to initiate a mobile payment and presented by either the payer or the payee. The following is excluded from the scope of this document: — details of payer and payee onboarding; — details of the supporting payment infrastructure, as described in 5.1.
- Standard30 pagesEnglish languagesale 15% off
This document uses a set of models that describe the flows of different types of data between distributed ledger technologies (DLT) and related systems, as well as between different DLT nodes. It provides a descriptive analysis of data flows in the development of use cases, as well as the basis for understanding the characteristics of DLT data flows, to support DLT application design and system analysis. The models referenced are in accordance with ISO 23257:2022 and the use case analysis approach provided in ISO/TR 3242:2022.
- Technical report49 pagesEnglish languagesale 15% off
This document defines fundamental terminology for blockchain and distributed ledger technologies.
- Standard14 pagesEnglish languagesale 15% off
- Standard13 pagesFrench languagesale 15% off
- Standard13 pagesFrench languagesale 15% off
This document specifies an acceptable security framework for the issuance and management of digital currencies using cryptographic mechanisms standardized by ISO/TC 68/SC 2 and other references. This document proposes a framework approach based on standards for mitigating vulnerabilities for digital currency systems. The objective is that security aspects are integrated by design and not added afterwards as an extra processing layer that needs to accommodate legacy infrastructures.
- Technical specification14 pagesEnglish languagesale 15% off
This document provides an overview of identifiers [and their standards and register(s)] relevant for the design of blockchain systems and the interoperability of those systems with non-blockchain systems. The following criteria were used for inclusion of identifiers in this document: — Identifiers (and their standards and registers) issued by the public sector for subjects and objects such as citizen numbers, business registration numbers or land registration numbers; — Identifiers that are internationally recognized and fulfil one of the following criteria: — An identifier is an international standard of an SDO (Standard Development Organization); — An identifier is a de facto standard according to the norms of the industry involved (even if it is not an international standard of an SDO). — Identifiers that have relevance for DLT systems as it fulfils one of the following criteria: — An identifier that has been used without DLT, but has proven to solve the problems of DLT services using DLT; — An identifier that was designed with the usage of DLT in mind from the beginning.
- Technical report50 pagesEnglish languagesale 15% off
This specification shows the modifications made to version 3.40 of CWA 16926-11 in version 3.50.
- Standardization document32 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report32 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes concepts and considerations on the use of trust anchors for systems leveraging blockchain and distributed ledger technologies (DLTs) for identity management, i.e. the mechanism by which one or more entities can create, be given, modify, use and revoke a set of identity attributes.
- Technical report25 pagesEnglish languagesale 15% off
This document describes the management of cryptographic keys in a blockchain, or distributed system used in the financial sector The objective of this document is to consider the impact of different types of key management processes that are required for PKI implementations in Blockchain and DLT projects
- Technical report18 pagesEnglish languagesale 15% off
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
This specification shows the modifications made to version 3.40 of CWA 16926-10 in version 3.50.
- Standardization document84 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report84 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-6 in version 3.50.
- Standardization document328 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report328 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-7 in version 3.50.
- Standardization document57 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report57 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-8 in version 3.50.
- Standardization document46 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report46 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-5 in version 3.50.
- Standardization document140 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report140 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-1 in version 3.50.
- Standardization document173 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report173 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-17 in version 3.50.
- Standardization document29 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report29 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-19 in version 3.50.
- Standardization document55 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report55 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-16 in version 3.50.
- Standardization document38 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report38 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-9 in version 3.50.
- Standardization document58 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report58 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-12 in version 3.50.
- Standardization document36 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report36 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-15 in version 3.50.
- Standardization document210 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report210 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-13 in version 3.50.
- Standardization document21 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report21 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-3 in version 3.50.
- Standardization document133 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report133 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-18 in version 3.50.
- Standardization document125 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report125 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-14 in version 3.50.
- Standardization document55 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report55 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-4 in version 3.50.
- Standardization document96 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report96 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes the management of symmetric and asymmetric cryptographic keys that can be used to protect sensitive information in financial services related to retail payments. The document covers all aspects of retail financial services, including connections between a card-accepting device and an Acquirer, between an Acquirer and a card Issuer, and between an ICC and a card-accepting device. It covers all phases of the key life cycle, including the generation, distribution, utilization, archiving, replacement and destruction of the keying material. This document covers manual and automated management of keying material, and any combination thereof, used for retail financial services. It includes guidance and requirements related to key separation, substitution prevention, identification, synchronization, integrity, confidentiality and compromise, as well as logging and auditing of key management events. Requirements associated with hardware used to manage keys have also been included in this document.
- Standard115 pagesEnglish languagesale 15% off
This specification describes the functionality of the services provided by the Depository (DEP) services under XFS, by defining the service-specific commands that can be issued, using the WFSGetInfo, WFSAsyncGetInfo, WFSExecute and WFSAsyncExecute functions.
A Depository is used for the acceptance and deposit of media into the device or terminal. There are two main types of depository: an envelope depository for the deposit of media in envelopes and a night safe depository for the deposit of bags containing bulk media.
An envelope depository accepts media, prints on the media and deposits the media into a holding container or bin. Some envelope depositories offer the capability to dispense an envelope to the customer at the start of a transaction. The customer takes this envelope, fills in the deposit media, possibly inscribes it and puts it into the deposit slot. The envelope is then accepted, printed and transported into a deposit container.
The envelope dispense mechanism may be part of the envelope depository device mechanism with the same entry/exit slot or it may be a separate mechanism with separate entry/exit slot.
Envelopes dispensed and not taken by the customer can be retracted back into the device. When the dispenser is a separate mechanism the envelope is retracted back into the dispenser container. When the dispenser is a common mechanism the envelope is retracted into the depository container.
A night safe depository normally only logs the deposit of a bag and does not print on the media.
- Standardization document47 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report47 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 specification shows the modifications made to version 3.40 of CWA 16926-13 in version 3.50.
- Standardization document21 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report21 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-8 in version 3.50.
- Standardization document46 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report46 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-17 in version 3.50.
- Standardization document29 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report29 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-14 in version 3.50.
- Standardization document55 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report55 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-10 in version 3.50.
- Standardization document84 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report84 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-16 in version 3.50.
- Standardization document38 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report38 pagesEnglish languagesale 10% offe-Library read for1 day
This specification shows the modifications made to version 3.40 of CWA 16926-12 in version 3.50.
- Standardization document36 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical report36 pagesEnglish languagesale 10% offe-Library read for1 day
- 1 (current)
- 2
- 3
- 4
- 5





