@mojaloop/api-snippets 17.2.5 → 17.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (190) hide show
  1. package/CHANGELOG.md +7 -0
  2. package/audit-ci.jsonc +1 -0
  3. package/docs/fspiop-rest-v1.0-openapi3-snippets.yaml +204 -805
  4. package/docs/fspiop-rest-v1.1-openapi3-snippets.yaml +2432 -2447
  5. package/docs/fspiop-rest-v2.0-openapi3-snippets.yaml +4841 -0
  6. package/docs/index.html +1 -0
  7. package/docs/sdk-scheme-adapter-backend-v2_0_0-openapi3-snippets.yaml +103 -345
  8. package/docs/sdk-scheme-adapter-outbound-v2_0_0-openapi3-snippets.yaml +150 -492
  9. package/docs/thirdparty-openapi3-snippets.yaml +296 -886
  10. package/fspiop/v1_1/openapi3/openapi.yaml +10 -2
  11. package/fspiop/v2_0/openapi3/components/headers/Content-Length.yaml +9 -0
  12. package/fspiop/v2_0/openapi3/components/headers/Content-Type.yaml +6 -0
  13. package/fspiop/v2_0/openapi3/components/parameters/Accept.yaml +8 -0
  14. package/fspiop/v2_0/openapi3/components/parameters/Content-Length.yaml +11 -0
  15. package/fspiop/v2_0/openapi3/components/parameters/Content-Type.yaml +8 -0
  16. package/fspiop/v2_0/openapi3/components/parameters/Date.yaml +6 -0
  17. package/fspiop/v2_0/openapi3/components/parameters/FSPIOP-Destination.yaml +13 -0
  18. package/fspiop/v2_0/openapi3/components/parameters/FSPIOP-Encryption.yaml +8 -0
  19. package/fspiop/v2_0/openapi3/components/parameters/FSPIOP-HTTP-Method.yaml +11 -0
  20. package/fspiop/v2_0/openapi3/components/parameters/FSPIOP-Signature.yaml +8 -0
  21. package/fspiop/v2_0/openapi3/components/parameters/FSPIOP-Source.yaml +10 -0
  22. package/fspiop/v2_0/openapi3/components/parameters/FSPIOP-URI.yaml +10 -0
  23. package/fspiop/v2_0/openapi3/components/parameters/ID.yaml +6 -0
  24. package/fspiop/v2_0/openapi3/components/parameters/SourceCurrency.yaml +6 -0
  25. package/fspiop/v2_0/openapi3/components/parameters/SubId.yaml +8 -0
  26. package/fspiop/v2_0/openapi3/components/parameters/TargetCurrency.yaml +6 -0
  27. package/fspiop/v2_0/openapi3/components/parameters/Type.yaml +6 -0
  28. package/fspiop/v2_0/openapi3/components/parameters/X-Forwarded-For.yaml +15 -0
  29. package/fspiop/v2_0/openapi3/components/responses/200.yaml +1 -0
  30. package/fspiop/v2_0/openapi3/components/responses/202.yaml +1 -0
  31. package/fspiop/v2_0/openapi3/components/responses/400.yaml +10 -0
  32. package/fspiop/v2_0/openapi3/components/responses/401.yaml +10 -0
  33. package/fspiop/v2_0/openapi3/components/responses/403.yaml +10 -0
  34. package/fspiop/v2_0/openapi3/components/responses/404.yaml +10 -0
  35. package/fspiop/v2_0/openapi3/components/responses/405.yaml +10 -0
  36. package/fspiop/v2_0/openapi3/components/responses/406.yaml +10 -0
  37. package/fspiop/v2_0/openapi3/components/responses/501.yaml +10 -0
  38. package/fspiop/v2_0/openapi3/components/responses/503.yaml +10 -0
  39. package/fspiop/v2_0/openapi3/components/schemas/Amount.yaml +11 -0
  40. package/fspiop/v2_0/openapi3/components/schemas/AmountType.yaml +14 -0
  41. package/fspiop/v2_0/openapi3/components/schemas/AuthenticationInfo.yaml +11 -0
  42. package/fspiop/v2_0/openapi3/components/schemas/AuthenticationType.yaml +12 -0
  43. package/fspiop/v2_0/openapi3/components/schemas/AuthenticationValue.yaml +9 -0
  44. package/fspiop/v2_0/openapi3/components/schemas/AuthorizationResponse.yaml +12 -0
  45. package/fspiop/v2_0/openapi3/components/schemas/AuthorizationsIDPutResponse.yaml +10 -0
  46. package/fspiop/v2_0/openapi3/components/schemas/BalanceOfPayments.yaml +9 -0
  47. package/fspiop/v2_0/openapi3/components/schemas/BinaryString.yaml +7 -0
  48. package/fspiop/v2_0/openapi3/components/schemas/BinaryString32.yaml +7 -0
  49. package/fspiop/v2_0/openapi3/components/schemas/BulkQuotesIDPutResponse.yaml +18 -0
  50. package/fspiop/v2_0/openapi3/components/schemas/BulkQuotesPostRequest.yaml +25 -0
  51. package/fspiop/v2_0/openapi3/components/schemas/BulkTransferState.yaml +18 -0
  52. package/fspiop/v2_0/openapi3/components/schemas/BulkTransfersIDPutResponse.yaml +18 -0
  53. package/fspiop/v2_0/openapi3/components/schemas/BulkTransfersPostRequest.yaml +30 -0
  54. package/fspiop/v2_0/openapi3/components/schemas/Code.yaml +5 -0
  55. package/fspiop/v2_0/openapi3/components/schemas/CorrelationId.yaml +10 -0
  56. package/fspiop/v2_0/openapi3/components/schemas/Currency.yaml +174 -0
  57. package/fspiop/v2_0/openapi3/components/schemas/CurrencyConverter.yaml +9 -0
  58. package/fspiop/v2_0/openapi3/components/schemas/Date.yaml +9 -0
  59. package/fspiop/v2_0/openapi3/components/schemas/DateOfBirth.yaml +6 -0
  60. package/fspiop/v2_0/openapi3/components/schemas/DateTime.yaml +14 -0
  61. package/fspiop/v2_0/openapi3/components/schemas/ErrorCode.yaml +11 -0
  62. package/fspiop/v2_0/openapi3/components/schemas/ErrorDescription.yaml +5 -0
  63. package/fspiop/v2_0/openapi3/components/schemas/ErrorInformation.yaml +13 -0
  64. package/fspiop/v2_0/openapi3/components/schemas/ErrorInformationObject.yaml +8 -0
  65. package/fspiop/v2_0/openapi3/components/schemas/ErrorInformationResponse.yaml +8 -0
  66. package/fspiop/v2_0/openapi3/components/schemas/Extension.yaml +11 -0
  67. package/fspiop/v2_0/openapi3/components/schemas/ExtensionKey.yaml +5 -0
  68. package/fspiop/v2_0/openapi3/components/schemas/ExtensionList.yaml +15 -0
  69. package/fspiop/v2_0/openapi3/components/schemas/ExtensionValue.yaml +5 -0
  70. package/fspiop/v2_0/openapi3/components/schemas/FirstName.yaml +9 -0
  71. package/fspiop/v2_0/openapi3/components/schemas/FspId.yaml +5 -0
  72. package/fspiop/v2_0/openapi3/components/schemas/FxCharge.yaml +19 -0
  73. package/fspiop/v2_0/openapi3/components/schemas/FxConversion.yaml +57 -0
  74. package/fspiop/v2_0/openapi3/components/schemas/FxMoney.yaml +10 -0
  75. package/fspiop/v2_0/openapi3/components/schemas/FxQuotesIDPutResponse.yaml +15 -0
  76. package/fspiop/v2_0/openapi3/components/schemas/FxQuotesPostRequest.yaml +15 -0
  77. package/fspiop/v2_0/openapi3/components/schemas/FxRate.yaml +15 -0
  78. package/fspiop/v2_0/openapi3/components/schemas/FxTransfersIDPatchResponse.yaml +16 -0
  79. package/fspiop/v2_0/openapi3/components/schemas/FxTransfersIDPutResponse.yaml +20 -0
  80. package/fspiop/v2_0/openapi3/components/schemas/FxTransfersPostRequest.yaml +41 -0
  81. package/fspiop/v2_0/openapi3/components/schemas/GeoCode.yaml +13 -0
  82. package/fspiop/v2_0/openapi3/components/schemas/IlpCondition.yaml +5 -0
  83. package/fspiop/v2_0/openapi3/components/schemas/IlpFulfilment.yaml +6 -0
  84. package/fspiop/v2_0/openapi3/components/schemas/IlpPacket.yaml +7 -0
  85. package/fspiop/v2_0/openapi3/components/schemas/IndividualQuote.yaml +29 -0
  86. package/fspiop/v2_0/openapi3/components/schemas/IndividualQuoteResult.yaml +26 -0
  87. package/fspiop/v2_0/openapi3/components/schemas/IndividualTransfer.yaml +19 -0
  88. package/fspiop/v2_0/openapi3/components/schemas/IndividualTransferResult.yaml +14 -0
  89. package/fspiop/v2_0/openapi3/components/schemas/Integer.yaml +7 -0
  90. package/fspiop/v2_0/openapi3/components/schemas/KYCInformation.yaml +33 -0
  91. package/fspiop/v2_0/openapi3/components/schemas/LastName.yaml +9 -0
  92. package/fspiop/v2_0/openapi3/components/schemas/Latitude.yaml +7 -0
  93. package/fspiop/v2_0/openapi3/components/schemas/Longitude.yaml +8 -0
  94. package/fspiop/v2_0/openapi3/components/schemas/MerchantClassificationCode.yaml +7 -0
  95. package/fspiop/v2_0/openapi3/components/schemas/MiddleName.yaml +9 -0
  96. package/fspiop/v2_0/openapi3/components/schemas/Money.yaml +11 -0
  97. package/fspiop/v2_0/openapi3/components/schemas/Name.yaml +17 -0
  98. package/fspiop/v2_0/openapi3/components/schemas/Note.yaml +6 -0
  99. package/fspiop/v2_0/openapi3/components/schemas/OtpValue.yaml +7 -0
  100. package/fspiop/v2_0/openapi3/components/schemas/ParticipantsIDPutResponse.yaml +17 -0
  101. package/fspiop/v2_0/openapi3/components/schemas/ParticipantsPostRequest.yaml +20 -0
  102. package/fspiop/v2_0/openapi3/components/schemas/ParticipantsTypeIDPutResponse.yaml +8 -0
  103. package/fspiop/v2_0/openapi3/components/schemas/ParticipantsTypeIDSubIDPostRequest.yaml +15 -0
  104. package/fspiop/v2_0/openapi3/components/schemas/PartiesTypeIDPutResponse.yaml +8 -0
  105. package/fspiop/v2_0/openapi3/components/schemas/Party.yaml +21 -0
  106. package/fspiop/v2_0/openapi3/components/schemas/PartyComplexName.yaml +10 -0
  107. package/fspiop/v2_0/openapi3/components/schemas/PartyIdInfo.yaml +19 -0
  108. package/fspiop/v2_0/openapi3/components/schemas/PartyIdType.yaml +54 -0
  109. package/fspiop/v2_0/openapi3/components/schemas/PartyIdentifier.yaml +6 -0
  110. package/fspiop/v2_0/openapi3/components/schemas/PartyName.yaml +5 -0
  111. package/fspiop/v2_0/openapi3/components/schemas/PartyPersonalInfo.yaml +10 -0
  112. package/fspiop/v2_0/openapi3/components/schemas/PartyResult.yaml +10 -0
  113. package/fspiop/v2_0/openapi3/components/schemas/PartySubIdOrType.yaml +7 -0
  114. package/fspiop/v2_0/openapi3/components/schemas/PersonalIdentifierType.yaml +51 -0
  115. package/fspiop/v2_0/openapi3/components/schemas/QRCODE.yaml +5 -0
  116. package/fspiop/v2_0/openapi3/components/schemas/QuotesIDPutResponse.yaml +27 -0
  117. package/fspiop/v2_0/openapi3/components/schemas/QuotesPostRequest.yaml +53 -0
  118. package/fspiop/v2_0/openapi3/components/schemas/Refund.yaml +10 -0
  119. package/fspiop/v2_0/openapi3/components/schemas/RefundReason.yaml +6 -0
  120. package/fspiop/v2_0/openapi3/components/schemas/ServicesFXPPutResponse.yaml +13 -0
  121. package/fspiop/v2_0/openapi3/components/schemas/ServicesFXPSourceCurrencyTargetCurrencyPutResponse.yaml +13 -0
  122. package/fspiop/v2_0/openapi3/components/schemas/TokenCode.yaml +6 -0
  123. package/fspiop/v2_0/openapi3/components/schemas/Transaction.yaml +50 -0
  124. package/fspiop/v2_0/openapi3/components/schemas/TransactionInitiator.yaml +16 -0
  125. package/fspiop/v2_0/openapi3/components/schemas/TransactionInitiatorType.yaml +14 -0
  126. package/fspiop/v2_0/openapi3/components/schemas/TransactionRequestState.yaml +14 -0
  127. package/fspiop/v2_0/openapi3/components/schemas/TransactionRequestsIDPutResponse.yaml +12 -0
  128. package/fspiop/v2_0/openapi3/components/schemas/TransactionRequestsPostRequest.yaml +30 -0
  129. package/fspiop/v2_0/openapi3/components/schemas/TransactionScenario.yaml +32 -0
  130. package/fspiop/v2_0/openapi3/components/schemas/TransactionState.yaml +14 -0
  131. package/fspiop/v2_0/openapi3/components/schemas/TransactionSubScenario.yaml +5 -0
  132. package/fspiop/v2_0/openapi3/components/schemas/TransactionType.yaml +20 -0
  133. package/fspiop/v2_0/openapi3/components/schemas/TransactionsIDPutResponse.yaml +14 -0
  134. package/fspiop/v2_0/openapi3/components/schemas/TransferState.yaml +19 -0
  135. package/fspiop/v2_0/openapi3/components/schemas/TransfersIDPatchResponse.yaml +13 -0
  136. package/fspiop/v2_0/openapi3/components/schemas/TransfersIDPutResponse.yaml +14 -0
  137. package/fspiop/v2_0/openapi3/components/schemas/TransfersPostRequest.yaml +28 -0
  138. package/fspiop/v2_0/openapi3/components/schemas/U2FPIN.yaml +8 -0
  139. package/fspiop/v2_0/openapi3/components/schemas/U2FPinValue.yaml +19 -0
  140. package/fspiop/v2_0/openapi3/components/schemas/UndefinedEnum.yaml +6 -0
  141. package/fspiop/v2_0/openapi3/openapi.yaml +136 -0
  142. package/fspiop/v2_0/openapi3/paths/authorizations_ID.yaml +110 -0
  143. package/fspiop/v2_0/openapi3/paths/authorizations_ID_error.yaml +48 -0
  144. package/fspiop/v2_0/openapi3/paths/bulkQuotes.yaml +46 -0
  145. package/fspiop/v2_0/openapi3/paths/bulkQuotes_ID.yaml +79 -0
  146. package/fspiop/v2_0/openapi3/paths/bulkQuotes_ID_error.yaml +49 -0
  147. package/fspiop/v2_0/openapi3/paths/bulkTransfers.yaml +46 -0
  148. package/fspiop/v2_0/openapi3/paths/bulkTransfers_ID.yaml +81 -0
  149. package/fspiop/v2_0/openapi3/paths/bulkTransfers_ID_error.yaml +49 -0
  150. package/fspiop/v2_0/openapi3/paths/fxQuotes.yaml +45 -0
  151. package/fspiop/v2_0/openapi3/paths/fxQuotes_ID.yaml +79 -0
  152. package/fspiop/v2_0/openapi3/paths/fxQuotes_ID_error.yaml +49 -0
  153. package/fspiop/v2_0/openapi3/paths/fxTransfers.yaml +45 -0
  154. package/fspiop/v2_0/openapi3/paths/fxTransfers_ID.yaml +118 -0
  155. package/fspiop/v2_0/openapi3/paths/fxTransfers_ID_error.yaml +49 -0
  156. package/fspiop/v2_0/openapi3/paths/participants.yaml +49 -0
  157. package/fspiop/v2_0/openapi3/paths/participants_ID.yaml +46 -0
  158. package/fspiop/v2_0/openapi3/paths/participants_ID_error.yaml +48 -0
  159. package/fspiop/v2_0/openapi3/paths/participants_Type_ID.yaml +167 -0
  160. package/fspiop/v2_0/openapi3/paths/participants_Type_ID_SubId.yaml +168 -0
  161. package/fspiop/v2_0/openapi3/paths/participants_Type_ID_SubId_error.yaml +50 -0
  162. package/fspiop/v2_0/openapi3/paths/participants_Type_ID_error.yaml +49 -0
  163. package/fspiop/v2_0/openapi3/paths/parties_Type_ID.yaml +81 -0
  164. package/fspiop/v2_0/openapi3/paths/parties_Type_ID_SubId.yaml +82 -0
  165. package/fspiop/v2_0/openapi3/paths/parties_Type_ID_SubId_error.yaml +50 -0
  166. package/fspiop/v2_0/openapi3/paths/parties_Type_ID_error.yaml +49 -0
  167. package/fspiop/v2_0/openapi3/paths/quotes.yaml +46 -0
  168. package/fspiop/v2_0/openapi3/paths/quotes_ID.yaml +79 -0
  169. package/fspiop/v2_0/openapi3/paths/quotes_ID_error.yaml +49 -0
  170. package/fspiop/v2_0/openapi3/paths/services_FXP.yaml +73 -0
  171. package/fspiop/v2_0/openapi3/paths/services_FXP_SourceCurrency_TargetCurrency.yaml +77 -0
  172. package/fspiop/v2_0/openapi3/paths/transactionRequests.yaml +47 -0
  173. package/fspiop/v2_0/openapi3/paths/transactionRequests_ID.yaml +81 -0
  174. package/fspiop/v2_0/openapi3/paths/transactionRequests_ID_error.yaml +50 -0
  175. package/fspiop/v2_0/openapi3/paths/transactions_ID.yaml +80 -0
  176. package/fspiop/v2_0/openapi3/paths/transactions_ID_error.yaml +48 -0
  177. package/fspiop/v2_0/openapi3/paths/transfers.yaml +46 -0
  178. package/fspiop/v2_0/openapi3/paths/transfers_ID.yaml +119 -0
  179. package/fspiop/v2_0/openapi3/paths/transfers_ID_error.yaml +49 -0
  180. package/lib/fspiop/v1_1/openapi.d.ts +524 -542
  181. package/lib/fspiop/v2_0/openapi.d.ts +3964 -0
  182. package/lib/fspiop/v2_0/openapi.js +7 -0
  183. package/lib/fspiop/v2_0/openapi.js.map +1 -0
  184. package/lib/scripts/json-schema-generator.js +4 -5
  185. package/lib/scripts/json-schema-generator.js.map +1 -1
  186. package/lib/scripts/openapi-refactor.d.ts +29 -0
  187. package/lib/scripts/openapi-refactor.js +70 -0
  188. package/lib/scripts/openapi-refactor.js.map +1 -0
  189. package/package.json +29 -21
  190. package/tsconfig.build.json +1 -1
