@mojaloop/api-snippets 17.2.5 → 17.3.0

package/docs/thirdparty-openapi3-snippets.yaml

@@ -19,10 +19,7 @@ servers:
 paths:
   /interface:
     post:
-      description: >-
-        Essential path to include schema definitions that are not used so that
-        these definitions get included into the openapi-cli bundle api
-        definition so that they get converted into typescript definitions.
+      description: Essential path to include schema definitions that are not used so that these definitions get included into the openapi-cli bundle api definition so that they get converted into typescript definitions.
       operationId: test
       requestBody:
         content:
@@ -32,8 +29,7 @@ paths:
                 - $ref: '#/components/schemas/ParticipantsIDPutResponse'
                 - $ref: '#/components/schemas/PartiesTypeIDPutResponse'
                 - $ref: '#/components/schemas/QuotesIDPutResponse'
-                - $ref: >-
-                    #/components/schemas/ThirdpartyRequestsTransactionsIDPatchResponse
+                - $ref: '#/components/schemas/ThirdpartyRequestsTransactionsIDPatchResponse'
                 - $ref: '#/components/schemas/AuthorizationResponseType'
                 - $ref: '#/components/schemas/ConsentStatusIssued'
                 - $ref: '#/components/schemas/IlpFulfilment'
@@ -62,9 +58,8 @@ paths:
     get:
       operationId: GetAccountsByUserId
       summary: GetAccountsByUserId
-      description: >
-        The HTTP request `GET /accounts/{ID}` is used to retrieve the list of
-        potential accounts available for linking.
+      description: |
+        The HTTP request `GET /accounts/{ID}` is used to retrieve the list of potential accounts available for linking.
       tags:
         - accounts
         - sampled
@@ -90,9 +85,8 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     put:
-      description: >
-        The HTTP request `PUT /accounts/{ID}` is used to return the list of
-        potential accounts available for linking
+      description: |
+        The HTTP request `PUT /accounts/{ID}` is used to return the list of potential accounts available for linking
       operationId: UpdateAccountsByUserId
       summary: UpdateAccountsByUserId
       tags:
@@ -145,9 +139,8 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     put:
-      description: >
-        The HTTP request `PUT /accounts/{ID}/error` is used to return error
-        information
+      description: |
+        The HTTP request `PUT /accounts/{ID}/error` is used to return error information
       operationId: UpdateAccountsByUserIdError
       summary: UpdateAccountsByUserIdError
       tags:
@@ -206,9 +199,7 @@ paths:
           $ref: '#/components/responses/503'
       operationId: HealthGet
       summary: Health check endpoint
-      description: >-
-        The HTTP request GET /health is used to return the current status of the
-        API.
+      description: The HTTP request GET /health is used to return the current status of the API.
   /metrics:
     get:
       tags:
@@ -252,12 +243,9 @@ paths:
         - sampled
       operationId: CreateConsentRequest
       summary: CreateConsentRequest
-      description: >
-        The HTTP request **POST /consentRequests** is used to request a DFSP to
-        grant access to one or more
-
-        accounts owned by a customer of the DFSP for the PISP who sends the
-        request.
+      description: |
+        The HTTP request **POST /consentRequests** is used to request a DFSP to grant access to one or more
+        accounts owned by a customer of the DFSP for the PISP who sends the request.
       parameters:
         - $ref: '#/components/parameters/Accept'
         - $ref: '#/components/parameters/Content-Length'
@@ -302,13 +290,9 @@ paths:
     get:
       operationId: GetConsentRequestsById
       summary: GetConsentRequestsById
-      description: >
-        The HTTP request `GET /consentRequests/{ID}` is used to get information
-        about a previously
-
-        requested consent. The *{ID}* in the URI should contain the
-        consentRequestId that was assigned to the
-
+      description: |
+        The HTTP request `GET /consentRequests/{ID}` is used to get information about a previously
+        requested consent. The *{ID}* in the URI should contain the consentRequestId that was assigned to the
         request by the PISP when the PISP originated the request.
       tags:
         - consentRequests
@@ -340,28 +324,15 @@ paths:
         - sampled
       operationId: UpdateConsentRequest
       summary: UpdateConsentRequest
-      description: >
-        A DFSP uses this callback to (1) inform the PISP that the consentRequest
-        has been accepted,
-
-        and (2) communicate to the PISP which `authChannel` it should use to
-        authenticate their user
-
+      description: |
+        A DFSP uses this callback to (1) inform the PISP that the consentRequest has been accepted,
+        and (2) communicate to the PISP which `authChannel` it should use to authenticate their user
         with.
 
