Diebold Nixdorf

DN Online & Mobile API

Diebold Nixdorf Online & Mobile API — the Vynamic Transaction Middleware surface used by online and mobile banking channels for cardless and mobile-initiated self-service transactions. 35 paths, bearer/OpenID Connect authentication; OpenAPI 3.0.3, version 3.2.1.

GitHub OpenAPI

Operations 39

GET /getRsaKey Returns the public key (RSA) for API request encryption. #
GET /getEcKey Returns the public key (ECIES) of the server system. #
GET /getVersion Returns API version info. #
GET /getAccounts Returns a list of accounts for the given consumerId. #
GET /getAccountTypes Returns a list of supported account types. #
GET /checkAccount Check for account. #
POST /createTransfer Create a transfer of funds request. #
GET /getTransactions Returns all transactions for the given account and consumerId. #
GET /getScheduledTransactions Returns all scheduled transactions for the given account and consumerId. #
GET /getAccountDetails Returns detailed information for the given account and consumerId. #
GET /getStandingOrders Returns a list of standing orders for the given consumerId. #
POST /createStandingOrder Create a standing order for the given account and consumerId. #
POST /updateStandingOrder Update an existing standing order by the given referenceId. #
POST /deleteStandingOrder Delete an existing standing order. #
POST /createCashout4Me Create a prestaged cashout (withdrawal) transaction. #
POST /createCashout2You Create a prestaged cash out transaction request. #
POST /createDeposit Create a prestaged cashin/deposit transaction request. #
POST /createBranchDeposit Create a prestaged deposit transaction request. #
POST /deletePrestagedTransaction Delete existing prestaged transactions. #
GET /getPrestagedTransactions Returns a list of all prestaged transactions for the given consumerId. #
POST /executePrestagedTransaction Execute a prestaged transaction at an ATM with an accessCode. #
POST /getLocations Get all ATM locations. #
POST /createDispute File a dispute #
GET /getCreditors Get a list of system wide defined payees. #
GET /getSinglePaymentOrderData Get the details of a system wide defined creditor as returned in the getCreditorsResponse of a getCreditors call. #
GET /getPreferences Get a list of user defined parameters. #
POST /setPreferences Set a list of user defined parameters, which can be used to store any information. #
GET /getClientBranding Get the client branding file. #
POST /updateAccountNickName Update the account nickname. #
GET /getGenericTransactionOrders Get a list of system defined generic transaction orders. #
POST /executeGenericTransactionOrder Set a list of user defined parameters, which can be used to store any information. #
POST /registerForRemoteNotifications Register a mobile device - either iOS or Android - for remote notifications. #
POST /unregisterForRemoteNotifications Register a mobile device - either iOS or Android - for remote notifications. #
GET /sepa-instant/pushPayment Get the status of a SEPA Instant credit transfer #
POST /sepa-instant/pushPayment Create a SEPA instant payment request #
DELETE /sepa-instant/pushPayment Cancel a SEPA instant payment request #
GET /sepa-instant/pullPayment Get the status of a SEPA instant pull payment #
POST /sepa-instant/pullPayment Authorize a pending SEPA instant payment request (pull payment) #
DELETE /sepa-instant/pullPayment Cancel a pending SEPA instant payment request (pull payment) #

Documentation

📖
APIReference
https://api.swaggerhub.com/apis/Diebold-Nixdorf/dn_online_mobile_api/3.2.1

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/diebold/refs/heads/main/openapi/diebold-dn-online-mobile-api-openapi.yml

Other Resources

🔗
Overlay
https://raw.githubusercontent.com/api-evangelist/diebold/refs/heads/main/overlays/diebold-dn-online-mobile-api-overlay.yaml

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/dn-online-mobile-api"
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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

diebold-dn-online-mobile-api-openapi.yml Raw ↑ 
openapi: 3.0.3
info:
  title: DN Online & Mobile API
  description: Diebold Nixdorf Online & Mobile API.
  version: 3.2.1
  contact:
    name: Diebold Nixdorf
    email: info.de@dieboldnixdorf.com
externalDocs:
  description: Find out more about Swagger
  url: http://swagger.io
tags:
- name: Transaction Middleware
  externalDocs:
    description: Product page
    url: https://www.dieboldnixdorf.com/en-us/banking/portfolio/software/
