FSPIOP API

Versions

Version	Date	Change Description
1.0	2018-03-13	Initial version
1.1	2020-05-19	1. This version contains a new option for a Payee FSP to request a commit notification from the Switch. The Switch should then send out the commit notification using the new request PATCH /transfers/{ID}. The option to use commit notification replaces the previous option of using the ”Optional Additional Clearing Check”. The section describing this has been replaced with the new section ”Commit Notification”. As the transfers resource has been updated with the new PATCH request, this resource has been updated to version 1.1. As part of adding the possibility to use a commit notification, the following changes has been made: a. PATCH has been added as an allowed HTTP Method in Section 3.2.2. b. The call flow for PATCH is described in Section 3.2.3.5. c. Table 6 in Section 6.1.1 has been updated to include PATCH as a possible HTTP Method. d. Section 6.7.1 contains the new version of the transfers resource. e. Section 6.7.2.6 contains the process for using commit notifications f. Section 6.7.3.3 describes the new PATCH /transfers/{ID} request. 2. In addition to the changes mentioned above regarding the commit notification, the following non-API affecting changes has been made: a. Updated Figure 6 as it contained a copy-paste error. b. Added Section 6.1.2 to describe a comprehensive view of the current version for each resource. c. Added a section for each resource to be able to see the resource version history. d. Minor editorial fixes. 3. The descriptions for two of the HTTP Header fields in Table 1 have been updated to add more specificity and context a. The description for the FSPIOP-Destination header field has been updated to indicate that it should be left empty if the destination is not known to the original sender, but in all other cases should be added by the original sender of a request. b. The description for the FSPIOP-URI header field has been updated to be more specific. 4. The examples used in this document have been updated to use the correct interpretation of the Complex type ExtensionList which is defined in Table 84. This doesn’t imply any change as such. a. Listing 5 has been updated in this regard. 5. The data model is updated to add an optional ExtensionList element to the PartyIdInfo complex type based on the Change Request: https://github.com/mojaloop/mojaloop-specification/issues/30. Following this, the data model as specified in Table 103 has been updated. For consistency, the data model for the POST /participants/{Type}/{ID} and POST /participants/{Type}/{ID}/{SubId} calls in Table 10 has been updated to include the optional ExtensionList element as well. 6. A new Section 6.5.2.2 is added to describe the process involved in the rejection of a quote. 7. A note is added to Section 6.7.4.1 to clarify the usage of ABORTED state in PUT /transfers/{ID} callbacks.
1.1.1	2021-09-22	This document version only adds information about optional HTTP headers regarding tracing support in Table 2, see Distributed Tracing Support for OpenAPI Interoperability for more information. There are no changes in any resources as part of this version.