@@ -0,0 +1,4841 @@
1
+ openapi: 3.0.2
2
+ info:
3
+ version: 2.0-draft
4
+ title: Open API for FSP Interoperability (FSPIOP)
5
+ description: >-
6
+ Revision date: 2023-11-23 Based on [API Definition updated on 2020-05-19
7
+ Version
8
+ 1.1](https://github.com/mojaloop/mojaloop-specification/blob/main/documents/v1.1-document-set/API%20Definition_v1.1.pdf).
9
+
10
+ This is implementation friendly version of the API definition.
11
+
12
+ It includes the below definitions needed for third-party functionality. -
13
+ AuthenticationType
14
+ - U2F enum
15
+ - AuthenticationValue
16
+ - oneOf is changed to anyOf
17
+ - new element is added U2FPinValue
18
+ - New element U2FPIN
19
+
20
+ **Note:** The API supports a maximum size of 65536 bytes (64 Kilobytes) in
21
+ the HTTP header.
22
+ license:
23
+ name: CC BY-ND 4.0
24
+ url: https://github.com/mojaloop/mojaloop-specification/blob/main/LICENSE.md
25
+ contact:
26
+ name: Sam Kummary
27
+ url: https://github.com/mojaloop/mojaloop-specification/issues
28
+ servers:
29
+ - url: protocol://hostname:<port>/switch/
30
+ variables:
31
+ protocol:
32
+ enum:
33
+ - http
34
+ - https
35
+ default: https
36
+ paths:
37
+ /participants/{Type}/{ID}:
38
+ parameters:
39
+ - $ref: "#/components/parameters/Type"
40
+ - $ref: "#/components/parameters/ID"
41
+ - $ref: "#/components/parameters/Content-Type"
42
+ - $ref: "#/components/parameters/Date"
43
+ - $ref: "#/components/parameters/X-Forwarded-For"
44
+ - $ref: "#/components/parameters/FSPIOP-Source"
45
+ - $ref: "#/components/parameters/FSPIOP-Destination"
46
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
47
+ - $ref: "#/components/parameters/FSPIOP-Signature"
48
+ - $ref: "#/components/parameters/FSPIOP-URI"
49
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
50
+ post:
51
+ description: >-
52
+ The HTTP request `POST /participants/{Type}/{ID}` (or `POST
53
+ /participants/{Type}/{ID}/{SubId}`) is used to create information in the
54
+ server regarding the provided identity, defined by `{Type}`, `{ID}`, and
55
+ optionally `{SubId}` (for example, `POST /participants/MSISDN/123456789`
56
+ or `POST /participants/BUSINESS/shoecompany/employee1`). An
57
+ ExtensionList element has been added to this reqeust in version v1.1
58
+ summary: Create participant information
59
+ tags:
60
+ - participants
61
+ operationId: ParticipantsByIDAndType
62
+ parameters:
63
+ - $ref: "#/components/parameters/Accept"
64
+ - $ref: "#/components/parameters/Content-Length"
65
+ requestBody:
66
+ description: Participant information to be created.
67
+ required: true
68
+ content:
69
+ application/json:
70
+ schema:
71
+ $ref: "#/components/schemas/ParticipantsTypeIDSubIDPostRequest"
72
+ responses:
73
+ "202":
74
+ $ref: "#/components/responses/202"
75
+ "400":
76
+ $ref: "#/components/responses/400"
77
+ "401":
78
+ $ref: "#/components/responses/401"
79
+ "403":
80
+ $ref: "#/components/responses/403"
81
+ "404":
82
+ $ref: "#/components/responses/404"
83
+ "405":
84
+ $ref: "#/components/responses/405"
85
+ "406":
86
+ $ref: "#/components/responses/406"
87
+ "501":
88
+ $ref: "#/components/responses/501"
89
+ "503":
90
+ $ref: "#/components/responses/503"
91
+ get:
92
+ description: >-
93
+ The HTTP request `GET /participants/{Type}/{ID}` (or `GET
94
+ /participants/{Type}/{ID}/{SubId}`) is used to find out in which FSP the
95
+ requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}`,
96
+ is located (for example, `GET /participants/MSISDN/123456789`, or `GET
97
+ /participants/BUSINESS/shoecompany/employee1`). This HTTP request should
98
+ support a query string for filtering of currency. To use filtering of
99
+ currency, the HTTP request `GET /participants/{Type}/{ID}?currency=XYZ`
100
+ should be used, where `XYZ` is the requested currency.
101
+ summary: Look up participant information
102
+ tags:
103
+ - participants
104
+ operationId: ParticipantsByTypeAndID
105
+ parameters:
106
+ - $ref: "#/components/parameters/Accept"
107
+ responses:
108
+ "202":
109
+ $ref: "#/components/responses/202"
110
+ "400":
111
+ $ref: "#/components/responses/400"
112
+ "401":
113
+ $ref: "#/components/responses/401"
114
+ "403":
115
+ $ref: "#/components/responses/403"
116
+ "404":
117
+ $ref: "#/components/responses/404"
118
+ "405":
119
+ $ref: "#/components/responses/405"
120
+ "406":
121
+ $ref: "#/components/responses/406"
122
+ "501":
123
+ $ref: "#/components/responses/501"
124
+ "503":
125
+ $ref: "#/components/responses/503"
126
+ put:
127
+ description: >-
128
+ The callback `PUT /participants/{Type}/{ID}` (or `PUT
129
+ /participants/{Type}/{ID}/{SubId}`) is used to inform the client of a
130
+ successful result of the lookup, creation, or deletion of the FSP
131
+ information related to the Party. If the FSP information is deleted, the
132
+ fspId element should be empty; otherwise the element should include the
133
+ FSP information for the Party.
134
+ summary: Return participant information
135
+ tags:
136
+ - participants
137
+ operationId: ParticipantsByTypeAndID3
138
+ parameters:
139
+ - $ref: "#/components/parameters/Content-Length"
140
+ requestBody:
141
+ description: Participant information returned.
142
+ required: true
143
+ content:
144
+ application/json:
145
+ schema:
146
+ $ref: "#/components/schemas/ParticipantsTypeIDPutResponse"
147
+ responses:
148
+ "200":
149
+ $ref: "#/components/responses/200"
150
+ "400":
151
+ $ref: "#/components/responses/400"
152
+ "401":
153
+ $ref: "#/components/responses/401"
154
+ "403":
155
+ $ref: "#/components/responses/403"
156
+ "404":
157
+ $ref: "#/components/responses/404"
158
+ "405":
159
+ $ref: "#/components/responses/405"
160
+ "406":
161
+ $ref: "#/components/responses/406"
162
+ "501":
163
+ $ref: "#/components/responses/501"
164
+ "503":
165
+ $ref: "#/components/responses/503"
166
+ delete:
167
+ description: >-
168
+ The HTTP request `DELETE /participants/{Type}/{ID}` (or `DELETE
169
+ /participants/{Type}/{ID}/{SubId}`) is used to delete information in the
170
+ server regarding the provided identity, defined by `{Type}` and `{ID}`)
171
+ (for example, `DELETE /participants/MSISDN/123456789`), and optionally
172
+ `{SubId}`. This HTTP request should support a query string to delete FSP
173
+ information regarding a specific currency only. To delete a specific
174
+ currency only, the HTTP request `DELETE
175
+ /participants/{Type}/{ID}?currency=XYZ` should be used, where `XYZ` is
176
+ the requested currency.
177
+
178
+
179
+ **Note:** The Account Lookup System should verify that it is the Party’s
180
+ current FSP that is deleting the FSP information.
181
+ summary: Delete participant information
182
+ tags:
183
+ - participants
184
+ operationId: ParticipantsByTypeAndID2
185
+ parameters:
186
+ - $ref: "#/components/parameters/Accept"
187
+ responses:
188
+ "202":
189
+ $ref: "#/components/responses/202"
190
+ "400":
191
+ $ref: "#/components/responses/400"
192
+ "401":
193
+ $ref: "#/components/responses/401"
194
+ "403":
195
+ $ref: "#/components/responses/403"
196
+ "404":
197
+ $ref: "#/components/responses/404"
198
+ "405":
199
+ $ref: "#/components/responses/405"
200
+ "406":
201
+ $ref: "#/components/responses/406"
202
+ "501":
203
+ $ref: "#/components/responses/501"
204
+ "503":
205
+ $ref: "#/components/responses/503"
206
+ /participants/{Type}/{ID}/error:
207
+ put:
208
+ description: >-
209
+ If the server is unable to find, create or delete the associated FSP of
210
+ the provided identity, or another processing error occurred, the error
211
+ callback `PUT /participants/{Type}/{ID}/error` (or `PUT
212
+ /participants/{Type}/{ID}/{SubId}/error`) is used.
213
+ summary: Return participant information error
214
+ tags:
215
+ - participants
216
+ operationId: ParticipantsErrorByTypeAndID
217
+ parameters:
218
+ - $ref: "#/components/parameters/Type"
219
+ - $ref: "#/components/parameters/ID"
220
+ - $ref: "#/components/parameters/Content-Length"
221
+ - $ref: "#/components/parameters/Content-Type"
222
+ - $ref: "#/components/parameters/Date"
223
+ - $ref: "#/components/parameters/X-Forwarded-For"
224
+ - $ref: "#/components/parameters/FSPIOP-Source"
225
+ - $ref: "#/components/parameters/FSPIOP-Destination"
226
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
227
+ - $ref: "#/components/parameters/FSPIOP-Signature"
228
+ - $ref: "#/components/parameters/FSPIOP-URI"
229
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
230
+ requestBody:
231
+ description: Details of the error returned.
232
+ required: true
233
+ content:
234
+ application/json:
235
+ schema:
236
+ $ref: "#/components/schemas/ErrorInformationObject"
237
+ responses:
238
+ "200":
239
+ $ref: "#/components/responses/200"
240
+ "400":
241
+ $ref: "#/components/responses/400"
242
+ "401":
243
+ $ref: "#/components/responses/401"
244
+ "403":
245
+ $ref: "#/components/responses/403"
246
+ "404":
247
+ $ref: "#/components/responses/404"
248
+ "405":
249
+ $ref: "#/components/responses/405"
250
+ "406":
251
+ $ref: "#/components/responses/406"
252
+ "501":
253
+ $ref: "#/components/responses/501"
254
+ "503":
255
+ $ref: "#/components/responses/503"
256
+ /participants/{Type}/{ID}/{SubId}:
257
+ parameters:
258
+ - $ref: "#/components/parameters/Type"
259
+ - $ref: "#/components/parameters/ID"
260
+ - $ref: "#/components/parameters/SubId"
261
+ - $ref: "#/components/parameters/Content-Type"
262
+ - $ref: "#/components/parameters/Date"
263
+ - $ref: "#/components/parameters/X-Forwarded-For"
264
+ - $ref: "#/components/parameters/FSPIOP-Source"
265
+ - $ref: "#/components/parameters/FSPIOP-Destination"
266
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
267
+ - $ref: "#/components/parameters/FSPIOP-Signature"
268
+ - $ref: "#/components/parameters/FSPIOP-URI"
269
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
270
+ post:
271
+ description: >-
272
+ The HTTP request `POST /participants/{Type}/{ID}` (or `POST
273
+ /participants/{Type}/{ID}/{SubId}`) is used to create information in the
274
+ server regarding the provided identity, defined by `{Type}`, `{ID}`, and
275
+ optionally `{SubId}` (for example, `POST /participants/MSISDN/123456789`
276
+ or `POST /participants/BUSINESS/shoecompany/employee1`). An
277
+ ExtensionList element has been added to this reqeust in version v1.1
278
+ summary: Create participant information
279
+ tags:
280
+ - participants
281
+ operationId: ParticipantsSubIdByTypeAndIDPost
282
+ parameters:
283
+ - $ref: "#/components/parameters/Accept"
284
+ - $ref: "#/components/parameters/Content-Length"
285
+ requestBody:
286
+ description: Participant information to be created.
287
+ required: true
288
+ content:
289
+ application/json:
290
+ schema:
291
+ $ref: "#/components/schemas/ParticipantsTypeIDSubIDPostRequest"
292
+ responses:
293
+ "202":
294
+ $ref: "#/components/responses/202"
295
+ "400":
296
+ $ref: "#/components/responses/400"
297
+ "401":
298
+ $ref: "#/components/responses/401"
299
+ "403":
300
+ $ref: "#/components/responses/403"
301
+ "404":
302
+ $ref: "#/components/responses/404"
303
+ "405":
304
+ $ref: "#/components/responses/405"
305
+ "406":
306
+ $ref: "#/components/responses/406"
307
+ "501":
308
+ $ref: "#/components/responses/501"
309
+ "503":
310
+ $ref: "#/components/responses/503"
311
+ get:
312
+ description: >-
313
+ The HTTP request `GET /participants/{Type}/{ID}` (or `GET
314
+ /participants/{Type}/{ID}/{SubId}`) is used to find out in which FSP the
315
+ requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}`,
316
+ is located (for example, `GET /participants/MSISDN/123456789`, or `GET
317
+ /participants/BUSINESS/shoecompany/employee1`). This HTTP request should
318
+ support a query string for filtering of currency. To use filtering of
319
+ currency, the HTTP request `GET /participants/{Type}/{ID}?currency=XYZ`
320
+ should be used, where `XYZ` is the requested currency.
321
+ summary: Look up participant information
322
+ tags:
323
+ - participants
324
+ operationId: ParticipantsSubIdByTypeAndID
325
+ parameters:
326
+ - $ref: "#/components/parameters/Accept"
327
+ responses:
328
+ "202":
329
+ $ref: "#/components/responses/202"
330
+ "400":
331
+ $ref: "#/components/responses/400"
332
+ "401":
333
+ $ref: "#/components/responses/401"
334
+ "403":
335
+ $ref: "#/components/responses/403"
336
+ "404":
337
+ $ref: "#/components/responses/404"
338
+ "405":
339
+ $ref: "#/components/responses/405"
340
+ "406":
341
+ $ref: "#/components/responses/406"
342
+ "501":
343
+ $ref: "#/components/responses/501"
344
+ "503":
345
+ $ref: "#/components/responses/503"
346
+ put:
347
+ description: >-
348
+ The callback `PUT /participants/{Type}/{ID}` (or `PUT
349
+ /participants/{Type}/{ID}/{SubId}`) is used to inform the client of a
350
+ successful result of the lookup, creation, or deletion of the FSP
351
+ information related to the Party. If the FSP information is deleted, the
352
+ fspId element should be empty; otherwise the element should include the
353
+ FSP information for the Party.
354
+ summary: Return participant information
355
+ tags:
356
+ - participants
357
+ operationId: ParticipantsSubIdByTypeAndID3
358
+ parameters:
359
+ - $ref: "#/components/parameters/Content-Length"
360
+ requestBody:
361
+ description: Participant information returned.
362
+ required: true
363
+ content:
364
+ application/json:
365
+ schema:
366
+ $ref: "#/components/schemas/ParticipantsTypeIDPutResponse"
367
+ responses:
368
+ "200":
369
+ $ref: "#/components/responses/200"
370
+ "400":
371
+ $ref: "#/components/responses/400"
372
+ "401":
373
+ $ref: "#/components/responses/401"
374
+ "403":
375
+ $ref: "#/components/responses/403"
376
+ "404":
377
+ $ref: "#/components/responses/404"
378
+ "405":
379
+ $ref: "#/components/responses/405"
380
+ "406":
381
+ $ref: "#/components/responses/406"
382
+ "501":
383
+ $ref: "#/components/responses/501"
384
+ "503":
385
+ $ref: "#/components/responses/503"
386
+ delete:
387
+ description: >-
388
+ The HTTP request `DELETE /participants/{Type}/{ID}` (or `DELETE
389
+ /participants/{Type}/{ID}/{SubId}`) is used to delete information in the
390
+ server regarding the provided identity, defined by `{Type}` and `{ID}`)
391
+ (for example, `DELETE /participants/MSISDN/123456789`), and optionally
392
+ `{SubId}`. This HTTP request should support a query string to delete FSP
393
+ information regarding a specific currency only. To delete a specific
394
+ currency only, the HTTP request `DELETE
395
+ /participants/{Type}/{ID}?currency=XYZ` should be used, where `XYZ` is
396
+ the requested currency.
397
+
398
+
399
+ **Note:** The Account Lookup System should verify that it is the Party’s
400
+ current FSP that is deleting the FSP information.
401
+ summary: Delete participant information
402
+ tags:
403
+ - participants
404
+ operationId: ParticipantsSubIdByTypeAndID2
405
+ parameters:
406
+ - $ref: "#/components/parameters/Accept"
407
+ responses:
408
+ "202":
409
+ $ref: "#/components/responses/202"
410
+ "400":
411
+ $ref: "#/components/responses/400"
412
+ "401":
413
+ $ref: "#/components/responses/401"
414
+ "403":
415
+ $ref: "#/components/responses/403"
416
+ "404":
417
+ $ref: "#/components/responses/404"
418
+ "405":
419
+ $ref: "#/components/responses/405"
420
+ "406":
421
+ $ref: "#/components/responses/406"
422
+ "501":
423
+ $ref: "#/components/responses/501"
424
+ "503":
425
+ $ref: "#/components/responses/503"
426
+ /participants/{Type}/{ID}/{SubId}/error:
427
+ put:
428
+ description: >-
429
+ If the server is unable to find, create or delete the associated FSP of
430
+ the provided identity, or another processing error occurred, the error
431
+ callback `PUT /participants/{Type}/{ID}/error` (or `PUT
432
+ /participants/{Type}/{ID}/{SubId}/error`) is used.
433
+ summary: Return participant information error
434
+ tags:
435
+ - participants
436
+ operationId: ParticipantsSubIdErrorByTypeAndID
437
+ parameters:
438
+ - $ref: "#/components/parameters/Type"
439
+ - $ref: "#/components/parameters/ID"
440
+ - $ref: "#/components/parameters/SubId"
441
+ - $ref: "#/components/parameters/Content-Length"
442
+ - $ref: "#/components/parameters/Content-Type"
443
+ - $ref: "#/components/parameters/Date"
444
+ - $ref: "#/components/parameters/X-Forwarded-For"
445
+ - $ref: "#/components/parameters/FSPIOP-Source"
446
+ - $ref: "#/components/parameters/FSPIOP-Destination"
447
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
448
+ - $ref: "#/components/parameters/FSPIOP-Signature"
449
+ - $ref: "#/components/parameters/FSPIOP-URI"
450
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
451
+ requestBody:
452
+ description: Details of the error returned.
453
+ required: true
454
+ content:
455
+ application/json:
456
+ schema:
457
+ $ref: "#/components/schemas/ErrorInformationObject"
458
+ responses:
459
+ "200":
460
+ $ref: "#/components/responses/200"
461
+ "400":
462
+ $ref: "#/components/responses/400"
463
+ "401":
464
+ $ref: "#/components/responses/401"
465
+ "403":
466
+ $ref: "#/components/responses/403"
467
+ "404":
468
+ $ref: "#/components/responses/404"
469
+ "405":
470
+ $ref: "#/components/responses/405"
471
+ "406":
472
+ $ref: "#/components/responses/406"
473
+ "501":
474
+ $ref: "#/components/responses/501"
475
+ "503":
476
+ $ref: "#/components/responses/503"
477
+ /participants:
478
+ post:
479
+ description: >-
480
+ The HTTP request `POST /participants` is used to create information in
481
+ the server regarding the provided list of identities. This request
482
+ should be used for bulk creation of FSP information for more than one
483
+ Party. The optional currency parameter should indicate that each
484
+ provided Party supports the currency.
485
+ summary: Create bulk participant information
486
+ tags:
487
+ - participants
488
+ operationId: Participants1
489
+ parameters:
490
+ - $ref: "#/components/parameters/Accept"
491
+ - $ref: "#/components/parameters/Content-Length"
492
+ - $ref: "#/components/parameters/Content-Type"
493
+ - $ref: "#/components/parameters/Date"
494
+ - $ref: "#/components/parameters/X-Forwarded-For"
495
+ - $ref: "#/components/parameters/FSPIOP-Source"
496
+ - $ref: "#/components/parameters/FSPIOP-Destination"
497
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
498
+ - $ref: "#/components/parameters/FSPIOP-Signature"
499
+ - $ref: "#/components/parameters/FSPIOP-URI"
500
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
501
+ requestBody:
502
+ description: Participant information to be created.
503
+ required: true
504
+ content:
505
+ application/json:
506
+ schema:
507
+ $ref: "#/components/schemas/ParticipantsPostRequest"
508
+ responses:
509
+ "202":
510
+ $ref: "#/components/responses/202"
511
+ "400":
512
+ $ref: "#/components/responses/400"
513
+ "401":
514
+ $ref: "#/components/responses/401"
515
+ "403":
516
+ $ref: "#/components/responses/403"
517
+ "404":
518
+ $ref: "#/components/responses/404"
519
+ "405":
520
+ $ref: "#/components/responses/405"
521
+ "406":
522
+ $ref: "#/components/responses/406"
523
+ "501":
524
+ $ref: "#/components/responses/501"
525
+ "503":
526
+ $ref: "#/components/responses/503"
527
+ /participants/{ID}:
528
+ put:
529
+ description: >-
530
+ The callback `PUT /participants/{ID}` is used to inform the client of
531
+ the result of the creation of the provided list of identities.
532
+ summary: Return bulk participant information
533
+ tags:
534
+ - participants
535
+ operationId: putParticipantsByID
536
+ parameters:
537
+ - $ref: "#/components/parameters/ID"
538
+ - $ref: "#/components/parameters/Content-Length"
539
+ - $ref: "#/components/parameters/Content-Type"
540
+ - $ref: "#/components/parameters/Date"
541
+ - $ref: "#/components/parameters/X-Forwarded-For"
542
+ - $ref: "#/components/parameters/FSPIOP-Source"
543
+ - $ref: "#/components/parameters/FSPIOP-Destination"
544
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
545
+ - $ref: "#/components/parameters/FSPIOP-Signature"
546
+ - $ref: "#/components/parameters/FSPIOP-URI"
547
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
548
+ requestBody:
549
+ description: Participant information returned.
550
+ required: true
551
+ content:
552
+ application/json:
553
+ schema:
554
+ $ref: "#/components/schemas/ParticipantsIDPutResponse"
555
+ responses:
556
+ "200":
557
+ $ref: "#/components/responses/200"
558
+ "400":
559
+ $ref: "#/components/responses/400"
560
+ "401":
561
+ $ref: "#/components/responses/401"
562
+ "403":
563
+ $ref: "#/components/responses/403"
564
+ "404":
565
+ $ref: "#/components/responses/404"
566
+ "405":
567
+ $ref: "#/components/responses/405"
568
+ "406":
569
+ $ref: "#/components/responses/406"
570
+ "501":
571
+ $ref: "#/components/responses/501"
572
+ "503":
573
+ $ref: "#/components/responses/503"
574
+ /participants/{ID}/error:
575
+ put:
576
+ description: >-
577
+ If there is an error during FSP information creation in the server, the
578
+ error callback `PUT /participants/{ID}/error` is used. The `{ID}` in the
579
+ URI should contain the requestId that was used for the creation of the
580
+ participant information.
581
+ summary: Return bulk participant information error
582
+ tags:
583
+ - participants
584
+ operationId: ParticipantsByIDAndError
585
+ parameters:
586
+ - $ref: "#/components/parameters/ID"
587
+ - $ref: "#/components/parameters/Content-Length"
588
+ - $ref: "#/components/parameters/Content-Type"
589
+ - $ref: "#/components/parameters/Date"
590
+ - $ref: "#/components/parameters/X-Forwarded-For"
591
+ - $ref: "#/components/parameters/FSPIOP-Source"
592
+ - $ref: "#/components/parameters/FSPIOP-Destination"
593
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
594
+ - $ref: "#/components/parameters/FSPIOP-Signature"
595
+ - $ref: "#/components/parameters/FSPIOP-URI"
596
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
597
+ requestBody:
598
+ description: Details of the error returned.
599
+ required: true
600
+ content:
601
+ application/json:
602
+ schema:
603
+ $ref: "#/components/schemas/ErrorInformationObject"
604
+ responses:
605
+ "200":
606
+ $ref: "#/components/responses/200"
607
+ "400":
608
+ $ref: "#/components/responses/400"
609
+ "401":
610
+ $ref: "#/components/responses/401"
611
+ "403":
612
+ $ref: "#/components/responses/403"
613
+ "404":
614
+ $ref: "#/components/responses/404"
615
+ "405":
616
+ $ref: "#/components/responses/405"
617
+ "406":
618
+ $ref: "#/components/responses/406"
619
+ "501":
620
+ $ref: "#/components/responses/501"
621
+ "503":
622
+ $ref: "#/components/responses/503"
623
+ /parties/{Type}/{ID}:
624
+ parameters:
625
+ - $ref: "#/components/parameters/Type"
626
+ - $ref: "#/components/parameters/ID"
627
+ - $ref: "#/components/parameters/Content-Type"
628
+ - $ref: "#/components/parameters/Date"
629
+ - $ref: "#/components/parameters/X-Forwarded-For"
630
+ - $ref: "#/components/parameters/FSPIOP-Source"
631
+ - $ref: "#/components/parameters/FSPIOP-Destination"
632
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
633
+ - $ref: "#/components/parameters/FSPIOP-Signature"
634
+ - $ref: "#/components/parameters/FSPIOP-URI"
635
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
636
+ get:
637
+ description: >-
638
+ The HTTP request `GET /parties/{Type}/{ID}` (or `GET
639
+ /parties/{Type}/{ID}/{SubId}`) is used to look up information regarding
640
+ the requested Party, defined by `{Type}`, `{ID}` and optionally
641
+ `{SubId}` (for example, `GET /parties/MSISDN/123456789`, or `GET
642
+ /parties/BUSINESS/shoecompany/employee1`).
643
+ summary: Look up party information
644
+ tags:
645
+ - parties
646
+ operationId: PartiesByTypeAndID
647
+ parameters:
648
+ - $ref: "#/components/parameters/Accept"
649
+ responses:
650
+ "202":
651
+ $ref: "#/components/responses/202"
652
+ "400":
653
+ $ref: "#/components/responses/400"
654
+ "401":
655
+ $ref: "#/components/responses/401"
656
+ "403":
657
+ $ref: "#/components/responses/403"
658
+ "404":
659
+ $ref: "#/components/responses/404"
660
+ "405":
661
+ $ref: "#/components/responses/405"
662
+ "406":
663
+ $ref: "#/components/responses/406"
664
+ "501":
665
+ $ref: "#/components/responses/501"
666
+ "503":
667
+ $ref: "#/components/responses/503"
668
+ put:
669
+ description: >-
670
+ The callback `PUT /parties/{Type}/{ID}` (or `PUT
671
+ /parties/{Type}/{ID}/{SubId}`) is used to inform the client of a
672
+ successful result of the Party information lookup.
673
+ summary: Return party information
674
+ tags:
675
+ - parties
676
+ operationId: PartiesByTypeAndID2
677
+ parameters:
678
+ - $ref: "#/components/parameters/Content-Length"
679
+ requestBody:
680
+ description: Party information returned.
681
+ required: true
682
+ content:
683
+ application/json:
684
+ schema:
685
+ $ref: "#/components/schemas/PartiesTypeIDPutResponse"
686
+ responses:
687
+ "200":
688
+ $ref: "#/components/responses/200"
689
+ "400":
690
+ $ref: "#/components/responses/400"
691
+ "401":
692
+ $ref: "#/components/responses/401"
693
+ "403":
694
+ $ref: "#/components/responses/403"
695
+ "404":
696
+ $ref: "#/components/responses/404"
697
+ "405":
698
+ $ref: "#/components/responses/405"
699
+ "406":
700
+ $ref: "#/components/responses/406"
701
+ "501":
702
+ $ref: "#/components/responses/501"
703
+ "503":
704
+ $ref: "#/components/responses/503"
705
+ /parties/{Type}/{ID}/error:
706
+ put:
707
+ description: >-
708
+ If the server is unable to find Party information of the provided
709
+ identity, or another processing error occurred, the error callback `PUT
710
+ /parties/{Type}/{ID}/error` (or `PUT /parties/{Type}/{ID}/{SubI}/error`)
711
+ is used.
712
+ summary: Return party information error
713
+ tags:
714
+ - parties
715
+ operationId: PartiesErrorByTypeAndID
716
+ parameters:
717
+ - $ref: "#/components/parameters/Type"
718
+ - $ref: "#/components/parameters/ID"
719
+ - $ref: "#/components/parameters/Content-Length"
720
+ - $ref: "#/components/parameters/Content-Type"
721
+ - $ref: "#/components/parameters/Date"
722
+ - $ref: "#/components/parameters/X-Forwarded-For"
723
+ - $ref: "#/components/parameters/FSPIOP-Source"
724
+ - $ref: "#/components/parameters/FSPIOP-Destination"
725
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
726
+ - $ref: "#/components/parameters/FSPIOP-Signature"
727
+ - $ref: "#/components/parameters/FSPIOP-URI"
728
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
729
+ requestBody:
730
+ description: Details of the error returned.
731
+ required: true
732
+ content:
733
+ application/json:
734
+ schema:
735
+ $ref: "#/components/schemas/ErrorInformationObject"
736
+ responses:
737
+ "200":
738
+ $ref: "#/components/responses/200"
739
+ "400":
740
+ $ref: "#/components/responses/400"
741
+ "401":
742
+ $ref: "#/components/responses/401"
743
+ "403":
744
+ $ref: "#/components/responses/403"
745
+ "404":
746
+ $ref: "#/components/responses/404"
747
+ "405":
748
+ $ref: "#/components/responses/405"
749
+ "406":
750
+ $ref: "#/components/responses/406"
751
+ "501":
752
+ $ref: "#/components/responses/501"
753
+ "503":
754
+ $ref: "#/components/responses/503"
755
+ /parties/{Type}/{ID}/{SubId}:
756
+ parameters:
757
+ - $ref: "#/components/parameters/Type"
758
+ - $ref: "#/components/parameters/ID"
759
+ - $ref: "#/components/parameters/SubId"
760
+ - $ref: "#/components/parameters/Content-Type"
761
+ - $ref: "#/components/parameters/Date"
762
+ - $ref: "#/components/parameters/X-Forwarded-For"
763
+ - $ref: "#/components/parameters/FSPIOP-Source"
764
+ - $ref: "#/components/parameters/FSPIOP-Destination"
765
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
766
+ - $ref: "#/components/parameters/FSPIOP-Signature"
767
+ - $ref: "#/components/parameters/FSPIOP-URI"
768
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
769
+ get:
770
+ description: >-
771
+ The HTTP request `GET /parties/{Type}/{ID}` (or `GET
772
+ /parties/{Type}/{ID}/{SubId}`) is used to look up information regarding
773
+ the requested Party, defined by `{Type}`, `{ID}` and optionally
774
+ `{SubId}` (for example, `GET /parties/MSISDN/123456789`, or `GET
775
+ /parties/BUSINESS/shoecompany/employee1`).
776
+ summary: Look up party information
777
+ tags:
778
+ - parties
779
+ operationId: PartiesSubIdByTypeAndID
780
+ parameters:
781
+ - $ref: "#/components/parameters/Accept"
782
+ responses:
783
+ "202":
784
+ $ref: "#/components/responses/202"
785
+ "400":
786
+ $ref: "#/components/responses/400"
787
+ "401":
788
+ $ref: "#/components/responses/401"
789
+ "403":
790
+ $ref: "#/components/responses/403"
791
+ "404":
792
+ $ref: "#/components/responses/404"
793
+ "405":
794
+ $ref: "#/components/responses/405"
795
+ "406":
796
+ $ref: "#/components/responses/406"
797
+ "501":
798
+ $ref: "#/components/responses/501"
799
+ "503":
800
+ $ref: "#/components/responses/503"
801
+ put:
802
+ description: >-
803
+ The callback `PUT /parties/{Type}/{ID}` (or `PUT
804
+ /parties/{Type}/{ID}/{SubId}`) is used to inform the client of a
805
+ successful result of the Party information lookup.
806
+ summary: Return party information
807
+ tags:
808
+ - parties
809
+ operationId: PartiesSubIdByTypeAndIDPut
810
+ parameters:
811
+ - $ref: "#/components/parameters/Content-Length"
812
+ requestBody:
813
+ description: Party information returned.
814
+ required: true
815
+ content:
816
+ application/json:
817
+ schema:
818
+ $ref: "#/components/schemas/PartiesTypeIDPutResponse"
819
+ responses:
820
+ "200":
821
+ $ref: "#/components/responses/200"
822
+ "400":
823
+ $ref: "#/components/responses/400"
824
+ "401":
825
+ $ref: "#/components/responses/401"
826
+ "403":
827
+ $ref: "#/components/responses/403"
828
+ "404":
829
+ $ref: "#/components/responses/404"
830
+ "405":
831
+ $ref: "#/components/responses/405"
832
+ "406":
833
+ $ref: "#/components/responses/406"
834
+ "501":
835
+ $ref: "#/components/responses/501"
836
+ "503":
837
+ $ref: "#/components/responses/503"
838
+ /parties/{Type}/{ID}/{SubId}/error:
839
+ put:
840
+ description: >-
841
+ If the server is unable to find Party information of the provided
842
+ identity, or another processing error occurred, the error callback `PUT
843
+ /parties/{Type}/{ID}/error` (or `PUT
844
+ /parties/{Type}/{ID}/{SubId}/error`) is used.
845
+ summary: Return party information error
846
+ tags:
847
+ - parties
848
+ operationId: PartiesSubIdErrorByTypeAndID
849
+ parameters:
850
+ - $ref: "#/components/parameters/Type"
851
+ - $ref: "#/components/parameters/ID"
852
+ - $ref: "#/components/parameters/SubId"
853
+ - $ref: "#/components/parameters/Content-Length"
854
+ - $ref: "#/components/parameters/Content-Type"
855
+ - $ref: "#/components/parameters/Date"
856
+ - $ref: "#/components/parameters/X-Forwarded-For"
857
+ - $ref: "#/components/parameters/FSPIOP-Source"
858
+ - $ref: "#/components/parameters/FSPIOP-Destination"
859
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
860
+ - $ref: "#/components/parameters/FSPIOP-Signature"
861
+ - $ref: "#/components/parameters/FSPIOP-URI"
862
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
863
+ requestBody:
864
+ description: Details of the error returned.
865
+ required: true
866
+ content:
867
+ application/json:
868
+ schema:
869
+ $ref: "#/components/schemas/ErrorInformationObject"
870
+ responses:
871
+ "200":
872
+ $ref: "#/components/responses/200"
873
+ "400":
874
+ $ref: "#/components/responses/400"
875
+ "401":
876
+ $ref: "#/components/responses/401"
877
+ "403":
878
+ $ref: "#/components/responses/403"
879
+ "404":
880
+ $ref: "#/components/responses/404"
881
+ "405":
882
+ $ref: "#/components/responses/405"
883
+ "406":
884
+ $ref: "#/components/responses/406"
885
+ "501":
886
+ $ref: "#/components/responses/501"
887
+ "503":
888
+ $ref: "#/components/responses/503"
889
+ /transactionRequests:
890
+ post:
891
+ description: >-
892
+ The HTTP request `POST /transactionRequests` is used to request the
893
+ creation of a transaction request for the provided financial transaction
894
+ in the server.
895
+ summary: Perform transaction request
896
+ tags:
897
+ - transactionRequests
898
+ operationId: TransactionRequests
899
+ parameters:
900
+ - $ref: "#/components/parameters/Accept"
901
+ - $ref: "#/components/parameters/Content-Length"
902
+ - $ref: "#/components/parameters/Content-Type"
903
+ - $ref: "#/components/parameters/Date"
904
+ - $ref: "#/components/parameters/X-Forwarded-For"
905
+ - $ref: "#/components/parameters/FSPIOP-Source"
906
+ - $ref: "#/components/parameters/FSPIOP-Destination"
907
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
908
+ - $ref: "#/components/parameters/FSPIOP-Signature"
909
+ - $ref: "#/components/parameters/FSPIOP-URI"
910
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
911
+ requestBody:
912
+ description: Transaction request to be created.
913
+ required: true
914
+ content:
915
+ application/json:
916
+ schema:
917
+ $ref: "#/components/schemas/TransactionRequestsPostRequest"
918
+ responses:
919
+ "202":
920
+ $ref: "#/components/responses/202"
921
+ "400":
922
+ $ref: "#/components/responses/400"
923
+ "401":
924
+ $ref: "#/components/responses/401"
925
+ "403":
926
+ $ref: "#/components/responses/403"
927
+ "404":
928
+ $ref: "#/components/responses/404"
929
+ "405":
930
+ $ref: "#/components/responses/405"
931
+ "406":
932
+ $ref: "#/components/responses/406"
933
+ "501":
934
+ $ref: "#/components/responses/501"
935
+ "503":
936
+ $ref: "#/components/responses/503"
937
+ /transactionRequests/{ID}:
938
+ parameters:
939
+ - $ref: "#/components/parameters/ID"
940
+ - $ref: "#/components/parameters/Content-Type"
941
+ - $ref: "#/components/parameters/Date"
942
+ - $ref: "#/components/parameters/X-Forwarded-For"
943
+ - $ref: "#/components/parameters/FSPIOP-Source"
944
+ - $ref: "#/components/parameters/FSPIOP-Destination"
945
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
946
+ - $ref: "#/components/parameters/FSPIOP-Signature"
947
+ - $ref: "#/components/parameters/FSPIOP-URI"
948
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
949
+ get:
950
+ description: >-
951
+ The HTTP request `GET /transactionRequests/{ID}` is used to get
952
+ information regarding a transaction request created or requested
953
+ earlier. The `{ID}` in the URI should contain the `transactionRequestId`
954
+ that was used for the creation of the transaction request.
955
+ summary: Retrieve transaction request information
956
+ tags:
957
+ - transactionRequests
958
+ operationId: TransactionRequestsByID
959
+ parameters:
960
+ - $ref: "#/components/parameters/Accept"
961
+ responses:
962
+ "202":
963
+ $ref: "#/components/responses/202"
964
+ "400":
965
+ $ref: "#/components/responses/400"
966
+ "401":
967
+ $ref: "#/components/responses/401"
968
+ "403":
969
+ $ref: "#/components/responses/403"
970
+ "404":
971
+ $ref: "#/components/responses/404"
972
+ "405":
973
+ $ref: "#/components/responses/405"
974
+ "406":
975
+ $ref: "#/components/responses/406"
976
+ "501":
977
+ $ref: "#/components/responses/501"
978
+ "503":
979
+ $ref: "#/components/responses/503"
980
+ put:
981
+ description: >-
982
+ The callback `PUT /transactionRequests/{ID}` is used to inform the
983
+ client of a requested or created transaction request. The `{ID}` in the
984
+ URI should contain the `transactionRequestId` that was used for the
985
+ creation of the transaction request, or the `{ID}` that was used in the
986
+ `GET /transactionRequests/{ID}`.
987
+ summary: Return transaction request information
988
+ tags:
989
+ - transactionRequests
990
+ operationId: TransactionRequestsByIDPut
991
+ parameters:
992
+ - $ref: "#/components/parameters/Content-Length"
993
+ requestBody:
994
+ description: Transaction request information returned.
995
+ required: true
996
+ content:
997
+ application/json:
998
+ schema:
999
+ $ref: "#/components/schemas/TransactionRequestsIDPutResponse"
1000
+ responses:
1001
+ "200":
1002
+ $ref: "#/components/responses/200"
1003
+ "400":
1004
+ $ref: "#/components/responses/400"
1005
+ "401":
1006
+ $ref: "#/components/responses/401"
1007
+ "403":
1008
+ $ref: "#/components/responses/403"
1009
+ "404":
1010
+ $ref: "#/components/responses/404"
1011
+ "405":
1012
+ $ref: "#/components/responses/405"
1013
+ "406":
1014
+ $ref: "#/components/responses/406"
1015
+ "501":
1016
+ $ref: "#/components/responses/501"
1017
+ "503":
1018
+ $ref: "#/components/responses/503"
1019
+ /transactionRequests/{ID}/error:
1020
+ put:
1021
+ description: >-
1022
+ If the server is unable to find or create a transaction request, or
1023
+ another processing error occurs, the error callback `PUT
1024
+ /transactionRequests/{ID}/error` is used. The `{ID}` in the URI should
1025
+ contain the `transactionRequestId` that was used for the creation of the
1026
+ transaction request, or the `{ID}` that was used in the `GET
1027
+ /transactionRequests/{ID}`.
1028
+ summary: Return transaction request information error
1029
+ tags:
1030
+ - transactionRequests
1031
+ operationId: TransactionRequestsErrorByID
1032
+ parameters:
1033
+ - $ref: "#/components/parameters/ID"
1034
+ - $ref: "#/components/parameters/Content-Length"
1035
+ - $ref: "#/components/parameters/Content-Type"
1036
+ - $ref: "#/components/parameters/Date"
1037
+ - $ref: "#/components/parameters/X-Forwarded-For"
1038
+ - $ref: "#/components/parameters/FSPIOP-Source"
1039
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1040
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1041
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1042
+ - $ref: "#/components/parameters/FSPIOP-URI"
1043
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1044
+ requestBody:
1045
+ description: Details of the error returned.
1046
+ required: true
1047
+ content:
1048
+ application/json:
1049
+ schema:
1050
+ $ref: "#/components/schemas/ErrorInformationObject"
1051
+ responses:
1052
+ "200":
1053
+ $ref: "#/components/responses/200"
1054
+ "400":
1055
+ $ref: "#/components/responses/400"
1056
+ "401":
1057
+ $ref: "#/components/responses/401"
1058
+ "403":
1059
+ $ref: "#/components/responses/403"
1060
+ "404":
1061
+ $ref: "#/components/responses/404"
1062
+ "405":
1063
+ $ref: "#/components/responses/405"
1064
+ "406":
1065
+ $ref: "#/components/responses/406"
1066
+ "501":
1067
+ $ref: "#/components/responses/501"
1068
+ "503":
1069
+ $ref: "#/components/responses/503"
1070
+ /quotes:
1071
+ post:
1072
+ description: >-
1073
+ The HTTP request `POST /quotes` is used to request the creation of a
1074
+ quote for the provided financial transaction in the server.
1075
+ summary: Calculate quote
1076
+ tags:
1077
+ - quotes
1078
+ operationId: Quotes
1079
+ parameters:
1080
+ - $ref: "#/components/parameters/Accept"
1081
+ - $ref: "#/components/parameters/Content-Length"
1082
+ - $ref: "#/components/parameters/Content-Type"
1083
+ - $ref: "#/components/parameters/Date"
1084
+ - $ref: "#/components/parameters/X-Forwarded-For"
1085
+ - $ref: "#/components/parameters/FSPIOP-Source"
1086
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1087
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1088
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1089
+ - $ref: "#/components/parameters/FSPIOP-URI"
1090
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1091
+ requestBody:
1092
+ description: Details of the quote to be created.
1093
+ required: true
1094
+ content:
1095
+ application/json:
1096
+ schema:
1097
+ $ref: "#/components/schemas/QuotesPostRequest"
1098
+ responses:
1099
+ "202":
1100
+ $ref: "#/components/responses/202"
1101
+ "400":
1102
+ $ref: "#/components/responses/400"
1103
+ "401":
1104
+ $ref: "#/components/responses/401"
1105
+ "403":
1106
+ $ref: "#/components/responses/403"
1107
+ "404":
1108
+ $ref: "#/components/responses/404"
1109
+ "405":
1110
+ $ref: "#/components/responses/405"
1111
+ "406":
1112
+ $ref: "#/components/responses/406"
1113
+ "501":
1114
+ $ref: "#/components/responses/501"
1115
+ "503":
1116
+ $ref: "#/components/responses/503"
1117
+ /quotes/{ID}:
1118
+ parameters:
1119
+ - $ref: "#/components/parameters/ID"
1120
+ - $ref: "#/components/parameters/Content-Type"
1121
+ - $ref: "#/components/parameters/Date"
1122
+ - $ref: "#/components/parameters/X-Forwarded-For"
1123
+ - $ref: "#/components/parameters/FSPIOP-Source"
1124
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1125
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1126
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1127
+ - $ref: "#/components/parameters/FSPIOP-URI"
1128
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1129
+ get:
1130
+ description: >-
1131
+ The HTTP request `GET /quotes/{ID}` is used to get information regarding
1132
+ a quote created or requested earlier. The `{ID}` in the URI should
1133
+ contain the `quoteId` that was used for the creation of the quote.
1134
+ summary: Retrieve quote information
1135
+ tags:
1136
+ - quotes
1137
+ operationId: QuotesByID
1138
+ parameters:
1139
+ - $ref: "#/components/parameters/Accept"
1140
+ responses:
1141
+ "202":
1142
+ $ref: "#/components/responses/202"
1143
+ "400":
1144
+ $ref: "#/components/responses/400"
1145
+ "401":
1146
+ $ref: "#/components/responses/401"
1147
+ "403":
1148
+ $ref: "#/components/responses/403"
1149
+ "404":
1150
+ $ref: "#/components/responses/404"
1151
+ "405":
1152
+ $ref: "#/components/responses/405"
1153
+ "406":
1154
+ $ref: "#/components/responses/406"
1155
+ "501":
1156
+ $ref: "#/components/responses/501"
1157
+ "503":
1158
+ $ref: "#/components/responses/503"
1159
+ put:
1160
+ description: >-
1161
+ The callback `PUT /quotes/{ID}` is used to inform the client of a
1162
+ requested or created quote. The `{ID}` in the URI should contain the
1163
+ `quoteId` that was used for the creation of the quote, or the `{ID}`
1164
+ that was used in the `GET /quotes/{ID}` request.
1165
+ summary: Return quote information
1166
+ tags:
1167
+ - quotes
1168
+ operationId: QuotesByID1
1169
+ parameters:
1170
+ - $ref: "#/components/parameters/Content-Length"
1171
+ requestBody:
1172
+ description: Quote information returned.
1173
+ required: true
1174
+ content:
1175
+ application/json:
1176
+ schema:
1177
+ $ref: "#/components/schemas/QuotesIDPutResponse"
1178
+ responses:
1179
+ "200":
1180
+ $ref: "#/components/responses/200"
1181
+ "400":
1182
+ $ref: "#/components/responses/400"
1183
+ "401":
1184
+ $ref: "#/components/responses/401"
1185
+ "403":
1186
+ $ref: "#/components/responses/403"
1187
+ "404":
1188
+ $ref: "#/components/responses/404"
1189
+ "405":
1190
+ $ref: "#/components/responses/405"
1191
+ "406":
1192
+ $ref: "#/components/responses/406"
1193
+ "501":
1194
+ $ref: "#/components/responses/501"
1195
+ "503":
1196
+ $ref: "#/components/responses/503"
1197
+ /quotes/{ID}/error:
1198
+ put:
1199
+ description: >-
1200
+ If the server is unable to find or create a quote, or some other
1201
+ processing error occurs, the error callback `PUT /quotes/{ID}/error` is
1202
+ used. The `{ID}` in the URI should contain the `quoteId` that was used
1203
+ for the creation of the quote, or the `{ID}` that was used in the `GET
1204
+ /quotes/{ID}` request.
1205
+ summary: Return quote information error
1206
+ tags:
1207
+ - quotes
1208
+ operationId: QuotesByIDAndError
1209
+ parameters:
1210
+ - $ref: "#/components/parameters/ID"
1211
+ - $ref: "#/components/parameters/Content-Length"
1212
+ - $ref: "#/components/parameters/Content-Type"
1213
+ - $ref: "#/components/parameters/Date"
1214
+ - $ref: "#/components/parameters/X-Forwarded-For"
1215
+ - $ref: "#/components/parameters/FSPIOP-Source"
1216
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1217
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1218
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1219
+ - $ref: "#/components/parameters/FSPIOP-URI"
1220
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1221
+ requestBody:
1222
+ description: Details of the error returned.
1223
+ required: true
1224
+ content:
1225
+ application/json:
1226
+ schema:
1227
+ $ref: "#/components/schemas/ErrorInformationObject"
1228
+ responses:
1229
+ "200":
1230
+ $ref: "#/components/responses/200"
1231
+ "400":
1232
+ $ref: "#/components/responses/400"
1233
+ "401":
1234
+ $ref: "#/components/responses/401"
1235
+ "403":
1236
+ $ref: "#/components/responses/403"
1237
+ "404":
1238
+ $ref: "#/components/responses/404"
1239
+ "405":
1240
+ $ref: "#/components/responses/405"
1241
+ "406":
1242
+ $ref: "#/components/responses/406"
1243
+ "501":
1244
+ $ref: "#/components/responses/501"
1245
+ "503":
1246
+ $ref: "#/components/responses/503"
1247
+ /authorizations/{ID}:
1248
+ parameters:
1249
+ - $ref: "#/components/parameters/ID"
1250
+ - $ref: "#/components/parameters/Content-Type"
1251
+ - $ref: "#/components/parameters/Date"
1252
+ - $ref: "#/components/parameters/X-Forwarded-For"
1253
+ - $ref: "#/components/parameters/FSPIOP-Source"
1254
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1255
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1256
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1257
+ - $ref: "#/components/parameters/FSPIOP-URI"
1258
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1259
+ get:
1260
+ description: >-
1261
+ The HTTP request `GET /authorizations/{ID}` is used to request the Payer
1262
+ to enter the applicable credentials in the Payee FSP system. The `{ID}`
1263
+ in the URI should contain the `transactionRequestID`, received from the
1264
+ `POST /transactionRequests` service earlier in the process. This request
1265
+ requires a query string to be included in the URI, with the following
1266
+ key-value pairs*:*
1267
+
1268
+
1269
+ - `authenticationType={Type}`, where `{Type}` value is a valid
1270
+ authentication type from the enumeration `AuthenticationType`.
1271
+
1272
+
1273
+ - `retriesLeft=={NrOfRetries}`, where `{NrOfRetries}` is the number of
1274
+ retries left before the financial transaction is rejected.
1275
+ `{NrOfRetries}` must be expressed in the form of the data type
1276
+ `Integer`. `retriesLeft=1` means that this is the last retry before the
1277
+ financial transaction is rejected.
1278
+
1279
+
1280
+ - `amount={Amount}`, where `{Amount}` is the transaction amount that
1281
+ will be withdrawn from the Payer’s account. `{Amount}` must be expressed
1282
+ in the form of the data type `Amount`.
1283
+
1284
+
1285
+ - `currency={Currency}`, where `{Currency}` is the transaction currency
1286
+ for the amount that will be withdrawn from the Payer’s account. The
1287
+ `{Currency}` value must be expressed in the form of the enumeration
1288
+ `CurrencyCode`.
1289
+
1290
+
1291
+ The following is an example URI containing all the required key-value
1292
+ pairs in the query string*:*
1293
+
1294
+
1295
+ `GET
1296
+ /authorization/3d492671-b7af-4f3f-88de-76169b1bdf88?authenticationType=OTP&retriesLeft=2&amount=102&currency=USD`
1297
+ summary: Perform authorization
1298
+ tags:
1299
+ - authorizations
1300
+ operationId: AuthorizationsByIDGet
1301
+ parameters:
1302
+ - $ref: "#/components/parameters/Accept"
1303
+ responses:
1304
+ "202":
1305
+ $ref: "#/components/responses/202"
1306
+ "400":
1307
+ $ref: "#/components/responses/400"
1308
+ "401":
1309
+ $ref: "#/components/responses/401"
1310
+ "403":
1311
+ $ref: "#/components/responses/403"
1312
+ "404":
1313
+ $ref: "#/components/responses/404"
1314
+ "405":
1315
+ $ref: "#/components/responses/405"
1316
+ "406":
1317
+ $ref: "#/components/responses/406"
1318
+ "501":
1319
+ $ref: "#/components/responses/501"
1320
+ "503":
1321
+ $ref: "#/components/responses/503"
1322
+ put:
1323
+ description: >-
1324
+ The callback `PUT /authorizations/{ID}` is used to inform the client of
1325
+ the result of a previously-requested authorization. The `{ID}` in the
1326
+ URI should contain the `{ID}` that was used in the `GET
1327
+ /authorizations/{ID}` request.
1328
+ summary: Return authorization result
1329
+ tags:
1330
+ - authorizations
1331
+ operationId: AuthorizationsByIDPut
1332
+ parameters:
1333
+ - $ref: "#/components/parameters/Content-Length"
1334
+ requestBody:
1335
+ description: Authorization result returned.
1336
+ required: true
1337
+ content:
1338
+ application/json:
1339
+ schema:
1340
+ $ref: "#/components/schemas/AuthorizationsIDPutResponse"
1341
+ responses:
1342
+ "200":
1343
+ $ref: "#/components/responses/200"
1344
+ "400":
1345
+ $ref: "#/components/responses/400"
1346
+ "401":
1347
+ $ref: "#/components/responses/401"
1348
+ "403":
1349
+ $ref: "#/components/responses/403"
1350
+ "404":
1351
+ $ref: "#/components/responses/404"
1352
+ "405":
1353
+ $ref: "#/components/responses/405"
1354
+ "406":
1355
+ $ref: "#/components/responses/406"
1356
+ "501":
1357
+ $ref: "#/components/responses/501"
1358
+ "503":
1359
+ $ref: "#/components/responses/503"
1360
+ /authorizations/{ID}/error:
1361
+ put:
1362
+ description: >-
1363
+ If the server is unable to find the transaction request, or another
1364
+ processing error occurs, the error callback `PUT
1365
+ /authorizations/{ID}/error` is used. The `{ID}` in the URI should
1366
+ contain the `{ID}` that was used in the `GET /authorizations/{ID}`.
1367
+ summary: Return authorization error
1368
+ tags:
1369
+ - authorizations
1370
+ operationId: AuthorizationsByIDAndError
1371
+ parameters:
1372
+ - $ref: "#/components/parameters/ID"
1373
+ - $ref: "#/components/parameters/Content-Length"
1374
+ - $ref: "#/components/parameters/Content-Type"
1375
+ - $ref: "#/components/parameters/Date"
1376
+ - $ref: "#/components/parameters/X-Forwarded-For"
1377
+ - $ref: "#/components/parameters/FSPIOP-Source"
1378
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1379
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1380
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1381
+ - $ref: "#/components/parameters/FSPIOP-URI"
1382
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1383
+ requestBody:
1384
+ description: Details of the error returned.
1385
+ required: true
1386
+ content:
1387
+ application/json:
1388
+ schema:
1389
+ $ref: "#/components/schemas/ErrorInformationObject"
1390
+ responses:
1391
+ "200":
1392
+ $ref: "#/components/responses/200"
1393
+ "400":
1394
+ $ref: "#/components/responses/400"
1395
+ "401":
1396
+ $ref: "#/components/responses/401"
1397
+ "403":
1398
+ $ref: "#/components/responses/403"
1399
+ "404":
1400
+ $ref: "#/components/responses/404"
1401
+ "405":
1402
+ $ref: "#/components/responses/405"
1403
+ "406":
1404
+ $ref: "#/components/responses/406"
1405
+ "501":
1406
+ $ref: "#/components/responses/501"
1407
+ "503":
1408
+ $ref: "#/components/responses/503"
1409
+ /transfers:
1410
+ post:
1411
+ description: >-
1412
+ The HTTP request `POST /transfers` is used to request the creation of a
1413
+ transfer for the next ledger, and a financial transaction for the Payee
1414
+ FSP.
1415
+ summary: Perform transfer
1416
+ tags:
1417
+ - transfers
1418
+ operationId: transfers
1419
+ parameters:
1420
+ - $ref: "#/components/parameters/Accept"
1421
+ - $ref: "#/components/parameters/Content-Length"
1422
+ - $ref: "#/components/parameters/Content-Type"
1423
+ - $ref: "#/components/parameters/Date"
1424
+ - $ref: "#/components/parameters/X-Forwarded-For"
1425
+ - $ref: "#/components/parameters/FSPIOP-Source"
1426
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1427
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1428
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1429
+ - $ref: "#/components/parameters/FSPIOP-URI"
1430
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1431
+ requestBody:
1432
+ description: Details of the transfer to be created.
1433
+ required: true
1434
+ content:
1435
+ application/json:
1436
+ schema:
1437
+ $ref: "#/components/schemas/TransfersPostRequest"
1438
+ responses:
1439
+ "202":
1440
+ $ref: "#/components/responses/202"
1441
+ "400":
1442
+ $ref: "#/components/responses/400"
1443
+ "401":
1444
+ $ref: "#/components/responses/401"
1445
+ "403":
1446
+ $ref: "#/components/responses/403"
1447
+ "404":
1448
+ $ref: "#/components/responses/404"
1449
+ "405":
1450
+ $ref: "#/components/responses/405"
1451
+ "406":
1452
+ $ref: "#/components/responses/406"
1453
+ "501":
1454
+ $ref: "#/components/responses/501"
1455
+ "503":
1456
+ $ref: "#/components/responses/503"
1457
+ /transfers/{ID}:
1458
+ parameters:
1459
+ - $ref: "#/components/parameters/ID"
1460
+ - $ref: "#/components/parameters/Content-Type"
1461
+ - $ref: "#/components/parameters/Date"
1462
+ - $ref: "#/components/parameters/X-Forwarded-For"
1463
+ - $ref: "#/components/parameters/FSPIOP-Source"
1464
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1465
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1466
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1467
+ - $ref: "#/components/parameters/FSPIOP-URI"
1468
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1469
+ get:
1470
+ description: >-
1471
+ The HTTP request `GET /transfers/{ID}` is used to get information
1472
+ regarding a transfer created or requested earlier. The `{ID}` in the URI
1473
+ should contain the `transferId` that was used for the creation of the
1474
+ transfer.
1475
+ summary: Retrieve transfer information
1476
+ tags:
1477
+ - transfers
1478
+ operationId: TransfersByIDGet
1479
+ parameters:
1480
+ - $ref: "#/components/parameters/Accept"
1481
+ responses:
1482
+ "202":
1483
+ $ref: "#/components/responses/202"
1484
+ "400":
1485
+ $ref: "#/components/responses/400"
1486
+ "401":
1487
+ $ref: "#/components/responses/401"
1488
+ "403":
1489
+ $ref: "#/components/responses/403"
1490
+ "404":
1491
+ $ref: "#/components/responses/404"
1492
+ "405":
1493
+ $ref: "#/components/responses/405"
1494
+ "406":
1495
+ $ref: "#/components/responses/406"
1496
+ "501":
1497
+ $ref: "#/components/responses/501"
1498
+ "503":
1499
+ $ref: "#/components/responses/503"
1500
+ patch:
1501
+ description: >-
1502
+ The HTTP request PATCH /transfers/<ID> is used by a Switch to update the
1503
+ state of a previously reserved transfer, if the Payee FSP has requested
1504
+ a commit notification when the Switch has completed processing of the
1505
+ transfer. The <ID> in the URI should contain the transferId that was
1506
+ used for the creation of the transfer. Please note that this request
1507
+ does not generate a callback.
1508
+ summary: Return transfer information
1509
+ tags:
1510
+ - transfers
1511
+ operationId: TransfersByIDPatch
1512
+ parameters:
1513
+ - $ref: "#/components/parameters/Content-Length"
1514
+ requestBody:
1515
+ description: Transfer notification upon completion.
1516
+ required: true
1517
+ content:
1518
+ application/json:
1519
+ schema:
1520
+ $ref: "#/components/schemas/TransfersIDPatchResponse"
1521
+ responses:
1522
+ "200":
1523
+ $ref: "#/components/responses/200"
1524
+ "400":
1525
+ $ref: "#/components/responses/400"
1526
+ "401":
1527
+ $ref: "#/components/responses/401"
1528
+ "403":
1529
+ $ref: "#/components/responses/403"
1530
+ "404":
1531
+ $ref: "#/components/responses/404"
1532
+ "405":
1533
+ $ref: "#/components/responses/405"
1534
+ "406":
1535
+ $ref: "#/components/responses/406"
1536
+ "501":
1537
+ $ref: "#/components/responses/501"
1538
+ "503":
1539
+ $ref: "#/components/responses/503"
1540
+ put:
1541
+ description: >-
1542
+ The callback `PUT /transfers/{ID}` is used to inform the client of a
1543
+ requested or created transfer. The `{ID}` in the URI should contain the
1544
+ `transferId` that was used for the creation of the transfer, or the
1545
+ `{ID}` that was used in the `GET /transfers/{ID}` request.
1546
+ summary: Return transfer information
1547
+ tags:
1548
+ - transfers
1549
+ operationId: TransfersByIDPut
1550
+ parameters:
1551
+ - $ref: "#/components/parameters/Content-Length"
1552
+ requestBody:
1553
+ description: Transfer information returned.
1554
+ required: true
1555
+ content:
1556
+ application/json:
1557
+ schema:
1558
+ $ref: "#/components/schemas/TransfersIDPutResponse"
1559
+ responses:
1560
+ "200":
1561
+ $ref: "#/components/responses/200"
1562
+ "400":
1563
+ $ref: "#/components/responses/400"
1564
+ "401":
1565
+ $ref: "#/components/responses/401"
1566
+ "403":
1567
+ $ref: "#/components/responses/403"
1568
+ "404":
1569
+ $ref: "#/components/responses/404"
1570
+ "405":
1571
+ $ref: "#/components/responses/405"
1572
+ "406":
1573
+ $ref: "#/components/responses/406"
1574
+ "501":
1575
+ $ref: "#/components/responses/501"
1576
+ "503":
1577
+ $ref: "#/components/responses/503"
1578
+ /transfers/{ID}/error:
1579
+ put:
1580
+ description: >-
1581
+ If the server is unable to find or create a transfer, or another
1582
+ processing error occurs, the error callback `PUT /transfers/{ID}/error`
1583
+ is used. The `{ID}` in the URI should contain the `transferId` that was
1584
+ used for the creation of the transfer, or the `{ID}` that was used in
1585
+ the `GET /transfers/{ID}`.
1586
+ summary: Return transfer information error
1587
+ tags:
1588
+ - transfers
1589
+ operationId: TransfersByIDAndError
1590
+ parameters:
1591
+ - $ref: "#/components/parameters/ID"
1592
+ - $ref: "#/components/parameters/Content-Length"
1593
+ - $ref: "#/components/parameters/Content-Type"
1594
+ - $ref: "#/components/parameters/Date"
1595
+ - $ref: "#/components/parameters/X-Forwarded-For"
1596
+ - $ref: "#/components/parameters/FSPIOP-Source"
1597
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1598
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1599
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1600
+ - $ref: "#/components/parameters/FSPIOP-URI"
1601
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1602
+ requestBody:
1603
+ description: Details of the error returned.
1604
+ required: true
1605
+ content:
1606
+ application/json:
1607
+ schema:
1608
+ $ref: "#/components/schemas/ErrorInformationObject"
1609
+ responses:
1610
+ "200":
1611
+ $ref: "#/components/responses/200"
1612
+ "400":
1613
+ $ref: "#/components/responses/400"
1614
+ "401":
1615
+ $ref: "#/components/responses/401"
1616
+ "403":
1617
+ $ref: "#/components/responses/403"
1618
+ "404":
1619
+ $ref: "#/components/responses/404"
1620
+ "405":
1621
+ $ref: "#/components/responses/405"
1622
+ "406":
1623
+ $ref: "#/components/responses/406"
1624
+ "501":
1625
+ $ref: "#/components/responses/501"
1626
+ "503":
1627
+ $ref: "#/components/responses/503"
1628
+ /transactions/{ID}:
1629
+ parameters:
1630
+ - $ref: "#/components/parameters/ID"
1631
+ - $ref: "#/components/parameters/Content-Type"
1632
+ - $ref: "#/components/parameters/Date"
1633
+ - $ref: "#/components/parameters/X-Forwarded-For"
1634
+ - $ref: "#/components/parameters/FSPIOP-Source"
1635
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1636
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1637
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1638
+ - $ref: "#/components/parameters/FSPIOP-URI"
1639
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1640
+ get:
1641
+ description: >-
1642
+ The HTTP request `GET /transactions/{ID}` is used to get transaction
1643
+ information regarding a financial transaction created earlier. The
1644
+ `{ID}` in the URI should contain the `transactionId` that was used for
1645
+ the creation of the quote, as the transaction is created as part of
1646
+ another process (the transfer process).
1647
+ summary: Retrieve transaction information
1648
+ tags:
1649
+ - transactions
1650
+ operationId: TransactionsByID
1651
+ parameters:
1652
+ - $ref: "#/components/parameters/Accept"
1653
+ responses:
1654
+ "202":
1655
+ $ref: "#/components/responses/202"
1656
+ "400":
1657
+ $ref: "#/components/responses/400"
1658
+ "401":
1659
+ $ref: "#/components/responses/401"
1660
+ "403":
1661
+ $ref: "#/components/responses/403"
1662
+ "404":
1663
+ $ref: "#/components/responses/404"
1664
+ "405":
1665
+ $ref: "#/components/responses/405"
1666
+ "406":
1667
+ $ref: "#/components/responses/406"
1668
+ "501":
1669
+ $ref: "#/components/responses/501"
1670
+ "503":
1671
+ $ref: "#/components/responses/503"
1672
+ put:
1673
+ description: >-
1674
+ The callback `PUT /transactions/{ID}` is used to inform the client of a
1675
+ requested transaction. The `{ID}` in the URI should contain the `{ID}`
1676
+ that was used in the `GET /transactions/{ID}` request.
1677
+ summary: Return transaction information
1678
+ tags:
1679
+ - transactions
1680
+ operationId: TransactionsByID1
1681
+ parameters:
1682
+ - $ref: "#/components/parameters/Content-Length"
1683
+ requestBody:
1684
+ description: Transaction information returned.
1685
+ required: true
1686
+ content:
1687
+ application/json:
1688
+ schema:
1689
+ $ref: "#/components/schemas/TransactionsIDPutResponse"
1690
+ responses:
1691
+ "200":
1692
+ $ref: "#/components/responses/200"
1693
+ "400":
1694
+ $ref: "#/components/responses/400"
1695
+ "401":
1696
+ $ref: "#/components/responses/401"
1697
+ "403":
1698
+ $ref: "#/components/responses/403"
1699
+ "404":
1700
+ $ref: "#/components/responses/404"
1701
+ "405":
1702
+ $ref: "#/components/responses/405"
1703
+ "406":
1704
+ $ref: "#/components/responses/406"
1705
+ "501":
1706
+ $ref: "#/components/responses/501"
1707
+ "503":
1708
+ $ref: "#/components/responses/503"
1709
+ /transactions/{ID}/error:
1710
+ put:
1711
+ description: >-
1712
+ If the server is unable to find or create a transaction, or another
1713
+ processing error occurs, the error callback `PUT
1714
+ /transactions/{ID}/error` is used. The `{ID}` in the URI should contain
1715
+ the `{ID}` that was used in the `GET /transactions/{ID}` request.
1716
+ summary: Return transaction information error
1717
+ tags:
1718
+ - transactions
1719
+ operationId: TransactionsErrorByID
1720
+ parameters:
1721
+ - $ref: "#/components/parameters/ID"
1722
+ - $ref: "#/components/parameters/Content-Length"
1723
+ - $ref: "#/components/parameters/Content-Type"
1724
+ - $ref: "#/components/parameters/Date"
1725
+ - $ref: "#/components/parameters/X-Forwarded-For"
1726
+ - $ref: "#/components/parameters/FSPIOP-Source"
1727
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1728
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1729
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1730
+ - $ref: "#/components/parameters/FSPIOP-URI"
1731
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1732
+ requestBody:
1733
+ description: Details of the error returned.
1734
+ required: true
1735
+ content:
1736
+ application/json:
1737
+ schema:
1738
+ $ref: "#/components/schemas/ErrorInformationObject"
1739
+ responses:
1740
+ "200":
1741
+ $ref: "#/components/responses/200"
1742
+ "400":
1743
+ $ref: "#/components/responses/400"
1744
+ "401":
1745
+ $ref: "#/components/responses/401"
1746
+ "403":
1747
+ $ref: "#/components/responses/403"
1748
+ "404":
1749
+ $ref: "#/components/responses/404"
1750
+ "405":
1751
+ $ref: "#/components/responses/405"
1752
+ "406":
1753
+ $ref: "#/components/responses/406"
1754
+ "501":
1755
+ $ref: "#/components/responses/501"
1756
+ "503":
1757
+ $ref: "#/components/responses/503"
1758
+ /bulkQuotes:
1759
+ post:
1760
+ description: >-
1761
+ The HTTP request `POST /bulkQuotes` is used to request the creation of a
1762
+ bulk quote for the provided financial transactions in the server.
1763
+ summary: Calculate bulk quote
1764
+ tags:
1765
+ - bulkQuotes
1766
+ operationId: BulkQuotes
1767
+ parameters:
1768
+ - $ref: "#/components/parameters/Accept"
1769
+ - $ref: "#/components/parameters/Content-Length"
1770
+ - $ref: "#/components/parameters/Content-Type"
1771
+ - $ref: "#/components/parameters/Date"
1772
+ - $ref: "#/components/parameters/X-Forwarded-For"
1773
+ - $ref: "#/components/parameters/FSPIOP-Source"
1774
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1775
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1776
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1777
+ - $ref: "#/components/parameters/FSPIOP-URI"
1778
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1779
+ requestBody:
1780
+ description: Details of the bulk quote to be created.
1781
+ required: true
1782
+ content:
1783
+ application/json:
1784
+ schema:
1785
+ $ref: "#/components/schemas/BulkQuotesPostRequest"
1786
+ responses:
1787
+ "202":
1788
+ $ref: "#/components/responses/202"
1789
+ "400":
1790
+ $ref: "#/components/responses/400"
1791
+ "401":
1792
+ $ref: "#/components/responses/401"
1793
+ "403":
1794
+ $ref: "#/components/responses/403"
1795
+ "404":
1796
+ $ref: "#/components/responses/404"
1797
+ "405":
1798
+ $ref: "#/components/responses/405"
1799
+ "406":
1800
+ $ref: "#/components/responses/406"
1801
+ "501":
1802
+ $ref: "#/components/responses/501"
1803
+ "503":
1804
+ $ref: "#/components/responses/503"
1805
+ /bulkQuotes/{ID}:
1806
+ parameters:
1807
+ - $ref: "#/components/parameters/ID"
1808
+ - $ref: "#/components/parameters/Content-Type"
1809
+ - $ref: "#/components/parameters/Date"
1810
+ - $ref: "#/components/parameters/X-Forwarded-For"
1811
+ - $ref: "#/components/parameters/FSPIOP-Source"
1812
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1813
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1814
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1815
+ - $ref: "#/components/parameters/FSPIOP-URI"
1816
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1817
+ get:
1818
+ description: >-
1819
+ The HTTP request `GET /bulkQuotes/{ID}` is used to get information
1820
+ regarding a bulk quote created or requested earlier. The `{ID}` in the
1821
+ URI should contain the `bulkQuoteId` that was used for the creation of
1822
+ the bulk quote.
1823
+ summary: Retrieve bulk quote information
1824
+ tags:
1825
+ - bulkQuotes
1826
+ operationId: BulkQuotesByID
1827
+ parameters:
1828
+ - $ref: "#/components/parameters/Accept"
1829
+ responses:
1830
+ "202":
1831
+ $ref: "#/components/responses/202"
1832
+ "400":
1833
+ $ref: "#/components/responses/400"
1834
+ "401":
1835
+ $ref: "#/components/responses/401"
1836
+ "403":
1837
+ $ref: "#/components/responses/403"
1838
+ "404":
1839
+ $ref: "#/components/responses/404"
1840
+ "405":
1841
+ $ref: "#/components/responses/405"
1842
+ "406":
1843
+ $ref: "#/components/responses/406"
1844
+ "501":
1845
+ $ref: "#/components/responses/501"
1846
+ "503":
1847
+ $ref: "#/components/responses/503"
1848
+ put:
1849
+ description: >-
1850
+ The callback `PUT /bulkQuotes/{ID}` is used to inform the client of a
1851
+ requested or created bulk quote. The `{ID}` in the URI should contain
1852
+ the `bulkQuoteId` that was used for the creation of the bulk quote, or
1853
+ the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request.
1854
+ summary: Return bulk quote information
1855
+ tags:
1856
+ - bulkQuotes
1857
+ operationId: BulkQuotesByID1
1858
+ parameters:
1859
+ - $ref: "#/components/parameters/Content-Length"
1860
+ requestBody:
1861
+ description: Bulk quote information returned.
1862
+ required: true
1863
+ content:
1864
+ application/json:
1865
+ schema:
1866
+ $ref: "#/components/schemas/BulkQuotesIDPutResponse"
1867
+ responses:
1868
+ "200":
1869
+ $ref: "#/components/responses/200"
1870
+ "400":
1871
+ $ref: "#/components/responses/400"
1872
+ "401":
1873
+ $ref: "#/components/responses/401"
1874
+ "403":
1875
+ $ref: "#/components/responses/403"
1876
+ "404":
1877
+ $ref: "#/components/responses/404"
1878
+ "405":
1879
+ $ref: "#/components/responses/405"
1880
+ "406":
1881
+ $ref: "#/components/responses/406"
1882
+ "501":
1883
+ $ref: "#/components/responses/501"
1884
+ "503":
1885
+ $ref: "#/components/responses/503"
1886
+ /bulkQuotes/{ID}/error:
1887
+ put:
1888
+ description: >-
1889
+ If the server is unable to find or create a bulk quote, or another
1890
+ processing error occurs, the error callback `PUT /bulkQuotes/{ID}/error`
1891
+ is used. The `{ID}` in the URI should contain the `bulkQuoteId` that was
1892
+ used for the creation of the bulk quote, or the `{ID}` that was used in
1893
+ the `GET /bulkQuotes/{ID}` request.
1894
+ summary: Return bulk quote information error
1895
+ tags:
1896
+ - bulkQuotes
1897
+ operationId: BulkQuotesErrorByID
1898
+ parameters:
1899
+ - $ref: "#/components/parameters/ID"
1900
+ - $ref: "#/components/parameters/Content-Length"
1901
+ - $ref: "#/components/parameters/Content-Type"
1902
+ - $ref: "#/components/parameters/Date"
1903
+ - $ref: "#/components/parameters/X-Forwarded-For"
1904
+ - $ref: "#/components/parameters/FSPIOP-Source"
1905
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1906
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1907
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1908
+ - $ref: "#/components/parameters/FSPIOP-URI"
1909
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1910
+ requestBody:
1911
+ description: Details of the error returned.
1912
+ required: true
1913
+ content:
1914
+ application/json:
1915
+ schema:
1916
+ $ref: "#/components/schemas/ErrorInformationObject"
1917
+ responses:
1918
+ "200":
1919
+ $ref: "#/components/responses/200"
1920
+ "400":
1921
+ $ref: "#/components/responses/400"
1922
+ "401":
1923
+ $ref: "#/components/responses/401"
1924
+ "403":
1925
+ $ref: "#/components/responses/403"
1926
+ "404":
1927
+ $ref: "#/components/responses/404"
1928
+ "405":
1929
+ $ref: "#/components/responses/405"
1930
+ "406":
1931
+ $ref: "#/components/responses/406"
1932
+ "501":
1933
+ $ref: "#/components/responses/501"
1934
+ "503":
1935
+ $ref: "#/components/responses/503"
1936
+ /bulkTransfers:
1937
+ post:
1938
+ description: >-
1939
+ The HTTP request `POST /bulkTransfers` is used to request the creation
1940
+ of a bulk transfer in the server.
1941
+ summary: Perform bulk transfer
1942
+ tags:
1943
+ - bulkTransfers
1944
+ operationId: BulkTransfers
1945
+ parameters:
1946
+ - $ref: "#/components/parameters/Accept"
1947
+ - $ref: "#/components/parameters/Content-Length"
1948
+ - $ref: "#/components/parameters/Content-Type"
1949
+ - $ref: "#/components/parameters/Date"
1950
+ - $ref: "#/components/parameters/X-Forwarded-For"
1951
+ - $ref: "#/components/parameters/FSPIOP-Source"
1952
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1953
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1954
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1955
+ - $ref: "#/components/parameters/FSPIOP-URI"
1956
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1957
+ requestBody:
1958
+ description: Details of the bulk transfer to be created.
1959
+ required: true
1960
+ content:
1961
+ application/json:
1962
+ schema:
1963
+ $ref: "#/components/schemas/BulkTransfersPostRequest"
1964
+ responses:
1965
+ "202":
1966
+ $ref: "#/components/responses/202"
1967
+ "400":
1968
+ $ref: "#/components/responses/400"
1969
+ "401":
1970
+ $ref: "#/components/responses/401"
1971
+ "403":
1972
+ $ref: "#/components/responses/403"
1973
+ "404":
1974
+ $ref: "#/components/responses/404"
1975
+ "405":
1976
+ $ref: "#/components/responses/405"
1977
+ "406":
1978
+ $ref: "#/components/responses/406"
1979
+ "501":
1980
+ $ref: "#/components/responses/501"
1981
+ "503":
1982
+ $ref: "#/components/responses/503"
1983
+ /bulkTransfers/{ID}:
1984
+ parameters:
1985
+ - $ref: "#/components/parameters/ID"
1986
+ - $ref: "#/components/parameters/Content-Type"
1987
+ - $ref: "#/components/parameters/Date"
1988
+ - $ref: "#/components/parameters/X-Forwarded-For"
1989
+ - $ref: "#/components/parameters/FSPIOP-Source"
1990
+ - $ref: "#/components/parameters/FSPIOP-Destination"
1991
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
1992
+ - $ref: "#/components/parameters/FSPIOP-Signature"
1993
+ - $ref: "#/components/parameters/FSPIOP-URI"
1994
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
1995
+ get:
1996
+ description: >-
1997
+ The HTTP request `GET /bulkTransfers/{ID}` is used to get information
1998
+ regarding a bulk transfer created or requested earlier. The `{ID}` in
1999
+ the URI should contain the `bulkTransferId` that was used for the
2000
+ creation of the bulk transfer.
2001
+ summary: Retrieve bulk transfer information
2002
+ tags:
2003
+ - bulkTransfers
2004
+ operationId: BulkTransferByID
2005
+ parameters:
2006
+ - $ref: "#/components/parameters/Accept"
2007
+ responses:
2008
+ "202":
2009
+ $ref: "#/components/responses/202"
2010
+ "400":
2011
+ $ref: "#/components/responses/400"
2012
+ "401":
2013
+ $ref: "#/components/responses/401"
2014
+ "403":
2015
+ $ref: "#/components/responses/403"
2016
+ "404":
2017
+ $ref: "#/components/responses/404"
2018
+ "405":
2019
+ $ref: "#/components/responses/405"
2020
+ "406":
2021
+ $ref: "#/components/responses/406"
2022
+ "501":
2023
+ $ref: "#/components/responses/501"
2024
+ "503":
2025
+ $ref: "#/components/responses/503"
2026
+ put:
2027
+ description: >-
2028
+ The callback `PUT /bulkTransfers/{ID}` is used to inform the client of a
2029
+ requested or created bulk transfer. The `{ID}` in the URI should contain
2030
+ the `bulkTransferId` that was used for the creation of the bulk transfer
2031
+ (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET
2032
+ /bulkTransfers/{ID}` request.
2033
+ summary: Return bulk transfer information
2034
+ tags:
2035
+ - bulkTransfers
2036
+ operationId: BulkTransfersByIDPut
2037
+ parameters:
2038
+ - $ref: "#/components/parameters/Content-Length"
2039
+ requestBody:
2040
+ description: Bulk transfer information returned.
2041
+ required: true
2042
+ content:
2043
+ application/json:
2044
+ schema:
2045
+ $ref: "#/components/schemas/BulkTransfersIDPutResponse"
2046
+ responses:
2047
+ "200":
2048
+ $ref: "#/components/responses/200"
2049
+ "400":
2050
+ $ref: "#/components/responses/400"
2051
+ "401":
2052
+ $ref: "#/components/responses/401"
2053
+ "403":
2054
+ $ref: "#/components/responses/403"
2055
+ "404":
2056
+ $ref: "#/components/responses/404"
2057
+ "405":
2058
+ $ref: "#/components/responses/405"
2059
+ "406":
2060
+ $ref: "#/components/responses/406"
2061
+ "501":
2062
+ $ref: "#/components/responses/501"
2063
+ "503":
2064
+ $ref: "#/components/responses/503"
2065
+ /bulkTransfers/{ID}/error:
2066
+ put:
2067
+ description: >-
2068
+ If the server is unable to find or create a bulk transfer, or another
2069
+ processing error occurs, the error callback `PUT
2070
+ /bulkTransfers/{ID}/error` is used. The `{ID}` in the URI should contain
2071
+ the `bulkTransferId` that was used for the creation of the bulk transfer
2072
+ (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET
2073
+ /bulkTransfers/{ID}` request.
2074
+ summary: Return bulk transfer information error
2075
+ tags:
2076
+ - bulkTransfers
2077
+ operationId: BulkTransfersErrorByID
2078
+ parameters:
2079
+ - $ref: "#/components/parameters/ID"
2080
+ - $ref: "#/components/parameters/Content-Length"
2081
+ - $ref: "#/components/parameters/Content-Type"
2082
+ - $ref: "#/components/parameters/Date"
2083
+ - $ref: "#/components/parameters/X-Forwarded-For"
2084
+ - $ref: "#/components/parameters/FSPIOP-Source"
2085
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2086
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2087
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2088
+ - $ref: "#/components/parameters/FSPIOP-URI"
2089
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2090
+ requestBody:
2091
+ description: Details of the error returned.
2092
+ required: true
2093
+ content:
2094
+ application/json:
2095
+ schema:
2096
+ $ref: "#/components/schemas/ErrorInformationObject"
2097
+ responses:
2098
+ "200":
2099
+ $ref: "#/components/responses/200"
2100
+ "400":
2101
+ $ref: "#/components/responses/400"
2102
+ "401":
2103
+ $ref: "#/components/responses/401"
2104
+ "403":
2105
+ $ref: "#/components/responses/403"
2106
+ "404":
2107
+ $ref: "#/components/responses/404"
2108
+ "405":
2109
+ $ref: "#/components/responses/405"
2110
+ "406":
2111
+ $ref: "#/components/responses/406"
2112
+ "501":
2113
+ $ref: "#/components/responses/501"
2114
+ "503":
2115
+ $ref: "#/components/responses/503"
2116
+ /fxQuotes:
2117
+ post:
2118
+ description: >-
2119
+ The HTTP request `POST /fxQuotes` is used to ask an FXP to provide a
2120
+ quotation for a currency conversion.
2121
+ summary: Calculate FX quote
2122
+ tags:
2123
+ - fxQuotes
2124
+ operationId: FxQuotesPost
2125
+ parameters:
2126
+ - $ref: "#/components/parameters/Accept"
2127
+ - $ref: "#/components/parameters/Content-Length"
2128
+ - $ref: "#/components/parameters/Content-Type"
2129
+ - $ref: "#/components/parameters/Date"
2130
+ - $ref: "#/components/parameters/X-Forwarded-For"
2131
+ - $ref: "#/components/parameters/FSPIOP-Source"
2132
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2133
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2134
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2135
+ - $ref: "#/components/parameters/FSPIOP-URI"
2136
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2137
+ requestBody:
2138
+ description: Details of the FX quote to be created.
2139
+ required: true
2140
+ content:
2141
+ application/json:
2142
+ schema:
2143
+ $ref: "#/components/schemas/FxQuotesPostRequest"
2144
+ responses:
2145
+ "202":
2146
+ $ref: "#/components/responses/202"
2147
+ "400":
2148
+ $ref: "#/components/responses/400"
2149
+ "401":
2150
+ $ref: "#/components/responses/401"
2151
+ "403":
2152
+ $ref: "#/components/responses/403"
2153
+ "404":
2154
+ $ref: "#/components/responses/404"
2155
+ "405":
2156
+ $ref: "#/components/responses/405"
2157
+ "406":
2158
+ $ref: "#/components/responses/406"
2159
+ "501":
2160
+ $ref: "#/components/responses/501"
2161
+ "503":
2162
+ $ref: "#/components/responses/503"
2163
+ /fxQuotes/{ID}:
2164
+ parameters:
2165
+ - $ref: "#/components/parameters/ID"
2166
+ - $ref: "#/components/parameters/Content-Type"
2167
+ - $ref: "#/components/parameters/Date"
2168
+ - $ref: "#/components/parameters/X-Forwarded-For"
2169
+ - $ref: "#/components/parameters/FSPIOP-Source"
2170
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2171
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2172
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2173
+ - $ref: "#/components/parameters/FSPIOP-URI"
2174
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2175
+ get:
2176
+ description: >-
2177
+ The HTTP request `GET /fxQuotes/{ID}` is used to request information
2178
+ regarding a request for quotation for a currency conversion which the
2179
+ sender has previously issued. The `{ID}` in the URI should contain the
2180
+ `conversionRequestId` that was used for the creation of the quote.
2181
+ summary: Retrieve FX quote information
2182
+ tags:
2183
+ - fxQuotes
2184
+ operationId: FxQuotesByIDGet
2185
+ parameters:
2186
+ - $ref: "#/components/parameters/Accept"
2187
+ responses:
2188
+ "202":
2189
+ $ref: "#/components/responses/202"
2190
+ "400":
2191
+ $ref: "#/components/responses/400"
2192
+ "401":
2193
+ $ref: "#/components/responses/401"
2194
+ "403":
2195
+ $ref: "#/components/responses/403"
2196
+ "404":
2197
+ $ref: "#/components/responses/404"
2198
+ "405":
2199
+ $ref: "#/components/responses/405"
2200
+ "406":
2201
+ $ref: "#/components/responses/406"
2202
+ "501":
2203
+ $ref: "#/components/responses/501"
2204
+ "503":
2205
+ $ref: "#/components/responses/503"
2206
+ put:
2207
+ description: >-
2208
+ The callback `PUT /fxQuotes/{ID}` is used to inform the requester about
2209
+ the outcome of a request for quotation for a currency conversion. The
2210
+ `{ID}` in the URI should contain the `conversionRequestId` that was used
2211
+ for the creation of the FX quote, or the `{ID}` that was used in the
2212
+ `GET /fxQuotes/{ID}` request.
2213
+ summary: Return FX quote information
2214
+ tags:
2215
+ - fxQuotes
2216
+ operationId: FxQuotesByIdPut
2217
+ parameters:
2218
+ - $ref: "#/components/parameters/Content-Length"
2219
+ requestBody:
2220
+ description: FX Quote information returned.
2221
+ required: true
2222
+ content:
2223
+ application/json:
2224
+ schema:
2225
+ $ref: "#/components/schemas/FxQuotesIDPutResponse"
2226
+ responses:
2227
+ "200":
2228
+ $ref: "#/components/responses/200"
2229
+ "400":
2230
+ $ref: "#/components/responses/400"
2231
+ "401":
2232
+ $ref: "#/components/responses/401"
2233
+ "403":
2234
+ $ref: "#/components/responses/403"
2235
+ "404":
2236
+ $ref: "#/components/responses/404"
2237
+ "405":
2238
+ $ref: "#/components/responses/405"
2239
+ "406":
2240
+ $ref: "#/components/responses/406"
2241
+ "501":
2242
+ $ref: "#/components/responses/501"
2243
+ "503":
2244
+ $ref: "#/components/responses/503"
2245
+ /fxQuotes/{ID}/error:
2246
+ put:
2247
+ description: >-
2248
+ If the FXP is unable to find or create a FX quote, or some other
2249
+ processing error occurs, the error callback `PUT /fxQuotes/{ID}/error`
2250
+ is used. The `{ID}` in the URI should contain the `conversionRequestId`
2251
+ that was used for the creation of the FX quote, or the `{ID}` that was
2252
+ used in the `GET /fxQuotes/{ID}` request.
2253
+ summary: Return FX quote information error
2254
+ tags:
2255
+ - fxQuotes
2256
+ operationId: FxQuotesByIDAndErrorPut
2257
+ parameters:
2258
+ - $ref: "#/components/parameters/ID"
2259
+ - $ref: "#/components/parameters/Content-Length"
2260
+ - $ref: "#/components/parameters/Content-Type"
2261
+ - $ref: "#/components/parameters/Date"
2262
+ - $ref: "#/components/parameters/X-Forwarded-For"
2263
+ - $ref: "#/components/parameters/FSPIOP-Source"
2264
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2265
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2266
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2267
+ - $ref: "#/components/parameters/FSPIOP-URI"
2268
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2269
+ requestBody:
2270
+ description: Details of the error returned.
2271
+ required: true
2272
+ content:
2273
+ application/json:
2274
+ schema:
2275
+ $ref: "#/components/schemas/ErrorInformationObject"
2276
+ responses:
2277
+ "200":
2278
+ $ref: "#/components/responses/200"
2279
+ "400":
2280
+ $ref: "#/components/responses/400"
2281
+ "401":
2282
+ $ref: "#/components/responses/401"
2283
+ "403":
2284
+ $ref: "#/components/responses/403"
2285
+ "404":
2286
+ $ref: "#/components/responses/404"
2287
+ "405":
2288
+ $ref: "#/components/responses/405"
2289
+ "406":
2290
+ $ref: "#/components/responses/406"
2291
+ "501":
2292
+ $ref: "#/components/responses/501"
2293
+ "503":
2294
+ $ref: "#/components/responses/503"
2295
+ /fxTransfers:
2296
+ post:
2297
+ description: >-
2298
+ The HTTP request `POST /fxTransfers` is used to ask an FXP to confirm
2299
+ the execution of an agreed currency conversion.
2300
+ summary: Perform FX transfer
2301
+ tags:
2302
+ - fxTransfers
2303
+ operationId: FxTransfersPost
2304
+ parameters:
2305
+ - $ref: "#/components/parameters/Accept"
2306
+ - $ref: "#/components/parameters/Content-Length"
2307
+ - $ref: "#/components/parameters/Content-Type"
2308
+ - $ref: "#/components/parameters/Date"
2309
+ - $ref: "#/components/parameters/X-Forwarded-For"
2310
+ - $ref: "#/components/parameters/FSPIOP-Source"
2311
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2312
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2313
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2314
+ - $ref: "#/components/parameters/FSPIOP-URI"
2315
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2316
+ requestBody:
2317
+ description: Details of the FX transfer to be created.
2318
+ required: true
2319
+ content:
2320
+ application/json:
2321
+ schema:
2322
+ $ref: "#/components/schemas/FxTransfersPostRequest"
2323
+ responses:
2324
+ "202":
2325
+ $ref: "#/components/responses/202"
2326
+ "400":
2327
+ $ref: "#/components/responses/400"
2328
+ "401":
2329
+ $ref: "#/components/responses/401"
2330
+ "403":
2331
+ $ref: "#/components/responses/403"
2332
+ "404":
2333
+ $ref: "#/components/responses/404"
2334
+ "405":
2335
+ $ref: "#/components/responses/405"
2336
+ "406":
2337
+ $ref: "#/components/responses/406"
2338
+ "501":
2339
+ $ref: "#/components/responses/501"
2340
+ "503":
2341
+ $ref: "#/components/responses/503"
2342
+ /fxTransfers/{ID}:
2343
+ parameters:
2344
+ - $ref: "#/components/parameters/ID"
2345
+ - $ref: "#/components/parameters/Content-Type"
2346
+ - $ref: "#/components/parameters/Date"
2347
+ - $ref: "#/components/parameters/X-Forwarded-For"
2348
+ - $ref: "#/components/parameters/FSPIOP-Source"
2349
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2350
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2351
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2352
+ - $ref: "#/components/parameters/FSPIOP-URI"
2353
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2354
+ get:
2355
+ description: >-
2356
+ The HTTP request `GET /fxTransfers/{ID}` s used to request information
2357
+ regarding a request for confirmation of a currency conversion which the
2358
+ sender has previously issued. The `{ID}` in the URI should contain the
2359
+ `commitRequestId` that was used for the creation of the FX transfer.
2360
+ summary: Retrieve FX transfer information
2361
+ tags:
2362
+ - fxTransfers
2363
+ operationId: FxTransfersByIDGet
2364
+ parameters:
2365
+ - $ref: "#/components/parameters/Accept"
2366
+ responses:
2367
+ "202":
2368
+ $ref: "#/components/responses/202"
2369
+ "400":
2370
+ $ref: "#/components/responses/400"
2371
+ "401":
2372
+ $ref: "#/components/responses/401"
2373
+ "403":
2374
+ $ref: "#/components/responses/403"
2375
+ "404":
2376
+ $ref: "#/components/responses/404"
2377
+ "405":
2378
+ $ref: "#/components/responses/405"
2379
+ "406":
2380
+ $ref: "#/components/responses/406"
2381
+ "501":
2382
+ $ref: "#/components/responses/501"
2383
+ "503":
2384
+ $ref: "#/components/responses/503"
2385
+ patch:
2386
+ description: >-
2387
+ The HTTP request PATCH /fxTransfers/<ID> is used to inform the requester
2388
+ about the final determination by the switch of the transfer a request
2389
+ for execution of a currency conversion. The <ID> in the URI should
2390
+ contain the commitRequestId that was used for the creation of the FX
2391
+ transfer. Please note that this request does not generate a callback.
2392
+ summary: Return FX transfer information
2393
+ tags:
2394
+ - fxTransfers
2395
+ operationId: FxTransfersByIDPatch
2396
+ parameters:
2397
+ - $ref: "#/components/parameters/Content-Length"
2398
+ requestBody:
2399
+ description: Transfer notification upon completion.
2400
+ required: true
2401
+ content:
2402
+ application/json:
2403
+ schema:
2404
+ $ref: "#/components/schemas/FxTransfersIDPatchResponse"
2405
+ responses:
2406
+ "200":
2407
+ $ref: "#/components/responses/200"
2408
+ "400":
2409
+ $ref: "#/components/responses/400"
2410
+ "401":
2411
+ $ref: "#/components/responses/401"
2412
+ "403":
2413
+ $ref: "#/components/responses/403"
2414
+ "404":
2415
+ $ref: "#/components/responses/404"
2416
+ "405":
2417
+ $ref: "#/components/responses/405"
2418
+ "406":
2419
+ $ref: "#/components/responses/406"
2420
+ "501":
2421
+ $ref: "#/components/responses/501"
2422
+ "503":
2423
+ $ref: "#/components/responses/503"
2424
+ put:
2425
+ description: >-
2426
+ The callback `PUT /fxTransfers/{ID}` is used to inform the requester
2427
+ about the outcome of a request for execution of a currency conversion.
2428
+ The `{ID}` in the URI should contain the `commitRequestId` that was used
2429
+ for the creation of the FX transfer, or the `{ID}` that was used in the
2430
+ `GET /fxTransfers/{ID}` request.
2431
+ summary: Return FX transfer information
2432
+ tags:
2433
+ - fxTransfers
2434
+ operationId: FxTransfersByIDPut
2435
+ parameters:
2436
+ - $ref: "#/components/parameters/Content-Length"
2437
+ requestBody:
2438
+ description: Transfer information returned.
2439
+ required: true
2440
+ content:
2441
+ application/json:
2442
+ schema:
2443
+ $ref: "#/components/schemas/FxTransfersIDPutResponse"
2444
+ responses:
2445
+ "200":
2446
+ $ref: "#/components/responses/200"
2447
+ "400":
2448
+ $ref: "#/components/responses/400"
2449
+ "401":
2450
+ $ref: "#/components/responses/401"
2451
+ "403":
2452
+ $ref: "#/components/responses/403"
2453
+ "404":
2454
+ $ref: "#/components/responses/404"
2455
+ "405":
2456
+ $ref: "#/components/responses/405"
2457
+ "406":
2458
+ $ref: "#/components/responses/406"
2459
+ "501":
2460
+ $ref: "#/components/responses/501"
2461
+ "503":
2462
+ $ref: "#/components/responses/503"
2463
+ /fxTransfers/{ID}/error:
2464
+ put:
2465
+ description: >-
2466
+ If the switch or FXP is unable to find or create a FX transfer, or
2467
+ another processing error occurs, the error callback `PUT
2468
+ /fxTransfers/{ID}/error` is used. The `{ID}` in the URI should contain
2469
+ the `commitRequestId` that was used for the creation of the FX transfer,
2470
+ or the `{ID}` that was used in the `GET /fxTransfers/{ID}`.
2471
+ summary: Return FX transfer information error
2472
+ tags:
2473
+ - fxTransfers
2474
+ operationId: FxTransfersByIDAndErrorPut
2475
+ parameters:
2476
+ - $ref: "#/components/parameters/ID"
2477
+ - $ref: "#/components/parameters/Content-Length"
2478
+ - $ref: "#/components/parameters/Content-Type"
2479
+ - $ref: "#/components/parameters/Date"
2480
+ - $ref: "#/components/parameters/X-Forwarded-For"
2481
+ - $ref: "#/components/parameters/FSPIOP-Source"
2482
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2483
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2484
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2485
+ - $ref: "#/components/parameters/FSPIOP-URI"
2486
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2487
+ requestBody:
2488
+ description: Details of the error returned.
2489
+ required: true
2490
+ content:
2491
+ application/json:
2492
+ schema:
2493
+ $ref: "#/components/schemas/ErrorInformationObject"
2494
+ responses:
2495
+ "200":
2496
+ $ref: "#/components/responses/200"
2497
+ "400":
2498
+ $ref: "#/components/responses/400"
2499
+ "401":
2500
+ $ref: "#/components/responses/401"
2501
+ "403":
2502
+ $ref: "#/components/responses/403"
2503
+ "404":
2504
+ $ref: "#/components/responses/404"
2505
+ "405":
2506
+ $ref: "#/components/responses/405"
2507
+ "406":
2508
+ $ref: "#/components/responses/406"
2509
+ "501":
2510
+ $ref: "#/components/responses/501"
2511
+ "503":
2512
+ $ref: "#/components/responses/503"
2513
+ /services/FXP:
2514
+ parameters:
2515
+ - $ref: "#/components/parameters/Content-Type"
2516
+ - $ref: "#/components/parameters/Date"
2517
+ - $ref: "#/components/parameters/X-Forwarded-For"
2518
+ - $ref: "#/components/parameters/FSPIOP-Source"
2519
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2520
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2521
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2522
+ - $ref: "#/components/parameters/FSPIOP-URI"
2523
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2524
+ get:
2525
+ description: >-
2526
+ The HTTP request `GET /services/FXP` is used to request information
2527
+ about the participants in a scheme who offer currency conversion
2528
+ services.
2529
+ summary: Obtain a list of the DFSPs in the scheme who provide FXP service
2530
+ tags:
2531
+ - servicesFXP
2532
+ operationId: ServicesFXPGet
2533
+ parameters:
2534
+ - $ref: "#/components/parameters/Accept"
2535
+ responses:
2536
+ "202":
2537
+ $ref: "#/components/responses/202"
2538
+ "400":
2539
+ $ref: "#/components/responses/400"
2540
+ "401":
2541
+ $ref: "#/components/responses/401"
2542
+ "403":
2543
+ $ref: "#/components/responses/403"
2544
+ "404":
2545
+ $ref: "#/components/responses/404"
2546
+ "405":
2547
+ $ref: "#/components/responses/405"
2548
+ "406":
2549
+ $ref: "#/components/responses/406"
2550
+ "501":
2551
+ $ref: "#/components/responses/501"
2552
+ "503":
2553
+ $ref: "#/components/responses/503"
2554
+ put:
2555
+ description: >-
2556
+ The callback `PUT /services/FXP` is used to inform the requester about
2557
+ participants in a scheme who offer currency conversion services. If no
2558
+ participants offer these services, the return object will be blank.
2559
+ tags:
2560
+ - servicesFXP
2561
+ operationId: ServicesFXPPut
2562
+ parameters:
2563
+ - $ref: "#/components/parameters/Content-Length"
2564
+ requestBody:
2565
+ description: The list of participant(s) who offer currency conversion services.
2566
+ required: true
2567
+ content:
2568
+ application/json:
2569
+ schema:
2570
+ $ref: "#/components/schemas/ServicesFXPPutResponse"
2571
+ responses:
2572
+ "200":
2573
+ $ref: "#/components/responses/200"
2574
+ "400":
2575
+ $ref: "#/components/responses/400"
2576
+ "401":
2577
+ $ref: "#/components/responses/401"
2578
+ "403":
2579
+ $ref: "#/components/responses/403"
2580
+ "404":
2581
+ $ref: "#/components/responses/404"
2582
+ "405":
2583
+ $ref: "#/components/responses/405"
2584
+ "406":
2585
+ $ref: "#/components/responses/406"
2586
+ "501":
2587
+ $ref: "#/components/responses/501"
2588
+ "503":
2589
+ $ref: "#/components/responses/503"
2590
+ /services/FXP/{SourceCurrency}/{TargetCurrency}:
2591
+ parameters:
2592
+ - $ref: "#/components/parameters/SourceCurrency"
2593
+ - $ref: "#/components/parameters/TargetCurrency"
2594
+ - $ref: "#/components/parameters/Content-Type"
2595
+ - $ref: "#/components/parameters/Date"
2596
+ - $ref: "#/components/parameters/X-Forwarded-For"
2597
+ - $ref: "#/components/parameters/FSPIOP-Source"
2598
+ - $ref: "#/components/parameters/FSPIOP-Destination"
2599
+ - $ref: "#/components/parameters/FSPIOP-Encryption"
2600
+ - $ref: "#/components/parameters/FSPIOP-Signature"
2601
+ - $ref: "#/components/parameters/FSPIOP-URI"
2602
+ - $ref: "#/components/parameters/FSPIOP-HTTP-Method"
2603
+ get:
2604
+ description: >-
2605
+ The HTTP request `GET /services/FXP/{SourceCurrency}/{TargetCurrency}`
2606
+ is used to request information about the participants in a scheme who
2607
+ offer currency conversion services in a particular currency corridor.
2608
+ The required corridor is specified by giving the ISO 4217 currency code
2609
+ for the SourceCurrency and the TargetCurrency.
2610
+ summary: Obtain a list of the DFSPs in the scheme who provide FXP service
2611
+ tags:
2612
+ - servicesFXP
2613
+ operationId: ServicesFXPSourceCurrencyTargetCurrencyGet
2614
+ parameters:
2615
+ - $ref: "#/components/parameters/Accept"
2616
+ responses:
2617
+ "202":
2618
+ $ref: "#/components/responses/202"
2619
+ "400":
2620
+ $ref: "#/components/responses/400"
2621
+ "401":
2622
+ $ref: "#/components/responses/401"
2623
+ "403":
2624
+ $ref: "#/components/responses/403"
2625
+ "404":
2626
+ $ref: "#/components/responses/404"
2627
+ "405":
2628
+ $ref: "#/components/responses/405"
2629
+ "406":
2630
+ $ref: "#/components/responses/406"
2631
+ "501":
2632
+ $ref: "#/components/responses/501"
2633
+ "503":
2634
+ $ref: "#/components/responses/503"
2635
+ put:
2636
+ description: >-
2637
+ The callback `PUT /services/FXP/{SourceCurrency}/{TargetCurrency}` is
2638
+ used to inform the requester about participants in a scheme who offer
2639
+ currency conversion services. If no participants offer these services,
2640
+ the return object will be blank. The required corridor is specified by
2641
+ giving the ISO 4217 currency code for the SourceCurrency and the
2642
+ TargetCurrency.
2643
+ tags:
2644
+ - servicesFXP
2645
+ operationId: ServicesFXPSourceCurrencyTargetCurrencyPut
2646
+ parameters:
2647
+ - $ref: "#/components/parameters/Content-Length"
2648
+ requestBody:
2649
+ description: The list of participant(s) who offer currency conversion services.
2650
+ required: true
2651
+ content:
2652
+ application/json:
2653
+ schema:
2654
+ $ref: >-
2655
+ #/components/schemas/ServicesFXPSourceCurrencyTargetCurrencyPutResponse
2656
+ responses:
2657
+ "200":
2658
+ $ref: "#/components/responses/200"
2659
+ "400":
2660
+ $ref: "#/components/responses/400"
2661
+ "401":
2662
+ $ref: "#/components/responses/401"
2663
+ "403":
2664
+ $ref: "#/components/responses/403"
2665
+ "404":
2666
+ $ref: "#/components/responses/404"
2667
+ "405":
2668
+ $ref: "#/components/responses/405"
2669
+ "406":
2670
+ $ref: "#/components/responses/406"
2671
+ "501":
2672
+ $ref: "#/components/responses/501"
2673
+ "503":
2674
+ $ref: "#/components/responses/503"
2675
+ components:
2676
+ schemas:
2677
+ Amount:
2678
+ title: Amount
2679
+ type: string
2680
+ pattern: ^([0]|([1-9][0-9]{0,17}))([.][0-9]{0,3}[1-9])?$
2681
+ description: >-
2682
+ The API data type Amount is a JSON String in a canonical format that is
2683
+ restricted by a regular expression for interoperability reasons. This
2684
+ pattern does not allow any trailing zeroes at all, but allows an amount
2685
+ without a minor currency unit. It also only allows four digits in the
2686
+ minor currency unit; a negative value is not allowed. Using more than 18
2687
+ digits in the major currency unit is not allowed.
2688
+ example: "123.45"
2689
+ AmountType:
2690
+ title: AmountType
2691
+ type: string
2692
+ enum:
2693
+ - SEND
2694
+ - RECEIVE
2695
+ description: >-
2696
+ Below are the allowed values for the enumeration AmountType.
2697
+
2698
+ - SEND - Amount the Payer would like to send, that is, the amount that
2699
+ should be withdrawn from the Payer account including any fees.
2700
+
2701
+ - RECEIVE - Amount the Payer would like the Payee to receive, that is,
2702
+ the amount that should be sent to the receiver exclusive of any fees.
2703
+ example: RECEIVE
2704
+ AuthenticationInfo:
2705
+ title: AuthenticationInfo
2706
+ type: object
2707
+ description: Data model for the complex type AuthenticationInfo.
2708
+ properties:
2709
+ authentication:
2710
+ $ref: "#/components/schemas/AuthenticationType"
2711
+ authenticationValue:
2712
+ $ref: "#/components/schemas/AuthenticationValue"
2713
+ required:
2714
+ - authentication
2715
+ - authenticationValue
2716
+ AuthenticationType:
2717
+ title: AuthenticationType
2718
+ type: string
2719
+ enum:
2720
+ - OTP
2721
+ - QRCODE
2722
+ - U2F
2723
+ description: |-
2724
+ Below are the allowed values for the enumeration AuthenticationType.
2725
+ - OTP - One-time password generated by the Payer FSP.
2726
+ - QRCODE - QR code used as One Time Password.
2727
+ - U2F - U2F is a new addition isolated to Thirdparty stream.
2728
+ example: OTP
2729
+ AuthenticationValue:
2730
+ title: AuthenticationValue
2731
+ anyOf:
2732
+ - $ref: "#/components/schemas/OtpValue"
2733
+ - $ref: "#/components/schemas/QRCODE"
2734
+ - $ref: "#/components/schemas/U2FPinValue"
2735
+ pattern: ^\d{3,10}$|^\S{1,64}$
2736
+ description: >-
2737
+ Contains the authentication value. The format depends on the
2738
+ authentication type used in the AuthenticationInfo complex type.
2739
+ AuthorizationResponse:
2740
+ title: AuthorizationResponse
2741
+ type: string
2742
+ enum:
2743
+ - ENTERED
2744
+ - REJECTED
2745
+ - RESEND
2746
+ description: |-
2747
+ Below are the allowed values for the enumeration.
2748
+ - ENTERED - Consumer entered the authentication value.
2749
+ - REJECTED - Consumer rejected the transaction.
2750
+ - RESEND - Consumer requested to resend the authentication value.
2751
+ example: ENTERED
2752
+ AuthorizationsIDPutResponse:
2753
+ title: AuthorizationsIDPutResponse
2754
+ type: object
2755
+ description: The object sent in the PUT /authorizations/{ID} callback.
2756
+ properties:
2757
+ authenticationInfo:
2758
+ $ref: "#/components/schemas/AuthenticationInfo"
2759
+ responseType:
2760
+ $ref: "#/components/schemas/AuthorizationResponse"
2761
+ required:
2762
+ - responseType
2763
+ BalanceOfPayments:
2764
+ title: BalanceOfPayments
2765
+ type: string
2766
+ pattern: ^[1-9]\d{2}$
2767
+ description: >-
2768
+ (BopCode) The API data type
2769
+ [BopCode](https://www.imf.org/external/np/sta/bopcode/) is a JSON String
2770
+ of 3 characters, consisting of digits only. Negative numbers are not
2771
+ allowed. A leading zero is not allowed.
2772
+ example: "123"
2773
+ BinaryString:
2774
+ type: string
2775
+ pattern: ^[A-Za-z0-9-_]+[=]{0,2}$
2776
+ description: >-
2777
+ The API data type BinaryString is a JSON String. The string is a
2778
+ base64url encoding of a string of raw bytes, where padding (character
2779
+ ‘=’) is added at the end of the data if needed to ensure that the string
2780
+ is a multiple of 4 characters. The length restriction indicates the
2781
+ allowed number of characters.
2782
+ BinaryString32:
2783
+ type: string
2784
+ pattern: ^[A-Za-z0-9-_]{43}$
2785
+ description: >-
2786
+ The API data type BinaryString32 is a fixed size version of the API data
2787
+ type BinaryString, where the raw underlying data is always of 32 bytes.
2788
+ The data type BinaryString32 should not use a padding character as the
2789
+ size of the underlying data is fixed.
2790
+ BulkQuotesIDPutResponse:
2791
+ title: BulkQuotesIDPutResponse
2792
+ type: object
2793
+ description: The object sent in the PUT /bulkQuotes/{ID} callback.
2794
+ properties:
2795
+ individualQuoteResults:
2796
+ type: array
2797
+ maxItems: 1000
2798
+ items:
2799
+ $ref: "#/components/schemas/IndividualQuoteResult"
2800
+ description: >-
2801
+ Fees for each individual transaction, if any of them are charged per
2802
+ transaction.
2803
+ expiration:
2804
+ $ref: "#/components/schemas/DateTime"
2805
+ extensionList:
2806
+ $ref: "#/components/schemas/ExtensionList"
2807
+ required:
2808
+ - expiration
2809
+ BulkQuotesPostRequest:
2810
+ title: BulkQuotesPostRequest
2811
+ type: object
2812
+ description: The object sent in the POST /bulkQuotes request.
2813
+ properties:
2814
+ bulkQuoteId:
2815
+ $ref: "#/components/schemas/CorrelationId"
2816
+ payer:
2817
+ $ref: "#/components/schemas/Party"
2818
+ geoCode:
2819
+ $ref: "#/components/schemas/GeoCode"
2820
+ expiration:
2821
+ $ref: "#/components/schemas/DateTime"
2822
+ individualQuotes:
2823
+ type: array
2824
+ minItems: 1
2825
+ maxItems: 1000
2826
+ items:
2827
+ $ref: "#/components/schemas/IndividualQuote"
2828
+ description: List of quotes elements.
2829
+ extensionList:
2830
+ $ref: "#/components/schemas/ExtensionList"
2831
+ required:
2832
+ - bulkQuoteId
2833
+ - payer
2834
+ - individualQuotes
2835
+ BulkTransferState:
2836
+ title: BulkTransactionState
2837
+ type: string
2838
+ enum:
2839
+ - RECEIVED
2840
+ - PENDING
2841
+ - ACCEPTED
2842
+ - PROCESSING
2843
+ - COMPLETED
2844
+ - REJECTED
2845
+ description: >-
2846
+ Below are the allowed values for the enumeration.
2847
+
2848
+ - RECEIVED - Payee FSP has received the bulk transfer from the Payer
2849
+ FSP.
2850
+
2851
+ - PENDING - Payee FSP has validated the bulk transfer.
2852
+
2853
+ - ACCEPTED - Payee FSP has accepted to process the bulk transfer.
2854
+
2855
+ - PROCESSING - Payee FSP has started to transfer fund to the Payees.
2856
+
2857
+ - COMPLETED - Payee FSP has completed transfer of funds to the Payees.
2858
+
2859
+ - REJECTED - Payee FSP has rejected to process the bulk transfer.
2860
+ example: RECEIVED
2861
+ BulkTransfersIDPutResponse:
2862
+ title: BulkTransfersIDPutResponse
2863
+ type: object
2864
+ description: The object sent in the PUT /bulkTransfers/{ID} callback.
2865
+ properties:
2866
+ completedTimestamp:
2867
+ $ref: "#/components/schemas/DateTime"
2868
+ individualTransferResults:
2869
+ type: array
2870
+ maxItems: 1000
2871
+ items:
2872
+ $ref: "#/components/schemas/IndividualTransferResult"
2873
+ description: List of IndividualTransferResult elements.
2874
+ bulkTransferState:
2875
+ $ref: "#/components/schemas/BulkTransferState"
2876
+ extensionList:
2877
+ $ref: "#/components/schemas/ExtensionList"
2878
+ required:
2879
+ - bulkTransferState
2880
+ BulkTransfersPostRequest:
2881
+ title: BulkTransfersPostRequest
2882
+ type: object
2883
+ description: The object sent in the POST /bulkTransfers request.
2884
+ properties:
2885
+ bulkTransferId:
2886
+ $ref: "#/components/schemas/CorrelationId"
2887
+ bulkQuoteId:
2888
+ $ref: "#/components/schemas/CorrelationId"
2889
+ payerFsp:
2890
+ $ref: "#/components/schemas/FspId"
2891
+ payeeFsp:
2892
+ $ref: "#/components/schemas/FspId"
2893
+ individualTransfers:
2894
+ type: array
2895
+ minItems: 1
2896
+ maxItems: 1000
2897
+ items:
2898
+ $ref: "#/components/schemas/IndividualTransfer"
2899
+ description: List of IndividualTransfer elements.
2900
+ expiration:
2901
+ $ref: "#/components/schemas/DateTime"
2902
+ extensionList:
2903
+ $ref: "#/components/schemas/ExtensionList"
2904
+ required:
2905
+ - bulkTransferId
2906
+ - bulkQuoteId
2907
+ - payerFsp
2908
+ - payeeFsp
2909
+ - individualTransfers
2910
+ - expiration
2911
+ Code:
2912
+ title: Code
2913
+ type: string
2914
+ pattern: ^[0-9a-zA-Z]{4,32}$
2915
+ description: Any code/token returned by the Payee FSP (TokenCode Type).
2916
+ example: Test-Code
2917
+ CorrelationId:
2918
+ title: CorrelationId
2919
+ type: string
2920
+ pattern: >-
2921
+ ^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
2922
+ description: >-
2923
+ Identifier that correlates all messages of the same sequence. The API
2924
+ data type UUID (Universally Unique Identifier) is a JSON String in
2925
+ canonical format, conforming to [RFC
2926
+ 4122](https://tools.ietf.org/html/rfc4122), that is restricted by a
2927
+ regular expression for interoperability reasons. A UUID is always 36
2928
+ characters long, 32 hexadecimal symbols and 4 dashes (‘-‘).
2929
+ example: b51ec534-ee48-4575-b6a9-ead2955b8069
2930
+ Currency:
2931
+ title: Currency
2932
+ description: >-
2933
+ The currency codes defined in [ISO
2934
+ 4217](https://www.iso.org/iso-4217-currency-codes.html) as three-letter
2935
+ alphabetic codes are used as the standard naming representation for
2936
+ currencies.
2937
+ type: string
2938
+ minLength: 3
2939
+ maxLength: 3
2940
+ enum:
2941
+ - AED
2942
+ - AFN
2943
+ - ALL
2944
+ - AMD
2945
+ - ANG
2946
+ - AOA
2947
+ - ARS
2948
+ - AUD
2949
+ - AWG
2950
+ - AZN
2951
+ - BAM
2952
+ - BBD
2953
+ - BDT
2954
+ - BGN
2955
+ - BHD
2956
+ - BIF
2957
+ - BMD
2958
+ - BND
2959
+ - BOB
2960
+ - BRL
2961
+ - BSD
2962
+ - BTN
2963
+ - BWP
2964
+ - BYN
2965
+ - BZD
2966
+ - CAD
2967
+ - CDF
2968
+ - CHF
2969
+ - CLP
2970
+ - CNY
2971
+ - COP
2972
+ - CRC
2973
+ - CUC
2974
+ - CUP
2975
+ - CVE
2976
+ - CZK
2977
+ - DJF
2978
+ - DKK
2979
+ - DOP
2980
+ - DZD
2981
+ - EGP
2982
+ - ERN
2983
+ - ETB
2984
+ - EUR
2985
+ - FJD
2986
+ - FKP
2987
+ - GBP
2988
+ - GEL
2989
+ - GGP
2990
+ - GHS
2991
+ - GIP
2992
+ - GMD
2993
+ - GNF
2994
+ - GTQ
2995
+ - GYD
2996
+ - HKD
2997
+ - HNL
2998
+ - HRK
2999
+ - HTG
3000
+ - HUF
3001
+ - IDR
3002
+ - ILS
3003
+ - IMP
3004
+ - INR
3005
+ - IQD
3006
+ - IRR
3007
+ - ISK
3008
+ - JEP
3009
+ - JMD
3010
+ - JOD
3011
+ - JPY
3012
+ - KES
3013
+ - KGS
3014
+ - KHR
3015
+ - KMF
3016
+ - KPW
3017
+ - KRW
3018
+ - KWD
3019
+ - KYD
3020
+ - KZT
3021
+ - LAK
3022
+ - LBP
3023
+ - LKR
3024
+ - LRD
3025
+ - LSL
3026
+ - LYD
3027
+ - MAD
3028
+ - MDL
3029
+ - MGA
3030
+ - MKD
3031
+ - MMK
3032
+ - MNT
3033
+ - MOP
3034
+ - MRO
3035
+ - MUR
3036
+ - MVR
3037
+ - MWK
3038
+ - MXN
3039
+ - MYR
3040
+ - MZN
3041
+ - NAD
3042
+ - NGN
3043
+ - NIO
3044
+ - NOK
3045
+ - NPR
3046
+ - NZD
3047
+ - OMR
3048
+ - PAB
3049
+ - PEN
3050
+ - PGK
3051
+ - PHP
3052
+ - PKR
3053
+ - PLN
3054
+ - PYG
3055
+ - QAR
3056
+ - RON
3057
+ - RSD
3058
+ - RUB
3059
+ - RWF
3060
+ - SAR
3061
+ - SBD
3062
+ - SCR
3063
+ - SDG
3064
+ - SEK
3065
+ - SGD
3066
+ - SHP
3067
+ - SLL
3068
+ - SOS
3069
+ - SPL
3070
+ - SRD
3071
+ - STD
3072
+ - SVC
3073
+ - SYP
3074
+ - SZL
3075
+ - THB
3076
+ - TJS
3077
+ - TMT
3078
+ - TND
3079
+ - TOP
3080
+ - TRY
3081
+ - TTD
3082
+ - TVD
3083
+ - TWD
3084
+ - TZS
3085
+ - UAH
3086
+ - UGX
3087
+ - USD
3088
+ - UYU
3089
+ - UZS
3090
+ - VEF
3091
+ - VND
3092
+ - VUV
3093
+ - WST
3094
+ - XAF
3095
+ - XCD
3096
+ - XDR
3097
+ - XOF
3098
+ - XPF
3099
+ - XTS
3100
+ - XXX
3101
+ - YER
3102
+ - ZAR
3103
+ - ZMW
3104
+ - ZWD
3105
+ CurrencyConverter:
3106
+ title: CurrencyConverter
3107
+ type: string
3108
+ enum:
3109
+ - PAYER
3110
+ - PAYEE
3111
+ description: >-
3112
+ Below are the allowed values for the enumeration CurrencyConverter. -
3113
+ PAYER - Currency conversion should be performed by the payer. - PAYEE -
3114
+ Currency conversion should be performed by the payee.
3115
+ Date:
3116
+ title: Date
3117
+ type: string
3118
+ pattern: >-
3119
+ ^(?:[1-9]\d{3}-(?:(?:0[1-9]|1[0-2])-(?:0[1-9]|1\d|2[0-8])|(?:0[13-9]|1[0-2])-(?:29|30)|(?:0[13578]|1[02])-31)|(?:[1-9]\d(?:0[48]|[2468][048]|[13579][26])|(?:[2468][048]|[13579][26])00)-02-29)$
3120
+ description: >-
3121
+ The API data type Date is a JSON String in a lexical format that is
3122
+ restricted by a regular expression for interoperability reasons. This
3123
+ format, as specified in ISO 8601, contains a date only. A more readable
3124
+ version of the format is yyyy-MM-dd. Examples are "1982-05-23",
3125
+ "1987-08-05”.
3126
+ DateOfBirth:
3127
+ title: DateofBirth (type Date)
3128
+ type: string
3129
+ pattern: >-
3130
+ ^(?:[1-9]\d{3}-(?:(?:0[1-9]|1[0-2])-(?:0[1-9]|1\d|2[0-8])|(?:0[13-9]|1[0-2])-(?:29|30)|(?:0[13578]|1[02])-31)|(?:[1-9]\d(?:0[48]|[2468][048]|[13579][26])|(?:[2468][048]|[13579][26])00)-02-29)$
3131
+ description: Date of Birth of the Party.
3132
+ example: "1966-06-16"
3133
+ DateTime:
3134
+ title: DateTime
3135
+ type: string
3136
+ pattern: >-
3137
+ ^(?:[1-9]\d{3}-(?:(?:0[1-9]|1[0-2])-(?:0[1-9]|1\d|2[0-8])|(?:0[13-9]|1[0-2])-(?:29|30)|(?:0[13578]|1[02])-31)|(?:[1-9]\d(?:0[48]|[2468][048]|[13579][26])|(?:[2468][048]|[13579][26])00)-02-29)T(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:(\.\d{3}))(?:Z|[+-][01]\d:[0-5]\d)$
3138
+ description: >-
3139
+ The API data type DateTime is a JSON String in a lexical format that is
3140
+ restricted by a regular expression for interoperability reasons. The
3141
+ format is according to [ISO
3142
+ 8601](https://www.iso.org/iso-8601-date-and-time-format.html), expressed
3143
+ in a combined date, time and time zone format. A more readable version
3144
+ of the format is yyyy-MM-ddTHH:mm:ss.SSS[-HH:MM]. Examples are
3145
+ "2016-05-24T08:38:08.699-04:00", "2016-05-24T08:38:08.699Z" (where Z
3146
+ indicates Zulu time zone, same as UTC).
3147
+ example: "2016-05-24T08:38:08.699-04:00"
3148
+ ErrorCode:
3149
+ title: ErrorCode
3150
+ type: string
3151
+ pattern: ^[1-9]\d{3}$
3152
+ description: >-
3153
+ The API data type ErrorCode is a JSON String of four characters,
3154
+ consisting of digits only. Negative numbers are not allowed. A leading
3155
+ zero is not allowed. Each error code in the API is a four-digit number,
3156
+ for example, 1234, where the first number (1 in the example) represents
3157
+ the high-level error category, the second number (2 in the example)
3158
+ represents the low-level error category, and the last two numbers (34 in
3159
+ the example) represent the specific error.
3160
+ example: "5100"
3161
+ ErrorDescription:
3162
+ title: ErrorDescription
3163
+ type: string
3164
+ minLength: 1
3165
+ maxLength: 128
3166
+ description: Error description string.
3167
+ ErrorInformation:
3168
+ title: ErrorInformation
3169
+ type: object
3170
+ description: Data model for the complex type ErrorInformation.
3171
+ properties:
3172
+ errorCode:
3173
+ $ref: "#/components/schemas/ErrorCode"
3174
+ errorDescription:
3175
+ $ref: "#/components/schemas/ErrorDescription"
3176
+ extensionList:
3177
+ $ref: "#/components/schemas/ExtensionList"
3178
+ required:
3179
+ - errorCode
3180
+ - errorDescription
3181
+ ErrorInformationObject:
3182
+ title: ErrorInformationObject
3183
+ type: object
3184
+ description: Data model for the complex type object that contains ErrorInformation.
3185
+ properties:
3186
+ errorInformation:
3187
+ $ref: "#/components/schemas/ErrorInformation"
3188
+ required:
3189
+ - errorInformation
3190
+ ErrorInformationResponse:
3191
+ title: ErrorInformationResponse
3192
+ type: object
3193
+ description: >-
3194
+ Data model for the complex type object that contains an optional element
3195
+ ErrorInformation used along with 4xx and 5xx responses.
3196
+ properties:
3197
+ errorInformation:
3198
+ $ref: "#/components/schemas/ErrorInformation"
3199
+ Extension:
3200
+ title: Extension
3201
+ type: object
3202
+ description: Data model for the complex type Extension.
3203
+ properties:
3204
+ key:
3205
+ $ref: "#/components/schemas/ExtensionKey"
3206
+ value:
3207
+ $ref: "#/components/schemas/ExtensionValue"
3208
+ required:
3209
+ - key
3210
+ - value
3211
+ ExtensionKey:
3212
+ title: ExtensionKey
3213
+ type: string
3214
+ minLength: 1
3215
+ maxLength: 32
3216
+ description: Extension key.
3217
+ ExtensionList:
3218
+ title: ExtensionList
3219
+ type: object
3220
+ description: >-
3221
+ Data model for the complex type ExtensionList. An optional list of
3222
+ extensions, specific to deployment.
3223
+ properties:
3224
+ extension:
3225
+ type: array
3226
+ items:
3227
+ $ref: "#/components/schemas/Extension"
3228
+ minItems: 1
3229
+ maxItems: 16
3230
+ description: Number of Extension elements.
3231
+ required:
3232
+ - extension
3233
+ ExtensionValue:
3234
+ title: ExtensionValue
3235
+ type: string
3236
+ minLength: 1
3237
+ maxLength: 128
3238
+ description: Extension value.
3239
+ FirstName:
3240
+ title: FirstName
3241
+ type: string
3242
+ minLength: 1
3243
+ maxLength: 128
3244
+ pattern: >-
3245
+ ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control}
3246
+ .,''-]{1,128}$
3247
+ description: First name of the Party (Name Type).
3248
+ example: Henrik
3249
+ FspId:
3250
+ title: FspId
3251
+ type: string
3252
+ minLength: 1
3253
+ maxLength: 32
3254
+ description: FSP identifier.
3255
+ FxCharge:
3256
+ title: FxCharge
3257
+ type: object
3258
+ description: >-
3259
+ An FXP will be able to specify a charge which it proposes to levy on the
3260
+ currency conversion operation using a FxCharge object.
3261
+ properties:
3262
+ chargeType:
3263
+ type: string
3264
+ minLength: 1
3265
+ maxLength: 32
3266
+ description: A description of the charge which is being levied.
3267
+ sourceAmount:
3268
+ allOf:
3269
+ - $ref: "#/components/schemas/Money"
3270
+ - description: >-
3271
+ The amount of the charge which is being levied, expressed in the
3272
+ source currency.
3273
+ targetAmount:
3274
+ allOf:
3275
+ - $ref: "#/components/schemas/Money"
3276
+ - description: >-
3277
+ The amount of the charge which is being levied, expressed in the
3278
+ target currency.
3279
+ required:
3280
+ - chargeType
3281
+ FxConversion:
3282
+ title: FxConversion
3283
+ type: object
3284
+ description: >-
3285
+ A DFSP will be able to request a currency conversion, and an FX provider
3286
+ will be able to describe its involvement in a proposed transfer, using a
3287
+ FxConversion object.
3288
+ properties:
3289
+ conversionId:
3290
+ allOf:
3291
+ - $ref: "#/components/schemas/CorrelationId"
3292
+ - description: An end-to-end identifier for the conversion request.
3293
+ determiningTransferId:
3294
+ allOf:
3295
+ - $ref: "#/components/schemas/CorrelationId"
3296
+ - description: >-
3297
+ The transaction ID of the transfer on whose success this
3298
+ currency conversion depends.
3299
+ initiatingFsp:
3300
+ allOf:
3301
+ - $ref: "#/components/schemas/FspId"
3302
+ - description: >-
3303
+ The id of the participant who is requesting a currency
3304
+ conversion.
3305
+ counterPartyFsp:
3306
+ allOf:
3307
+ - $ref: "#/components/schemas/FspId"
3308
+ - description: The ID of the FXP performing the conversion.
3309
+ amountType:
3310
+ allOf:
3311
+ - $ref: "#/components/schemas/AmountType"
3312
+ - description: >-
3313
+ This is the AmountType for the base transaction - If SEND - then
3314
+ any charges levied by the FXP as part of the transaction will be
3315
+ deducted by the FXP from the amount shown for the target party
3316
+ in the conversion. If RECEIVE - then any charges levied by the
3317
+ FXP as part of the transaction will be added by the FXP to the
3318
+ amount shown for the source party in the conversion.
3319
+ sourceAmount:
3320
+ allOf:
3321
+ - $ref: "#/components/schemas/FxMoney"
3322
+ - description: The amount to be converted, expressed in the source currency.
3323
+ targetAmount:
3324
+ allOf:
3325
+ - $ref: "#/components/schemas/FxMoney"
3326
+ - description: The converted amount, expressed in the target currency.
3327
+ expiration:
3328
+ allOf:
3329
+ - $ref: "#/components/schemas/DateTime"
3330
+ - description: >-
3331
+ The end of the period for which the currency conversion is
3332
+ required to remain valid.
3333
+ charges:
3334
+ type: array
3335
+ description: >-
3336
+ One or more charges which the FXP intends to levy as part of the
3337
+ currency conversion, or which the payee DFSP intends to add to the
3338
+ amount transferred.
3339
+ items:
3340
+ $ref: "#/components/schemas/FxCharge"
3341
+ minItems: 0
3342
+ maxItems: 16
3343
+ extensionList:
3344
+ allOf:
3345
+ - $ref: "#/components/schemas/ExtensionList"
3346
+ - description: The extension list for the currency conversion request.
3347
+ required:
3348
+ - conversionId
3349
+ - initiatingFsp
3350
+ - counterPartyFsp
3351
+ - amountType
3352
+ - sourceAmount
3353
+ - targetAmount
3354
+ - expiration
3355
+ FxMoney:
3356
+ title: FxMoney
3357
+ type: object
3358
+ description: >-
3359
+ Data model for the complex type FxMoney; This is based on the type Money
3360
+ but allows the amount to be optional to support FX quotations.
3361
+ properties:
3362
+ currency:
3363
+ $ref: "#/components/schemas/Currency"
3364
+ amount:
3365
+ $ref: "#/components/schemas/Amount"
3366
+ required:
3367
+ - currency
3368
+ FxQuotesIDPutResponse:
3369
+ title: FxQuotesIDPutResponse
3370
+ type: object
3371
+ description: The object sent in the PUT /fxQuotes/{ID} callback.
3372
+ properties:
3373
+ condition:
3374
+ allOf:
3375
+ - $ref: "#/components/schemas/IlpCondition"
3376
+ - description: The ILP condition for the conversion.
3377
+ conversionTerms:
3378
+ allOf:
3379
+ - $ref: "#/components/schemas/FxConversion"
3380
+ - description: >-
3381
+ The terms under which the FXP will undertake the currency
3382
+ conversion proposed by the requester.
3383
+ required:
3384
+ - conversionTerms
3385
+ FxQuotesPostRequest:
3386
+ title: FxQuotesPostRequest
3387
+ type: object
3388
+ description: The object sent in the POST /fxQuotes request.
3389
+ properties:
3390
+ conversionRequestId:
3391
+ allOf:
3392
+ - $ref: "#/components/schemas/CorrelationId"
3393
+ - description: An end-to-end identifier for the conversion quotation request.
3394
+ conversionTerms:
3395
+ allOf:
3396
+ - $ref: "#/components/schemas/FxConversion"
3397
+ - description: >-
3398
+ The terms of the currency conversion for which a quotation is
3399
+ sought.
3400
+ required:
3401
+ - conversionRequestId
3402
+ - conversionTerms
3403
+ FxRate:
3404
+ title: FxRate
3405
+ type: object
3406
+ description: >-
3407
+ The FxRate object contains information about a currency conversion in
3408
+ the transfer. It can be used by parties to the transfer to exchange
3409
+ information with each other about the exchange rate for the transfer, to
3410
+ ensure that the best rate can be agreed on.
3411
+ properties:
3412
+ sourceAmount:
3413
+ allOf:
3414
+ - $ref: "#/components/schemas/Money"
3415
+ - description: The amount of the transfer in the source currency.
3416
+ targetAmount:
3417
+ allOf:
3418
+ - $ref: "#/components/schemas/Money"
3419
+ - description: The amount of the transfer in the target currency.
3420
+ required:
3421
+ - sourceAmount
3422
+ - targetAmount
3423
+ FxTransfersIDPatchResponse:
3424
+ title: FxTransfersIDPatchResponse
3425
+ type: object
3426
+ description: PATCH /fxTransfers/{ID} object
3427
+ properties:
3428
+ completedTimestamp:
3429
+ allOf:
3430
+ - $ref: "#/components/schemas/DateTime"
3431
+ - description: Time and date when the conversion was executed.
3432
+ conversionState:
3433
+ allOf:
3434
+ - $ref: "#/components/schemas/TransferState"
3435
+ - description: The current status of the conversion request.
3436
+ extensionList:
3437
+ $ref: "#/components/schemas/ExtensionList"
3438
+ required:
3439
+ - conversionState
3440
+ FxTransfersIDPutResponse:
3441
+ title: FxTransfersIDPutResponse
3442
+ type: object
3443
+ description: The object sent in the PUT /fxTransfers/{ID} callback.
3444
+ properties:
3445
+ fulfilment:
3446
+ allOf:
3447
+ - $ref: "#/components/schemas/IlpFulfilment"
3448
+ - description: >-
3449
+ The fulfilment of the condition specified for the currency
3450
+ conversion. Mandatory if the conversion has been executed
3451
+ successfully.
3452
+ completedTimestamp:
3453
+ allOf:
3454
+ - $ref: "#/components/schemas/DateTime"
3455
+ - description: Time and date when the conversion was executed.
3456
+ conversionState:
3457
+ allOf:
3458
+ - $ref: "#/components/schemas/TransferState"
3459
+ - description: The current status of the conversion request.
3460
+ extensionList:
3461
+ $ref: "#/components/schemas/ExtensionList"
3462
+ required:
3463
+ - conversionState
3464
+ FxTransfersPostRequest:
3465
+ title: FxTransfersPostRequest
3466
+ type: object
3467
+ description: The object sent in the POST /fxTransfers request.
3468
+ properties:
3469
+ commitRequestId:
3470
+ allOf:
3471
+ - $ref: "#/components/schemas/CorrelationId"
3472
+ - description: An end-to-end identifier for the confirmation request.
3473
+ determiningTransferId:
3474
+ allOf:
3475
+ - $ref: "#/components/schemas/CorrelationId"
3476
+ - description: >-
3477
+ The transaction ID of the transfer to which this currency
3478
+ conversion relates, if the conversion is part of a transfer. If
3479
+ the conversion is a bulk currency purchase, this field should be
3480
+ omitted.
3481
+ initiatingFsp:
3482
+ allOf:
3483
+ - $ref: "#/components/schemas/FspId"
3484
+ - description: Identifier for the FSP who is requesting a currency conversion.
3485
+ counterPartyFsp:
3486
+ allOf:
3487
+ - $ref: "#/components/schemas/FspId"
3488
+ - description: >-
3489
+ Identifier for the FXP who is performing the currency
3490
+ conversion.
3491
+ sourceAmount:
3492
+ allOf:
3493
+ - $ref: "#/components/schemas/Money"
3494
+ - description: The amount being offered for conversion by the requesting FSP.
3495
+ targetAmount:
3496
+ allOf:
3497
+ - $ref: "#/components/schemas/Money"
3498
+ - description: >-
3499
+ The amount which the FXP is to credit to the requesting FSP in
3500
+ the target currency.
3501
+ condition:
3502
+ allOf:
3503
+ - $ref: "#/components/schemas/IlpCondition"
3504
+ - description: >-
3505
+ ILP condition received by the requesting FSP when the quote was
3506
+ approved.
3507
+ expiration:
3508
+ $ref: "#/components/schemas/DateTime"
3509
+ required:
3510
+ - commitRequestId
3511
+ - initiatingFsp
3512
+ - counterPartyFsp
3513
+ - sourceAmount
3514
+ - targetAmount
3515
+ - condition
3516
+ GeoCode:
3517
+ title: GeoCode
3518
+ type: object
3519
+ description: >-
3520
+ Data model for the complex type GeoCode. Indicates the geographic
3521
+ location from where the transaction was initiated.
3522
+ properties:
3523
+ latitude:
3524
+ $ref: "#/components/schemas/Latitude"
3525
+ longitude:
3526
+ $ref: "#/components/schemas/Longitude"
3527
+ required:
3528
+ - latitude
3529
+ - longitude
3530
+ IlpCondition:
3531
+ title: IlpCondition
3532
+ type: string
3533
+ pattern: ^[A-Za-z0-9-_]{43}$
3534
+ maxLength: 48
3535
+ description: Condition that must be attached to the transfer by the Payer.
3536
+ IlpFulfilment:
3537
+ title: IlpFulfilment
3538
+ type: string
3539
+ pattern: ^[A-Za-z0-9-_]{43}$
3540
+ maxLength: 48
3541
+ description: Fulfilment that must be attached to the transfer by the Payee.
3542
+ example: WLctttbu2HvTsa1XWvUoGRcQozHsqeu9Ahl2JW9Bsu8
3543
+ IlpPacket:
3544
+ title: IlpPacket
3545
+ type: string
3546
+ pattern: ^[A-Za-z0-9-_]+[=]{0,2}$
3547
+ minLength: 1
3548
+ maxLength: 32768
3549
+ description: Information for recipient (transport layer information).
3550
+ example: >-
3551
+ AYIBgQAAAAAAAASwNGxldmVsb25lLmRmc3AxLm1lci45T2RTOF81MDdqUUZERmZlakgyOVc4bXFmNEpLMHlGTFGCAUBQU0svMS4wCk5vbmNlOiB1SXlweUYzY3pYSXBFdzVVc05TYWh3CkVuY3J5cHRpb246IG5vbmUKUGF5bWVudC1JZDogMTMyMzZhM2ItOGZhOC00MTYzLTg0NDctNGMzZWQzZGE5OGE3CgpDb250ZW50LUxlbmd0aDogMTM1CkNvbnRlbnQtVHlwZTogYXBwbGljYXRpb24vanNvbgpTZW5kZXItSWRlbnRpZmllcjogOTI4MDYzOTEKCiJ7XCJmZWVcIjowLFwidHJhbnNmZXJDb2RlXCI6XCJpbnZvaWNlXCIsXCJkZWJpdE5hbWVcIjpcImFsaWNlIGNvb3BlclwiLFwiY3JlZGl0TmFtZVwiOlwibWVyIGNoYW50XCIsXCJkZWJpdElkZW50aWZpZXJcIjpcIjkyODA2MzkxXCJ9IgA
3552
+ IndividualQuote:
3553
+ title: IndividualQuote
3554
+ type: object
3555
+ description: Data model for the complex type IndividualQuote.
3556
+ properties:
3557
+ quoteId:
3558
+ $ref: "#/components/schemas/CorrelationId"
3559
+ transactionId:
3560
+ $ref: "#/components/schemas/CorrelationId"
3561
+ payee:
3562
+ $ref: "#/components/schemas/Party"
3563
+ amountType:
3564
+ $ref: "#/components/schemas/AmountType"
3565
+ amount:
3566
+ $ref: "#/components/schemas/Money"
3567
+ fees:
3568
+ $ref: "#/components/schemas/Money"
3569
+ transactionType:
3570
+ $ref: "#/components/schemas/TransactionType"
3571
+ note:
3572
+ $ref: "#/components/schemas/Note"
3573
+ extensionList:
3574
+ $ref: "#/components/schemas/ExtensionList"
3575
+ required:
3576
+ - quoteId
3577
+ - transactionId
3578
+ - payee
3579
+ - amountType
3580
+ - amount
3581
+ - transactionType
3582
+ IndividualQuoteResult:
3583
+ title: IndividualQuoteResult
3584
+ type: object
3585
+ description: Data model for the complex type IndividualQuoteResult.
3586
+ properties:
3587
+ quoteId:
3588
+ $ref: "#/components/schemas/CorrelationId"
3589
+ payee:
3590
+ $ref: "#/components/schemas/Party"
3591
+ transferAmount:
3592
+ $ref: "#/components/schemas/Money"
3593
+ payeeReceiveAmount:
3594
+ $ref: "#/components/schemas/Money"
3595
+ payeeFspFee:
3596
+ $ref: "#/components/schemas/Money"
3597
+ payeeFspCommission:
3598
+ $ref: "#/components/schemas/Money"
3599
+ ilpPacket:
3600
+ $ref: "#/components/schemas/IlpPacket"
3601
+ condition:
3602
+ $ref: "#/components/schemas/IlpCondition"
3603
+ errorInformation:
3604
+ $ref: "#/components/schemas/ErrorInformation"
3605
+ extensionList:
3606
+ $ref: "#/components/schemas/ExtensionList"
3607
+ required:
3608
+ - quoteId
3609
+ IndividualTransfer:
3610
+ title: IndividualTransfer
3611
+ type: object
3612
+ description: Data model for the complex type IndividualTransfer.
3613
+ properties:
3614
+ transferId:
3615
+ $ref: "#/components/schemas/CorrelationId"
3616
+ transferAmount:
3617
+ $ref: "#/components/schemas/Money"
3618
+ ilpPacket:
3619
+ $ref: "#/components/schemas/IlpPacket"
3620
+ condition:
3621
+ $ref: "#/components/schemas/IlpCondition"
3622
+ extensionList:
3623
+ $ref: "#/components/schemas/ExtensionList"
3624
+ required:
3625
+ - transferId
3626
+ - transferAmount
3627
+ - ilpPacket
3628
+ - condition
3629
+ IndividualTransferResult:
3630
+ title: IndividualTransferResult
3631
+ type: object
3632
+ description: Data model for the complex type IndividualTransferResult.
3633
+ properties:
3634
+ transferId:
3635
+ $ref: "#/components/schemas/CorrelationId"
3636
+ fulfilment:
3637
+ $ref: "#/components/schemas/IlpFulfilment"
3638
+ errorInformation:
3639
+ $ref: "#/components/schemas/ErrorInformation"
3640
+ extensionList:
3641
+ $ref: "#/components/schemas/ExtensionList"
3642
+ required:
3643
+ - transferId
3644
+ Integer:
3645
+ title: Integer
3646
+ type: string
3647
+ pattern: ^[1-9]\d*$
3648
+ description: >-
3649
+ The API data type Integer is a JSON String consisting of digits only.
3650
+ Negative numbers and leading zeroes are not allowed. The data type is
3651
+ always limited to a specific number of digits.
3652
+ KYCInformation:
3653
+ title: KYCInformation
3654
+ type: string
3655
+ minLength: 1
3656
+ maxLength: 2048
3657
+ description: >-
3658
+ KYC information for the party in a form mandated by an individual
3659
+ scheme.
3660
+ example: |-
3661
+ {
3662
+ "metadata": {
3663
+ "format": "JSON",
3664
+ "version": "1.0",
3665
+ "description": "Data containing KYC Information"
3666
+ },
3667
+ "data": {
3668
+ "name": "John Doe",
3669
+ "dob": "1980-05-15",
3670
+ "gender": "Male",
3671
+ "address": "123 Main Street, Anytown, USA",
3672
+ "email": "johndoe@example.com",
3673
+ "phone": "+1 555-123-4567",
3674
+ "nationality": "US",
3675
+ "passport_number": "AB1234567",
3676
+ "issue_date": "2010-02-20",
3677
+ "expiry_date": "2025-02-20",
3678
+ "bank_account_number": "1234567890",
3679
+ "bank_name": "Example Bank",
3680
+ "employer": "ABC Company",
3681
+ "occupation": "Software Engineer",
3682
+ "income": "$80,000 per year",
3683
+ "marital_status": "Single",
3684
+ "dependents": 0,
3685
+ "risk_level": "Low"
3686
+ }
3687
+ }
3688
+ LastName:
3689
+ title: LastName
3690
+ type: string
3691
+ minLength: 1
3692
+ maxLength: 128
3693
+ pattern: >-
3694
+ ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control}
3695
+ .,''-]{1,128}$
3696
+ description: Last name of the Party (Name Type).
3697
+ example: Karlsson
3698
+ Latitude:
3699
+ title: Latitude
3700
+ type: string
3701
+ pattern: >-
3702
+ ^(\+|-)?(?:90(?:(?:\.0{1,6})?)|(?:[0-9]|[1-8][0-9])(?:(?:\.[0-9]{1,6})?))$
3703
+ description: >-
3704
+ The API data type Latitude is a JSON String in a lexical format that is
3705
+ restricted by a regular expression for interoperability reasons.
3706
+ example: "+45.4215"
3707
+ Longitude:
3708
+ title: Longitude
3709
+ type: string
3710
+ pattern: >-
3711
+ ^(\+|-)?(?:180(?:(?:\.0{1,6})?)|(?:[0-9]|[1-9][0-9]|1[0-7][0-9])(?:(?:\.[0-9]{1,6})?))$
3712
+ description: >-
3713
+ The API data type Longitude is a JSON String in a lexical format that is
3714
+ restricted by a regular expression for interoperability reasons.
3715
+ example: "+75.6972"
3716
+ MerchantClassificationCode:
3717
+ title: MerchantClassificationCode
3718
+ type: string
3719
+ pattern: ^[\d]{1,4}$
3720
+ description: >-
3721
+ A limited set of pre-defined numbers. This list would be a limited set
3722
+ of numbers identifying a set of popular merchant types like School Fees,
3723
+ Pubs and Restaurants, Groceries, etc.
3724
+ MiddleName:
3725
+ title: MiddleName
3726
+ type: string
3727
+ minLength: 1
3728
+ maxLength: 128
3729
+ pattern: >-
3730
+ ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control}
3731
+ .,''-]{1,128}$
3732
+ description: Middle name of the Party (Name Type).
3733
+ example: Johannes
3734
+ Money:
3735
+ title: Money
3736
+ type: object
3737
+ description: Data model for the complex type Money.
3738
+ properties:
3739
+ currency:
3740
+ $ref: "#/components/schemas/Currency"
3741
+ amount:
3742
+ $ref: "#/components/schemas/Amount"
3743
+ required:
3744
+ - currency
3745
+ - amount
3746
+ Name:
3747
+ title: Name
3748
+ type: string
3749
+ pattern: ^(?!\s*$)[\w .,'-]{1,128}$
3750
+ description: >-
3751
+ The API data type Name is a JSON String, restricted by a regular
3752
+ expression to avoid characters which are generally not used in a name.
3753
+
3754
+
3755
+ Regular Expression - The regular expression for restricting the Name
3756
+ type is "^(?!\s*$)[\w .,'-]{1,128}$". The restriction does not allow a
3757
+ string consisting of whitespace only, all Unicode characters are
3758
+ allowed, as well as the period (.) (apostrophe (‘), dash (-), comma (,)
3759
+ and space characters ( ).
3760
+
3761
+
3762
+ **Note:** In some programming languages, Unicode support must be
3763
+ specifically enabled. For example, if Java is used, the flag
3764
+ UNICODE_CHARACTER_CLASS must be enabled to allow Unicode characters.
3765
+ Note:
3766
+ title: Note
3767
+ type: string
3768
+ minLength: 1
3769
+ maxLength: 128
3770
+ description: Memo assigned to transaction.
3771
+ example: Note sent to Payee.
3772
+ OtpValue:
3773
+ title: OtpValue
3774
+ type: string
3775
+ pattern: ^\d{3,10}$
3776
+ description: >-
3777
+ The API data type OtpValue is a JSON String of 3 to 10 characters,
3778
+ consisting of digits only. Negative numbers are not allowed. One or more
3779
+ leading zeros are allowed.
3780
+ ParticipantsIDPutResponse:
3781
+ title: ParticipantsIDPutResponse
3782
+ type: object
3783
+ description: The object sent in the PUT /participants/{ID} callback.
3784
+ properties:
3785
+ partyList:
3786
+ type: array
3787
+ items:
3788
+ $ref: "#/components/schemas/PartyResult"
3789
+ minItems: 1
3790
+ maxItems: 10000
3791
+ description: >-
3792
+ List of PartyResult elements that were either created or failed to
3793
+ be created.
3794
+ currency:
3795
+ $ref: "#/components/schemas/Currency"
3796
+ required:
3797
+ - partyList
3798
+ ParticipantsPostRequest:
3799
+ title: ParticipantsPostRequest
3800
+ type: object
3801
+ description: The object sent in the POST /participants request.
3802
+ properties:
3803
+ requestId:
3804
+ $ref: "#/components/schemas/CorrelationId"
3805
+ partyList:
3806
+ type: array
3807
+ items:
3808
+ $ref: "#/components/schemas/PartyIdInfo"
3809
+ minItems: 1
3810
+ maxItems: 10000
3811
+ description: >-
3812
+ List of PartyIdInfo elements that the client would like to update or
3813
+ create FSP information about.
3814
+ currency:
3815
+ $ref: "#/components/schemas/Currency"
3816
+ required:
3817
+ - requestId
3818
+ - partyList
3819
+ ParticipantsTypeIDPutResponse:
3820
+ title: ParticipantsTypeIDPutResponse
3821
+ type: object
3822
+ description: >-
3823
+ The object sent in the PUT /participants/{Type}/{ID}/{SubId} and
3824
+ /participants/{Type}/{ID} callbacks.
3825
+ properties:
3826
+ fspId:
3827
+ $ref: "#/components/schemas/FspId"
3828
+ ParticipantsTypeIDSubIDPostRequest:
3829
+ title: ParticipantsTypeIDSubIDPostRequest
3830
+ type: object
3831
+ description: >-
3832
+ The object sent in the POST /participants/{Type}/{ID}/{SubId} and
3833
+ /participants/{Type}/{ID} requests. An additional optional ExtensionList
3834
+ element has been added as part of v1.1 changes.
3835
+ properties:
3836
+ fspId:
3837
+ $ref: "#/components/schemas/FspId"
3838
+ currency:
3839
+ $ref: "#/components/schemas/Currency"
3840
+ extensionList:
3841
+ $ref: "#/components/schemas/ExtensionList"
3842
+ required:
3843
+ - fspId
3844
+ PartiesTypeIDPutResponse:
3845
+ title: PartiesTypeIDPutResponse
3846
+ type: object
3847
+ description: The object sent in the PUT /parties/{Type}/{ID} callback.
3848
+ properties:
3849
+ party:
3850
+ $ref: "#/components/schemas/Party"
3851
+ required:
3852
+ - party
3853
+ Party:
3854
+ title: Party
3855
+ type: object
3856
+ description: Data model for the complex type Party.
3857
+ properties:
3858
+ partyIdInfo:
3859
+ $ref: "#/components/schemas/PartyIdInfo"
3860
+ merchantClassificationCode:
3861
+ $ref: "#/components/schemas/MerchantClassificationCode"
3862
+ name:
3863
+ $ref: "#/components/schemas/PartyName"
3864
+ personalInfo:
3865
+ $ref: "#/components/schemas/PartyPersonalInfo"
3866
+ supportedCurrencies:
3867
+ type: array
3868
+ description: Currencies in which the party can receive funds.
3869
+ items:
3870
+ $ref: "#/components/schemas/Currency"
3871
+ minItems: 0
3872
+ maxItems: 16
3873
+ required:
3874
+ - partyIdInfo
3875
+ PartyComplexName:
3876
+ title: PartyComplexName
3877
+ type: object
3878
+ description: Data model for the complex type PartyComplexName.
3879
+ properties:
3880
+ firstName:
3881
+ $ref: "#/components/schemas/FirstName"
3882
+ middleName:
3883
+ $ref: "#/components/schemas/MiddleName"
3884
+ lastName:
3885
+ $ref: "#/components/schemas/LastName"
3886
+ PartyIdInfo:
3887
+ title: PartyIdInfo
3888
+ type: object
3889
+ description: >-
3890
+ Data model for the complex type PartyIdInfo. An ExtensionList element
3891
+ has been added to this reqeust in version v1.1
3892
+ properties:
3893
+ partyIdType:
3894
+ $ref: "#/components/schemas/PartyIdType"
3895
+ partyIdentifier:
3896
+ $ref: "#/components/schemas/PartyIdentifier"
3897
+ partySubIdOrType:
3898
+ $ref: "#/components/schemas/PartySubIdOrType"
3899
+ fspId:
3900
+ $ref: "#/components/schemas/FspId"
3901
+ extensionList:
3902
+ $ref: "#/components/schemas/ExtensionList"
3903
+ required:
3904
+ - partyIdType
3905
+ - partyIdentifier
3906
+ PartyIdType:
3907
+ title: PartyIdType
3908
+ type: string
3909
+ enum:
3910
+ - MSISDN
3911
+ - EMAIL
3912
+ - PERSONAL_ID
3913
+ - BUSINESS
3914
+ - DEVICE
3915
+ - ACCOUNT_ID
3916
+ - IBAN
3917
+ - ALIAS
3918
+ description: >-
3919
+ Below are the allowed values for the enumeration.
3920
+
3921
+ - MSISDN - An MSISDN (Mobile Station International Subscriber Directory
3922
+ Number, that is, the phone number) is used as reference to a
3923
+ participant. The MSISDN identifier should be in international format
3924
+ according to the [ITU-T E.164
3925
+ standard](https://www.itu.int/rec/T-REC-E.164/en). Optionally, the
3926
+ MSISDN may be prefixed by a single plus sign, indicating the
3927
+ international prefix.
3928
+
3929
+ - EMAIL - An email is used as reference to a participant. The format of
3930
+ the email should be according to the informational [RFC
3931
+ 3696](https://tools.ietf.org/html/rfc3696).
3932
+
3933
+ - PERSONAL_ID - A personal identifier is used as reference to a
3934
+ participant. Examples of personal identification are passport number,
3935
+ birth certificate number, and national registration number. The
3936
+ identifier number is added in the PartyIdentifier element. The personal
3937
+ identifier type is added in the PartySubIdOrType element.
3938
+
3939
+ - BUSINESS - A specific Business (for example, an organization or a
3940
+ company) is used as reference to a participant. The BUSINESS identifier
3941
+ can be in any format. To make a transaction connected to a specific
3942
+ username or bill number in a Business, the PartySubIdOrType element
3943
+ should be used.
3944
+
3945
+ - DEVICE - A specific device (for example, a POS or ATM) ID connected to
3946
+ a specific business or organization is used as reference to a Party. For
3947
+ referencing a specific device under a specific business or organization,
3948
+ use the PartySubIdOrType element.
3949
+
3950
+ - ACCOUNT_ID - A bank account number or FSP account ID should be used as
3951
+ reference to a participant. The ACCOUNT_ID identifier can be in any
3952
+ format, as formats can greatly differ depending on country and FSP.
3953
+
3954
+ - IBAN - A bank account number or FSP account ID is used as reference to
3955
+ a participant. The IBAN identifier can consist of up to 34 alphanumeric
3956
+ characters and should be entered without whitespace.
3957
+
3958
+ - ALIAS An alias is used as reference to a participant. The alias should
3959
+ be created in the FSP as an alternative reference to an account owner.
3960
+ Another example of an alias is a username in the FSP system. The ALIAS
3961
+ identifier can be in any format. It is also possible to use the
3962
+ PartySubIdOrType element for identifying an account under an Alias
3963
+ defined by the PartyIdentifier.
3964
+ PartyIdentifier:
3965
+ title: PartyIdentifier
3966
+ type: string
3967
+ minLength: 1
3968
+ maxLength: 128
3969
+ description: Identifier of the Party.
3970
+ example: "16135551212"
3971
+ PartyName:
3972
+ title: PartyName
3973
+ type: string
3974
+ minLength: 1
3975
+ maxLength: 128
3976
+ description: Name of the Party. Could be a real name or a nickname.
3977
+ PartyPersonalInfo:
3978
+ title: PartyPersonalInfo
3979
+ type: object
3980
+ description: Data model for the complex type PartyPersonalInfo.
3981
+ properties:
3982
+ complexName:
3983
+ $ref: "#/components/schemas/PartyComplexName"
3984
+ dateOfBirth:
3985
+ $ref: "#/components/schemas/DateOfBirth"
3986
+ kycInformation:
3987
+ $ref: "#/components/schemas/KYCInformation"
3988
+ PartyResult:
3989
+ title: PartyResult
3990
+ type: object
3991
+ description: Data model for the complex type PartyResult.
3992
+ properties:
3993
+ partyId:
3994
+ $ref: "#/components/schemas/PartyIdInfo"
3995
+ errorInformation:
3996
+ $ref: "#/components/schemas/ErrorInformation"
3997
+ required:
3998
+ - partyId
3999
+ PartySubIdOrType:
4000
+ title: PartySubIdOrType
4001
+ type: string
4002
+ minLength: 1
4003
+ maxLength: 128
4004
+ description: >-
4005
+ Either a sub-identifier of a PartyIdentifier, or a sub-type of the
4006
+ PartyIdType, normally a PersonalIdentifierType.
4007
+ PersonalIdentifierType:
4008
+ title: PersonalIdentifierType
4009
+ type: string
4010
+ enum:
4011
+ - PASSPORT
4012
+ - NATIONAL_REGISTRATION
4013
+ - DRIVING_LICENSE
4014
+ - ALIEN_REGISTRATION
4015
+ - NATIONAL_ID_CARD
4016
+ - EMPLOYER_ID
4017
+ - TAX_ID_NUMBER
4018
+ - SENIOR_CITIZENS_CARD
4019
+ - MARRIAGE_CERTIFICATE
4020
+ - HEALTH_CARD
4021
+ - VOTERS_ID
4022
+ - UNITED_NATIONS
4023
+ - OTHER_ID
4024
+ description: >-
4025
+ Below are the allowed values for the enumeration.
4026
+
4027
+ - PASSPORT - A passport number is used as reference to a Party.
4028
+
4029
+ - NATIONAL_REGISTRATION - A national registration number is used as
4030
+ reference to a Party.
4031
+
4032
+ - DRIVING_LICENSE - A driving license is used as reference to a Party.
4033
+
4034
+ - ALIEN_REGISTRATION - An alien registration number is used as reference
4035
+ to a Party.
4036
+
4037
+ - NATIONAL_ID_CARD - A national ID card number is used as reference to a
4038
+ Party.
4039
+
4040
+ - EMPLOYER_ID - A tax identification number is used as reference to a
4041
+ Party.
4042
+
4043
+ - TAX_ID_NUMBER - A tax identification number is used as reference to a
4044
+ Party.
4045
+
4046
+ - SENIOR_CITIZENS_CARD - A senior citizens card number is used as
4047
+ reference to a Party.
4048
+
4049
+ - MARRIAGE_CERTIFICATE - A marriage certificate number is used as
4050
+ reference to a Party.
4051
+
4052
+ - HEALTH_CARD - A health card number is used as reference to a Party.
4053
+
4054
+ - VOTERS_ID - A voter’s identification number is used as reference to a
4055
+ Party.
4056
+
4057
+ - UNITED_NATIONS - An UN (United Nations) number is used as reference to
4058
+ a Party.
4059
+
4060
+ - OTHER_ID - Any other type of identification type number is used as
4061
+ reference to a Party.
4062
+ QRCODE:
4063
+ title: QRCODE
4064
+ type: string
4065
+ minLength: 1
4066
+ maxLength: 64
4067
+ description: QR code used as a One Time Password.
4068
+ QuotesIDPutResponse:
4069
+ title: QuotesIDPutResponse
4070
+ type: object
4071
+ description: The object sent in the PUT /quotes/{ID} callback.
4072
+ properties:
4073
+ transferAmount:
4074
+ $ref: "#/components/schemas/Money"
4075
+ payeeReceiveAmount:
4076
+ $ref: "#/components/schemas/Money"
4077
+ payeeFspFee:
4078
+ $ref: "#/components/schemas/Money"
4079
+ payeeFspCommission:
4080
+ $ref: "#/components/schemas/Money"
4081
+ expiration:
4082
+ $ref: "#/components/schemas/DateTime"
4083
+ geoCode:
4084
+ $ref: "#/components/schemas/GeoCode"
4085
+ ilpPacket:
4086
+ $ref: "#/components/schemas/IlpPacket"
4087
+ condition:
4088
+ $ref: "#/components/schemas/IlpCondition"
4089
+ extensionList:
4090
+ $ref: "#/components/schemas/ExtensionList"
4091
+ required:
4092
+ - transferAmount
4093
+ - expiration
4094
+ - ilpPacket
4095
+ - condition
4096
+ QuotesPostRequest:
4097
+ title: QuotesPostRequest
4098
+ type: object
4099
+ description: The object sent in the POST /quotes request.
4100
+ properties:
4101
+ quoteId:
4102
+ $ref: "#/components/schemas/CorrelationId"
4103
+ transactionId:
4104
+ $ref: "#/components/schemas/CorrelationId"
4105
+ transactionRequestId:
4106
+ $ref: "#/components/schemas/CorrelationId"
4107
+ payee:
4108
+ $ref: "#/components/schemas/Party"
4109
+ payer:
4110
+ $ref: "#/components/schemas/Party"
4111
+ amountType:
4112
+ $ref: "#/components/schemas/AmountType"
4113
+ amount:
4114
+ $ref: "#/components/schemas/Money"
4115
+ fees:
4116
+ $ref: "#/components/schemas/Money"
4117
+ transactionType:
4118
+ $ref: "#/components/schemas/TransactionType"
4119
+ converter:
4120
+ allOf:
4121
+ - $ref: "#/components/schemas/CurrencyConverter"
4122
+ - description: >-
4123
+ An optional field which will allow the payer DFSP to specify
4124
+ which DFSP it wants to undertake currency conversion. This is
4125
+ useful incase of if the sender wants the recipient to receive a
4126
+ specified amount of the target currency, but the payer DFSP does
4127
+ not want to undertake the currency conversion. In this case, the
4128
+ amount of the transfer would be expressed in the target currency
4129
+ and the amountType would be set to RECEIVE.
4130
+ currencyConversion:
4131
+ allOf:
4132
+ - $ref: "#/components/schemas/FxRate"
4133
+ - description: >-
4134
+ Used by the debtor party if it wants to share information about
4135
+ the currency conversion it proposes to make; or if it is
4136
+ required by scheme rules to share this information. This object
4137
+ contains the amount of the transfer in the source and target
4138
+ currencies, but does not identify the FXP being used.
4139
+ geoCode:
4140
+ $ref: "#/components/schemas/GeoCode"
4141
+ note:
4142
+ $ref: "#/components/schemas/Note"
4143
+ expiration:
4144
+ $ref: "#/components/schemas/DateTime"
4145
+ extensionList:
4146
+ $ref: "#/components/schemas/ExtensionList"
4147
+ required:
4148
+ - quoteId
4149
+ - transactionId
4150
+ - payee
4151
+ - payer
4152
+ - amountType
4153
+ - amount
4154
+ - transactionType
4155
+ Refund:
4156
+ title: Refund
4157
+ type: object
4158
+ description: Data model for the complex type Refund.
4159
+ properties:
4160
+ originalTransactionId:
4161
+ $ref: "#/components/schemas/CorrelationId"
4162
+ refundReason:
4163
+ $ref: "#/components/schemas/RefundReason"
4164
+ required:
4165
+ - originalTransactionId
4166
+ RefundReason:
4167
+ title: RefundReason
4168
+ type: string
4169
+ minLength: 1
4170
+ maxLength: 128
4171
+ description: Reason for the refund.
4172
+ example: Free text indicating reason for the refund.
4173
+ ServicesFXPPutResponse:
4174
+ title: ServicesFXPPutResponse
4175
+ type: object
4176
+ description: The object sent in the PUT /services/FXP callback.
4177
+ properties:
4178
+ providers:
4179
+ type: array
4180
+ description: >-
4181
+ The FSP Id(s) of the participant(s) who offer currency conversion
4182
+ services.
4183
+ items:
4184
+ $ref: "#/components/schemas/FspId"
4185
+ minItems: 0
4186
+ maxItems: 16
4187
+ required:
4188
+ - providers
4189
+ ServicesFXPSourceCurrencyTargetCurrencyPutResponse:
4190
+ title: ServicesFXPSourceCurrencyTargetCurrencyPutResponse
4191
+ type: object
4192
+ description: >-
4193
+ The object sent in the PUT
4194
+ /services/FXP/{SourceCurrency}/{TargetCurrency} callback.
4195
+ properties:
4196
+ providers:
4197
+ type: array
4198
+ description: >-
4199
+ The FSP Id(s) of the participant(s) who offer currency conversion
4200
+ services.
4201
+ items:
4202
+ $ref: "#/components/schemas/FspId"
4203
+ minItems: 0
4204
+ maxItems: 16
4205
+ required:
4206
+ - providers
4207
+ TokenCode:
4208
+ title: TokenCode
4209
+ type: string
4210
+ pattern: ^[0-9a-zA-Z]{4,32}$
4211
+ description: >-
4212
+ The API data type TokenCode is a JSON String between 4 and 32
4213
+ characters, consisting of digits or upper- or lowercase characters from
4214
+ a to z.
4215
+ Transaction:
4216
+ title: Transaction
4217
+ type: object
4218
+ description: >-
4219
+ Data model for the complex type Transaction. The Transaction type is
4220
+ used to carry end-to-end data between the Payer FSP and the Payee FSP in
4221
+ the ILP Packet. Both the transactionId and the quoteId in the data model
4222
+ are decided by the Payer FSP in the POST /quotes request.
4223
+ properties:
4224
+ transactionId:
4225
+ $ref: "#/components/schemas/CorrelationId"
4226
+ quoteId:
4227
+ $ref: "#/components/schemas/CorrelationId"
4228
+ payee:
4229
+ $ref: "#/components/schemas/Party"
4230
+ payer:
4231
+ $ref: "#/components/schemas/Party"
4232
+ amount:
4233
+ $ref: "#/components/schemas/Money"
4234
+ payeeReceiveAmount:
4235
+ allOf:
4236
+ - $ref: "#/components/schemas/Money"
4237
+ - description: The amount that the beneficiary will receive.
4238
+ converter:
4239
+ allOf:
4240
+ - $ref: "#/components/schemas/CurrencyConverter"
4241
+ - description: >-
4242
+ An optional field which will allow the payer DFSP to specify
4243
+ which DFSP it wants to undertake currency conversion. This is
4244
+ useful incase of if the sender wants the recipient to receive a
4245
+ specified amount of the target currency, but the payer DFSP does
4246
+ not want to undertake the currency conversion. In this case, the
4247
+ amount of the transfer would be expressed in the target currency
4248
+ and the amountType would be set to RECEIVE.
4249
+ currencyConversion:
4250
+ allOf:
4251
+ - $ref: "#/components/schemas/FxRate"
4252
+ - description: >-
4253
+ Used by the debtor party if it wants to share information about
4254
+ the currency conversion it proposes to make; or if it is
4255
+ required by scheme rules to share this information. This object
4256
+ contains the amount of the transfer in the source and target
4257
+ currencies, but does not identify the FXP being used.
4258
+ transactionType:
4259
+ $ref: "#/components/schemas/TransactionType"
4260
+ note:
4261
+ $ref: "#/components/schemas/Note"
4262
+ extensionList:
4263
+ $ref: "#/components/schemas/ExtensionList"
4264
+ required:
4265
+ - transactionId
4266
+ - quoteId
4267
+ - payee
4268
+ - payer
4269
+ - amount
4270
+ - transactionType
4271
+ TransactionInitiator:
4272
+ title: TransactionInitiator
4273
+ type: string
4274
+ enum:
4275
+ - PAYER
4276
+ - PAYEE
4277
+ description: >-
4278
+ Below are the allowed values for the enumeration.
4279
+
4280
+ - PAYER - Sender of funds is initiating the transaction. The account to
4281
+ send from is either owned by the Payer or is connected to the Payer in
4282
+ some way.
4283
+
4284
+ - PAYEE - Recipient of the funds is initiating the transaction by
4285
+ sending a transaction request. The Payer must approve the transaction,
4286
+ either automatically by a pre-generated OTP or by pre-approval of the
4287
+ Payee, or by manually approving in his or her own Device.
4288
+ example: PAYEE
4289
+ TransactionInitiatorType:
4290
+ title: TransactionInitiatorType
4291
+ type: string
4292
+ enum:
4293
+ - CONSUMER
4294
+ - AGENT
4295
+ - BUSINESS
4296
+ - DEVICE
4297
+ description: |-
4298
+ Below are the allowed values for the enumeration.
4299
+ - CONSUMER - Consumer is the initiator of the transaction.
4300
+ - AGENT - Agent is the initiator of the transaction.
4301
+ - BUSINESS - Business is the initiator of the transaction.
4302
+ - DEVICE - Device is the initiator of the transaction.
4303
+ example: CONSUMER
4304
+ TransactionRequestState:
4305
+ title: TransactionRequestState
4306
+ type: string
4307
+ enum:
4308
+ - RECEIVED
4309
+ - PENDING
4310
+ - ACCEPTED
4311
+ - REJECTED
4312
+ description: |-
4313
+ Below are the allowed values for the enumeration.
4314
+ - RECEIVED - Payer FSP has received the transaction from the Payee FSP.
4315
+ - PENDING - Payer FSP has sent the transaction request to the Payer.
4316
+ - ACCEPTED - Payer has approved the transaction.
4317
+ - REJECTED - Payer has rejected the transaction.
4318
+ example: RECEIVED
4319
+ TransactionRequestsIDPutResponse:
4320
+ title: TransactionRequestsIDPutResponse
4321
+ type: object
4322
+ description: The object sent in the PUT /transactionRequests/{ID} callback.
4323
+ properties:
4324
+ transactionId:
4325
+ $ref: "#/components/schemas/CorrelationId"
4326
+ transactionRequestState:
4327
+ $ref: "#/components/schemas/TransactionRequestState"
4328
+ extensionList:
4329
+ $ref: "#/components/schemas/ExtensionList"
4330
+ required:
4331
+ - transactionRequestState
4332
+ TransactionRequestsPostRequest:
4333
+ title: TransactionRequestsPostRequest
4334
+ type: object
4335
+ description: The object sent in the POST /transactionRequests request.
4336
+ properties:
4337
+ transactionRequestId:
4338
+ $ref: "#/components/schemas/CorrelationId"
4339
+ payee:
4340
+ $ref: "#/components/schemas/Party"
4341
+ payer:
4342
+ $ref: "#/components/schemas/PartyIdInfo"
4343
+ amount:
4344
+ $ref: "#/components/schemas/Money"
4345
+ transactionType:
4346
+ $ref: "#/components/schemas/TransactionType"
4347
+ note:
4348
+ $ref: "#/components/schemas/Note"
4349
+ geoCode:
4350
+ $ref: "#/components/schemas/GeoCode"
4351
+ authenticationType:
4352
+ $ref: "#/components/schemas/AuthenticationType"
4353
+ expiration:
4354
+ $ref: "#/components/schemas/DateTime"
4355
+ extensionList:
4356
+ $ref: "#/components/schemas/ExtensionList"
4357
+ required:
4358
+ - transactionRequestId
4359
+ - payee
4360
+ - payer
4361
+ - amount
4362
+ - transactionType
4363
+ TransactionScenario:
4364
+ title: TransactionScenario
4365
+ type: string
4366
+ enum:
4367
+ - DEPOSIT
4368
+ - WITHDRAWAL
4369
+ - TRANSFER
4370
+ - PAYMENT
4371
+ - REFUND
4372
+ description: >-
4373
+ Below are the allowed values for the enumeration.
4374
+
4375
+ - DEPOSIT - Used for performing a Cash-In (deposit) transaction. In a
4376
+ normal scenario, electronic funds are transferred from a Business
4377
+ account to a Consumer account, and physical cash is given from the
4378
+ Consumer to the Business User.
4379
+
4380
+ - WITHDRAWAL - Used for performing a Cash-Out (withdrawal) transaction.
4381
+ In a normal scenario, electronic funds are transferred from a Consumer’s
4382
+ account to a Business account, and physical cash is given from the
4383
+ Business User to the Consumer.
4384
+
4385
+ - TRANSFER - Used for performing a P2P (Peer to Peer, or Consumer to
4386
+ Consumer) transaction.
4387
+
4388
+ - PAYMENT - Usually used for performing a transaction from a Consumer to
4389
+ a Merchant or Organization, but could also be for a B2B (Business to
4390
+ Business) payment. The transaction could be online for a purchase in an
4391
+ Internet store, in a physical store where both the Consumer and Business
4392
+ User are present, a bill payment, a donation, and so on.
4393
+
4394
+ - REFUND - Used for performing a refund of transaction.
4395
+ example: DEPOSIT
4396
+ TransactionState:
4397
+ title: TransactionState
4398
+ type: string
4399
+ enum:
4400
+ - RECEIVED
4401
+ - PENDING
4402
+ - COMPLETED
4403
+ - REJECTED
4404
+ description: |-
4405
+ Below are the allowed values for the enumeration.
4406
+ - RECEIVED - Payee FSP has received the transaction from the Payer FSP.
4407
+ - PENDING - Payee FSP has validated the transaction.
4408
+ - COMPLETED - Payee FSP has successfully performed the transaction.
4409
+ - REJECTED - Payee FSP has failed to perform the transaction.
4410
+ example: RECEIVED
4411
+ TransactionSubScenario:
4412
+ title: TransactionSubScenario
4413
+ type: string
4414
+ pattern: ^[A-Z_]{1,32}$
4415
+ description: >-
4416
+ Possible sub-scenario, defined locally within the scheme (UndefinedEnum
4417
+ Type).
4418
+ example: LOCALLY_DEFINED_SUBSCENARIO
4419
+ TransactionType:
4420
+ title: TransactionType
4421
+ type: object
4422
+ description: Data model for the complex type TransactionType.
4423
+ properties:
4424
+ scenario:
4425
+ $ref: "#/components/schemas/TransactionScenario"
4426
+ subScenario:
4427
+ $ref: "#/components/schemas/TransactionSubScenario"
4428
+ initiator:
4429
+ $ref: "#/components/schemas/TransactionInitiator"
4430
+ initiatorType:
4431
+ $ref: "#/components/schemas/TransactionInitiatorType"
4432
+ refundInfo:
4433
+ $ref: "#/components/schemas/Refund"
4434
+ balanceOfPayments:
4435
+ $ref: "#/components/schemas/BalanceOfPayments"
4436
+ required:
4437
+ - scenario
4438
+ - initiator
4439
+ - initiatorType
4440
+ TransactionsIDPutResponse:
4441
+ title: TransactionsIDPutResponse
4442
+ type: object
4443
+ description: The object sent in the PUT /transactions/{ID} callback.
4444
+ properties:
4445
+ completedTimestamp:
4446
+ $ref: "#/components/schemas/DateTime"
4447
+ transactionState:
4448
+ $ref: "#/components/schemas/TransactionState"
4449
+ code:
4450
+ $ref: "#/components/schemas/Code"
4451
+ extensionList:
4452
+ $ref: "#/components/schemas/ExtensionList"
4453
+ required:
4454
+ - transactionState
4455
+ TransferState:
4456
+ title: TransferState
4457
+ type: string
4458
+ enum:
4459
+ - RECEIVED
4460
+ - RESERVED
4461
+ - COMMITTED
4462
+ - ABORTED
4463
+ description: >-
4464
+ Below are the allowed values for the enumeration.
4465
+
4466
+ - RECEIVED - Next ledger has received the transfer.
4467
+
4468
+ - RESERVED - Next ledger has reserved the transfer.
4469
+
4470
+ - COMMITTED - Next ledger has successfully performed the transfer.
4471
+
4472
+ - ABORTED - Next ledger has aborted the transfer due to a rejection or
4473
+ failure to perform the transfer.
4474
+ example: RESERVED
4475
+ TransfersIDPatchResponse:
4476
+ title: TransfersIDPatchResponse
4477
+ type: object
4478
+ description: PATCH /transfers/{ID} object
4479
+ properties:
4480
+ completedTimestamp:
4481
+ $ref: "#/components/schemas/DateTime"
4482
+ transferState:
4483
+ $ref: "#/components/schemas/TransferState"
4484
+ extensionList:
4485
+ $ref: "#/components/schemas/ExtensionList"
4486
+ required:
4487
+ - completedTimestamp
4488
+ - transferState
4489
+ TransfersIDPutResponse:
4490
+ title: TransfersIDPutResponse
4491
+ type: object
4492
+ description: The object sent in the PUT /transfers/{ID} callback.
4493
+ properties:
4494
+ fulfilment:
4495
+ $ref: "#/components/schemas/IlpFulfilment"
4496
+ completedTimestamp:
4497
+ $ref: "#/components/schemas/DateTime"
4498
+ transferState:
4499
+ $ref: "#/components/schemas/TransferState"
4500
+ extensionList:
4501
+ $ref: "#/components/schemas/ExtensionList"
4502
+ required:
4503
+ - transferState
4504
+ TransfersPostRequest:
4505
+ title: TransfersPostRequest
4506
+ type: object
4507
+ description: The object sent in the POST /transfers request.
4508
+ properties:
4509
+ transferId:
4510
+ $ref: "#/components/schemas/CorrelationId"
4511
+ payeeFsp:
4512
+ $ref: "#/components/schemas/FspId"
4513
+ payerFsp:
4514
+ $ref: "#/components/schemas/FspId"
4515
+ amount:
4516
+ $ref: "#/components/schemas/Money"
4517
+ ilpPacket:
4518
+ $ref: "#/components/schemas/IlpPacket"
4519
+ condition:
4520
+ $ref: "#/components/schemas/IlpCondition"
4521
+ expiration:
4522
+ $ref: "#/components/schemas/DateTime"
4523
+ extensionList:
4524
+ $ref: "#/components/schemas/ExtensionList"
4525
+ required:
4526
+ - transferId
4527
+ - payeeFsp
4528
+ - payerFsp
4529
+ - amount
4530
+ - ilpPacket
4531
+ - condition
4532
+ - expiration
4533
+ U2FPIN:
4534
+ title: U2FPIN
4535
+ type: string
4536
+ pattern: ^\S{1,64}$
4537
+ minLength: 1
4538
+ maxLength: 64
4539
+ description: >
4540
+ U2F challenge-response, where payer FSP verifies if the response
4541
+ provided by end-user device matches the previously registered key.
4542
+ U2FPinValue:
4543
+ title: U2FPinValue
4544
+ type: object
4545
+ description: >
4546
+ U2F challenge-response, where payer FSP verifies if the response
4547
+ provided by end-user device matches the previously registered key.
4548
+ properties:
4549
+ pinValue:
4550
+ allOf:
4551
+ - $ref: "#/components/schemas/U2FPIN"
4552
+ description: U2F challenge-response.
4553
+ counter:
4554
+ allOf:
4555
+ - $ref: "#/components/schemas/Integer"
4556
+ description: >-
4557
+ Sequential counter used for cloning detection. Present only for U2F
4558
+ authentication.
4559
+ required:
4560
+ - pinValue
4561
+ - counter
4562
+ UndefinedEnum:
4563
+ title: UndefinedEnum
4564
+ type: string
4565
+ pattern: ^[A-Z_]{1,32}$
4566
+ description: >-
4567
+ The API data type UndefinedEnum is a JSON String consisting of 1 to 32
4568
+ uppercase characters including an underscore character (_).
4569
+ parameters:
4570
+ Accept:
4571
+ name: Accept
4572
+ in: header
4573
+ required: true
4574
+ schema:
4575
+ type: string
4576
+ description: >-
4577
+ The `Accept` header field indicates the version of the API the client
4578
+ would like the server to use.
4579
+ Content-Length:
4580
+ name: Content-Length
4581
+ in: header
4582
+ required: false
4583
+ schema:
4584
+ type: integer
4585
+ description: >-
4586
+ The `Content-Length` header field indicates the anticipated size of the
4587
+ payload body. Only sent if there is a body.
4588
+
4589
+
4590
+ **Note:** The API supports a maximum size of 5242880 bytes (5
4591
+ Megabytes).
4592
+ Content-Type:
4593
+ name: Content-Type
4594
+ in: header
4595
+ schema:
4596
+ type: string
4597
+ required: true
4598
+ description: >-
4599
+ The `Content-Type` header indicates the specific version of the API used
4600
+ to send the payload body.
4601
+ Date:
4602
+ name: Date
4603
+ in: header
4604
+ schema:
4605
+ type: string
4606
+ required: true
4607
+ description: The `Date` header field indicates the date when the request was sent.
4608
+ FSPIOP-Destination:
4609
+ name: FSPIOP-Destination
4610
+ in: header
4611
+ schema:
4612
+ type: string
4613
+ required: false
4614
+ description: >-
4615
+ The `FSPIOP-Destination` header field is a non-HTTP standard field used
4616
+ by the API for HTTP header based routing of requests and responses to
4617
+ the destination. The field must be set by the original sender of the
4618
+ request if the destination is known (valid for all services except GET
4619
+ /parties) so that any entities between the client and the server do not
4620
+ need to parse the payload for routing purposes. If the destination is
4621
+ not known (valid for service GET /parties), the field should be left
4622
+ empty.
4623
+ FSPIOP-Encryption:
4624
+ name: FSPIOP-Encryption
4625
+ in: header
4626
+ schema:
4627
+ type: string
4628
+ required: false
4629
+ description: >-
4630
+ The `FSPIOP-Encryption` header field is a non-HTTP standard field used
4631
+ by the API for applying end-to-end encryption of the request.
4632
+ FSPIOP-HTTP-Method:
4633
+ name: FSPIOP-HTTP-Method
4634
+ in: header
4635
+ schema:
4636
+ type: string
4637
+ required: false
4638
+ description: >-
4639
+ The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used
4640
+ by the API for signature verification, should contain the service HTTP
4641
+ method. Required if signature verification is used, for more
4642
+ information, see [the API Signature
4643
+ document](https://github.com/mojaloop/docs/tree/main/Specification%20Document%20Set).
4644
+ FSPIOP-Signature:
4645
+ name: FSPIOP-Signature
4646
+ in: header
4647
+ schema:
4648
+ type: string
4649
+ required: false
4650
+ description: >-
4651
+ The `FSPIOP-Signature` header field is a non-HTTP standard field used by
4652
+ the API for applying an end-to-end request signature.
4653
+ FSPIOP-Source:
4654
+ name: FSPIOP-Source
4655
+ in: header
4656
+ schema:
4657
+ type: string
4658
+ required: true
4659
+ description: >-
4660
+ The `FSPIOP-Source` header field is a non-HTTP standard field used by
4661
+ the API for identifying the sender of the HTTP request. The field should
4662
+ be set by the original sender of the request. Required for routing and
4663
+ signature verification (see header field `FSPIOP-Signature`).
4664
+ FSPIOP-URI:
4665
+ name: FSPIOP-URI
4666
+ in: header
4667
+ schema:
4668
+ type: string
4669
+ required: false
4670
+ description: >-
4671
+ The `FSPIOP-URI` header field is a non-HTTP standard field used by the
4672
+ API for signature verification, should contain the service URI. Required
4673
+ if signature verification is used, for more information, see [the API
4674
+ Signature
4675
+ document](https://github.com/mojaloop/docs/tree/main/Specification%20Document%20Set).
4676
+ ID:
4677
+ name: ID
4678
+ in: path
4679
+ required: true
4680
+ schema:
4681
+ type: string
4682
+ description: The identifier value.
4683
+ SourceCurrency:
4684
+ name: SourceCurrency
4685
+ in: path
4686
+ required: true
4687
+ schema:
4688
+ type: string
4689
+ description: ISO 4217 currency code for the source currency.
4690
+ SubId:
4691
+ name: SubId
4692
+ in: path
4693
+ required: true
4694
+ schema:
4695
+ type: string
4696
+ description: >-
4697
+ A sub-identifier of the party identifier, or a sub-type of the party
4698
+ identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`.
4699
+ TargetCurrency:
4700
+ name: TargetCurrency
4701
+ in: path
4702
+ required: true
4703
+ schema:
4704
+ type: string
4705
+ description: ISO 4217 currency code for the target currency.
4706
+ Type:
4707
+ name: Type
4708
+ in: path
4709
+ required: true
4710
+ schema:
4711
+ type: string
4712
+ description: The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`.
4713
+ X-Forwarded-For:
4714
+ name: X-Forwarded-For
4715
+ in: header
4716
+ schema:
4717
+ type: string
4718
+ required: false
4719
+ description: >-
4720
+ The `X-Forwarded-For` header field is an unofficially accepted standard
4721
+ used for informational purposes of the originating client IP address, as
4722
+ a request might pass multiple proxies, firewalls, and so on. Multiple
4723
+ `X-Forwarded-For` values should be expected and supported by
4724
+ implementers of the API.
4725
+
4726
+
4727
+ **Note:** An alternative to `X-Forwarded-For` is defined in [RFC
4728
+ 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC
4729
+ 7239 is less-used and supported than `X-Forwarded-For`.
4730
+ responses:
4731
+ "200":
4732
+ description: OK
4733
+ "202":
4734
+ description: Accepted
4735
+ "400":
4736
+ description: Bad Request
4737
+ content:
4738
+ application/json:
4739
+ schema:
4740
+ $ref: "#/components/schemas/ErrorInformationResponse"
4741
+ headers:
4742
+ Content-Length:
4743
+ $ref: "#/components/headers/Content-Length"
4744
+ Content-Type:
4745
+ $ref: "#/components/headers/Content-Type"
4746
+ "401":
4747
+ description: Unauthorized
4748
+ content:
4749
+ application/json:
4750
+ schema:
4751
+ $ref: "#/components/schemas/ErrorInformationResponse"
4752
+ headers:
4753
+ Content-Length:
4754
+ $ref: "#/components/headers/Content-Length"
4755
+ Content-Type:
4756
+ $ref: "#/components/headers/Content-Type"
4757
+ "403":
4758
+ description: Forbidden
4759
+ content:
4760
+ application/json:
4761
+ schema:
4762
+ $ref: "#/components/schemas/ErrorInformationResponse"
4763
+ headers:
4764
+ Content-Length:
4765
+ $ref: "#/components/headers/Content-Length"
4766
+ Content-Type:
4767
+ $ref: "#/components/headers/Content-Type"
4768
+ "404":
4769
+ description: Not Found
4770
+ content:
4771
+ application/json:
4772
+ schema:
4773
+ $ref: "#/components/schemas/ErrorInformationResponse"
4774
+ headers:
4775
+ Content-Length:
4776
+ $ref: "#/components/headers/Content-Length"
4777
+ Content-Type:
4778
+ $ref: "#/components/headers/Content-Type"
4779
+ "405":
4780
+ description: Method Not Allowed
4781
+ content:
4782
+ application/json:
4783
+ schema:
4784
+ $ref: "#/components/schemas/ErrorInformationResponse"
4785
+ headers:
4786
+ Content-Length:
4787
+ $ref: "#/components/headers/Content-Length"
4788
+ Content-Type:
4789
+ $ref: "#/components/headers/Content-Type"
4790
+ "406":
4791
+ description: Not Acceptable
4792
+ content:
4793
+ application/json:
4794
+ schema:
4795
+ $ref: "#/components/schemas/ErrorInformationResponse"
4796
+ headers:
4797
+ Content-Length:
4798
+ $ref: "#/components/headers/Content-Length"
4799
+ Content-Type:
4800
+ $ref: "#/components/headers/Content-Type"
4801
+ "501":
4802
+ description: Not Implemented
4803
+ content:
4804
+ application/json:
4805
+ schema:
4806
+ $ref: "#/components/schemas/ErrorInformationResponse"
4807
+ headers:
4808
+ Content-Length:
4809
+ $ref: "#/components/headers/Content-Length"
4810
+ Content-Type:
4811
+ $ref: "#/components/headers/Content-Type"
4812
+ "503":
4813
+ description: Service Unavailable
4814
+ content:
4815
+ application/json:
4816
+ schema:
4817
+ $ref: "#/components/schemas/ErrorInformationResponse"
4818
+ headers:
4819
+ Content-Length:
4820
+ $ref: "#/components/headers/Content-Length"
4821
+ Content-Type:
4822
+ $ref: "#/components/headers/Content-Type"
4823
+ headers:
4824
+ Content-Length:
4825
+ required: false
4826
+ schema:
4827
+ type: integer
4828
+ description: >-
4829
+ The `Content-Length` header field indicates the anticipated size of the
4830
+ payload body. Only sent if there is a body.
4831
+
4832
+
4833
+ **Note:** The API supports a maximum size of 5242880 bytes (5
4834
+ Megabytes).
4835
+ Content-Type:
4836
+ schema:
4837
+ type: string
4838
+ required: true
4839
+ description: >-
4840
+ The `Content-Type` header indicates the specific version of the API used
4841
+ to send the payload body.