components:
  schemas:
    ErrorPayload:
      properties:
        failures:
          items:
            $ref: '#/components/schemas/Failure'
          type: array
        request:
          $ref: '#/components/schemas/RequestEcho'
      type: object
    ErrorResponse:
      properties:
        groupHeader:
          $ref: '#/components/schemas/ExternalResponseHeader'
        response:
          $ref: '#/components/schemas/ErrorPayload'
      type: object
    ExternalResponseHeader:
      properties:
        creationDateTime:
          format: date-time
          type: string
        httpCode:
          format: int32
          type: integer
        messageIdentification:
          type: string
      type: object
    Failure:
      properties:
        code:
          type: string
        description:
          type: string
        path:
          type: string
        type:
          type: string
      type: object
    RequestEcho:
      properties:
        url:
          type: string
      type: object
host: api.nordeaopenbanking.com
info:
  description: Multi-Payout Instant
  title: Multi-Payout Instant API
  version: '1.1'
openapi: 3.0.1
paths:
  /premium/v1/multi-payout-instant:
    post:
      description: Initiate Multi-Payout Instant payments
      operationId: initiation
      parameters:
      - description: Technical header for internal Nordea processing. Not to be provided
          while calling API
        in: header
        name: Authorization
        required: true
        schema:
          type: string
      - description: Id of the Client
        in: header
        name: X-IBM-Client-Id
        required: true
        schema:
          type: string
      - description: Secret password generated for the Client
        in: header
        name: X-IBM-Client-Secret
        required: true
        schema:
          type: string
      - description: 'A signature of request by the API Consumer on application level.
          The process of signing a request is described in ''Signing HTTP Messages''
          RFC draft version 10 (<a href="https://tools.ietf.org/html/draft-cavage-http-signatures-10"
          target="_blank">https://tools.ietf.org/html/draft-cavage-http-signatures-10</a>).
          The request signature needs to be sent in the ''Signature'' HTTP header
          as described in the RFC. Additional requirements from Nordea - The only
          allowed algorithm is RSA-SHA256 - The key size for the used RSA key pair
          has to be at least 2048 bit - The keyId is the clientId of your application
          originating from the Nordea Developer Portal - We require the following
          headers to be used in the signature * Request without body: (request-target)
          X-Nordea-Originating-Host X-Nordea-Originating-Date * Request with body:
          (request-target) X-Nordea-Originating-Host X-Nordea-Originating-Date Content-type
          Digest * The request-target is a combination of the HTTP action verb and
          the request URI path'
        in: header
        name: Signature
        required: true
        schema:
          type: string
      - description: HTTP header element for specification of the domain name of the
          server. It is similar to standard HTTP 'Host' header but it won't be overridden
          by proxies. It also allows to set it under JavaScript in browser while standard
          'Host' is forbidden
        in: header
        name: X-Nordea-Originating-Host
        required: true
        schema:
          type: string
      - description: 'HTTP header element for date and time represented as RFC 7231
          Full Dates (GMT). Example date: {}Wed, 24 Apr 2019 14:00:37 GMT{}. It is
          similar to standard HTTP ''Date'' expect that it allows to set it under
          JavaScript in browser while standard ''Date'' is forbidden'
        in: header
        name: X-Nordea-Originating-Date
        required: true
        schema:
          type: string
      - description: "The Digest Header header as defined in [RFC3230] contains a\
          \ Hash of the message body. The only hash algorithms that may be used to\
          \ calculate the Digest within the context of this specification are SHA-256\
          \ and SHA-512 as defined in [RFC5843]. For POST with \u2018application/x-www-form-urlencoded\u2019\
          \ content type Digest should be calculated for normalized string created\
          \ from request parameters like this: 'param1=value1&param2=value2\u2019\
          . It is important that parameters should be placed in alphabetic order"
        in: header
        name: Digest
        required: true
        schema:
          type: string
      requestBody:
        content:
          application/xml:
            schema:
              type: string
        description: Pain.001.001.09
        required: true
      responses:
        '202':
          content:
            application/xml:
              schema:
                type: string
          description: Multi-Payout Instant payments result with Pain.002.001.10
        '403':
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Credential failure
      tags:
      - multi-payout-instant-v1
  /premium/v1/multi-payout-instant/report/{batch_identification}:
    get:
      description: Get Multi-Payout Instant report
      operationId: report
      parameters:
      - description: Technical header for internal Nordea processing. Not to be provided
          while calling API
        in: header
        name: Authorization
        required: true
        schema:
          type: string
      - description: Id of the Client
        in: header
        name: X-IBM-Client-Id
        required: true
        schema:
          type: string
      - description: Secret password generated for the Client
        in: header
        name: X-IBM-Client-Secret
        required: true
        schema:
          type: string
      - description: 'A signature of request by the API Consumer on application level.
          The process of signing a request is described in ''Signing HTTP Messages''
          RFC draft version 10 (<a href="https://tools.ietf.org/html/draft-cavage-http-signatures-10"
          target="_blank">https://tools.ietf.org/html/draft-cavage-http-signatures-10</a>).
          The request signature needs to be sent in the ''Signature'' HTTP header
          as described in the RFC. Additional requirements from Nordea - The only
          allowed algorithm is RSA-SHA256 - The key size for the used RSA key pair
          has to be at least 2048 bit - The keyId is the clientId of your application
          originating from the Nordea Developer Portal - We require the following
          headers to be used in the signature * Request without body: (request-target)
          X-Nordea-Originating-Host X-Nordea-Originating-Date * Request with body:
          (request-target) X-Nordea-Originating-Host X-Nordea-Originating-Date Content-type
          Digest * The request-target is a combination of the HTTP action verb and
          the request URI path'
        in: header
        name: Signature
        required: true
        schema:
          type: string
      - description: HTTP header element for specification of the domain name of the
          server. It is similar to standard HTTP 'Host' header but it won't be overridden
          by proxies. It also allows to set it under JavaScript in browser while standard
          'Host' is forbidden
        in: header
        name: X-Nordea-Originating-Host
        required: true
        schema:
          type: string
      - description: 'HTTP header element for date and time represented as RFC 7231
          Full Dates (GMT). Example date: {}Wed, 24 Apr 2019 14:00:37 GMT{}. It is
          similar to standard HTTP ''Date'' expect that it allows to set it under
          JavaScript in browser while standard ''Date'' is forbidden'
        in: header
        name: X-Nordea-Originating-Date
        required: true
        schema:
          type: string
      - description: message_identification from Group Header provided in Pain002
          response
        in: path
        name: batch_identification
        required: true
        schema:
          type: string
      - description: Optional. Provide if only specific payment identification and
          its transactions are to be returned
        in: query
        name: payment_information_identification
        required: false
        schema:
          type: string
      - description: Optional. Provide if only specific transaction from specific
          payment identification is to be returned. payment_information_identification
          must be provided
        in: query
        name: end_to_end_identification
        required: false
        schema:
          type: string
      responses:
        '200':
          content:
            application/xml:
              schema:
                type: string
          description: Multi-Payout Instant payments report with Pain.002.001.10
        '404':
          content:
            application/xml:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Multi-Payout Instant payments not found
      tags:
      - multi-payout-instant-v1
servers:
- description: Generated server url
  url: https://multi-payout-instant-sandbox-obh.esp.rs.dev01.qaoneadr.local/corporate
tags:
- description: Multi-Payout Instant V1
  name: multi-payout-instant-v1