-
-        When a PISP requests a series of permissions from a DFSP on behalf of a
-        DFSP’s customer, not all
-
-        the permissions requested may be granted by the DFSP. Conversely, the
-        out-of-band authorization
-
-        process  may result in additional privileges being granted by the
-        account holder to the PISP. The
-
-        **PUT /consentRequests/**_{ID}_ resource returns the current state of
-        the permissions relating to a
-
+        When a PISP requests a series of permissions from a DFSP on behalf of a DFSP’s customer, not all
+        the permissions requested may be granted by the DFSP. Conversely, the out-of-band authorization
+        process  may result in additional privileges being granted by the account holder to the PISP. The
+        **PUT /consentRequests/**_{ID}_ resource returns the current state of the permissions relating to a
         particular authorization request.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
@@ -398,10 +369,8 @@ paths:
         - sampled
       operationId: PatchConsentRequest
       summary: PatchConsentRequest
-      description: >
-        After the user completes an out-of-band authorization with the DFSP, the
-        PISP will receive a token which they can use to prove to the DFSP that
-        the user trusts this PISP.
+      description: |
+        After the user completes an out-of-band authorization with the DFSP, the PISP will receive a token which they can use to prove to the DFSP that the user trusts this PISP.
       parameters:
         - $ref: '#/components/parameters/Accept'
         - $ref: '#/components/parameters/Content-Length'
@@ -448,9 +417,8 @@ paths:
         - sampled
       operationId: NotifyErrorConsentRequests
       summary: NotifyErrorConsentRequests
-      description: >
-        DFSP responds to the PISP if something went wrong with validating an OTP
-        or secret.
+      description: |
+        DFSP responds to the PISP if something went wrong with validating an OTP or secret.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
       requestBody:
@@ -496,10 +464,8 @@ paths:
         - sampled
       operationId: PostConsents
       summary: PostConsents
-      description: >
-        The **POST /consents** request is used to request the creation of a
-        consent for interactions between a PISP and the DFSP who owns the
-        account which a PISP’s customer wants to allow the PISP access to.
+      description: |
+        The **POST /consents** request is used to request the creation of a consent for interactions between a PISP and the DFSP who owns the account which a PISP’s customer wants to allow the PISP access to.
       parameters:
         - $ref: '#/components/parameters/Accept'
         - $ref: '#/components/parameters/Content-Length'
@@ -543,11 +509,8 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     get:
-      description: >
-        The **GET /consents/**_{ID}_ resource allows a party to enquire after
-        the status of a consent. The *{ID}* used in the URI of the request
-        should be the consent request ID which was used to identify the consent
-        when it was created.
+      description: |
+        The **GET /consents/**_{ID}_ resource allows a party to enquire after the status of a consent. The *{ID}* used in the URI of the request should be the consent request ID which was used to identify the consent when it was created.
       tags:
         - consents
       operationId: GetConsent
@@ -574,12 +537,10 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     patch:
-      description: >
+      description: |
         The HTTP request `PATCH /consents/{ID}` is used
 
-
-        - In account linking in the Credential Registration phase. Used by a
-        DFSP
+        - In account linking in the Credential Registration phase. Used by a DFSP
           to notify a PISP a credential has been verified and registered with an
           Auth service.
 
@@ -624,16 +585,11 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     put:
-      description: >
-        The HTTP request `PUT /consents/{ID}` is used by the PISP and Auth
-        Service.
-
-
-        - Called by a `PISP` to after signing a challenge. Sent to an DFSP for
-        verification.
+      description: |
+        The HTTP request `PUT /consents/{ID}` is used by the PISP and Auth Service.
 
-        - Called by a `auth-service` to notify a DFSP that a credential has been
-        verified and registered.
+        - Called by a `PISP` to after signing a challenge. Sent to an DFSP for verification.
+        - Called by a `auth-service` to notify a DFSP that a credential has been verified and registered.
       tags:
         - consents
         - sampled
@@ -671,19 +627,12 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     delete:
-      description: >
+      description: |
         Used by PISP, DFSP
 
-
-        The **DELETE /consents/**_{ID}_ request is used to request the
-        revocation of a previously agreed consent.
-
-        For tracing and auditing purposes, the switch should be sure not to
-        delete the consent physically;
-
-        instead, information relating to the consent should be marked as deleted
-        and requests relating to the
-
+        The **DELETE /consents/**_{ID}_ request is used to request the revocation of a previously agreed consent.
+        For tracing and auditing purposes, the switch should be sure not to delete the consent physically;
+        instead, information relating to the consent should be marked as deleted and requests relating to the
         consent should not be honoured.
       operationId: DeleteConsentByID
       parameters:
@@ -727,9 +676,8 @@ paths:
         - sampled
       operationId: NotifyErrorConsents
       summary: NotifyErrorConsents
-      description: >
-        DFSP responds to the PISP if something went wrong with validating or
-        storing consent.
+      description: |
+        DFSP responds to the PISP if something went wrong with validating or storing consent.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
       requestBody:
@@ -770,12 +718,7 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     post:
-      description: >-
-        The HTTP request `POST /participants` is used to create information in
-        the server regarding the provided list of identities. This request
-        should be used for bulk creation of FSP information for more than one
-        Party. The optional currency parameter should indicate that each
-        provided Party supports the currency.
+      description: The HTTP request `POST /participants` is used to create information in the server regarding the provided list of identities. This request should be used for bulk creation of FSP information for more than one Party. The optional currency parameter should indicate that each provided Party supports the currency.
       summary: Create bulk participant information
       tags:
         - participants
@@ -823,9 +766,7 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     put:
-      description: >-
-        The callback `PUT /participants/{ID}` is used to inform the client of
-        the result of the creation of the provided list of identities.
+      description: The callback `PUT /participants/{ID}` is used to inform the client of the result of the creation of the provided list of identities.
       summary: Return bulk participant information
       tags:
         - participants
@@ -872,11 +813,7 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     put:
-      description: >-
-        If there is an error during FSP information creation in the server, the
-        error callback `PUT /participants/{ID}/error` is used. The `{ID}` in the
-        URI should contain the requestId that was used for the creation of the
-        participant information.
+      description: If there is an error during FSP information creation in the server, the error callback `PUT /participants/{ID}/error` is used. The `{ID}` in the URI should contain the requestId that was used for the creation of the participant information.
       summary: Return bulk participant information error
       tags:
         - participants
@@ -924,13 +861,7 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     post:
-      description: >-
-        The HTTP request `POST /participants/{Type}/{ID}` (or `POST
-        /participants/{Type}/{ID}/{SubId}`) is used to create information in the
-        server regarding the provided identity, defined by `{Type}`, `{ID}`, and
-        optionally `{SubId}` (for example, `POST /participants/MSISDN/123456789`
-        or `POST /participants/BUSINESS/shoecompany/employee1`). An
-        ExtensionList element has been added to this reqeust in version v1.1
+      description: The HTTP request `POST /participants/{Type}/{ID}` (or `POST /participants/{Type}/{ID}/{SubId}`) is used to create information in the server regarding the provided identity, defined by `{Type}`, `{ID}`, and optionally `{SubId}` (for example, `POST /participants/MSISDN/123456789` or `POST /participants/BUSINESS/shoecompany/employee1`). An ExtensionList element has been added to this reqeust in version v1.1
       summary: Create participant information
       tags:
         - participants
@@ -966,15 +897,7 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     get:
-      description: >-
-        The HTTP request `GET /participants/{Type}/{ID}` (or `GET
-        /participants/{Type}/{ID}/{SubId}`) is used to find out in which FSP the
-        requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}`,
-        is located (for example, `GET /participants/MSISDN/123456789`, or `GET
-        /participants/BUSINESS/shoecompany/employee1`). This HTTP request should
-        support a query string for filtering of currency. To use filtering of
-        currency, the HTTP request `GET /participants/{Type}/{ID}?currency=XYZ`
-        should be used, where `XYZ` is the requested currency.
+      description: The HTTP request `GET /participants/{Type}/{ID}` (or `GET /participants/{Type}/{ID}/{SubId}`) is used to find out in which FSP the requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}`, is located (for example, `GET /participants/MSISDN/123456789`, or `GET /participants/BUSINESS/shoecompany/employee1`). This HTTP request should support a query string for filtering of currency. To use filtering of currency, the HTTP request `GET /participants/{Type}/{ID}?currency=XYZ` should be used, where `XYZ` is the requested currency.
       summary: Look up participant information
       tags:
         - participants
@@ -1001,13 +924,7 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     put:
-      description: >-
-        The callback `PUT /participants/{Type}/{ID}` (or `PUT
-        /participants/{Type}/{ID}/{SubId}`) is used to inform the client of a
-        successful result of the lookup, creation, or deletion of the FSP
-        information related to the Party. If the FSP information is deleted, the
-        fspId element should be empty; otherwise the element should include the
-        FSP information for the Party.
+      description: The callback `PUT /participants/{Type}/{ID}` (or `PUT /participants/{Type}/{ID}/{SubId}`) is used to inform the client of a successful result of the lookup, creation, or deletion of the FSP information related to the Party. If the FSP information is deleted, the fspId element should be empty; otherwise the element should include the FSP information for the Party.
       summary: Return participant information
       tags:
         - participants
@@ -1041,20 +958,10 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     delete:
-      description: >-
-        The HTTP request `DELETE /participants/{Type}/{ID}` (or `DELETE
-        /participants/{Type}/{ID}/{SubId}`) is used to delete information in the
-        server regarding the provided identity, defined by `{Type}` and `{ID}`)
-        (for example, `DELETE /participants/MSISDN/123456789`), and optionally
-        `{SubId}`. This HTTP request should support a query string to delete FSP
-        information regarding a specific currency only. To delete a specific
-        currency only, the HTTP request `DELETE
-        /participants/{Type}/{ID}?currency=XYZ` should be used, where `XYZ` is
-        the requested currency.
-
+      description: |-
+        The HTTP request `DELETE /participants/{Type}/{ID}` (or `DELETE /participants/{Type}/{ID}/{SubId}`) is used to delete information in the server regarding the provided identity, defined by `{Type}` and `{ID}`) (for example, `DELETE /participants/MSISDN/123456789`), and optionally `{SubId}`. This HTTP request should support a query string to delete FSP information regarding a specific currency only. To delete a specific currency only, the HTTP request `DELETE /participants/{Type}/{ID}?currency=XYZ` should be used, where `XYZ` is the requested currency.
 
-        **Note:** The Account Lookup System should verify that it is the Party’s
-        current FSP that is deleting the FSP information.
+        **Note:** The Account Lookup System should verify that it is the Party’s current FSP that is deleting the FSP information.
       summary: Delete participant information
       tags:
         - participants
@@ -1094,11 +1001,7 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     put:
-      description: >-
-        If the server is unable to find, create or delete the associated FSP of
-        the provided identity, or another processing error occurred, the error
-        callback `PUT /participants/{Type}/{ID}/error` (or `PUT
-        /participants/{Type}/{ID}/{SubId}/error`) is used.
+      description: If the server is unable to find, create or delete the associated FSP of the provided identity, or another processing error occurred, the error callback `PUT /participants/{Type}/{ID}/error` (or `PUT /participants/{Type}/{ID}/{SubId}/error`) is used.
       summary: Return participant information error
       tags:
         - participants
@@ -1147,10 +1050,8 @@ paths:
     get:
       operationId: GetServicesByServiceType
       summary: GetServicesByServiceType
-      description: >
-        The HTTP request `GET /services/{ServiceType}` is used to retrieve the
-        list of participants
-
+      description: |
+        The HTTP request `GET /services/{ServiceType}` is used to retrieve the list of participants
         that support a specified service.
       parameters:
         - $ref: '#/components/parameters/Accept'
@@ -1177,10 +1078,8 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     put:
-      description: >
-        The HTTP request `PUT /services/{ServiceType}` is used to return list of
-        participants
-
+      description: |
+        The HTTP request `PUT /services/{ServiceType}` is used to return list of participants
         that support a specified service.
       operationId: PutServicesByServiceType
       summary: PutServicesByServiceType
@@ -1227,9 +1126,8 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     put:
-      description: >
-        The HTTP request `PUT /services/{ServiceType}/error` is used to return
-        error information
+      description: |
+        The HTTP request `PUT /services/{ServiceType}/error` is used to return error information
       operationId: PutServicesByServiceTypeAndError
       summary: PutServicesByServiceTypeAndError
       tags:
@@ -1277,9 +1175,7 @@ paths:
     post:
       operationId: ThirdpartyRequestsTransactionsPost
       summary: ThirdpartyRequestsTransactionsPost
-      description: >-
-        The HTTP request POST `/thirdpartyRequests/transactions` is used by a
-        PISP to initiate a 3rd party Transaction request with a DFSP
+      description: The HTTP request POST `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP
       tags:
         - thirdpartyRequests
         - sampled
@@ -1330,10 +1226,8 @@ paths:
         - sampled
       operationId: GetThirdpartyTransactionRequests
       summary: GetThirdpartyTransactionRequests
-      description: >
-        The HTTP request `GET /thirdpartyRequests/transactions/{ID}` is used to
-        request the
-
+      description: |
+        The HTTP request `GET /thirdpartyRequests/transactions/{ID}` is used to request the
         retrieval of a third party transaction request.
       parameters:
         - $ref: '#/components/parameters/Accept'
@@ -1362,13 +1256,10 @@ paths:
         - sampled
       operationId: UpdateThirdPartyTransactionRequests
       summary: UpdateThirdPartyTransactionRequests
-      description: >
-        The HTTP request `PUT /thirdpartyRequests/transactions/{ID}` is used by
-        the DFSP to inform the client about
-
+      description: |
+        The HTTP request `PUT /thirdpartyRequests/transactions/{ID}` is used by the DFSP to inform the client about
         the status of a previously requested thirdparty transaction request.
 
-
         Switch(Thirdparty API Adapter) -> PISP
       parameters:
         - $ref: '#/components/parameters/Content-Length'
@@ -1402,13 +1293,10 @@ paths:
     patch:
       operationId: NotifyThirdpartyTransactionRequests
       summary: NotifyThirdpartyTransactionRequests
-      description: >
-        The HTTP request `PATCH /thirdpartyRequests/transactions/{ID}` is used
-        to
-
+      description: |
+        The HTTP request `PATCH /thirdpartyRequests/transactions/{ID}` is used to
         notify a thirdparty of the outcome of a transaction request.
 
-
         Switch(Thirdparty API Adapter) -> PISP
       tags:
         - thirdpartyRequests
@@ -1420,8 +1308,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: >-
-                #/components/schemas/ThirdpartyRequestsTransactionsIDPatchResponse
+              $ref: '#/components/schemas/ThirdpartyRequestsTransactionsIDPatchResponse'
             example:
               transactionRequestState: ACCEPTED
               transactionState: COMMITTED
@@ -1462,16 +1349,10 @@ paths:
         - sampled
       operationId: ThirdpartyTransactionRequestsError
       summary: ThirdpartyTransactionRequestsError
-      description: >
-        If the server is unable to find the transaction request, or another
-        processing error occurs,
-
-        the error callback `PUT /thirdpartyRequests/transactions/{ID}/error` is
-        used.
-
-        The `{ID}` in the URI should contain the `transactionRequestId` that was
-        used for the creation of
-
+      description: |
+        If the server is unable to find the transaction request, or another processing error occurs,
+        the error callback `PUT /thirdpartyRequests/transactions/{ID}/error` is used.
+        The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of
         the thirdparty transaction request.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
@@ -1513,10 +1394,8 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     post:
-      description: >
-        The HTTP request **POST /thirdpartyRequests/authorizations** is used to
-        request the validation by a customer for the transfer described in the
-        request.
+      description: |
+        The HTTP request **POST /thirdpartyRequests/authorizations** is used to request the validation by a customer for the transfer described in the request.
       operationId: PostThirdpartyRequestsAuthorizations
       summary: PostThirdpartyRequestsAuthorizations
       tags:
@@ -1564,15 +1443,10 @@ paths:
       - $ref: '#/components/parameters/FSPIOP-URI'
       - $ref: '#/components/parameters/FSPIOP-HTTP-Method'
     get:
-      description: >
-        The HTTP request **GET /thirdpartyRequests/authorizations/**_{ID}_ is
-        used to get information relating
-
-        to a previously issued authorization request. The *{ID}* in the request
-        should match the
-
-        `authorizationRequestId` which was given when the authorization request
-        was created.
+      description: |
+        The HTTP request **GET /thirdpartyRequests/authorizations/**_{ID}_ is used to get information relating
+        to a previously issued authorization request. The *{ID}* in the request should match the
+        `authorizationRequestId` which was given when the authorization request was created.
       operationId: GetThirdpartyRequestsAuthorizationsById
       summary: GetThirdpartyRequestsAuthorizationsById
       tags:
@@ -1600,18 +1474,12 @@ paths:
         '503':
           $ref: '#/components/responses/503'
     put:
-      description: >
-        After receiving the **POST /thirdpartyRequests/authorizations**, the
-        PISP will present the details of the
-
-        transaction to their user, and request that the client sign the
-        `challenge` field using the credential
-
+      description: |
+        After receiving the **POST /thirdpartyRequests/authorizations**, the PISP will present the details of the
+        transaction to their user, and request that the client sign the `challenge` field using the credential
         they previously registered.
 
-
-        The signed challenge will be sent back by the PISP in **PUT
-        /thirdpartyRequests/authorizations/**_{ID}_:
+        The signed challenge will be sent back by the PISP in **PUT /thirdpartyRequests/authorizations/**_{ID}_:
       operationId: PutThirdpartyRequestsAuthorizationsById
       summary: PutThirdpartyRequestsAuthorizationsById
       tags:
@@ -1625,12 +1493,9 @@ paths:
           application/json:
             schema:
               oneOf:
-                - $ref: >-
-                    #/components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseRejected
-                - $ref: >-
-                    #/components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseFIDO
-                - $ref: >-
-                    #/components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseGeneric
+                - $ref: '#/components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseRejected'
+                - $ref: '#/components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseFIDO'
+                - $ref: '#/components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseGeneric'
       responses:
         '200':
           $ref: '#/components/responses/200'
@@ -1668,23 +1533,14 @@ paths:
         - sampled
       operationId: PutThirdpartyRequestsAuthorizationsByIdAndError
       summary: PutThirdpartyRequestsAuthorizationsByIdAndError
-      description: >
-        The HTTP request `PUT /thirdpartyRequests/authorizations/{ID}/error` is
-        used by the DFSP or PISP to inform
-
-        the other party that something went wrong with a Thirdparty Transaction
-        Authorization Request.
-
-
-        The PISP may use this to tell the DFSP that the Thirdparty Transaction
-        Authorization Request is invalid or doesn't
+      description: |
+        The HTTP request `PUT /thirdpartyRequests/authorizations/{ID}/error` is used by the DFSP or PISP to inform
+        the other party that something went wrong with a Thirdparty Transaction Authorization Request.
 
+        The PISP may use this to tell the DFSP that the Thirdparty Transaction Authorization Request is invalid or doesn't
         match a `transactionRequestId`.
 
-
-        The DFSP may use this to tell the PISP that the signed challenge
-        returned in `PUT /thirdpartyRequest/authorizations/{ID}`
-
+        The DFSP may use this to tell the PISP that the signed challenge returned in `PUT /thirdpartyRequest/authorizations/{ID}`
         was invalid.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
@@ -1731,9 +1587,8 @@ paths:
         - sampled
       operationId: PostThirdpartyRequestsVerifications
       summary: PostThirdpartyRequestsVerifications
-      description: >
-        The HTTP request `POST /thirdpartyRequests/verifications` is used by the
-        DFSP to verify a third party authorization.
+      description: |
+        The HTTP request `POST /thirdpartyRequests/verifications` is used by the DFSP to verify a third party authorization.
       parameters:
         - $ref: '#/components/parameters/Accept'
         - $ref: '#/components/parameters/Content-Length'
@@ -1744,10 +1599,8 @@ paths:
           application/json:
             schema:
               oneOf:
-                - $ref: >-
-                    #/components/schemas/ThirdpartyRequestsVerificationsPostRequestFIDO
-                - $ref: >-
-                    #/components/schemas/ThirdpartyRequestsVerificationsPostRequestGeneric
+                - $ref: '#/components/schemas/ThirdpartyRequestsVerificationsPostRequestFIDO'
+                - $ref: '#/components/schemas/ThirdpartyRequestsVerificationsPostRequestGeneric'
       responses:
         '202':
           $ref: '#/components/responses/202'
@@ -1785,12 +1638,9 @@ paths:
         - sampled
       operationId: GetThirdpartyRequestsVerificationsById
       summary: GetThirdpartyRequestsVerificationsById
-      description: >
+      description: |
         The HTTP request `/thirdpartyRequests/verifications/{ID}` is used to get
-
-        information regarding a previously created or requested authorization.
-        The *{ID}*
-
+        information regarding a previously created or requested authorization. The *{ID}*
         in the URI should contain the verification request ID
       parameters:
         - $ref: '#/components/parameters/Accept'
@@ -1819,17 +1669,10 @@ paths:
         - sampled
       operationId: PutThirdpartyRequestsVerificationsById
       summary: PutThirdpartyRequestsVerificationsById
-      description: >-
-        The HTTP request `PUT /thirdpartyRequests/verifications/{ID}` is used by
-        the Auth-Service to inform the DFSP of a successful result in validating
-        the verification of a Thirdparty Transaction Request.
-
-        If the validation fails, the auth-service will send back `PUT
-        /thirdpartyRequests/verifications/{ID}` with `authenticationResponse:
-        'REJECTED'`.
-
-        In unplanned error cases the Auth-Service MUST use `PUT
-        /thirdpartyRequests/verifications/{ID}/error`.
+      description: |-
+        The HTTP request `PUT /thirdpartyRequests/verifications/{ID}` is used by the Auth-Service to inform the DFSP of a successful result in validating the verification of a Thirdparty Transaction Request.
+        If the validation fails, the auth-service will send back `PUT /thirdpartyRequests/verifications/{ID}` with `authenticationResponse: 'REJECTED'`.
+        In unplanned error cases the Auth-Service MUST use `PUT /thirdpartyRequests/verifications/{ID}/error`.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
       requestBody:
@@ -1838,8 +1681,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: >-
-                #/components/schemas/ThirdpartyRequestsVerificationsIDPutResponse
+              $ref: '#/components/schemas/ThirdpartyRequestsVerificationsIDPutResponse'
             example:
               authenticationResponse: VERIFIED
       responses:
@@ -1879,12 +1721,9 @@ paths:
         - sampled
       operationId: PutThirdpartyRequestsVerificationsByIdAndError
       summary: PutThirdpartyRequestsVerificationsByIdAndError
-      description: >
-        The HTTP request `PUT /thirdpartyRequests/verifications/{ID}/error` is
-        used by the Auth-Service to inform
-
-        the DFSP of a failure in validating or looking up the verification of a
-        Thirdparty Transaction Request.
+      description: |
+        The HTTP request `PUT /thirdpartyRequests/verifications/{ID}/error` is used by the Auth-Service to inform
+        the DFSP of a failure in validating or looking up the verification of a Thirdparty Transaction Request.
       parameters:
         - $ref: '#/components/parameters/Content-Length'
       requestBody:
@@ -1929,114 +1768,49 @@ components:
         - ALIAS
         - CONSENT
         - THIRD_PARTY_LINK
-      description: >
+      description: |
         Below are the allowed values for the enumeration.
-
         - MSISDN - An MSISDN (Mobile Station International Subscriber Directory
-
-        Number, that is, the phone number) is used as reference to a
-        participant.
-
+        Number, that is, the phone number) is used as reference to a participant.
         The MSISDN identifier should be in international format according to the
-
         [ITU-T E.164 standard](https://www.itu.int/rec/T-REC-E.164/en).
-
-        Optionally, the MSISDN may be prefixed by a single plus sign, indicating
-        the
-
+        Optionally, the MSISDN may be prefixed by a single plus sign, indicating the
         international prefix.
-
         - EMAIL - An email is used as reference to a
-
-        participant. The format of the email should be according to the
-        informational
-
+        participant. The format of the email should be according to the informational
         [RFC 3696](https://tools.ietf.org/html/rfc3696).
-
-        - PERSONAL_ID - A personal identifier is used as reference to a
-        participant.
-
-        Examples of personal identification are passport number, birth
-        certificate
-
-        number, and national registration number. The identifier number is added
-        in 
-
-        the PartyIdentifier element. The personal identifier type is added in
-        the
-
+        - PERSONAL_ID - A personal identifier is used as reference to a participant.
+        Examples of personal identification are passport number, birth certificate
+        number, and national registration number. The identifier number is added in 
+        the PartyIdentifier element. The personal identifier type is added in the
         PartySubIdOrType element.
-
-        - BUSINESS - A specific Business (for example, an organization or a
-        company)
-
-        is used as reference to a participant. The BUSINESS identifier can be in
-        any
-
-        format. To make a transaction connected to a specific username or bill
-        number
-
+        - BUSINESS - A specific Business (for example, an organization or a company)
+        is used as reference to a participant. The BUSINESS identifier can be in any
+        format. To make a transaction connected to a specific username or bill number
         in a Business, the PartySubIdOrType element should be used.
-
-        - DEVICE - A specific device (for example, a POS or ATM) ID connected to
-        a
-
+        - DEVICE - A specific device (for example, a POS or ATM) ID connected to a
         specific business or organization is used as reference to a Party.
-
-        For referencing a specific device under a specific business or
-        organization,
-
+        For referencing a specific device under a specific business or organization,
         use the PartySubIdOrType element.
-
         - ACCOUNT_ID - A bank account number or FSP account ID should be used as
-
-        reference to a participant. The ACCOUNT_ID identifier can be in any
-        format,
-
+        reference to a participant. The ACCOUNT_ID identifier can be in any format,
         as formats can greatly differ depending on country and FSP.
-
-        - IBAN - A bank account number or FSP account ID is used as reference to
-        a
-
+        - IBAN - A bank account number or FSP account ID is used as reference to a
         participant. The IBAN identifier can consist of up to 34 alphanumeric
-
         characters and should be entered without whitespace.
-
-        - ALIAS An alias is used as reference to a participant. The alias should
-        be
-
+        - ALIAS An alias is used as reference to a participant. The alias should be
         created in the FSP as an alternative reference to an account owner.
-
         Another example of an alias is a username in the FSP system.
-
-        The ALIAS identifier can be in any format. It is also possible to use
-        the
-
-        PartySubIdOrType element for identifying an account under an Alias
-        defined
-
+        The ALIAS identifier can be in any format. It is also possible to use the
+        PartySubIdOrType element for identifying an account under an Alias defined
         by the PartyIdentifier.
-
-        - CONSENT - A Consent represents an agreement between a PISP, a Customer
-        and
-
-        a DFSP which allows the PISP permission to perform actions on behalf of
-        the 
-
-        customer. A Consent has an authoritative source: either the DFSP who
-        issued 
-
+        - CONSENT - A Consent represents an agreement between a PISP, a Customer and
+        a DFSP which allows the PISP permission to perform actions on behalf of the 
+        customer. A Consent has an authoritative source: either the DFSP who issued 
         the Consent, or an Auth Service which administers the Consent.
-
-        - THIRD_PARTY_LINK - A Third Party Link represents an agreement between
-        a PISP,
-
-        a DFSP, and a specific Customer's account at the DFSP. The content of
-        the link 
-
-        is created by the DFSP at the time when it gives permission to the PISP
-        for 
-
+        - THIRD_PARTY_LINK - A Third Party Link represents an agreement between a PISP,
+        a DFSP, and a specific Customer's account at the DFSP. The content of the link 
+        is created by the DFSP at the time when it gives permission to the PISP for 
         specific access to a given account.
       example: PERSONAL_ID
     PartyIdentifier:
@@ -2051,9 +1825,7 @@ components:
       type: string
       minLength: 1
       maxLength: 128
-      description: >-
-        Either a sub-identifier of a PartyIdentifier, or a sub-type of the
-        PartyIdType, normally a PersonalIdentifierType.
+      description: Either a sub-identifier of a PartyIdentifier, or a sub-type of the PartyIdType, normally a PersonalIdentifierType.
     FspId:
       title: FspId
       type: string
@@ -2087,9 +1859,7 @@ components:
     ExtensionList:
       title: ExtensionList
       type: object
-      description: >-
-        Data model for the complex type ExtensionList. An optional list of
-        extensions, specific to deployment.
+      description: Data model for the complex type ExtensionList. An optional list of extensions, specific to deployment.
       properties:
         extension:
           type: array
@@ -2122,14 +1892,7 @@ components:
       title: ErrorCode
       type: string
       pattern: ^[1-9]\d{3}$
-      description: >-
-        The API data type ErrorCode is a JSON String of four characters,
-        consisting of digits only. Negative numbers are not allowed. A leading
-        zero is not allowed. Each error code in the API is a four-digit number,
-        for example, 1234, where the first number (1 in the example) represents
-        the high-level error category, the second number (2 in the example)
-        represents the low-level error category, and the last two numbers (34 in
-        the example) represent the specific error.
+      description: The API data type ErrorCode is a JSON String of four characters, consisting of digits only. Negative numbers are not allowed. A leading zero is not allowed. Each error code in the API is a four-digit number, for example, 1234, where the first number (1 in the example) represents the high-level error category, the second number (2 in the example) represents the low-level error category, and the last two numbers (34 in the example) represent the specific error.
       example: '5100'
     ErrorDescription:
       title: ErrorDescription
@@ -2164,11 +1927,7 @@ components:
         - partyId
     Currency:
       title: Currency
-      description: >-
-        The currency codes defined in [ISO
-        4217](https://www.iso.org/iso-4217-currency-codes.html) as three-letter
-        alphabetic codes are used as the standard naming representation for
-        currencies.
+      description: The currency codes defined in [ISO 4217](https://www.iso.org/iso-4217-currency-codes.html) as three-letter alphabetic codes are used as the standard naming representation for currencies.
       type: string
       minLength: 3
       maxLength: 3
@@ -2348,9 +2107,7 @@ components:
             $ref: '#/components/schemas/PartyResult'
           minItems: 1
           maxItems: 10000
-          description: >-
-            List of PartyResult elements that were either created or failed to
-            be created.
+          description: List of PartyResult elements that were either created or failed to be created.
         currency:
           $ref: '#/components/schemas/Currency'
       required:
@@ -2359,10 +2116,7 @@ components:
       title: MerchantClassificationCode
       type: string
       pattern: ^[\d]{1,4}$
-      description: >-
-        A limited set of pre-defined numbers. This list would be a limited set
-        of numbers identifying a set of popular merchant types like School Fees,
-        Pubs and Restaurants, Groceries, etc.
+      description: A limited set of pre-defined numbers. This list would be a limited set of numbers identifying a set of popular merchant types like School Fees, Pubs and Restaurants, Groceries, etc.
     PartyName:
       title: PartyName
       type: string
@@ -2374,9 +2128,7 @@ components:
       type: string
       minLength: 1
       maxLength: 128
-      pattern: >-
-        ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control}
-        .,''-]{1,128}$
+      pattern: ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control} .,''-]{1,128}$
       description: First name of the Party (Name Type).
       example: Henrik
     MiddleName:
@@ -2384,9 +2136,7 @@ components:
       type: string
       minLength: 1
       maxLength: 128
-      pattern: >-
-        ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control}
-        .,''-]{1,128}$
+      pattern: ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control} .,''-]{1,128}$
       description: Middle name of the Party (Name Type).
       example: Johannes
     LastName:
@@ -2394,9 +2144,7 @@ components:
       type: string
       minLength: 1
       maxLength: 128
-      pattern: >-
-        ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control}
-        .,''-]{1,128}$
+      pattern: ^(?!\s*$)[\p{L}\p{gc=Mark}\p{digit}\p{gc=Connector_Punctuation}\p{Join_Control} .,''-]{1,128}$
       description: Last name of the Party (Name Type).
       example: Karlsson
     PartyComplexName:
@@ -2413,8 +2161,7 @@ components:
     DateOfBirth:
       title: DateofBirth (type Date)
       type: string
-      pattern: >-
-        ^(?:[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)$
+      pattern: ^(?:[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)$
       description: Date of Birth of the Party.
       example: '1966-06-16'
     PartyPersonalInfo:
@@ -2444,15 +2191,11 @@ components:
     PartiesTypeIDPutResponse:
       title: PartiesTypeIDPutResponse
       type: object
-      description: >
+      description: |
         The object sent in the PUT /parties/{Type}/{ID} callback.
 
-
-        This is a variant based on FSPIOP `PartiesTypeIDPutResponse`
-        specification.
-
+        This is a variant based on FSPIOP `PartiesTypeIDPutResponse` specification.
         Main difference being that it returns a `Party` with the newly added
-
         `accounts` property.
       properties:
         party:
@@ -2463,13 +2206,7 @@ components:
       title: Amount
       type: string
       pattern: ^([0]|([1-9][0-9]{0,17}))([.][0-9]{0,3}[1-9])?$
-      description: >-
-        The API data type Amount is a JSON String in a canonical format that is
-        restricted by a regular expression for interoperability reasons. This
-        pattern does not allow any trailing zeroes at all, but allows an amount
-        without a minor currency unit. It also only allows four digits in the
-        minor currency unit; a negative value is not allowed. Using more than 18
-        digits in the major currency unit is not allowed.
+      description: The API data type Amount is a JSON String in a canonical format that is restricted by a regular expression for interoperability reasons. This pattern does not allow any trailing zeroes at all, but allows an amount without a minor currency unit. It also only allows four digits in the minor currency unit; a negative value is not allowed. Using more than 18 digits in the major currency unit is not allowed.
       example: '123.45'
     Money:
       title: Money
@@ -2486,42 +2223,25 @@ components:
     DateTime:
       title: DateTime
       type: string
-      pattern: >-
-        ^(?:[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)$
-      description: >-
-        The API data type DateTime is a JSON String in a lexical format that is
-        restricted by a regular expression for interoperability reasons. The
-        format is according to [ISO
-        8601](https://www.iso.org/iso-8601-date-and-time-format.html), expressed
-        in a combined date, time and time zone format. A more readable version
-        of the format is yyyy-MM-ddTHH:mm:ss.SSS[-HH:MM]. Examples are
-        "2016-05-24T08:38:08.699-04:00", "2016-05-24T08:38:08.699Z" (where Z
-        indicates Zulu time zone, same as UTC).
+      pattern: ^(?:[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)$
+      description: The API data type DateTime is a JSON String in a lexical format that is restricted by a regular expression for interoperability reasons. The format is according to [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html), expressed in a combined date, time and time zone format. A more readable version of the format is yyyy-MM-ddTHH:mm:ss.SSS[-HH:MM]. Examples are "2016-05-24T08:38:08.699-04:00", "2016-05-24T08:38:08.699Z" (where Z indicates Zulu time zone, same as UTC).
       example: '2016-05-24T08:38:08.699-04:00'
     Latitude:
       title: Latitude
       type: string
-      pattern: >-
-        ^(\+|-)?(?:90(?:(?:\.0{1,6})?)|(?:[0-9]|[1-8][0-9])(?:(?:\.[0-9]{1,6})?))$
-      description: >-
-        The API data type Latitude is a JSON String in a lexical format that is
-        restricted by a regular expression for interoperability reasons.
+      pattern: ^(\+|-)?(?:90(?:(?:\.0{1,6})?)|(?:[0-9]|[1-8][0-9])(?:(?:\.[0-9]{1,6})?))$
+      description: The API data type Latitude is a JSON String in a lexical format that is restricted by a regular expression for interoperability reasons.
       example: '+45.4215'
     Longitude:
       title: Longitude
       type: string
-      pattern: >-
-        ^(\+|-)?(?:180(?:(?:\.0{1,6})?)|(?:[0-9]|[1-9][0-9]|1[0-7][0-9])(?:(?:\.[0-9]{1,6})?))$
-      description: >-
-        The API data type Longitude is a JSON String in a lexical format that is
-        restricted by a regular expression for interoperability reasons.
+      pattern: ^(\+|-)?(?:180(?:(?:\.0{1,6})?)|(?:[0-9]|[1-9][0-9]|1[0-7][0-9])(?:(?:\.[0-9]{1,6})?))$
+      description: The API data type Longitude is a JSON String in a lexical format that is restricted by a regular expression for interoperability reasons.
       example: '+75.6972'
     GeoCode:
       title: GeoCode
       type: object
-      description: >-
-        Data model for the complex type GeoCode. Indicates the geographic
-        location from where the transaction was initiated.
+      description: Data model for the complex type GeoCode. Indicates the geographic location from where the transaction was initiated.
       properties:
         latitude:
           $ref: '#/components/schemas/Latitude'
@@ -2537,8 +2257,7 @@ components:
       minLength: 1
       maxLength: 32768
       description: Information for recipient (transport layer information).
-      example: >-
-        AYIBgQAAAAAAAASwNGxldmVsb25lLmRmc3AxLm1lci45T2RTOF81MDdqUUZERmZlakgyOVc4bXFmNEpLMHlGTFGCAUBQU0svMS4wCk5vbmNlOiB1SXlweUYzY3pYSXBFdzVVc05TYWh3CkVuY3J5cHRpb246IG5vbmUKUGF5bWVudC1JZDogMTMyMzZhM2ItOGZhOC00MTYzLTg0NDctNGMzZWQzZGE5OGE3CgpDb250ZW50LUxlbmd0aDogMTM1CkNvbnRlbnQtVHlwZTogYXBwbGljYXRpb24vanNvbgpTZW5kZXItSWRlbnRpZmllcjogOTI4MDYzOTEKCiJ7XCJmZWVcIjowLFwidHJhbnNmZXJDb2RlXCI6XCJpbnZvaWNlXCIsXCJkZWJpdE5hbWVcIjpcImFsaWNlIGNvb3BlclwiLFwiY3JlZGl0TmFtZVwiOlwibWVyIGNoYW50XCIsXCJkZWJpdElkZW50aWZpZXJcIjpcIjkyODA2MzkxXCJ9IgA
+      example: AYIBgQAAAAAAAASwNGxldmVsb25lLmRmc3AxLm1lci45T2RTOF81MDdqUUZERmZlakgyOVc4bXFmNEpLMHlGTFGCAUBQU0svMS4wCk5vbmNlOiB1SXlweUYzY3pYSXBFdzVVc05TYWh3CkVuY3J5cHRpb246IG5vbmUKUGF5bWVudC1JZDogMTMyMzZhM2ItOGZhOC00MTYzLTg0NDctNGMzZWQzZGE5OGE3CgpDb250ZW50LUxlbmd0aDogMTM1CkNvbnRlbnQtVHlwZTogYXBwbGljYXRpb24vanNvbgpTZW5kZXItSWRlbnRpZmllcjogOTI4MDYzOTEKCiJ7XCJmZWVcIjowLFwidHJhbnNmZXJDb2RlXCI6XCJpbnZvaWNlXCIsXCJkZWJpdE5hbWVcIjpcImFsaWNlIGNvb3BlclwiLFwiY3JlZGl0TmFtZVwiOlwibWVyIGNoYW50XCIsXCJkZWJpdElkZW50aWZpZXJcIjpcIjkyODA2MzkxXCJ9IgA
     IlpCondition:
       title: IlpCondition
       type: string
@@ -2606,19 +2325,11 @@ components:
     ThirdpartyRequestsTransactionsIDPatchResponse:
       title: ThirdpartyRequestsTransactionsIDPatchResponse
       type: object
-      description: >-
+      description: |-
         Used by: DFSP
-
-        The issuing PISP will expect a response to their request for a transfer
-        which describes the finalized state of the requested transfer.
-
-        This response will be given by a PATCH call on the
-        /thirdpartyRequests/transactions/{ID} resource.
-
-        The {ID} given in the query string should be the transactionRequestId
-        which was originally used by the PISP to identify the transaction
-        request.
-
+        The issuing PISP will expect a response to their request for a transfer which describes the finalized state of the requested transfer.
+        This response will be given by a PATCH call on the /thirdpartyRequests/transactions/{ID} resource.
+        The {ID} given in the query string should be the transactionRequestId which was originally used by the PISP to identify the transaction request.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31612-post-thirdpartyrequestsauthorizations
       properties:
         completedTimestamp:
@@ -2660,10 +2371,7 @@ components:
       title: Integer
       type: string
       pattern: ^[1-9]\d*$
-      description: >-
-        The API data type Integer is a JSON String consisting of digits only.
-        Negative numbers and leading zeroes are not allowed. The data type is
-        always limited to a specific number of digits.
+      description: The API data type Integer is a JSON String consisting of digits only. Negative numbers and leading zeroes are not allowed. The data type is always limited to a specific number of digits.
     Note:
       title: Note
       type: string
@@ -2676,9 +2384,8 @@ components:
       type: string
       enum:
         - THIRD_PARTY_LINK
-      description: >
-        - THIRD_PARTY_LINK - is the DFSP's internal reference which allows DFSP
-        to find out the corresponding consent
+      description: |
+        - THIRD_PARTY_LINK - is the DFSP's internal reference which allows DFSP to find out the corresponding consent
       example: PERSONAL_ID
     PartyIdInfoTPLink:
       title: PartyIdInfo
@@ -2701,15 +2408,9 @@ components:
     ServiceType:
       title: ServiceType
       type: string
-      description: >-
-        The ServiceType enumeration describes the types of role for which a DFSP
-        may query using the /services resource.
-
-        Below are the allowed values for the enumeration ServiceType -
-        THIRD_PARTY_DFSP - Enum used to query for DFSPs that have thirdparty
-        features enabled. - PISP - Enum used to query for PISPs. - AUTH_SERVICE
-        - Participants which provide Authentication Services.
-
+      description: |-
+        The ServiceType enumeration describes the types of role for which a DFSP may query using the /services resource.
+        Below are the allowed values for the enumeration ServiceType - THIRD_PARTY_DFSP - Enum used to query for DFSPs that have thirdparty features enabled. - PISP - Enum used to query for PISPs. - AUTH_SERVICE - Participants which provide Authentication Services.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#3229-servicetype
       enum:
         - THIRD_PARTY_DFSP
@@ -2718,15 +2419,8 @@ components:
     CorrelationId:
       title: CorrelationId
       type: string
-      pattern: >-
-        ^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
-      description: >-
-        Identifier that correlates all messages of the same sequence. The API
-        data type UUID (Universally Unique Identifier) is a JSON String in
-        canonical format, conforming to [RFC
-        4122](https://tools.ietf.org/html/rfc4122), that is restricted by a
-        regular expression for interoperability reasons. A UUID is always 36
-        characters long, 32 hexadecimal symbols and 4 dashes (‘-‘).
+      pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
+      description: Identifier that correlates all messages of the same sequence. The API data type UUID (Universally Unique Identifier) is a JSON String in canonical format, conforming to [RFC 4122](https://tools.ietf.org/html/rfc4122), that is restricted by a regular expression for interoperability reasons. A UUID is always 36 characters long, 32 hexadecimal symbols and 4 dashes (‘-‘).
       example: b51ec534-ee48-4575-b6a9-ead2955b8069
     ParticipantsPostRequest:
       title: ParticipantsPostRequest
@@ -2755,14 +2449,10 @@ components:
       enum:
         - SEND
         - RECEIVE
-      description: >-
+      description: |-
         Below are the allowed values for the enumeration AmountType.
-
-        - SEND - Amount the Payer would like to send, that is, the amount that
-        should be withdrawn from the Payer account including any fees.
-
-        - RECEIVE - Amount the Payer would like the Payee to receive, that is,
-        the amount that should be sent to the receiver exclusive of any fees.
+        - SEND - Amount the Payer would like to send, that is, the amount that should be withdrawn from the Payer account including any fees.
+        - RECEIVE - Amount the Payer would like the Payee to receive, that is, the amount that should be sent to the receiver exclusive of any fees.
       example: RECEIVE
     TransactionScenario:
       title: TransactionScenario
@@ -2773,37 +2463,19 @@ components:
         - TRANSFER
         - PAYMENT
         - REFUND
-      description: >-
+      description: |-
         Below are the allowed values for the enumeration.
-
-        - DEPOSIT - Used for performing a Cash-In (deposit) transaction. In a
-        normal scenario, electronic funds are transferred from a Business
-        account to a Consumer account, and physical cash is given from the
-        Consumer to the Business User.
-
-        - WITHDRAWAL - Used for performing a Cash-Out (withdrawal) transaction.
-        In a normal scenario, electronic funds are transferred from a Consumer’s
-        account to a Business account, and physical cash is given from the
-        Business User to the Consumer.
-
-        - TRANSFER - Used for performing a P2P (Peer to Peer, or Consumer to
-        Consumer) transaction.
-
-        - PAYMENT - Usually used for performing a transaction from a Consumer to
-        a Merchant or Organization, but could also be for a B2B (Business to
-        Business) payment. The transaction could be online for a purchase in an
-        Internet store, in a physical store where both the Consumer and Business
-        User are present, a bill payment, a donation, and so on.
-
+        - DEPOSIT - Used for performing a Cash-In (deposit) transaction. In a normal scenario, electronic funds are transferred from a Business account to a Consumer account, and physical cash is given from the Consumer to the Business User.
+        - WITHDRAWAL - Used for performing a Cash-Out (withdrawal) transaction. In a normal scenario, electronic funds are transferred from a Consumer’s account to a Business account, and physical cash is given from the Business User to the Consumer.
+        - TRANSFER - Used for performing a P2P (Peer to Peer, or Consumer to Consumer) transaction.
+        - PAYMENT - Usually used for performing a transaction from a Consumer to a Merchant or Organization, but could also be for a B2B (Business to Business) payment. The transaction could be online for a purchase in an Internet store, in a physical store where both the Consumer and Business User are present, a bill payment, a donation, and so on.
         - REFUND - Used for performing a refund of transaction.
       example: DEPOSIT
     TransactionSubScenario:
       title: TransactionSubScenario
       type: string
       pattern: ^[A-Z_]{1,32}$
-      description: >-
-        Possible sub-scenario, defined locally within the scheme (UndefinedEnum
-        Type).
+      description: Possible sub-scenario, defined locally within the scheme (UndefinedEnum Type).
       example: LOCALLY_DEFINED_SUBSCENARIO
     TransactionInitiator:
       title: TransactionInitiator
@@ -2811,17 +2483,10 @@ components:
       enum:
         - PAYER
         - PAYEE
-      description: >-
+      description: |-
         Below are the allowed values for the enumeration.
-
-        - PAYER - Sender of funds is initiating the transaction. The account to
-        send from is either owned by the Payer or is connected to the Payer in
-        some way.
-
-        - PAYEE - Recipient of the funds is initiating the transaction by
-        sending a transaction request. The Payer must approve the transaction,
-        either automatically by a pre-generated OTP or by pre-approval of the
-        Payee, or by manually approving in his or her own Device.
+        - PAYER - Sender of funds is initiating the transaction. The account to send from is either owned by the Payer or is connected to the Payer in some way.
+        - PAYEE - Recipient of the funds is initiating the transaction by sending a transaction request. The Payer must approve the transaction, either automatically by a pre-generated OTP or by pre-approval of the Payee, or by manually approving in his or her own Device.
       example: PAYEE
     TransactionInitiatorType:
       title: TransactionInitiatorType
@@ -2860,11 +2525,7 @@ components:
       title: BalanceOfPayments
       type: string
       pattern: ^[1-9]\d{2}$
-      description: >-
-        (BopCode) The API data type
-        [BopCode](https://www.imf.org/external/np/sta/bopcode/) is a JSON String
-        of 3 characters, consisting of digits only. Negative numbers are not
-        allowed. A leading zero is not allowed.
+      description: (BopCode) The API data type [BopCode](https://www.imf.org/external/np/sta/bopcode/) is a JSON String of 3 characters, consisting of digits only. Negative numbers are not allowed. A leading zero is not allowed.
       example: '123'
     TransactionType:
       title: TransactionType
@@ -2894,20 +2555,11 @@ components:
       properties:
         quoteId:
           $ref: '#/components/schemas/CorrelationId'
-          description: >-
-            Common ID between the FSPs for the quote object, decided by the
-            Payer FSP. The ID should be reused for resends of the same quote for
-            a transaction. A new ID should be generated for each new quote for a
-            transaction.
+          description: Common ID between the FSPs for the quote object, decided by the Payer FSP. The ID should be reused for resends of the same quote for a transaction. A new ID should be generated for each new quote for a transaction.
           example: b51ec534-ee48-4575-b6a9-ead2955b8069
         transactionId:
           $ref: '#/components/schemas/CorrelationId'
-          description: >-
-            Common ID (decided by the Payer FSP) between the FSPs for the future
-            transaction object. The actual transaction will be created as part
-            of a successful transfer process. The ID should be reused for
-            resends of the same quote for a transaction. A new ID should be
-            generated for each new quote for a transaction.
+          description: Common ID (decided by the Payer FSP) between the FSPs for the future transaction object. The actual transaction will be created as part of a successful transfer process. The ID should be reused for resends of the same quote for a transaction. A new ID should be generated for each new quote for a transaction.
           example: a8323bc6-c228-4df2-ae82-e5a997baf899
         transactionRequestId:
           $ref: '#/components/schemas/CorrelationId'
@@ -2925,39 +2577,23 @@ components:
           example: SEND
         amount:
           $ref: '#/components/schemas/Money'
-          description: >-
-            Depending on amountType - If SEND - The amount the Payer would like
-            to send, that is, the amount that should be withdrawn from the Payer
-            account including any fees. The amount is updated by each
-            participating entity in the transaction. If RECEIVE - The amount the
-            Payee should receive, that is, the amount that should be sent to the
-            receiver exclusive any fees. The amount is not updated by any of the
-            participating entities.
+          description: Depending on amountType - If SEND - The amount the Payer would like to send, that is, the amount that should be withdrawn from the Payer account including any fees. The amount is updated by each participating entity in the transaction. If RECEIVE - The amount the Payee should receive, that is, the amount that should be sent to the receiver exclusive any fees. The amount is not updated by any of the participating entities.
         fees:
           $ref: '#/components/schemas/Money'
-          description: >-
-            The fees in the transaction. The fees element should be empty if
-            fees should be non-disclosed. The fees element should be non-empty
-            if fees should be disclosed.
+          description: The fees in the transaction. The fees element should be empty if fees should be non-disclosed. The fees element should be non-empty if fees should be disclosed.
         transactionType:
           $ref: '#/components/schemas/TransactionType'
           description: Type of transaction for which the quote is requested.
         geoCode:
           $ref: '#/components/schemas/GeoCode'
-          description: >-
-            Longitude and Latitude of the initiating Party. Can be used to
-            detect fraud.
+          description: Longitude and Latitude of the initiating Party. Can be used to detect fraud.
         note:
           $ref: '#/components/schemas/Note'
           description: A memo that will be attached to the transaction.
           example: Free-text memo.
         expiration:
           $ref: '#/components/schemas/DateTime'
-          description: >-
-            Expiration is optional. It can be set to get a quick failure in case
-            the peer FSP takes too long to respond. Also, it may be beneficial
-            for Consumer, Agent, and Merchant to know that their request has a
-            time limit.
+          description: Expiration is optional. It can be set to get a quick failure in case the peer FSP takes too long to respond. Also, it may be beneficial for Consumer, Agent, and Merchant to know that their request has a time limit.
           example: '2016-05-24T08:38:08.699-04:00'
         extensionList:
           $ref: '#/components/schemas/ExtensionList'
@@ -2973,9 +2609,7 @@ components:
     ErrorInformationResponse:
       title: ErrorInformationResponse
       type: object
-      description: >-
-        Data model for the complex type object that contains an optional element
-        ErrorInformation used along with 4xx and 5xx responses.
+      description: Data model for the complex type object that contains an optional element ErrorInformation used along with 4xx and 5xx responses.
       properties:
         errorInformation:
           $ref: '#/components/schemas/ErrorInformation'
@@ -2983,44 +2617,21 @@ components:
       title: Name
       type: string
       pattern: ^(?!\s*$)[\w .,'-]{1,128}$
-      description: >-
-        The API data type Name is a JSON String, restricted by a regular
-        expression to avoid characters which are generally not used in a name.
-
-
-        Regular Expression - The regular expression for restricting the Name
-        type is "^(?!\s*$)[\w .,'-]{1,128}$". The restriction does not allow a
-        string consisting of whitespace only, all Unicode characters are
-        allowed, as well as the period (.) (apostrophe (‘), dash (-), comma (,)
-        and space characters ( ).
+      description: |-
+        The API data type Name is a JSON String, restricted by a regular expression to avoid characters which are generally not used in a name.
 
+        Regular Expression - The regular expression for restricting the Name type is "^(?!\s*$)[\w .,'-]{1,128}$". The restriction does not allow a string consisting of whitespace only, all Unicode characters are allowed, as well as the period (.) (apostrophe (‘), dash (-), comma (,) and space characters ( ).
 
-        **Note:** In some programming languages, Unicode support must be
-        specifically enabled. For example, if Java is used, the flag
-        UNICODE_CHARACTER_CLASS must be enabled to allow Unicode characters.
+        **Note:** In some programming languages, Unicode support must be specifically enabled. For example, if Java is used, the flag UNICODE_CHARACTER_CLASS must be enabled to allow Unicode characters.
     AccountAddress:
       title: AccountAddress
       type: string
-      description: >-
-        The AccountAddress data type is a variable length string with a maximum
-        size of 1023 characters and consists of:
-
-        Alphanumeric characters, upper or lower case. (Addresses are
-        case-sensitive so that they can contain data encoded in formats such as
-        base64url.)
-
-        - Underscore (_) - Tilde (~) - Hyphen (-) - Period (.) Addresses MUST
-        NOT end in a period (.) character
-
-        An entity providing accounts to parties (i.e. a participant) can provide
-        any value for an AccountAddress that is meaningful to that entity. It
-        does not need to provide an address that makes the account identifiable
-        outside the entity's domain.
-
-        IMPORTANT: The policy for defining addresses and the life-cycle of these
-        is at the discretion of the address space owner (the payer DFSP in this
-        case).
-
+      description: |-
+        The AccountAddress data type is a variable length string with a maximum size of 1023 characters and consists of:
+        Alphanumeric characters, upper or lower case. (Addresses are case-sensitive so that they can contain data encoded in formats such as base64url.)
+        - Underscore (_) - Tilde (~) - Hyphen (-) - Period (.) Addresses MUST NOT end in a period (.) character
+        An entity providing accounts to parties (i.e. a participant) can provide any value for an AccountAddress that is meaningful to that entity. It does not need to provide an address that makes the account identifiable outside the entity's domain.
+        IMPORTANT: The policy for defining addresses and the life-cycle of these is at the discretion of the address space owner (the payer DFSP in this case).
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#3212-accountaddress
       pattern: ^([0-9A-Za-z_~\-\.]+[0-9A-Za-z_~\-])$
       minLength: 1
@@ -3028,9 +2639,8 @@ components:
     Account:
       title: Account
       type: object
-      description: >-
+      description: |-
         Data model for the complex type Account.
-
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#3211-account
       properties:
         accountNickname:
@@ -3046,10 +2656,8 @@ components:
     AccountList:
       title: AccountList
       type: array
-      description: >-
-        The AccountList data model is used to hold information about the
-        accounts that a party controls.
-
+      description: |-
+        The AccountList data model is used to hold information about the accounts that a party controls.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#3213-accountlist
       items:
         $ref: '#/components/schemas/Account'
@@ -3058,16 +2666,10 @@ components:
     AccountsIDPutResponse:
       title: AccountsIDPutResponse
       type: object
-      description: >-
+      description: |-
         Callback and data model information for GET /accounts/{ID}:
-
-        Callback - PUT /accounts/{ID} Error Callback - PUT /accounts/{ID}/error
-        Data Model - Empty body
-
-        The PUT /accounts/{ID} response is used to inform the requester of the
-        result of a request for accounts information. The identifier ID given in
-        the call are the values given in the original request.
-
+        Callback - PUT /accounts/{ID} Error Callback - PUT /accounts/{ID}/error Data Model - Empty body
+        The PUT /accounts/{ID} response is used to inform the requester of the result of a request for accounts information. The identifier ID given in the call are the values given in the original request.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31121--put-accountsid
       properties:
         accounts:
@@ -3088,22 +2690,14 @@ components:
     ScopeAction:
       title: ScopeAction
       type: string
-      description: >
+      description: |
         The ScopeAction element contains an access type which a PISP can request
-
         from a DFSP, or which a DFSP can grant to a PISP.
-
         It must be a member of the appropriate enumeration.
 
-
-        - ACCOUNTS_GET_BALANCE: PISP can request a balance for the linked
-        account
-
-        - ACCOUNTS_TRANSFER: PISP can request a transfer of funds from the
-        linked account in the DFSP
-
-        - ACCOUNTS_STATEMENT: PISP can request a statement of individual
-        transactions on a user's account
+        - ACCOUNTS_GET_BALANCE: PISP can request a balance for the linked account
+        - ACCOUNTS_TRANSFER: PISP can request a transfer of funds from the linked account in the DFSP
+        - ACCOUNTS_STATEMENT: PISP can request a statement of individual transactions on a user's account
       enum:
         - ACCOUNTS_GET_BALANCE
         - ACCOUNTS_TRANSFER
@@ -3111,11 +2705,8 @@ components:
     Scope:
       title: Scope
       type: object
-      description: >-
-        The Scope element contains an identifier defining, in the terms of a
-        DFSP, an account on which access types can be requested or granted. It
-        also defines the access types which are requested or granted.
-
+      description: |-
+        The Scope element contains an identifier defining, in the terms of a DFSP, an account on which access types can be requested or granted. It also defines the access types which are requested or granted.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#32121-scope
       properties:
         address:
@@ -3145,33 +2736,23 @@ components:
       pattern: ^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?
       minLength: 1
       maxLength: 512
-      description: >
-        The API data type Uri is a JSON string in a canonical format that is
-        restricted by a regular expression for interoperability reasons.
+      description: |
+        The API data type Uri is a JSON string in a canonical format that is restricted by a regular expression for interoperability reasons.
     ConsentRequestsPostRequest:
       title: ConsentRequestsPostRequest
       type: object
-      description: >-
+      description: |-
         Used by: PISP
-
-        The HTTP request POST /consentRequests is used to request a DFSP to
-        grant access to one or more accounts owned by a customer of the DFSP for
-        the PISP who sends the request.
-
+        The HTTP request POST /consentRequests is used to request a DFSP to grant access to one or more accounts owned by a customer of the DFSP for the PISP who sends the request.
         Callback and data model for POST /consentRequests:
-
-        Callback: PUT /consentRequests/{ID} Error callback: PUT
-        /consentRequests/{ID}/error Data model - see below url
-
+        Callback: PUT /consentRequests/{ID} Error callback: PUT /consentRequests/{ID}/error Data model - see below url
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31212-post-consentrequests
       properties:
         consentRequestId:
           $ref: '#/components/schemas/CorrelationId'
         userId:
           type: string
-          description: >-
-            The identifier used in the **GET /accounts/**_{ID}_. Used by the
-            DFSP to correlate an account lookup to a `consentRequest`
+          description: The identifier used in the **GET /accounts/**_{ID}_. Used by the DFSP to correlate an account lookup to a `consentRequest`
           minLength: 1
           maxLength: 128
         scopes:
@@ -3206,17 +2787,12 @@ components:
     ConsentRequestsIDPutResponseWeb:
       title: ConsentRequestsIDPutResponseWeb
       type: object
-      description: >
+      description: |
         The object sent in a `PUT /consentRequests/{ID}` request.
 
-
-        Schema used in the request consent phase of the account linking web
-        flow,
-
+        Schema used in the request consent phase of the account linking web flow,
         the result is the PISP being instructed on a specific URL where this
-
         supposed user should be redirected. This URL should be a place where
-
         the user can prove their identity (e.g., by logging in).
       properties:
         scopes:
@@ -3253,12 +2829,10 @@ components:
     ConsentRequestsIDPutResponseOTP:
       title: ConsentRequestsIDPutResponseOTP
       type: object
-      description: >
+      description: |
         The object sent in a `PUT /consentRequests/{ID}` request.
 
-
-        Schema used in the request consent phase of the account linking OTP/SMS
-        flow.
+        Schema used in the request consent phase of the account linking OTP/SMS flow.
       properties:
         scopes:
           type: array
@@ -3283,22 +2857,13 @@ components:
     BinaryString:
       type: string
       pattern: ^[A-Za-z0-9-_]+[=]{0,2}$
-      description: >-
-        The API data type BinaryString is a JSON String. The string is a
-        base64url  encoding of a string of raw bytes, where padding (character
-        ‘=’) is added at the end of the data if needed to ensure that the string
-        is a multiple of 4 characters. The length restriction indicates the
-        allowed number of characters.
+      description: The API data type BinaryString is a JSON String. The string is a base64url  encoding of a string of raw bytes, where padding (character ‘=’) is added at the end of the data if needed to ensure that the string is a multiple of 4 characters. The length restriction indicates the allowed number of characters.
     ConsentRequestsIDPatchRequest:
       title: ConsentRequestsIDPatchRequest
       type: object
-      description: >-
+      description: |-
         Used by: PISP
-
-        After the user completes an out-of-band authorization with the DFSP, the
-        PISP will receive a token which they can use to prove to the DFSP that
-        the user trusts this PISP.
-
+        After the user completes an out-of-band authorization with the DFSP, the PISP will receive a token which they can use to prove to the DFSP that the user trusts this PISP.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31222-patch-consentrequestsid
       properties:
         authToken:
@@ -3313,12 +2878,8 @@ components:
       enum:
         - FIDO
         - GENERIC
-      description: >-
-        The type of the Credential. - "FIDO" - The credential is based on a FIDO
-        challenge. Its payload is a FIDOPublicKeyCredentialAttestation object. -
-        "GENERIC" - The credential is based on a simple public key validation.
-        Its payload is a GenericCredential object.
-
+      description: |-
+        The type of the Credential. - "FIDO" - The credential is based on a FIDO challenge. Its payload is a FIDOPublicKeyCredentialAttestation object. - "GENERIC" - The credential is based on a simple public key validation. Its payload is a GenericCredential object.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#3226-credentialtype
     CredentialStatusPending:
       title: CredentialStatusPending
@@ -3331,9 +2892,8 @@ components:
     GenericCredential:
       title: GenericCredential
       type: object
-      description: >
-        A publicKey + signature of a challenge for a generic public/private
-        keypair.
+      description: |
+        A publicKey + signature of a challenge for a generic public/private keypair.
       properties:
         publicKey:
           $ref: '#/components/schemas/BinaryString'
@@ -3346,18 +2906,12 @@ components:
     FIDOPublicKeyCredentialAttestation:
       title: FIDOPublicKeyCredentialAttestation
       type: object
-      description: >
+      description: |
         A data model representing a FIDO Attestation result. Derived from 
-
-        [`PublicKeyCredential`
-        Interface](https://w3c.github.io/webauthn/#iface-pkcredential).
-
+        [`PublicKeyCredential` Interface](https://w3c.github.io/webauthn/#iface-pkcredential).
 
         The `PublicKeyCredential` interface represents the below fields with
-
-        a Type of Javascript
-        [ArrayBuffer](https://heycam.github.io/webidl/#idl-ArrayBuffer).
-
+        a Type of Javascript [ArrayBuffer](https://heycam.github.io/webidl/#idl-ArrayBuffer).
         For this API, we represent ArrayBuffers as base64 encoded utf-8 strings.
       properties:
         id:
@@ -3407,18 +2961,12 @@ components:
     SignedCredential:
       title: SignedCredential
       type: object
-      description: >
+      description: |
         A credential used to allow a user to prove their identity and access
-
         to an account with a DFSP.
 
-
-        SignedCredential is a special formatting of the credential to allow us
-        to be
-
-        more explicit about the `status` field - it should only ever be PENDING
-        when
-
+        SignedCredential is a special formatting of the credential to allow us to be
+        more explicit about the `status` field - it should only ever be PENDING when
         updating a credential.
       properties:
         credentialType:
@@ -3486,20 +3034,15 @@ components:
         consentId:
           allOf:
             - $ref: '#/components/schemas/CorrelationId'
-          description: >
-            Common ID between the PISP and the Payer DFSP for the consent
-            object. The ID
-
-            should be reused for re-sends of the same consent. A new ID should
-            be generated
-
+          description: |
+            Common ID between the PISP and the Payer DFSP for the consent object. The ID
+            should be reused for re-sends of the same consent. A new ID should be generated
             for each new consent.
         consentRequestId:
           allOf:
             - $ref: '#/components/schemas/CorrelationId'
-          description: >
-            The ID given to the original consent request on which this consent
-            is based.
+          description: |
+            The ID given to the original consent request on which this consent is based.
         scopes:
           type: array
           minLength: 1
@@ -3518,12 +3061,9 @@ components:
     ConsentsIDPutResponseSigned:
       title: ConsentsIDPutResponseSigned
       type: object
-      description: >
-        The HTTP request `PUT /consents/{ID}` is used by the PISP to update a
-        Consent with a signed challenge and register a credential.
-
-        Called by a `PISP` to after signing a challenge. Sent to a DFSP for
-        verification.
+      description: |
+        The HTTP request `PUT /consents/{ID}` is used by the PISP to update a Consent with a signed challenge and register a credential.
+        Called by a `PISP` to after signing a challenge. Sent to a DFSP for verification.
       properties:
         status:
           $ref: '#/components/schemas/ConsentStatusIssued'
@@ -3550,18 +3090,12 @@ components:
     VerifiedCredential:
       title: VerifiedCredential
       type: object
-      description: >
+      description: |
         A credential used to allow a user to prove their identity and access
-
         to an account with a DFSP.
 
-
-        VerifiedCredential is a special formatting of Credential to allow us to
-        be
-
-        more explicit about the `status` field - it should only ever be VERIFIED
-        when
-
+        VerifiedCredential is a special formatting of Credential to allow us to be
+        more explicit about the `status` field - it should only ever be VERIFIED when
         updating a credential.
       properties:
         credentialType:
@@ -3579,12 +3113,9 @@ components:
     ConsentsIDPutResponseVerified:
       title: ConsentsIDPutResponseVerified
       type: object
-      description: >
-        The HTTP request `PUT /consents/{ID}` is used by the DFSP or
-        Auth-Service to update a Consent object once it has been Verified.
-
-        Called by a `auth-service` to notify a DFSP that a credential has been
-        verified and registered.
+      description: |
+        The HTTP request `PUT /consents/{ID}` is used by the DFSP or Auth-Service to update a Consent object once it has been Verified.
+        Called by a `auth-service` to notify a DFSP that a credential has been verified and registered.
       properties:
         status:
           $ref: '#/components/schemas/ConsentStatusIssued'
@@ -3649,19 +3180,14 @@ components:
     ParticipantsTypeIDPutResponse:
       title: ParticipantsTypeIDPutResponse
       type: object
-      description: >-
-        The object sent in the PUT /participants/{Type}/{ID}/{SubId} and
-        /participants/{Type}/{ID} callbacks.
+      description: The object sent in the PUT /participants/{Type}/{ID}/{SubId} and /participants/{Type}/{ID} callbacks.
       properties:
         fspId:
           $ref: '#/components/schemas/FspId'
     ParticipantsTypeIDSubIDPostRequest:
       title: ParticipantsTypeIDSubIDPostRequest
       type: object
-      description: >-
-        The object sent in the POST /participants/{Type}/{ID}/{SubId} and
-        /participants/{Type}/{ID} requests. An additional optional ExtensionList
-        element has been added as part of v1.1 changes.
+      description: The object sent in the POST /participants/{Type}/{ID}/{SubId} and /participants/{Type}/{ID} requests. An additional optional ExtensionList element has been added as part of v1.1 changes.
       properties:
         fspId:
           $ref: '#/components/schemas/FspId'
@@ -3674,17 +3200,11 @@ components:
     ServicesServiceTypePutResponse:
       title: ServicesServiceTypePutResponse
       type: object
-      description: >-
+      description: |-
         Used by: Switch
-
-        The callback PUT /services/{ServiceType} is used to inform the client of
-        a successful result of the service information lookup.
-
+        The callback PUT /services/{ServiceType} is used to inform the client of a successful result of the service information lookup.
         Callback and data model information for GET /services/{ServiceType}:
-
-        Callback - PUT /services/{ServiceType} Error Callback - PUT
-        /services/{ServiceType}/error Data Model - Empty body
-
+        Callback - PUT /services/{ServiceType} Error Callback - PUT /services/{ServiceType}/error Data Model - Empty body
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31531-put-servicesservicetype
       properties:
         providers:
@@ -3700,30 +3220,18 @@ components:
     ThirdpartyRequestsTransactionsPostRequest:
       title: ThirdpartyRequestsTransactionsPostRequest
       type: object
-      description: >-
+      description: |-
         Used by: PISP
-
-        The HTTP request POST /thirdpartyRequests/transactions is used to
-        request the creation of a transaction request on the server for the
-        transfer described in the request.
-
-        Callback and data model information for POST
-        /thirdpartyRequests/transactions:
-
-        Callback - PUT /thirdpartyRequests/transactions/{ID} Error Callback -
-        PUT /thirdpartyRequests/transactions/{ID}/error Data Model - See link
-        below
-
+        The HTTP request POST /thirdpartyRequests/transactions is used to request the creation of a transaction request on the server for the transfer described in the request.
+        Callback and data model information for POST /thirdpartyRequests/transactions:
+        Callback - PUT /thirdpartyRequests/transactions/{ID} Error Callback - PUT /thirdpartyRequests/transactions/{ID}/error Data Model - See link below
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31712-post-thirdpartyrequeststransactions
       properties:
         transactionRequestId:
           allOf:
             - $ref: '#/components/schemas/CorrelationId'
-          description: >
-            Common ID between the PISP and the Payer DFSP for the transaction
-            request object. The ID should be reused for resends of the same
-            transaction request. A new ID should be generated for each new
-            transaction request.
+          description: |
+            Common ID between the PISP and the Payer DFSP for the transaction request object. The ID should be reused for resends of the same transaction request. A new ID should be generated for each new transaction request.
         payee:
           allOf:
             - $ref: '#/components/schemas/Party'
@@ -3751,10 +3259,8 @@ components:
           description: A memo that will be attached to the transaction.
         expiration:
           type: string
-          description: >
-            Date and time until when the transaction request is valid. It can be
-            set to get a quick failure in case the peer FSP takes too long to
-            respond.
+          description: |
+            Date and time until when the transaction request is valid. It can be set to get a quick failure in case the peer FSP takes too long to respond.
           example: '2016-05-24T08:38:08.699-04:00'
         extensionList:
           $ref: '#/components/schemas/ExtensionList'
@@ -3769,15 +3275,9 @@ components:
     ThirdpartyRequestsTransactionsIDPutResponse:
       title: ThirdpartyRequestsTransactionsIDPutResponse
       type: object
-      description: >-
+      description: |-
         Used by: DFSP
-
-        After a PISP requests the creation of a Third Party Transaction request
-        (POST /thirdpartyRequests/transactions) or the status of a previously
-        created Third Party Transaction request (GET
-        /thirdpartyRequests/transactions/{ID}), the DFSP will send this
-        callback.
-
+        After a PISP requests the creation of a Third Party Transaction request (POST /thirdpartyRequests/transactions) or the status of a previously created Third Party Transaction request (GET /thirdpartyRequests/transactions/{ID}), the DFSP will send this callback.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31721-put-thirdpartyrequeststransactionsid
       properties:
         transactionId:
@@ -3790,20 +3290,11 @@ components:
         - transactionRequestState
     ThirdpartyRequestsAuthorizationsPostRequest:
       title: ThirdpartyRequestsAuthorizationsPostRequest
-      description: >-
+      description: |-
         Used by: DFSP
-
-        The HTTP request POST /thirdpartyRequests/authorizations is used to
-        request the validation by a customer for the transfer described in the
-        request.
-
-        Callback and data model information for POST
-        /thirdpartyRequests/authorizations:
-
-        Callback - PUT /thirdpartyRequests/authorizations/{ID} Error Callback -
-        PUT /thirdpartyRequests/authorizations/{ID}/error Data Model - See below
-        url
-
+        The HTTP request POST /thirdpartyRequests/authorizations is used to request the validation by a customer for the transfer described in the request.
+        Callback and data model information for POST /thirdpartyRequests/authorizations:
+        Callback - PUT /thirdpartyRequests/authorizations/{ID} Error Callback - PUT /thirdpartyRequests/authorizations/{ID}/error Data Model - See below url
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31612-post-thirdpartyrequestsauthorizations
       type: object
       properties:
@@ -3817,27 +3308,19 @@ components:
         transferAmount:
           allOf:
             - $ref: '#/components/schemas/Money'
-          description: >-
-            The amount that will be debited from the sending customer's account
-            as a consequence of the transaction.
+          description: The amount that will be debited from the sending customer's account as a consequence of the transaction.
         payeeReceiveAmount:
           allOf:
             - $ref: '#/components/schemas/Money'
-          description: >-
-            The amount that will be credited to the receiving customer's account
-            as a consequence of the transaction.
+          description: The amount that will be credited to the receiving customer's account as a consequence of the transaction.
         fees:
           allOf:
             - $ref: '#/components/schemas/Money'
-          description: >-
-            The amount of fees that the paying customer will be charged as part
-            of the transaction.
+          description: The amount of fees that the paying customer will be charged as part of the transaction.
         payer:
           allOf:
             - $ref: '#/components/schemas/PartyIdInfo'
-          description: >-
-            Information about the Payer type, id, sub-type/id, FSP Id in the
-            proposed financial transaction.
+          description: Information about the Payer type, id, sub-type/id, FSP Id in the proposed financial transaction.
         payee:
           allOf:
             - $ref: '#/components/schemas/Party'
@@ -3847,9 +3330,7 @@ components:
         expiration:
           allOf:
             - $ref: '#/components/schemas/DateTime'
-          description: >-
-            The time by which the transfer must be completed, set by the payee
-            DFSP.
+          description: The time by which the transfer must be completed, set by the payee DFSP.
         extensionList:
           $ref: '#/components/schemas/ExtensionList'
       required:
@@ -3874,9 +3355,7 @@ components:
     ThirdpartyRequestsAuthorizationsIDPutResponseRejected:
       title: ThirdpartyRequestsAuthorizationsIDPutResponseRejected
       type: object
-      description: >-
-        The object sent in the PUT /thirdpartyRequests/authorizations/{ID}
-        callback.
+      description: The object sent in the PUT /thirdpartyRequests/authorizations/{ID} callback.
       properties:
         responseType:
           $ref: '#/components/schemas/AuthorizationResponseTypeRejected'
@@ -3900,20 +3379,14 @@ components:
     FIDOPublicKeyCredentialAssertion:
       title: FIDOPublicKeyCredentialAssertion
       type: object
-      description: >
+      description: |
         A data model representing a FIDO Assertion result.
-
         Derived from PublicKeyCredential Interface in WebAuthN.
 
-
-        The PublicKeyCredential interface represents the below fields with a
-        Type of
-
+        The PublicKeyCredential interface represents the below fields with a Type of
         Javascript ArrayBuffer.
-
         For this API, we represent ArrayBuffers as base64 encoded utf-8 strings.
 
-
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#32128-fidopublickeycredentialassertion
       properties:
         id:
@@ -3948,9 +3421,8 @@ components:
               maxLength: 512
             signature:
               type: string
-              description: >
-                The signature generated by the private key associated with this
-                credential.
+              description: |
+                The signature generated by the private key associated with this credential.
               minLength: 59
               maxLength: 256
             userHandle:
@@ -3991,9 +3463,7 @@ components:
     ThirdpartyRequestsAuthorizationsIDPutResponseFIDO:
       title: ThirdpartyRequestsAuthorizationsIDPutResponseFIDO
       type: object
-      description: >-
-        The object sent in the PUT /thirdpartyRequests/authorizations/{ID}
-        callback.
+      description: The object sent in the PUT /thirdpartyRequests/authorizations/{ID} callback.
       properties:
         responseType:
           $ref: '#/components/schemas/AuthorizationResponseTypeAccepted'
@@ -4026,9 +3496,7 @@ components:
     ThirdpartyRequestsAuthorizationsIDPutResponseGeneric:
       title: ThirdpartyRequestsAuthorizationsIDPutResponseGeneric
       type: object
-      description: >-
-        The object sent in the PUT /thirdpartyRequests/authorizations/{ID}
-        callback.
+      description: The object sent in the PUT /thirdpartyRequests/authorizations/{ID} callback.
       properties:
         responseType:
           $ref: '#/components/schemas/AuthorizationResponseTypeAccepted'
@@ -4054,10 +3522,8 @@ components:
         consentId:
           allOf:
             - $ref: '#/components/schemas/CorrelationId'
-          description: >
-            The id of the stored consent object that contains the credential
-            with which to verify
-
+          description: |
+            The id of the stored consent object that contains the credential with which to verify
             the signed challenge against.
         signedPayloadType:
           $ref: '#/components/schemas/SignedPayloadTypeFIDO'
@@ -4085,10 +3551,8 @@ components:
         consentId:
           allOf:
             - $ref: '#/components/schemas/CorrelationId'
-          description: >
-            The id of the stored consent object that contains the credential
-            with which to verify
-
+          description: |
+            The id of the stored consent object that contains the credential with which to verify
             the signed challenge against.
         signedPayloadType:
           $ref: '#/components/schemas/SignedPayloadTypeGeneric'
@@ -4107,24 +3571,15 @@ components:
       type: string
       enum:
         - VERIFIED
-      description: >-
-        The AuthenticationResponse enumeration describes the result of
-        authenticating verification request.
-
-        Below are the allowed values for the enumeration AuthenticationResponse.
-        - VERIFIED - The challenge was correctly signed.
+      description: |-
+        The AuthenticationResponse enumeration describes the result of authenticating verification request.
+        Below are the allowed values for the enumeration AuthenticationResponse. - VERIFIED - The challenge was correctly signed.
     ThirdpartyRequestsVerificationsIDPutResponse:
       title: ThirdpartyRequestsVerificationsIDPutResponse
       type: object
-      description: >-
+      description: |-
         Used by: Auth Service
-
-        The callback PUT /thirdpartyRequests/verifications/{ID} is used to
-        inform the client of the result of an authorization check. The {ID} in
-        the URI should contain the authorizationRequestId which was used to
-        request the check, or the {ID} that was used in the GET
-        /thirdpartyRequests/verifications/{ID}.
-
+        The callback PUT /thirdpartyRequests/verifications/{ID} is used to inform the client of the result of an authorization check. The {ID} in the URI should contain the authorizationRequestId which was used to request the check, or the {ID} that was used in the GET /thirdpartyRequests/verifications/{ID}.
         https://github.com/mojaloop/documentation/blob/main/website/versioned_docs/v1.0.1/api/thirdparty/data-models.md#31821-put-thirdpartyrequestsverificationsid
       properties:
         authenticationResponse:
@@ -4147,9 +3602,7 @@ components:
       schema:
         type: string
       required: true
-      description: >-
-        The `Content-Type` header indicates the specific version of the API used
-        to send the payload body.
+      description: The `Content-Type` header indicates the specific version of the API used to send the payload body.
     Date:
       name: Date
       in: header
@@ -4163,107 +3616,69 @@ components:
       schema:
         type: string
       required: false
-      description: >-
-        The `X-Forwarded-For` header field is an unofficially accepted standard
-        used for informational purposes of the originating client IP address, as
-        a request might pass multiple proxies, firewalls, and so on. Multiple
-        `X-Forwarded-For` values should be expected and supported by
-        implementers of the API.
-
+      description: |-
+        The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
 
-        **Note:** An alternative to `X-Forwarded-For` is defined in [RFC
-        7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC
-        7239 is less-used and supported than `X-Forwarded-For`.
+        **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
     FSPIOP-Source:
       name: FSPIOP-Source
       in: header
       schema:
         type: string
       required: true
-      description: >-
-        The `FSPIOP-Source` header field is a non-HTTP standard field used by
-        the API for identifying the sender of the HTTP request. The field should
-        be set by the original sender of the request. Required for routing and
-        signature verification (see header field `FSPIOP-Signature`).
+      description: The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`).
     FSPIOP-Destination:
       name: FSPIOP-Destination
       in: header
       schema:
         type: string
       required: false
-      description: >-
-        The `FSPIOP-Destination` header field is a non-HTTP standard field used
-        by the API for HTTP header based routing of requests and responses to
-        the destination. The field must be set by the original sender of the
-        request if the destination is known (valid for all services except GET
-        /parties) so that any entities between the client and the server do not
-        need to parse the payload for routing purposes. If the destination is
-        not known (valid for service GET /parties), the field should be left
-        empty.
+      description: The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty.
     FSPIOP-Encryption:
       name: FSPIOP-Encryption
       in: header
       schema:
         type: string
       required: false
-      description: >-
-        The `FSPIOP-Encryption` header field is a non-HTTP standard field used
-        by the API for applying end-to-end encryption of the request.
+      description: The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request.
     FSPIOP-Signature:
       name: FSPIOP-Signature
       in: header
       schema:
         type: string
       required: false
-      description: >-
-        The `FSPIOP-Signature` header field is a non-HTTP standard field used by
-        the API for applying an end-to-end request signature.
+      description: The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature.
     FSPIOP-URI:
       name: FSPIOP-URI
       in: header
       schema:
         type: string
       required: false
-      description: >-
-        The `FSPIOP-URI` header field is a non-HTTP standard field used by the
-        API for signature verification, should contain the service URI. Required
-        if signature verification is used, for more information, see [the API
-        Signature
-        document](https://github.com/mojaloop/docs/tree/main/Specification%20Document%20Set).
+      description: The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/main/Specification%20Document%20Set).
     FSPIOP-HTTP-Method:
       name: FSPIOP-HTTP-Method
       in: header
       schema:
         type: string
       required: false
-      description: >-
-        The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used
-        by the API for signature verification, should contain the service HTTP
-        method. Required if signature verification is used, for more
-        information, see [the API Signature
-        document](https://github.com/mojaloop/docs/tree/main/Specification%20Document%20Set).
+      description: The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/main/Specification%20Document%20Set).
     Accept:
       name: Accept
       in: header
       required: true
       schema:
         type: string
-      description: >-
-        The `Accept` header field indicates the version of the API the client
-        would like the server to use.
+      description: The `Accept` header field indicates the version of the API the client would like the server to use.
     Content-Length:
       name: Content-Length
       in: header
       required: false
       schema:
         type: integer
-      description: >-
-        The `Content-Length` header field indicates the anticipated size of the
-        payload body. Only sent if there is a body.
-
+      description: |-
+        The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
 
-        **Note:** The API supports a maximum size of 5242880 bytes (5
-        Megabytes).
+        **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
     Type:
       name: Type
       in: path
@@ -4376,17 +3791,12 @@ components:
       required: false
       schema:
         type: integer
-      description: >-
-        The `Content-Length` header field indicates the anticipated size of the
-        payload body. Only sent if there is a body.
-
+      description: |-
+        The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
 
-        **Note:** The API supports a maximum size of 5242880 bytes (5
-        Megabytes).
+        **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
     Content-Type:
       schema:
         type: string
       required: true
-      description: >-
-        The `Content-Type` header indicates the specific version of the API used
-        to send the payload body.
+      description: The `Content-Type` header indicates the specific version of the API used to send the payload body.