mojaloop-specification
mojaloop-specification copied to clipboard
Change Request: ISO 20022 Version of FSPIOP API
Open API for FSP Interoperability - Change Request
Table of Contents
-
1. Preface
- 1.1 Change Request Information
- 1.2 Document Version Information
-
2. Problem Description
- 2.1 Background
- 2.2 Current Behaviour
- 2.3 Requested Behaviour
- 3 Proposed Solution Options
1. Preface
___This section contains basic information regarding the change request.
1.1 Change Request Information
| Requested By | Michael Richards, INFITX | | Change Request Status | In review ☒ / Approved ☐ / Rejected ☐ | | Approved/Rejected Date | |
1.2 Document Version Information
Version | Date | Author | Change Description |
---|---|---|---|
1.0 | 2023-01-19 | Michael Richards | Initial version of change request. |
2. Problem Description
___2.1 Background
The Mojaloop Foundation intends to publish a version of the FSPIOP API which uses ISO 20022 documents as the body of its messages. Initial analysis suggests that the existing ISO 20022 messages are not suitable for our purposes. We have proposed a number of new messages to meet our requirements. The ISO 20022 Payments SEG has asked us to investigate the possibility of modifying existing messages to meet our purposes. Accordingly, we have produced an analysis of the changes to the core payment execution message (pacs.008) that we think will be required to meet the Mojaloop requirements. A copy of the analysis is available here.
In addition, we have produced a sequence diagram showing how a simple P2P transfer could be made in a Mojaloop system using ISO 20022 messages including the proposed modifications. We need this sequence diagram to be reviewed by FSPIOP experts to ensure that the ISO 20022 implementation is solid. Please respond by commenting on this issue.
2.2 Current Behaviour
Standard FSPIOP behaviour
Explain how you would like the API to behave.
The same way as it does now, but using agreed ISO 20022 messages