TietoEVRY

Tietoevry SEPA Direct Debits

A SEPA Direct Debit gateway for Creditor and Debtor roles, allowing creditors to initiate payments, cancel (reverse) them and issue refunds, and debtors to reject payments and raise chargebacks, with an event-notification webhook mechanism that pushes state changes for payments, refunds and incoming collections to Creditor-Notification-URI and Debtor-Notification-URI endpoints.

GitHub OpenAPI

Operations 15

POST /{receiveRefund} (Webhook) Receive a Refund #
POST /{receivePaymentCharge} (Webhook) Receive Payment Charge #
POST /{verifyCreditorAndAccounts} (Webhook) Verify creditor and accounts #
POST /{confirmAvailabilityOfFunds} (Webhook) Confirm availability of funds #
POST /v1/creditor/payments Create payment #
POST /{receivePaymentStatus} (Callback) Receive Payment Status #
GET /v1/creditor/payments/{payment-id} Get payment #
POST /v1/creditor/payments/{payment-id}/actions/cancel Cancel payment #
POST /v1/creditor/payments/{payment-id}/refunds Create a refund #
POST /{receiveRefundStatus} (Callback) Receive Refund Status #
GET /v1/creditor/payments/{payment-id}/refunds/{refund-id} Get refund #
POST /v1/debtor/payments/{payment-id}/actions/reject Reject payment #
POST /v1/debtor/payments/{payment-id}/chargebacks Create a chargeback #
POST /{receiveChargebackStatus} (Callback) Receive Chargeback Status #
GET /v1/debtor/payments/{payment-id}/chargebacks/{chargeback-id} Get chargeback #

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/tietoevry/refs/heads/main/openapi/tietoevry-sepa-direct-debit-api-gateway.yaml
⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/tietoevry/refs/heads/main/openapi/tietoevry-sepa-direct-debit.yaml

Other Resources

🔗
Overlay
https://raw.githubusercontent.com/api-evangelist/tietoevry/refs/heads/main/overlays/tietoevry-sepa-direct-debit-api-gateway-overlay.yaml
🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/tietoevry/refs/heads/main/asyncapi/tietoevry-sepa-direct-debit-webhooks.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/tietoevry-sepa-direct-debits"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

tietoevry-sepa-direct-debit-api-gateway.yaml Raw ↑ 
openapi: 3.0.1
info:
  title: SEPA Direct Debits
  description: |
    This service enables clients to initiate and accept SEPA Direct Debit payments.
    It includes an API for Creditor and for Debtor roles, which allows to initiate Payments and Refunds, accept payments and create Chargebacks.
    The API also includes an Event Notification mechanism to stay notified about the state changes of Payments, Refunds and about incoming Payments.
  version: '1'
  contact:
    name: Tietoevry Payment Services
    url: 'https://tieto.ob5.konts.lv/documentation/payment-services/sepa-direct-debit/v1.0'
servers:
  - url: 'https://payments.api.tieto.com/sandbox/v1/sepadd'
    description: Sepa DD Sandbox service
  - url: 'https://payments.api.tieto.com/live/v1/sepadd'
    description: Sepa DD Live service
security:
  - bearerToken: []
tags:
  - name: Creditor
    description: Operation for creditors
  - name: Debtor
    description: Operation for debtors