servers:
- url: http://localhost:8080/tm-om-api/v4
  description: Transaction Middleware (VTE) 3.0+
- url: https://localhost:8080/tm-om-api/v4
  description: Transaction Middleware (VTE) 3.0+
paths:
  /getRsaKey:
    get:
      tags:
      - Accessibility API
      summary: Returns the public key (RSA) for API request encryption.
      description: "If the client decides to use the __RSA/AES__ encryption scheme the __/getRsaKey__ endpoint can be used\
        \ to obtain the server's public RSA key in PEM format. \n\nThe client is liable to encrypt all security relevant request\
        \ parameters and parts of the request body (where applicable) with a 256 bit AES key of his own choosing.\n\nThe key\
        \ parameters and initialization vector (128 bit) must be encrypted with the server's  public RSA key and transmitted\
        \ alongside the request."
      operationId: getRsaKey
      responses:
        '200':
          $ref: '#/components/responses/getRsaKeyResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getEcKey:
    get:
      tags:
      - Accessibility API
      summary: Returns the public key (ECIES) of the server system.
      description: 'If the client decides to use the __ECIES__ encryption scheme the __/getEcKey__ endpoint can be used to
        obtain the servers public EC key in PEM format.


        This key is used to encrypt critical request parameters and parts of  the request body (where applicable).


        ### NOTE:

        The ECIES implementation of iOS is not standard-compliant. At least until now.<br> In contrary to the description
        provided, Apple does not use authentication data in GCM.<br> That''s why __for iOS clients the RSA/AES based solution
        MUST be used__ by using the __/getRsaKey__ endpoint.'
      operationId: getEcKey
      responses:
        '200':
          $ref: '#/components/responses/getEcKeyResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getVersion:
    get:
      tags:
      - Accessibility API
      summary: Returns API version info.
      description: Returns API version information.
      operationId: getVersion
      responses:
        '200':
          $ref: '#/components/responses/getVersionResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getAccounts:
    get:
      tags:
      - Account Management API
      summary: Returns a list of accounts for the given consumerId.
      description: "Returns a list of accounts for the given consumerId (see __GetAccountsResponsePayload__).\n\n### Example\
        \ Response: \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\": null\
        \                      \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n           \
        \ \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n    \
        \    }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the response\
        \ payload. After the payload encryption the key parameters are encrypted with the client's public RSA key (see __clientSecretparam__).\
        \ The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity that is attached to the response\
        \ body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__) to encrypt the\
        \ response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached to the response\
        \ body."
      operationId: getAccounts
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/bankCodeParam'
      responses:
        '200':
          $ref: '#/components/responses/getAccountsResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getAccountTypes:
    get:
      tags:
      - Account Management API
      summary: Returns a list of supported account types.
      description: "Returns a list of supported account types (see __GetAccountTypesResponsePayload__).\n\n### Example Response:\
        \ \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\": null          \
        \            \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n            \"payload\"\
        : \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n        }\n    }\n\
        \n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the response payload.\
        \ After the payload encryption the key parameters are encrypted with the client's public RSA key (see __clientSecretparam__).\
        \ The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity that is attached to the response\
        \ body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__) to encrypt the\
        \ response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached to the response\
        \ body."
      operationId: getAccountTypes
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      responses:
        '200':
          $ref: '#/components/responses/getAccountTypesResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /checkAccount:
    get:
      tags:
      - Account Management API
      summary: Check for account.
      description: "Check if a given account does exist (see __CheckAccountResponse__).\n### Example Response:\n\n    {\n\
        \      \"responseStatus\": {\n        \"success\": true\n      }\n    }"
      operationId: checkAccount
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/bankCodeParam'
      - $ref: '#/components/parameters/accountNumberParam'
      - $ref: '#/components/parameters/accountTypeParam'
      responses:
        '200':
          $ref: '#/components/responses/checkAccountResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /createTransfer:
    post:
      tags:
      - Account Management API
      summary: Create a transfer of funds request.
      description: "Create a transfer of funds request. Returns a referenceId if the transfer was created successfully (see\
        \ __CreateTransferResponsePayload__).\n\nThe transfer's source account must be owned by the customer with the given\
        \ consumerId (see __CreateTransferRequestPayload__).\n\n### Example Response: \n\n    {\n        \"responseStatus\"\
        : {\n            \"success\": true,\n            \"error\": null                      \n        },\n        \"cryptoEnvelope\"\
        : {\n            \"keyParams\": null,\n            \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\
        \n        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt\
        \ the response payload. After the payload encryption the key parameters are encrypted with the client's public RSA\
        \ key (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: createTransfer
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      requestBody:
        $ref: '#/components/requestBodies/createTransferRequestBody'
      responses:
        '200':
          $ref: '#/components/responses/createTransferResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getTransactions:
    get:
      tags:
      - Account Management API
      summary: Returns all transactions for the given account and consumerId.
      description: "Returns all transactions for the given account and consumerId (see __GetTransactionsResponsePayload__).\n\
        ### Example Response: \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\"\
        : null                      \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n      \
        \      \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n\
        \        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the\
        \ response payload. After the payload encryption the key parameters are encrypted with the client's public RSA key\
        \ (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: getTransactions
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/bankCodeParam'
      - $ref: '#/components/parameters/accountNumberParam'
      - $ref: '#/components/parameters/accountTypeParam'
      - name: endDate
        in: query
        description: "The __endDate__ parameter can be used to delimit  the results by the transactions' creation date. The\
          \ validation pattern is __ISO-8601 Date__ (YYYY-MM-DD).  If __endDate__ is not provided the date of the  current\
          \ day is used.\n\nBy default all transactions within 10 days prior to the given __endDate__ are selected. The 10\
          \ day offset can be adjusted on the server's configuration page in OCM. The configuration parameters are as follows:\n\
          \n    \"configurationParams\": [\n      {\n        \"owner\": \"OM-API\",a\n        \"sectionName\": \"API\",\n\
          \        \"name\": \"getTransactions.endDateOffset\",\n        \"value\": \"10\",\n        \"secure\": false,\n\
          \        \"description\": \"StartDate offset in days.\"\n      }\n    ]"
        schema:
          type: string
          pattern: ([12]\d{3}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01]))
          example: '2022-01-31'
      responses:
        '200':
          $ref: '#/components/responses/getTransactionsResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getScheduledTransactions:
    get:
      tags:
      - Account Management API
      summary: Returns all scheduled transactions for the given account and consumerId.
      description: "Returns all scheduled transactions for the given account and consumerId (see __GetScheduledTransactionsResponsePayload__).\n\
        ### Example Response: \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\"\
        : null                      \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n      \
        \      \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n\
        \        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the\
        \ response payload. After the payload encryption the key parameters are encrypted with the client's public RSA key\
        \ (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: getScheduledTransactions
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/bankCodeParam'
      - $ref: '#/components/parameters/accountNumberParam'
      - $ref: '#/components/parameters/accountTypeParam'
      responses:
        '200':
          $ref: '#/components/responses/getScheduledTransactionsResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getAccountDetails:
    get:
      tags:
      - Account Management API
      summary: Returns detailed information for the given account and consumerId.
      description: "Returns detailed information for the given account and consumerId (see __GetAccountDetailsResponsePayload__).\n\
        ### Example Response: \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\"\
        : null                      \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n      \
        \      \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n\
        \        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the\
        \ response payload. After the payload encryption the key parameters are encrypted with the client's public RSA key\
        \ (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: getAccountDetails
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/bankCodeParam'
      - $ref: '#/components/parameters/accountNumberParam'
      - $ref: '#/components/parameters/accountTypeParam'
      responses:
        '200':
          $ref: '#/components/responses/getAccountDetailsResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /getStandingOrders:
    get:
      tags:
      - Standing Order API
      summary: Returns a list of standing orders for the given consumerId.
      description: "Returns a list of standing orders for the given consumerId (see __GetStandingOrdersResponsePayload__).\n\
        ### Example Response: \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\"\
        : null                      \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n      \
        \      \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n\
        \        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the\
        \ response payload. After the payload encryption the key parameters are encrypted with the client's public RSA key\
        \ (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: getStandingOrders
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      responses:
        '200':
          $ref: '#/components/responses/getStandingOrdersResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /createStandingOrder:
    post:
      tags:
      - Standing Order API
      summary: Create a standing order for the given account and consumerId.
      description: "Create a standing order (recurring transfer) for the given account and consumerId. Returns a referenceId\
        \ if the transfer was created successfully (see __CreateTransferResponsePayload__).\n\nThe transfer's source account\
        \ must be owned by the customer with the given consumerId. Additionally a period for the recurring transaction must\
        \ be specified (see __StandingOrderRequestPayload__).\n\n### Example Response: \n\n    {\n        \"responseStatus\"\
        : {\n            \"success\": true,\n            \"error\": null                      \n        },\n        \"cryptoEnvelope\"\
        : {\n            \"keyParams\": null,\n            \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\
        \n        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt\
        \ the response payload. After the payload encryption the key parameters are encrypted with the client's public RSA\
        \ key (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: createStandingOrder
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      requestBody:
        $ref: '#/components/requestBodies/standingOrderRequestBody'
      responses:
        '200':
          $ref: '#/components/responses/createStandingOrderResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /updateStandingOrder:
    post:
      tags:
      - Standing Order API
      summary: Update an existing standing order by the given referenceId.
      description: "Update a standing order with the given __referenceId__ (see __CreateTransferResponsePayload__).\n\nThe\
        \ request body's __CryptoEnvelope__ carries the same payload as in a __/createStandingOrder__ request. The __referenceId__\
        \ parameter is used to identify and update the stored standing order. \n### Example Response: \n\n    {\n        \"\
        responseStatus\": {\n            \"success\": true,\n            \"error\": null                      \n        },\n\
        \        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n            \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\
        \n        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt\
        \ the response payload. After the payload encryption the key parameters are encrypted with the client's public RSA\
        \ key (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: updateStandingOrder
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/referenceIdParam'
      requestBody:
        $ref: '#/components/requestBodies/standingOrderRequestBody'
      responses:
        '200':
          $ref: '#/components/responses/updateStandingOrderResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /deleteStandingOrder:
    post:
      tags:
      - Standing Order API
      summary: Delete an existing standing order.
      description: "Delete a standing order with the given __referenceID__ (see __referenceIdParam__).\n### Example Response:\
        \ \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\": null          \
        \            \n        }\n    }"
      operationId: deleteStandingOrder
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      - $ref: '#/components/parameters/referenceIdParam'
      responses:
        '200':
          $ref: '#/components/responses/deleteStandingOrderResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /createCashout4Me:
    post:
      tags:
      - Prestaged Transaction API
      summary: Create a prestaged cashout (withdrawal) transaction.
      description: "Create a prestaged cashout (withdrawal) transaction request. The server creates the transaction if the\
        \ request can be validated and processed successfully. It is mapped to the consumerId and has a configurable lifetime\
        \  after which the transaction expires (via OCM). To execute the transaction at an ATM or with a contact-less  mobile\
        \ application (see __/executePrestagedTransaction__) an accessCode is returned in the response.  Optionally this code\
        \ can be sent by Email or SMS.\n\nThe request data payload is described by the __CreateCashout4MeRequestPayload__\
        \ schema.\n\nWhen the transaction was created successfully the server returns details about the transaction  (see\
        \ __CreateCashout4MeResponsePayload__).\n### Example Response: \n\n    {\n        \"responseStatus\": {\n        \
        \    \"success\": true,\n            \"error\": null                      \n        },\n        \"cryptoEnvelope\"\
        : {\n            \"keyParams\": null,\n            \"payload\": \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\
        \n        }\n    }\n\n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt\
        \ the response payload. After the payload encryption the key parameters are encrypted with the client's public RSA\
        \ key (see __clientSecretparam__). The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity\
        \ that is attached to the response body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__)\
        \ to encrypt the response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached\
        \ to the response body."
      operationId: createCashout4Me
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      requestBody:
        $ref: '#/components/requestBodies/createCashout4MeRequestBody'
      responses:
        '200':
          $ref: '#/components/responses/createCashout4MeResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /createCashout2You:
    post:
      tags:
      - Prestaged Transaction API
      summary: Create a prestaged cash out transaction request.
      description: "Create a prestaged cashout (withdrawal) transaction request. The server creates the transaction if the\
        \ request can be validated and processed successfully. It is mapped to the consumerId and has a configurable lifetime\
        \  after which the transaction expires (via OCM). To execute the transaction at an ATM or with a contact-less  mobile\
        \ application (see __/executePrestagedTransaction__) an accessCode is created and sent to a  third party member. This\
        \ step is __not__ optional for this request type.  The accessCode can be sent by Email or SMS.\n\nThe request data\
        \ payload is described by the __CreateCashout2YouRequestPayload__ schema.\n\nWhen the transaction was created successfully\
        \ the server returns details about the transaction  (see __CreateCashout2YouResponsePayload__).\n\n### Example Response:\
        \ \n\n    {\n        \"responseStatus\": {\n            \"success\": true,\n            \"error\": null          \
        \            \n        },\n        \"cryptoEnvelope\": {\n            \"keyParams\": null,\n            \"payload\"\
        : \"1Dbp80MYqQ/z3+dzIVqxBhHXg6Awu/S1XVbK7OcbHZCw5ubyMrv4TjZLq5+U6bvtiRBWFeitgcWWb8Ng+TjOWQ==\"\n        }\n    }\n\
        \n\n__Using RSA/AES:__\nThe server generates an AES key (256 bit) and iv (128 bit) to encrypt the response payload.\
        \ After the payload encryption the key parameters are encrypted with the client's public RSA key (see __clientSecretparam__).\
        \ The encrypted key parameters and payload are stored in a __CryptoEnvelope__ entity that is attached to the response\
        \ body.\n\n__Using ECIES:__\nThe server uses the client's EC public key (see __clientSecretParam__) to encrypt the\
        \ response payload. The encrypted payload is stored in a __CryptoEnvelope__ entity that is attached to the response\
        \ body."
      operationId: createCashout2You
      parameters:
      - $ref: '#/components/parameters/clientSecretParam'
      - $ref: '#/components/parameters/sessionTokenParam'
      - $ref: '#/components/parameters/consumerIdParam'
      requestBody:
        $ref: '#/components/requestBodies/createCashout2YouRequestBody'
      responses:
        '200':
          $ref: '#/components/responses/createCashout2YouResponse'
        '400':
          $ref: '#/components/responses/badRequestResponse'
        '401':
          $ref: '#/components/responses/unauthorizedResponse'
        '404':
          $ref: '#/components/responses/notFoundResponse'
        default:
          $ref: '#/components/responses/defaultResponse'
  /createDeposit:
    post:
      tags:
      - Prestaged Transaction API
      summary: Create a prestaged cashin/deposit transaction request.
      description: "## Creating a prestaged cashin/deposit transaction request.\nThe __/createDeposit__ endpoint expects only\
        \ one required property - besides the credentials - to form a valid request. The __targetAccount__ property is used\
        \ to designate where the deposited money should be transferred. The optional __amount__ property is not required because\
        \ the general assumption is that ahead of time, nobody knows which amount will be deposited. The currency for the\
        \ deposited amount defaults to a configurable value on the server side, e.g. __USD__.\n\nIf the __targetAccount__\
        \ is a foreign currency account the optional __amount__ property should be used to designate the foreign currency,\
        \ e.g. __EUR__. The __amount__ property's value cannot be __null__ but any other string encoded value like __\"20.00\"\
        __ suffices to pass schema validation.\n\n    \"amount\": {\n        \"value\": \"20.00\",\n        \"currency\":\
        \ \"EUR\"\n    }\n\nIn the server's response the amount will have the same value except for split deposits.\n## Split\
        \ deposits\nThe pupose of split depoits is to transfer funds on different accounts owned by the client in one transaction.\
        \ The intention to create a split deposit is indicated by the presence of the __splitData__ porperty in the request.\
        \ The property is an array of __AccountWithAmount__ objects, each containg a __ShortAccountInfo__ and an __Amount__\
        \ object. They are not limited in numbers and may not contain negative amounts. When the transaction is executed the\
        \ splits are handled first and in the order they were defined. See the following request body as example.\n### Example:\
        \ default currency split request\n\n    {\n        \"targetAccount\": {\n            \"accountNumber\": \"7800

# --- truncated at 32 KB (198 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/diebold/refs/heads/main/openapi/diebold-dn-online-mobile-api-openapi.yml