PRICES include / exclude VAT
Homepage>BS Standards>35 INFORMATION TECHNOLOGY. OFFICE MACHINES>35.240 Applications of information technology>35.240.40 IT applications in banking>PD ISO/TS 23029:2020 Web-service-based application programming interface (WAPI) in financial services
Sponsored link
immediate downloadReleased: 2020-02-28
PD ISO/TS 23029:2020 Web-service-based application programming interface (WAPI) in financial services

PD ISO/TS 23029:2020

Web-service-based application programming interface (WAPI) in financial services

Format
Availability
Price and currency
English Secure PDF
Immediate download
348.00 EUR
You can read the standard for 1 hour. More information in the category: E-reading
Reading the standard
for 1 hour
34.80 EUR
You can read the standard for 24 hours. More information in the category: E-reading
Reading the standard
for 24 hours
104.40 EUR
English Hardcopy
In stock
348.00 EUR
Standard number:PD ISO/TS 23029:2020
Pages:62
Released:2020-02-28
ISBN:978 0 580 52461 5
Status:Standard
DESCRIPTION

PD ISO/TS 23029:2020


This standard PD ISO/TS 23029:2020 Web-service-based application programming interface (WAPI) in financial services is classified in these ICS categories:
  • 35.240.40 IT applications in banking

This document defines the framework, function and protocols for an API ecosystem that will enable online synchronised interaction. Specifically, the document:

  • defines a logical and technical layered approach for developing APIs, including transformational rules. Specific logical models (such as ISO 20022 models) are not included, but they will be referenced in the context of specific scenarios for guidance purposes;

  • will primarily be thought about from a RESTful design point of view, but will consider alternative architectural styles (such as WebSocket and Webhook) where other blueprints or scenarios are offered;

  • defines for the API ecosystem design principles of an API, rules of a Web-service-based API, the data payload and version control;

  • sets out considerations relevant to security, identity and registration of an API ecosystem. Specific technical solutions will not be defined, but they will be referenced in the context of specific scenarios for guidance purposes;

  • defines architectural usage beyond query/response asynchronous messaging towards publish/subscribe to support advanced and existing business models.

This document does not include:

  • a specific technical specification of an API implementation in financial services;

  • the development of JSON APIs based on the ISO 20022 specific message formats, such as PAIN, CAMT and PACS;

  • a technical specification that is defined or determined by specific legal frameworks.