paths:
  /{receiveRefund}:
    post:
      operationId: receiveRefund
      summary: (Webhook) Receive a Refund
      description: To receive creditor-initiated refunds, the client must host an endpoint, which the system will invoke. The Refund references one or more original payments.
      tags:
        - Debtor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - type: object
                  properties:
                    refundId:
                      type: string
                      description: Refund identification
                      example: 3d9bbfe2-1942-4036-b1e3-d49e65c26a29
                    payments:
                      type: array
                      items:
                        type: object
                        properties:
                          paymentId:
                            type: string
                            description: Payment identification
                            example: 3d9bbfe2-1942-4036-b1e3-d49e65c26a28
                - $ref: '#/components/schemas/PaymentRequest'
      responses:
        '204':
          description: Received a refund processed successfully
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /{receivePaymentCharge}:
    post:
      operationId: receivePaymentCharge
      summary: (Webhook) Receive Payment Charge
      description: 'To receive incoming Direct Debits, the client must host a payment charges endpoint, which will be called by the system.'
      tags:
        - Debtor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - type: object
                  properties:
                    paymentId:
                      type: string
                      description: Payment identification
                      example: 6aa06e57-031d-4359-ae5d-0188cb7817c7
                - $ref: '#/components/schemas/PaymentRequest'
      responses:
        '204':
          description: Payment charge is received successfully
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /{verifyCreditorAndAccounts}:
    post:
      operationId: verifyCreditorAndAccounts
      summary: (Webhook) Verify creditor and accounts
      description: "The system will call back to the client to verify the effective state of the Creditor and of the creditor's Accounts. This callback may occur multiple times during the processing of a payment, and the client must host an endpoint, which will be called by the system"
      tags:
        - Creditor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                creditor:
                  type: object
                  properties:
                    creditorId:
                      type: string
                      description: Identification of Creditors, e.g. a SEPA Creditor ID.
                      example: DE452399865083
                    creditorName:
                      type: string
                      description: Creditor Name
                    creditorAddress:
                      $ref: '#/components/schemas/Address'
                account:
                  type: object
                  description: Account that need to be verified
                  properties:
                    iban:
                      type: string
                      description: IBAN of an account
                      example: DE89370400440532013000
                    currency:
                      type: string
                      description: ISO 4217 Alpha 3 currency code
                      example: EUR
                    ownerName:
                      type: string
                      description: Owner name
                    name:
                      type: string
                    bic:
                      type: string
                      description: BICFI
                      example: AAAADEBBXXX
                    status:
                      type: string
                      description: Status of the account
                      example: enabled
      responses:
        '204':
          description: Successful creditor and account check
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /{confirmAvailabilityOfFunds}:
    post:
      operationId: confirmAvailabilityOfFunds
      summary: (Webhook) Confirm availability of funds
      description: |
        When processing incoming Direct Debits, the payment engine requires early on the information about the availability of funds on the debtor account.
        The client must host an endpoint, which will be called by the system for that purpose, during pre-processing of incoming payments.
      tags:
        - Debtor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                account:
                  $ref: '#/components/schemas/AccountReference'
                instructedAmount:
                  $ref: '#/components/schemas/Amount'
      responses:
        '204':
          description: Funds available
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /v1/creditor/payments:
    post:
      operationId: createPayment
      summary: Create payment
      description: 'To initiate a Payment, the Creditor must provide essential information, including the account information, the instructed amount, remittance and information about the Mandate.'
      tags:
        - Creditor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
        - name: Creditor-Notification-URI
          in: header
          description: 'URI of a webhook, which will receive event notifications about the particular initiated payment'
          schema:
            type: string
      requestBody:
        description: Payment body
        required: true
        content:
          application/json:
            schema:
              allOf:
                - $ref: '#/components/schemas/PaymentRequest'
                - type: object
                  properties:
                    metadata:
                      type: object
                      description: Data that provides information about payment
                      example:
                        anyKey: value
      responses:
        '201':
          description: Create payment message is received
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PaymentStatus'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /{receivePaymentStatus}:
    post:
      operationId: receivePaymentStatus
      summary: (Callback) Receive Payment Status
      description: |
        When creating a Payment, the client specifies a Creditor-Notification-URI header during the payment initiation request, the system will post event notifications to that specific URI.
        Essentially, events, which change the state of a particular payment, are posted back to the client, to the specified URI.
      tags:
        - Creditor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - $ref: '#/components/schemas/PaymentStatus'
                - $ref: '#/components/schemas/Event'
      responses:
        '204':
          description: Received payment status processed succesfully
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /v1/creditor/payments/{payment-id}:
    parameters:
      - $ref: '#/components/parameters/payment-id'
    get:
      operationId: getPayment
      summary: Get payment
      description: Get previously initiated payment message
      tags:
        - Creditor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
      responses:
        '200':
          description: Previously initiated payment message is found
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PaymentStatus'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  '/v1/creditor/payments/{payment-id}/actions/cancel':
    parameters:
      - $ref: '#/components/parameters/payment-id'
    post:
      operationId: cancelPayment
      summary: Cancel payment
      description: To cancel (reverse) a payment, the following request can be used. The reason code should be specified, e.g. "MD05" - "Collection not due".
      tags:
        - Creditor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
      requestBody:
        description: Reason
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                reasonCode:
                  $ref: '#/components/schemas/ReasonCode'
      responses:
        '204':
          description: Payment cancellation request is processed successfully
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /v1/creditor/payments/{payment-id}/refunds:
    parameters:
      - $ref: '#/components/parameters/payment-id'
    post:
      operationId: createRefund
      summary: Create a refund
      description: |
        To create a Refund for a previously initiated Payment, use the refunds endpoint.
        The paymentId of the original Payment must be specified.
        In addition, the original amount must be specified, and it must be equal to the original amount of the initial Payment, minus all previously made refunds to that initial Payment.

        The Creditor-Notification-URI header in the request specifies the URI of a webhook, which will receive event notifications about the particular created refund.
      tags:
        - Creditor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
        - name: Creditor-Notification-URI
          in: header
          description: 'URI of a webhook, which will receive event notifications about the particular initiated payment'
          schema:
            type: string
      requestBody:
        description: Reason
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                instructedAmount:
                  $ref: '#/components/schemas/Amount'
                originalAmount:
                  $ref: '#/components/schemas/Amount'
                metadata:
                  type: object
                  description: Data that provides information about payment
                  example:
                    anyKey: value
      responses:
        '201':
          description: Refund request is received
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RefundStatus'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /{receiveRefundStatus}:
    post:
      operationId: receiveRefundStatus
      summary: (Callback) Receive Refund Status
      description: |
        When creating a Refund, the client specifies a Creditor-Notification-URI header during the refund creation request,
        the system will post event notifications to that specific URI.
        Essentially, events, which change the state of the refund, are posted back to the client, to the specified URI.
      tags:
        - Creditor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - $ref: '#/components/schemas/RefundStatus'
                - $ref: '#/components/schemas/Event'
      responses:
        '204':
          description: Receive refund status processed succesfully
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /v1/creditor/payments/{payment-id}/refunds/{refund-id}:
    parameters:
      - $ref: '#/components/parameters/payment-id'
      - name: refund-id
        in: path
        required: true
        description: Refund identification
        schema:
          type: string
    get:
      operationId: getRefund
      summary: Get refund
      description: Get previously initiated refund request
      tags:
        - Creditor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
      responses:
        '200':
          description: Previously initiated refund request is found
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RefundStatus'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  '/v1/debtor/payments/{payment-id}/actions/reject':
    parameters:
      - $ref: '#/components/parameters/payment-id'
    post:
      operationId: rejectPayment
      summary: Reject payment
      description: |
        To reject a payment, the following request can be used.

        The reason code of rejection should be specified, e.g. "MD01" - "No Mandate".
      tags:
        - Debtor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
      requestBody:
        description: Reason
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                reasonCode:
                  $ref: '#/components/schemas/ReasonCode'
      responses:
        '204':
          description: Payment rejection message processed successfully
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /v1/debtor/payments/{payment-id}/chargebacks:
    parameters:
      - $ref: '#/components/parameters/payment-id'
    post:
      operationId: chargebackPayment
      summary: Create a chargeback
      description: |
        To create a Chargeback, the following request can be used.

        The reason code of rejection should be specified, e.g. "MD06" - "Refund Request By End Customer".
      tags:
        - Debtor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
        - name: Debtor-Notification-URI
          in: header
          description: 'URI of a webhook, which will receive event notifications about the particular initiated payment'
          schema:
            type: string
      requestBody:
        description: Reason
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                reasonCode:
                  $ref: '#/components/schemas/ReasonCode'
      responses:
        '201':
          description: Chargeback creation message processed successfully
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ChargebackStatus'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /{receiveChargebackStatus}:
    post:
      operationId: receiveChargebackStatus
      summary: (Callback) Receive Chargeback Status
      description: |
        Notifications about the client-initiated Chargeback status shall be posted to the Debtor-Notification-URI, which has been specified during the creation of the Chargeback.
      tags:
        - Debtor
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - $ref: '#/components/schemas/ChargebackStatus'
                - $ref: '#/components/schemas/Event'
      responses:
        '204':
          description: Received chargeback status message processed successfully
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
  /v1/debtor/payments/{payment-id}/chargebacks/{chargeback-id}:
    parameters:
      - $ref: '#/components/parameters/payment-id'
      - name: chargeback-id
        in: path
        required: true
        description: Chargeback identification
        schema:
          type: string
    get:
      operationId: getChargeback
      summary: Get chargeback
      description: Get previously initiated chargeback message
      tags:
        - Debtor
      parameters:
        - $ref: '#/components/parameters/X-Request-ID'
        - $ref: '#/components/parameters/Digest'
        - $ref: '#/components/parameters/Signature'
        - $ref: '#/components/parameters/Signature-Certificate'
      responses:
        '200':
          description: Previously initiated chargeback message is found
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ChargebackStatus'
        4XX:
          description: Bad request
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        5XX:
          description: Internal server error
          headers:
            X-Request-ID:
              $ref: '#/components/headers/X-Request-ID-5XX'
components:
  headers:
    X-Request-ID:
      description: 'ID of the request, unique to the call'
      required: true
      schema:
        type: string
        format: uuid
    X-Request-ID-5XX:
      description: 'ID of the request, unique to the call'
      schema:
        type: string
        format: uuid
  parameters:
    X-Request-ID:
      name: X-Request-ID
      in: header
      description: 'ID of the request, unique to the call'
      required: true
      schema:
        type: string
        format: uuid
    X-Request-ID-5XX:
      name: X-Request-ID
      in: header
      description: 'ID of the request, unique to the call'
      schema:
        type: string
        format: uuid
    Digest:
      name: Digest
      in: header
      description: Is contained if and only if the "Signature" element is contained in the header of the request.
      schema:
        type: string
      required: false # conditional
      example: 'SHA-256=hl1/Eps8BEQW58FJhDApwJXjGY4nr1ArGDHIT25vq6A='
    Signature:
      name: Signature
      in: header
      description: |
        A signature of the request by the TPP on application level. This might be mandated by ASPSP.
      schema:
        type: string
      required: false # conditional
      example: >
        keyId="SN=9FA1,CA=CN=D-TRUST%20CA%202-1%202015,O=D-Trust%20GmbH,C=DE",algorithm="rsa-sha256", headers="Digest X-Request-ID PSU-ID TPP-Redirect-URI Date", signature="Base64(RSA-SHA256(signing string))"
    Signature-Certificate:
      name: Signature-Certificate
      in: header
      description: |
        The certificate used for signing the request, in base64 encoding.
        Must be contained if a signature is contained.
      schema:
        type: string
        format: byte
      required: false # conditional
    payment-id:
      name: payment-id
      in: path
      required: true
      description: Payment identification
      schema:
        type: string
  schemas:
    TransactionStatus:
      description: |
        The transaction status is filled with codes of the ISO 20022 data table:
        - 'ACCP': 'AcceptedCustomerProfile' -
          Preceding check of technical validation was successful.
          Customer profile check was also successful.
        - 'ACSC': 'AcceptedSettlementCompleted' -
          Settlement on the debtor’s account has been completed.

          **Usage:** this can be used by the first agent to report to the debtor that the transaction has been completed.

          **Warning:** this status is provided for transaction status reasons, not for financial information.
          It can only be used after bilateral agreement.
        - 'ACSP': 'AcceptedSettlementInProcess' -
          All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution.
        - 'ACTC': 'AcceptedTechnicalValidation' -
          Authentication and syntactical and semantical validation are successful.
        - 'ACWC': 'AcceptedWithChange' -
          Instruction is accepted but a change will be made, such as date or remittance not sent.
        - 'ACWP': 'AcceptedWithoutPosting' -
          Payment instruction included in the credit transfer is accepted without being posted to the creditor customer’s account.
        - 'RCVD': 'Received' -
          Payment initiation has been received by the receiving agent.
        - 'PDNG': 'Pending' -
          Payment initiation or individual transaction included in the payment initiation is pending.
          Further checks and status update will be performed.
        - 'RJCT': 'Rejected' -
          Payment initiation or individual transaction included in the payment initiation has been rejected.
        - 'CANC': 'Cancelled'
          Payment initiation has been cancelled before execution

          **Remark:** *Change Request to ISO20022 is still needed.*
      type: string
      enum:
        - 'ACCP'
        - 'ACSC'
        - 'ACSP'
        - 'ACTC'
        - 'ACWC'
        - 'ACWP'
        - 'RCVD'
        - 'PDNG'
        - 'RJCT'
        - 'CANC'
      example: 'ACCP'
    ErrorResponse:
      type: object
      required:
        - transactionStatus
      properties:
        messages:
          type: array
          description: Messages on operational issues.
          items:
            type: object
            required:
              - category
              - code
            properties:
              category:
                type: string
                description: Category of the message category
                enum:
                  - 'ERROR'
                  - 'WARNING'
              code:
                type: string
                enum:
                  - 'CERTIFICATE_INVALID'
                  - 'CERTIFICATE_EXPIRED'
                  - 'CERTIFICATE_BLOCKED'
                  - 'CERTIFICATE_REVOKED'
                  - 'CERTIFICATE_MISSING'
                  - 'SIGNATURE_INVALID'
                  - 'SIGNATURE_MISSING'
                  - 'FORMAT_ERROR'
                  - 'PARAMETER_NOT_SUPPORTED'
                  - 'PSU_CREDENTIALS_INVALID'
                  - 'SERVICE_INVALID'
                  - 'SERVICE_BLOCKED'
                  - 'TOKEN_UNKNOWN'
                  - 'TOKEN_INVALID'
                  - 'TOKEN_EXPIRED'
                  - 'RESOURCE_UNKNOWN'
                  - 'RESOURCE_EXPIRED'
                  - 'TIMESTAMP_INVALID'
                  - 'PERIOD_INVALID'
                  - 'SCA_METHOD_UNKNOWN'
                  - 'PRODUCT_INVALID'
                  - 'PRODUCT_UNKNOWN'
                  - 'PAYMENT_FAILED'
                  - 'REQUIRED_KID_MISSING'
                  - 'EXECUTION_DATE_INVALID'
                  - 'ACCESS_EXCEEDED'
                  - 'REQUESTED_FORMATS_INVALID'
                  - 'CARD_INVALID'
                  - 'NO_PIIS_ACTIVATION'
              text:
                type: string
                description: Additional explaining text
        transactionStatus:
          $ref: '#/components/schemas/TransactionStatus'
    Amount:
      type: object
      required:
        - amount
        - currency
      properties:
        amount:
          type: string
          description: |
            The amount given with fractional digits, where fractions must be compliant to the currency definition.
            Up to 14 significant figures. Negative amounts are signed by minus.
            The decimal separator is a dot.

            **Example:**
            Valid representations for EUR with up to two decimals are:

              * 1056
              * 5768.2
              * -1.50
              * 5877.78
          example: '1000'
        currency:
          type: string
          description: ISO 4217 Alpha 3 currency code
          example: EUR
    AccountReference:
      type: object
      required:
        - iban
      properties:
        iban:
          type: string
          description: IBAN of an account
          example: DE89370400440532013000
    RemittanceInformationStructured:
      type: object
      description: Structured remittance information
      properties:
        reference:
          type: string
          example: REF123123
    MandateInformat

# --- truncated at 32 KB (36 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/tietoevry/refs/heads/main/openapi/tietoevry-sepa-direct-debit-api-gateway.yaml