API Market documentation

Corporate Payments API - details

The Corporate Payments API facilitates client applications (consumers) to initiate credit transfer payments from any nominated Nordea customer payment account (the debtor account). There are a number of conditions as to who may initiate payment, who is required to authorize payment and what rules need to be followed when formulating a payment instruction. These details are explained within this API specification.

The Corporate Payments API enables initiation (creation) of credit transfer instructions. The consuming client application can use API requests to:

Create a payment instruction - single credit transfer instructions only
Confirm the payment
Track payment execution status
Verify the payment
Cancelling the payment

Changes from the previous version

This is the change log of Corporate payments API. The topmost item is the latest version and the changes described in it are relative to the previous version which is listed directly below.

Version 3.1

In Swedish domestic credit transfer payment types ‘Within Nordea SE’ and ‘Other bank SE’ creditor name is mandatory.

Version 3.0

All payment endpoints can be accessed only with a token authorized by a PSU. Tokens authorized by a corporate netbank administrators are not valid for Corporate Payments API version 3 onwards. See more in the Corporate access authorization API V3 documentation.
PSU no longer needs to perform SCA during payment initiation request.
Added new endpoint * *verify **. See more from Payment verification section.
Two new parameters added into payment list endpoint Fetching list of payments: created_by_me and confirmable_by_me.
Support for the “Confirmation of availability of funds” calculation has been added into Get payment details-endpoint. See more in the Getting payment details section.

Payment Flow

All payment endpoints can only be accessed with a token authorized by a PSU with a scope "PAYMENTS_PSD2". It is important to notice that token is used to identify the PSU and all payment operations are registered as performed by the PSU, therefore, whenever the SCA is required, it must be performed by the same PSU who has authorized the token. For more details please see: Corporate access authorization API V3.

In the simplest possible case the flow might be represented diagrammatically thus:

Payment Flow Diagram 1

However, if payment must be confirmed by more than one payment service user, the flow might be extended to appear thus:

Payment Flow Diagram 2

Payment Initiation services are accessed via the following endpoints:

Payment initiation

POST /corporate/v3/payments

Specifications: Initiate payment

Initial (POST) request received to initiate payment via the API. The request includes the payment instruction with a “template_id”. Sending different Payment Template Id will result with initiation of different credit transfer type. Each of requests assigned to each template id has its specific validations and fields available.

Nordea’s Open Banking service will verify the payment instruction and return a payment identifier (payment_id) to the client.

See payment initiation example.

The payment must be always separately confirmed before it will be executed – once or several times, depending on scenario. See pictures above. For more information about payment confirmation, refer to section Payment confirmation

The payment can be also suspended, for example due to security reasons, then the payment will require an additional verification through strong customer authentication. Those cases can be identified by two fields in the response: “payment_status” with value “AUTHORIZATION_PARTIAL” and “payment_status_reason” with value “info.payment.verification_required”. In such case, please follow the Payment verification scenario.

If the error occurs during payment initiation, the payment can change the status to “PAYMENT_REJECTED”, in such case the payment can’t be processed any more and new one needs to be initiated.

Payment confirmation

PUT /corporate/v3/payments/<payment_id>/confirm

Specifications: Confirm payment execution

The “payment_id” in the request must be the payment id (_id) originally returned from the initiation of a credit transfer payment. Request must contain authorization details with possibility to select preferred authentication option. For more information please check Authentication Flow.

If the confirmation fails for any reason, the status will change to “AUTHORIZATION_FAILED”. The reason for failure should be found and resolved, then the confirmation request can be sent again for the same or different PSU.

See payment confirmation example.

All payments apart from SEPA_INSTANT_CREDIT_TRANSFER_FI needs to be confirmed before the end of its requested execution date, or they will be rejected.

Multiple payments confirmation

POST /corporate/v3/payments/confirm

Specifications: Confirm multiple payment execution

Each of the payment requires at least one confirmation before the payment can be executed and first confirmation must be done by same PSU who created the payment. When authorization is needed, then payment status records as AUTHORIZATION_PARTIAL with a payment status reason different from “info.payment.verification_required”. (See Payment verification for more information what to do in case of payment status reason “info.payment.verification_required”.) The request accepts the list of payment ids which must contain the payment ids originally returned from the initiation of a credit transfer payment and authorization details with possibility to select preferred authentication option. For more information please check Authentication Flow. All payments will be confirmed with a single SCA. Upon success, status of each payment object will be updated to AUTHORIZATION_PENDING.

See confirm multiple payment example.

All payments apart from SEPA_INSTANT_CREDIT_TRANSFER_FI needs to be confirmed before the end of its requested execution date, or they will be rejected.

When using the signing functionality for multiple payments, the PISP (Payment Initiation Service Provider) needs to ensure that the PSU is authorized to see all payments in the request.

Payment verification

PUT /corporate/v3/payments/<payment_id>/verify

Specifications: Verify payment execution

The additional verification for a payment is the exceptional flow when a payment is suspended due to security reasons. It can be identified by “payment_status” with value “AUTHORIZATION_PARTIAL” and “payment_status_reason” with value “info.payment.verification_required”.

Any user is allowed to verify a payment. It doesn’t need to be the same as the one initiating the payment. Only the access to view the payments from the debtor account are required.

If the additional verification fails for any reason, the status will change to “AUTHORIZATION_FAILED”. The reason for failure should be found and resolved, then the verification request can be sent again for the same or different PSU.

See verify a payment example.

After payment has been successfully verified, payment should follow the normal flow. PSU who initiated the payment, must confirm a payment first, and then it depends on configuration if more confirmation needed or will a payment be executed after first confirmation.

Getting payment details

GET /corporate/v3/payments/<payment_id>

Specifications: Get payment details

At any stage of the process the client application can obtain status of the payment instruction’s progress by making a GET request which returns full details of the instruction and its current state. The “payment_id” in the request must be the payment id (_id) originally returned from the initiation of a credit transfer payment.

See Get payment details example.

Confirmation of availability of funds

To request “Confirmation of Availability of Funds” calculation result, payment details request must contain parameter request_availability_of_funds.

Possible response for CoF-calculation are following:

Availability of funds status	Description
AVAILABLE	There is sufficient available balance on the account to cover the payment amount.
NOT_AVAILABLE	There is not sufficient available balance on the account to cover the payment amount.
NOT_SUPPORTED	Availability of funds check is not supported for the payment.
VERIFICATION_FAILED	Availability of funds check could not be performed due to technical or other failure.

Currency exchange is not included. If debtor account currency is different from the currency in payment instruction, then “NOT_SUPPORTED” value is returned.

Cash pool accounts will be excluded. If debtor account belongs to cash pool then NOT_SUPPORTED value returned.

See Checking confirmation of availability of funds example

Fetching list of payments

GET /corporate/v3/payments

Specifications: Payments list

Request list of the payment instructions with details and status. The response delivers the current status and all details of the payment instructions matching the search criteria.

The response is paginated with the maximum number of payment instructions per page is 20.

See Fetching list of payments example.

Payment cancellation

PATCH /corporate/v3/payments/<payment_id>

Specifications: Cancel a payment

Used for payments cancellation. Upon success, the status of the payment object will be updated to “AUTHORIZATION_PENDING” together with the status reason “info.payment.cancellation_in_progress”.

The “payment_id” in the request must be the payment id (_id) originally returned from the initiation of a credit transfer payment.

Cancelled payments will be still available to see but their “payment_status” will be visible as “PAYMENT_CANCELLED” which is the final status, therefore those payments cannot be changed anymore. Not all statuses can be cancelled, for example, payments with status “PAYMENT_REJECTED”, “AUTHORIZATION_PENDING” or “PAYMENT_EXECUTED” cannot be cancelled.

If the cancellation fails for any reason, the status will change to “AUTHORIZATION_FAILED”. The reason for failure should be found and resolved, then the cancellation request can be sent again for the same or different PSU.

See Cancel a payment example.

Multiple payments cancellation

POST /corporate/v3/payments/cancel

Specifications: Cancel multiple payments

Used to cancel multiple payments with one request. The request accepts the list of payment ids which must contain the payment ids originally returned from the initiation of a credit transfer payment and authorization details with possibility to select preferred authentication option. For more information please check Authentication Flow. All payments will be confirmed with a single SCA.

Upon success, status of each payment object will be updated to “AUTHORIZATION_PENDING” together with the status reason “info.payment.cancellation_in_progress”.

Not all statuses can be cancelled, for example, payments with status “PAYMENT_REJECTED”, “AUTHORIZATION_PENDING” or “PAYMENT_EXECUTED” cannot be cancelled.

See Cancel multiple payments example.

Payment templates

The following templates are available when requesting initiation of a credit transfer.

Template id	Description of the payment	Available in Sandbox	Available in production
DENMARK
Domestic templates
DOMESTIC_CREDIT_TRANSFER_DK	Initiation of Danish Domestic Bank Transfer in DKK.	Yes	Yes
DOMESTIC_TRANSFER_FORM_WITH_OCR_DK	Initiation of Danish Transfer Form with reference in DKK.	Yes	Yes
DOMESTIC_TRANSFER_FORM_DK	Initiation of Danish Transfer Form without reference in DKK.	Yes	Yes
SALARY_PENSION_DK	Initiation of salary or pension payments where the debtor and creditor account is in DKK and Nordea Denmark.	Yes	Yes
INSTANT_CREDIT_TRANSFER_DK	Initiation of instant credit transfers in Denmark. The debtor account is in Nordea DK and creditor account is in Nordea DK or in another Danish bank.	Yes	No
INSTANT_SALARY_PENSION_DK	Initiation of instant salary or pension payments in Denmark. The debtor account is in Nordea DK and creditor account is in Nordea DK or in another Danish bank.	Yes	No
Cross currency templates
CROSS_BORDER_DK	Initiation of a currency transfer where the debtor account in any currency is in Nordea Denmark. Creditor account can be in any currency and in any bank. Template also covers SEPA Credit Transfers from Denmark to the banks in SEPA area.	Yes	Yes
CURRENCY_TRANSFER_NORDEA_DK	Initiation of a currency transfer where both accounts are in Nordea Denmark. At least one of the accounts or payment amount is other than DKK.	Yes	Yes
FINANCIAL_PAYMENT_DK	Initiation of a currency transfer to any bank where the debtor account is in any currency, in Nordea Denmark. Creditor account is in another bank. Either the creditor or the debtor is a financial institution.	Yes	Yes
Intercompany templates
INTERCOMPANY_DOMESTIC_PAYMENT_DK	Initiation of transfer where the debit account is in Nordea DK and credit account is in Nordea DK or in another Danish bank. Transfer is allowed between DKK currency, with accounts in Nordea DK. For creditor account in other Danish bank, transfer is accepted only for DKK currency.	Yes	Yes
INTERCOMPANY_CROSS_BORDER_DK	Initiation of a currency transfer to any bank outside Denmark. The debtor account belongs to Nordea Denmark and can be in any currency.	Yes	Yes
INTERCOMPANY_CURRENCY_TRANSFER_DK	Initiation of a currency transfer where the debit and credit accounts are in Nordea DK. At least one of the accounts or payment amount is other than DKK.	Yes	Yes
INTERCOMPANY_INSTANT_CREDIT_TRANSFER_DK	Initiation of intercompany instant credit transfers in Denmark. The debtor account is in Nordea DK and creditor account is in Denmark and registered in the same agreement as debtor account.	Yes	No
Global Cash Pool transfer template
GLOBAL_CASH_POOL_TRANSFER_DK	Initiation of a global cash pool transfer in Nordea between transaction accounts in the same cash pool structure. The accounts need to be in the same currency. This template covers both domestic and cross-border.	Yes	Yes
FINLAND
Domestic templates
SEPA_CREDIT_TRANSFER_FI	Initiation of Finnish SEPA Credit Transfer in EUR. The creditor account can be in any bank in SEPA area.	Yes	Yes
SEPA_INSTANT_CREDIT_TRANSFER_FI	Initiation of SEPA Credit Transfer Instant in Euro in the SEPA area from Finland. Creditor bank must be part of the SEPA Instant scheme.	Yes	Yes
Cross currency templates
CROSS_BORDER_FI	Initiation of a currency transfer where the debtor account in any currency is in Nordea Finland. Creditor account can be in any currency and in any bank.	Yes	Yes
FINANCIAL_PAYMENT_FI	Initiation of a currency transfer to any bank where the debtor account is in any currency, in Nordea Finland. Creditor account is in another bank. Either the creditor or the debtor is a financial institution.	Yes	Yes
CURRENCY_TRANSFER_NORDEA_FI	Initiation of a currency transfer where both accounts are in Nordea Finland. At least one of the accounts or payment amount is other than EUR.	Yes	Yes
Intercompany templates
INTERCOMPANY_DOMESTIC_PAYMENT_FI	Initiation of transfer where the debit account is in Nordea FI and credit account is in Nordea FI or in another Finnish bank. Transfer is accepted for EUR currency only.	Yes	Yes
INTERCOMPANY_CROSS_BORDER_FI	Initiation of a currency transfer to any bank outside Finland. The debtor account belongs to Nordea Finland and can be in any currency.	Yes	Yes
INTERCOMPANY_CURRENCY_TRANSFER_FI	Initiation of a currency transfer where the debit and credit accounts are in Nordea FI. At least one of the accounts or payment amount is other than EUR.	Yes	Yes
Global Cash Pool transfer template
GLOBAL_CASH_POOL_TRANSFER_FI	Initiation of a global cash pool transfer in Nordea between transaction accounts in the same cash pool structure. The accounts need to be in the same currency. This template covers both domestic and cross-border.	Yes	Yes
NORWAY
Domestic templates
DOMESTIC_CREDIT_TRANSFER_NO	Initiation of Norwegian Domestic Payment in NOK.	Yes	Yes
DOMESTIC_KID_TRANSFER_NO	Initiation of Norwegian KID Payment in NOK.	Yes	Yes
SALARY_PAYMENT_NO	Initiation of salary payments where the debtor and creditor accounts are in NOK. Debtor account is in Nordea Norway. Creditor account is in any bank in Norway (also in Nordea).	Yes	Yes
Cross currency templates
CROSS_BORDER_NO	Initiation of a currency transfer where debtor account is in Nordea NO and the creditor account is in Nordea NO, in another Norwegian bank or any bank outside Norway. At least one of the accounts or payment amount is other than NOK. This template should also be used for SEPA Credit Transfers in Euro to the banks in SEPA area and express-payment.	Yes	Yes
FINANCIAL_PAYMENT_NO	Initiation of a currency transfer to any bank where the debtor account in any currency is in Nordea Norway. Creditor account can be in any currency and in any bank. Either the creditor or the debtor is a financial institution.	Yes	Yes
Intercompany templates
INTERCOMPANY_DOMESTIC_PAYMENT_NO	Initiation of transfer where the debit account is in Nordea NO and credit account is in Nordea NO or in another Norwegian bank. Both account and payment currency must be NOK.	Yes	Yes
INTERCOMPANY_CROSS_BORDER_NO	Initiation of a currency transfer where debtor account is in Nordea NO and the creditor account is in Nordea NO, in another Norwegian bank or any bank outside Norway. At least one of the accounts or payment amount is other than NOK.	Yes	Yes
Global Cash Pool transfer template
GLOBAL_CASH_POOL_TRANSFER_NO	Initiation of a global cash pool transfer in Nordea between transaction accounts in the same cash pool structure. The accounts need to be in the same currency. This template covers both domestic and cross-border.	Yes	Yes
SWEDEN
Domestic templates
DOMESTIC_CREDIT_TRANSFER_SE	Initiation of Swedish Domestic Bank Transfer in SEK.	Yes	Yes
SDV_DOMESTIC_PAYMENT_SE	Initiation of transfer where the debtor account is in Nordea Sweden. Creditor account is in any other bank in Sweden, other than Nordea. Both account and payment currency must be SEK. Payment urgency is always same-day-value (SDV).	Yes	Yes
Cross currency templates
CROSS_BORDER_SE	Initiation of a currency transfer to any bank outside Sweden. The debtor account in any currency is in Nordea Sweden. Template also covers SEPA Credit Transfers from Sweden to the banks in SEPA area. Please note that for payments above 150,000 SEK, field regulatory_reporting.purpose_code is required in Sweden.	Yes	Yes
CURRENCY_TRANSFER_SE	Initiation of a transfer where debtor account is in Nordea SE and creditor account is in Nordea SE or in another Swedish bank. At least one of the accounts or payment amount is other than SEK.	Yes	Yes
FINANCIAL_PAYMENT_SE	Initiation of a currency transfer to any bank where the debtor account is in any currency, in Nordea Sweden. Creditor account is in another bank. Either the creditor or the debtor is a financial institution.	Yes	Yes
Intercompany templates
INTERCOMPANY_DOMESTIC_PAYMENT_SE	Initiation of transfer where the debit account is in Nordea SE and credit account is in Nordea SE or in another Swedish bank. Transfer is allowed between EUR and/or SEK currency, with accounts in Nordea SE. For creditor account in other Swedish bank, transfer is accepted only for SEK currency.	Yes	Yes
INTERCOMPANY_CROSS_BORDER_SE	Initiation of a currency transfer to any bank outside Sweden. The debtor account belongs to Nordea Sweden and can be in any currency.	Yes	Yes
INTERCOMPANY_CURRENCY_TRANSFER_SE	Initiation of a currency transfer where the debit and credit accounts are in Nordea SE. At least one of the accounts or payment amount is other than SEK or EUR.	Yes	Yes
Global Cash Pool transfer template
GLOBAL_CASH_POOL_TRANSFER_SE	Initiation of a global cash pool transfer in Nordea between transaction accounts in the same cash pool structure. The accounts need to be in the same currency. This template covers both domestic and cross-border.	Yes	Yes

*Intercompany templates ** - Used for payments between companies belonging to the same group, to move funds between companies’ own accounts within the Nordea Group (domestic and cross-border) or outside the Nordea Group if the accounts are included in the Corporate Netbank agreement.

The funds will be available on the same day, if payments are within Nordea. For payments outside the Nordea Group, Nordea can never guarantee that the funds will be available on the same day in the beneficiary account.

*Future dated payments ** - The user should use the field “requested_execution_date” with future-date in the Payment Initiation request.

*Recurring payments ** - This feature is currently available only in Finland. Customers will be able to set a recurrence for the payment.

The frequency options are weekly or monthly, and the payment can be repeated continuously or until a certain date. This feature is currently available for all the payments types available in Finland, except for Financial payment template (FINANCIAL_PAYMENT_FI).

*NemKonto payments ** - This feature is currently available only in Denmark for DOMESTIC_CREDIT_TRANSFER_DK and SALARY_PENSION_DK.

The product can be compared to a regular account-to-account payment, where the credit account number is replaced by a CPR/CVR/SE number. The customer can make these payments with URGENCY_NORMAL or URGENCY_SAMEDAY. The customer should have a NemKonto payment agreement.

Payment status

The reported state of a client’s payment instruction can be any of the following…

Payment Status	Explanation
AUTHORIZATION_PENDING	The payment instruction has been successfully received and authentication of a nominated user is currently in progress as part of the payment authorization process.
AUTHORIZATION_PARTIAL	Payment instruction is only partially authorized and one or more further users are required to authorize the payment in order to complete the payment authorization process. Client must nominate a further user.
AUTHORIZATION_FAILED	The last nominated user failed to authorize the payment. Either they failed to authenticate or do not have authorization rights on the specified debtor account. Client must nominate a further user. There can also be system failure and then customer could retry with same user.
PAYMENT_ACCEPTED	The payment instruction has been fully authorized and passed to Nordea’s payments engine for processing as per the payment scheme rules.
PAYMENT_EXECUTED	Payment has been executed and booked on the remitter’s account. The timing of clearing on the creditor’s account will be dependent on payment scheme and processing by the creditor’s bank.
PAYMENT_REJECTED	Payment instruction has been rejected. Reason is provided within the payment_status_reason code in response.
PAYMENT_CANCELLED	Payment instruction has been cancelled.
NOT_FOUND	Payment id was not found. Only applicable for confirmation and cancellation of multiple payments.

Real-world cases where a payment might be rejected because for example the creditor account is unreachable or the debtor account has insufficient funds are not modeled in the sandbox environment.

Cut-off times

The cut-off time is the latest time when Nordea accepts and effects payment orders to and from customers. The cut-off time varies depending on country, payment type and currency involved.

If you want the payment to be executed within the same day, please remember to finally confirm it before its cut-off time. To check the cut-off times for specific payment types and countries, please visit https://www.nordea.com/en/our-services/cash-management/cut-off-times

Authentication Flow

Authentication Types

Authentication Type	Description	Available in Sandbox	Available in production
REDIRECT	Initiation of redirect OAuth flow where Corporate Netbank user requesting the authorization will be able to confirm the instruction using one of supported authentication methods via Nordea page.	Yes	Yes
Authentication Methods:
- BANKID_SE	Authentication using BankID. Only available for Swedish users.	Yes	Yes
- MTA	Authentication using Nordea ID mobile application. Available for all Corporate Netbank users.	Yes	Yes
- QRT	Authentication using Nordea ID device. Available for all Corporate Netbank users.	Yes	No
DECOUPLED	Immediate initiation of authentication session on Corporate Netbank user device. User will be able to confirm the instruction by selected authentication method.	Yes	Yes
Authentication Methods:
- MTA	Authentication using Nordea ID mobile application. Available for all Corporate Netbank users.	Yes	Yes
- BANKID_SE	Authentication using BankID. Only available for Swedish users.	Yes	Yes

Whilst operating the Payments API in our sandbox environment authentication types behavior is adjusted.

When using REDIRECT authentication type, execution of redirect link will automatically progress to the next stage in the authorization process. Ordinarily in real-world use, at this point the user would be redirected to Nordea page where they would be invited to securely authenticate themselves.

Get BankId Se authentication details (Decoupled Flow)

GET /corporate/premium/v1/authentications/bankid_se/{authentication_id}

When “authentication_type” = “DECOUPLED” and “authentication_method” = “BANKID_SE” values are selected, in the response “authentication_id” field is provided. Authentication ID is to be used in the below endpoint.

In the response, when applicable, qr_data and auto_start_token values are returned. Qr_data is converted to QR code and scanned by end user BankId SE mobile application.

If, BankId application on customer mobile application needs to be used directly, “auto_start_token” has to be used.

As long as the status is WAITING_FOR_USER, new qr_data is generated in small intervals, so it’s advised to poll for the endpoint approximately every second until SUCCESS or FAILED status appears. Access token is not required to use authentications endpoints. Please see the examples section for better understanding.

The status will give the state of signing as below.

Status	Description
WAITING_FOR_USER	Awaiting end user signing assignment.
IN_PROGRESS	End user signing process is in progress.
SUCCESS	Signing process has completed successfully.
FAILED	Signing was not completed by end user and needs to be started again.

See Get details of the BankID SE authentication example.

Corporate payments API examples

Here you can find examples how to use the Corporate Payments API endpoints.

Create a payment Instruction example

This endpoint URL has the following form:

POST /corporate/v3/payments

This endpoint supports POST HTTP method. The following headers must be used:

Content-Type: application/json
Authorization: Bearer {access_token}
X-IBM-Client: {client_id}
X-IBM-Client-Secret: {client_secret}
Digest: {digest}
Signature: {signature}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

SANDBOX ONLY

To make a payment in need of additional verification, please add:

*X-Response-Scenarios: paymentVerificationRequired **

The body of the request will vary, determined by the type of payment requested and the payment template chosen. The following example is provided for a Finnish SEPA Credit Transfer instruction:

{
  "payment_instruction": {
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "amount": "123.45",
    "currency": "EUR",
    "end_to_end_id": "13227asdfds",
    "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
    "requested_execution_date": "2025-10-07",
    "debtor": {
      "account": {
        "currency": "EUR",
        "type": "IBAN",
        "value": "FI6816603001007528"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "type": "IBAN",
        "value": "FI1350001520000081"
      },
      "message": "Invoice 5071",
      "name": "Screws and Nuts Ltd"
    }
  }
}

Where the payment request is valid the response will be 201 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "253963cee3e4cc7d",
    "creation_date_time": "2025-10-07T09:42:35.401168152Z",
    "http_code": 201
  },
  "response": {
    "_id": "3b87765c-fcaa-4859-b977-a854773494bd",
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
    "end_to_end_id": "13227asdfds",
    "amount": "123.45",
    "requested_execution_date": "2025-10-07",
    "currency": "EUR",
    "urgency": "NORMAL",
    "debtor": {
      "account": {
        "value": "FI6816603001007528",
        "type": "IBAN",
        "currency": "EUR"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "value": "FI1350001520000081",
        "type": "IBAN"
      },
      "name": "Screws and Nuts Ltd",
      "message": "Invoice 5071"
    },
    "status_timestamp": "2025-10-07T09:42:35.401174311",
    "create_timestamp": "2025-10-07T09:42:35.400231551",
    "payment_status": "PAYMENT_INITIATED",
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments"
      },
      {
        "rel": "confirm",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/confirm"
      },
      {
        "rel": "cancel",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/cancel"
      },
      {
        "rel": "details",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd"
      }
    ]
  }
}

Fetching details of the Payment example

This endpoint URL has the following form:

GET /corporate/v3/payments/<payment_id>

This endpoint supports GET HTTP method. The following headers must be used:

Authorization: Bearer {access_token}
Signature: {signature}
X-IBM-Client-Id: {client_id}
X-IBM-Client-Secret: {client_secret}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The following query parameters are supported:

request_availability_of_funds: {true/false}

See Checking confirmation of availability of funds below.

Where the request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "692ef0520e3cec40",
    "creation_date_time": "2025-10-07T10:14:26.902114944Z",
    "http_code": 200
  },
  "response": {
    "_id": "3b87765c-fcaa-4859-b977-a854773494bd",
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
    "end_to_end_id": "13227asdfds",
    "amount": "123.45",
    "requested_execution_date": "2025-10-07",
    "execution_date": "2025-10-07",
    "currency": "EUR",
    "urgency": "NORMAL",
    "debtor": {
      "account": {
        "value": "FI6816603001007528",
        "type": "IBAN",
        "currency": "EUR"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "value": "FI1350001520000081",
        "type": "IBAN"
      },
      "name": "Screws and Nuts Ltd",
      "message": "Invoice 5071",
      "bank": {
        "bic": "NDEAFIHH",
        "country": "FI"
      }
    },
    "status_timestamp": "2025-10-07T10:14:26.902124328",
    "create_timestamp": "2025-10-07T09:42:35.400231551",
    "payment_status": "AUTHORIZATION_PARTIAL",
    "payment_status_reason": "info.payment.verification_required",
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd"
      },
      {
        "rel": "confirm",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/confirm"
      },
      {
        "rel": "cancel",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/cancel"
      }
    ]
  }
}

Checking confirmation of availability of funds example

This endpoint URL has the following form:

GET /corporate/v3/payments/<payment_id>?request_availability_of_funds=true

This endpoint supports GET HTTP method. The following headers must be used:

Authorization: Bearer {access_token}
Signature: {signature}
X-IBM-Client-Id: {client_id}
X-IBM-Client-Secret: {client_secret}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The following query parameters are supported:

request_availability_of_funds: {true/false}

Where the request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "692ef0520e3cec40",
    "creation_date_time": "2025-10-07T10:14:26.902114944Z",
    "http_code": 200
  },
  "response": {
    "_id": "3b87765c-fcaa-4859-b977-a854773494bd",
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
    "end_to_end_id": "13227asdfds",
    "amount": "123.45",
    "requested_execution_date": "2025-10-07",
    "execution_date": "2025-10-07",
    "currency": "EUR",
    "urgency": "NORMAL",
    "debtor": {
      "account": {
        "value": "FI6816603001007528",
        "type": "IBAN",
        "currency": "EUR"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "value": "FI1350001520000081",
        "type": "IBAN"
      },
      "name": "Screws and Nuts Ltd",
      "message": "Invoice 5071",
      "bank": {
        "bic": "NDEAFIHH",
        "country": "FI"
      }
    },
    "status_timestamp": "2025-10-07T10:14:26.902124328",
    "create_timestamp": "2025-10-07T09:42:35.400231551",
    "payment_status": "AUTHORIZATION_PARTIAL",
    "availability_of_funds": {
      "status": "AVAILABLE"
    },
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd"
      },
      {
        "rel": "confirm",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/confirm"
      },
      {
        "rel": "cancel",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/cancel"
      }
    ]
  }
}

Fetching list of payments example

This endpoint URL has the following form:

GET /corporate/v3/payments

This endpoint supports GET HTTP method. The following headers must be used:

Authorization: Bearer {access_token}
Signature: {signature}
X-IBM-Client-Id: {client_id}
X-IBM-Client-Secret: {client_secret}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The following query parameters are supported:

creation_from_timestamp: {creation_from_timestamp}
creation_to_timestamp: {creation_to_timestamp}
execution_from_date: {execution_from_date}
execution_to_date: {execution_to_date}
debtor_account: {debtor_account}
min_amount: {min_amount}
max_amount: {max_amount}
payment_status: {payment_status}
created_by: {created_by}
page: {page}
size: {size}
created_by_me: {true/false}
confirmable_by_me: {true/false}

Where the request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "40d418bc738b9d7d",
    "creation_date_time": "2025-10-07T10:19:36.536128252Z",
    "http_code": 200
  },
  "response": {
    "payments": [
      {
        "_id": "3b87765c-fcaa-4859-b977-a854773494bd",
        "template_id": "SEPA_CREDIT_TRANSFER_FI",
        "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
        "end_to_end_id": "13227asdfds",
        "amount": "123.45",
        "requested_execution_date": "2025-10-07",
        "execution_date": "2025-10-07",
        "currency": "EUR",
        "urgency": "NORMAL",
        "debtor": {
          "account": {
            "value": "FI6816603001007528",
            "type": "IBAN",
            "currency": "EUR"
          },
          "own_reference": "Own message"
        },
        "creditor": {
          "account": {
            "value": "FI1350001520000081",
            "type": "IBAN"
          },
          "name": "Screws and Nuts Ltd",
          "message": "Invoice 5071",
          "bank": {
            "bic": "NDEAFIHH",
            "country": "FI"
          }
        },
        "status_timestamp": "2025-10-07T10:19:36.536142574",
        "create_timestamp": "2025-10-07T09:42:35.400231551",
        "payment_status": "AUTHORIZATION_PARTIAL",
        "payment_status_reason": "info.payment.verification_required",
        "_links": [
          {
            "rel": "details",
            "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd"
          },
          {
            "rel": "confirm",
            "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/confirm"
          },
          {
            "rel": "cancel",
            "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/cancel"
          }
        ]
      },
      {
        "_id": "6e1771f9-60ec-46ff-89c0-a03f3236c7ac",
        "template_id": "SEPA_CREDIT_TRANSFER_FI",
        "external_id": "669ecca2-3659-429f-982d-7dca4f458820",
        "end_to_end_id": "13227asdfds",
        "amount": "12.45",
        "requested_execution_date": "2025-10-07",
        "execution_date": "2025-10-07",
        "currency": "EUR",
        "urgency": "NORMAL",
        "debtor": {
          "account": {
            "value": "FI6816603001007528",
            "type": "IBAN",
            "currency": "EUR"
          },
          "own_reference": "Own message"
        },
        "creditor": {
          "account": {
            "value": "FI1350001520000081",
            "type": "IBAN"
          },
          "name": "Screws and Nuts Ltd",
          "message": "Invoice 5071",
          "bank": {
            "bic": "NDEAFIHH",
            "country": "FI"
          }
        },
        "status_timestamp": "2025-10-07T10:19:36.536218969",
        "create_timestamp": "2025-10-07T06:53:49.886133015",
        "payment_status": "AUTHORIZATION_FAILED",
        "payment_status_reason": "error.payment.not_authorized",
        "_links": [
          {
            "rel": "details",
            "href": "/v3/payments/6e1771f9-60ec-46ff-89c0-a03f3236c7ac"
          },
          {
            "rel": "confirm",
            "href": "/v3/payments/6e1771f9-60ec-46ff-89c0-a03f3236c7ac/confirm"
          },
          {
            "rel": "cancel",
            "href": "/v3/payments/6e1771f9-60ec-46ff-89c0-a03f3236c7ac/cancel"
          }
        ]
      }
    ],
    "_links": [
      {
        "rel": "first",
        "href": "/v3/payments?confirmable_by_me=true&page=1&size=20"
      },
      {
        "rel": "self",
        "href": "/v3/payments?confirmable_by_me=true&page=1&size=20"
      },
      {
        "rel": "last",
        "href": "/v3/payments?confirmable_by_me=true&page=1&size=20"
      }
    ]
  }
}

Confirming a Payment example

This endpoint URL has the following form:

PUT /corporate/v3/payments/<payment_id>/confirm

This endpoint supports PUT HTTP method. The following headers must be used:

Content-Type: application/json
Authorization: Bearer {access_token}
X-IBM-Client: {client_id}
X-IBM-Client-Secret: {client_secret}
Digest: {digest}
Signature: {signature}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The body of the request will vary, determined by the authentication type chosen.

Example of DECOUPLED authentication type with MTA authentication method

{
  "authentication_type": "DECOUPLED",
  "authentication_method": "MTA"
}

Example of DECOUPLED authentication type with BANKID_SE authentication method

{
  "authentication_type": "DECOUPLED",
  "authentication_method": "BANKID_SE"
}

Example of REDIRECT authentication type

{
  "authentication_type": "REDIRECT",
  "redirect_uri": "http://test.com",
  "state": "state",
  "authentication_method": "BANKID_SE",
  "language": "en"
}

Where the payment request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "f8f5433f1bd613f6",
    "creation_date_time": "2025-10-07T10:29:06.396641931Z",
    "http_code": 200
  },
  "response": {
    "_id": "3b87765c-fcaa-4859-b977-a854773494bd",
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
    "end_to_end_id": "13227asdfds",
    "amount": "123.45",
    "requested_execution_date": "2025-10-07",
    "execution_date": "2025-10-07",
    "currency": "EUR",
    "urgency": "NORMAL",
    "debtor": {
      "account": {
        "value": "FI6816603001007528",
        "type": "IBAN",
        "currency": "EUR"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "value": "FI1350001520000081",
        "type": "IBAN"
      },
      "name": "Screws and Nuts Ltd",
      "message": "Invoice 5071",
      "bank": {
        "bic": "NDEAFIHH",
        "country": "FI"
      }
    },
    "status_timestamp": "2025-10-07T10:29:06.396651105",
    "create_timestamp": "2025-10-07T09:42:35.400231551",
    "payment_status": "AUTHORIZATION_PENDING",
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/confirm"
      },
      {
        "rel": "details",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd"
      },
      {
        "rel": "redirect",
        "href": "https://sandbox-corporate-obh.esp.rs.dev01.qaoneadr.local/payments/identify?client_id=Psf34PDHxdLy2Sfyr4UF&code_challenge_method=S256&redirect_uri=https%3A%2F%2Fsandbox-corporate-obh.esp.rs.dev01.qaoneadr.local%2Fpayments%2Foauth&response_type=code&code_challenge=EJ1L0DAiF6bFxSVTgz_oC30Yy40qy3eAqqgfdP-lpUk&scope=openid+agreement&state=0eeeea02-0552-4fa2-a0bb-aae13d8f1ef8&nonce=lm3tKcz78U0eAQ4fv3PPOTTEO6M7VJGBJltwHjvU&login_hint=bankid_se&signing_token=eyJjdHkiOiJKV1QiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiUlNBLU9BRVAtMjU2In0.koGa_1DQl_S84zv_-oo2SNeSobmrEb9J4Vvx8z9OPbjc2ZfJXRYZyBlLCSUi-8xAfTbG4xxsBDhOJAQYCu3Z24tzMGPbvcg6w1eQILFMYpF-FNcVQBKFewTEmUwJMLWmAtWAdfQWulGYCdkVZIwmm1AcHD2YgdOsoivMNyG-NzsS8eNGnUZBSBVtBOjjYUs0XCYkAhJCOSTGru7B4tDggTjInBnO43oFhKU3k_tuuJyUv7bW3Dylufg6umPXJJV6gyIG7-n4M_VmdHJ8OCbpYcydeFnwEkZ0NEDQKJ52fMCZpV7BBhxPHDnZUIim_9Cze39Tq8yjGEakBlpm_UY8Pg.87kW-rtI7ctFG7-U.tv-H4prcj9gw_PDDLQIA6nzG1BmRKi9T47FYB12IKlsJyrsiJtNKbkQM5XALFOiefXQ16JysH3yoDdAcPaLccBIH_lWmeRsAoVYsBG8Di3bXrHZrpNyzCmpYNKoh9Sp6SXSh77Oq0jrZHf0LNxkJCM4pNjCr4joyC0PBol1wX8nTaiC9dL--8djrVh3dlm82Z9JU8-3A9ogYs8Q38QXHkg1Q3KxUwtl4hPmxtgDl-JLMRGFeEBoybyvNt4gmQpOtIT1Zp-hsx63_yBOjik5fSnUq4kAOKVKUsmZu9nwRuX4vEzsLa-loiSpHi9a-X-hubqI6E5L-9z-Vs69ENGluANTXJXTNzFEYfirEOZoQAQlmEGQjK7gKqXH0-QycVCutp76Wh8bGU7_bHWBbgNew-ZBMq9rCSb4aqo7B_ZMHHmQWBUp_U6Dt-DTniQoBLbY5hUG0MepmOszpFM_NEzklRLrTeWwdb_W6C3bVY1g1vnukzIpalhMQcDiO5P9-yaihg14n940x7NfnPvSGHgFWCh_vjE0a-dTXHR-BcDdqQlZuFGiGmXnNlnM817sa5F5i_2CIVW--XC1-PpdcEgelZknBln5LF6OpXZlD5JglbFPhEopYz4vLiq8mLrOPWo7Ap7H6f57N.yKlEsXHeS-RxLcN7i9HC4A"
      }
    ]
  }
}

Please note that redirect links presence is determined by selected authentication_type and authentication_method

Confirming multiple payments example

This endpoint URL has the following form:

POST/corporate/v3/payments/confirm

This endpoint supports PUT HTTP method. The following headers must be used:

Content-Type: application/json
Authorization: Bearer {access_token}
X-IBM-Client: {client_id}
X-IBM-Client-Secret: {client_secret}
Digest: {digest}
Signature: {signature}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The body of the request will vary, determined by the authentication type chosen.

Example of DECOUPLED authentication type with MTA authentication method

{
  "authorization_details": {
    "authentication_type": "DECOUPLED",
    "authentication_method": "MTA"
  },
  "payment_details": {
    "payment_id_list": [
      "6e1771f9-60ec-46ff-89c0-a03f3236c7ac"
    ]
  }
}

Example of DECOUPLED authentication type with BANKID_SE authentication method

{
  "authorization_details": {
    "authentication_type": "DECOUPLED",
    "authentication_method": "BANKID_SE"
  },
  "payment_details": {
    "payment_id_list": [
      "6e1771f9-60ec-46ff-89c0-a03f3236c7ac"
    ]
  }
}

Example of REDIRECT authentication type

{
  "authorization_details": {
    "authentication_type": "REDIRECT",
    "redirect_uri": "https://www.nordea.com",
    "state": "state",
    "authentication_method": "BANKID_SE",
    "language": "en"
  },
  "payment_details": {
    "payment_id_list": [
      "6e1771f9-60ec-46ff-89c0-a03f3236c7ac"
    ]
  }
}

Where the payment request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "cf0707aad0138415",
    "creation_date_time": "2025-10-07T10:39:50.255344212Z",
    "http_code": 200
  },
  "response": {
    "payments": [
      {
        "_id": "6e1771f9-60ec-46ff-89c0-a03f3236c7ac",
        "template_id": "SEPA_CREDIT_TRANSFER_FI",
        "external_id": "669ecca2-3659-429f-982d-7dca4f458820",
        "end_to_end_id": "13227asdfds",
        "amount": "12.45",
        "requested_execution_date": "2025-10-07",
        "execution_date": "2025-10-07",
        "currency": "EUR",
        "urgency": "NORMAL",
        "debtor": {
          "account": {
            "value": "FI6816603001007528",
            "type": "IBAN",
            "currency": "EUR"
          },
          "own_reference": "Own message"
        },
        "creditor": {
          "account": {
            "value": "FI1350001520000081",
            "type": "IBAN"
          },
          "name": "Screws and Nuts Ltd",
          "message": "Invoice 5071",
          "bank": {
            "bic": "NDEAFIHH",
            "country": "FI"
          }
        },
        "status_timestamp": "2025-10-07T10:39:50.255358243",
        "create_timestamp": "2025-10-07T06:53:49.886133015",
        "payment_status": "AUTHORIZATION_PENDING",
        "_links": [
          {
            "rel": "details",
            "href": "/v3/payments/6e1771f9-60ec-46ff-89c0-a03f3236c7ac"
          }
        ]
      }
    ],
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/confirm"
      },
      {
        "rel": "redirect",
        "href": "https://sandbox-corporate-obh.esp.rs.dev01.qaoneadr.local/payments/identify?client_id=Psf34PDHxdLy2Sfyr4UF&code_challenge_method=S256&redirect_uri=https%3A%2F%2Fsandbox-corporate-obh.esp.rs.dev01.qaoneadr.local%2Fpayments%2Foauth&response_type=code&code_challenge=NjN_hh414zKwTD5JAEqSBAYmuuZMbsLv7yOkyjtRc58&scope=openid+agreement&state=74dcde36-7a62-4148-a5e7-e289744eb05a&nonce=n2BAeXzQoZ19NpkecydX2ipl9QfGxD6LEo7Cu6Ji&login_hint=bankid_se&signing_token=eyJjdHkiOiJKV1QiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiUlNBLU9BRVAtMjU2In0.z2AyVpUSQILsDQziwzvc-BqP12aWX0CQCerruvKWgwqyjkHBjhD8u_FrtDmey_yxD6fIWYgC-iLyGosVCo9g74twnRQtRQGdPIifiUMtkmZTIKt3Ex5hDDuYWhPss42f8r8sCAh3B9e5XA8vw1DdaWsOjNpwpJVvYUL4kttL-SfBimgAz2w5AkGkGHWMm6IObP8d947rh8Dbq_0zfk2khz6knE1QeC9ikNm9XInoGARjL51v23huFFe1EvsphAmkwjx6UeUdNd4gdylGPEvBI1uqacQ3DAy1oXrnaAB2PAjIv1X9X6XvuFJPUM9ujXJpJUr5URTm0y0iqMmIlLAt4Q.xiQidOua6libEn-C.kYILWL75C1g5uBmw7Jdp1MEne-EteTxG91mOzyJrgufZOjBL1vtUlmHEx_NZs7j5_TIpAQeNnQGE_4MK94uueQ9M8ePyYVHdrVWXDMWCCwHOooXlS16Zb36d9ugmiXi95pfLToL1S8oLjTNG5FHHzeBkXGZdnXoB2iofbPS8bZ9mJqoLi7OJjZ6oVwKOMaYaD4-oH7tbaAr0RKv7C_JCaQX9gSB9xxiCuZFVN-e5d2PmRRpUmA5gHvVtXkgKwtUYuwXrHWsEu545MgDKPexu2P4C2SD0BjgMs4_q8zmA-dGUve-oBrnz-VA1zk7jLtuUkxNglLcjzqcumCbygxtG4eLMLoSYSZEsQHeH-efj-Td_chPm9a_UC20sQ1CZ3jT_YTZLEBFuQzaXg_TVv24_xsmSCNU_BYXVfExfaxzKrxL8IJtzhBA-Mx4hm5rd4blaAPO_SSw9sj2q2Bci2-HsrgZ1mdiQZEeIU088F2wZtLUGgErJHg9MoJDRNjnRmsuIfy65h9X5EVHqavzE-MKmhtiQvYXfYqLxG8pLO2VSaj6oFkA-U-EAb3heB0YOD8y65phkZ2ta-TopResdCD8alrGA4aGuhE0LHgqkJvTWEm93g0B-z2RejDw9b6sh6hERBL4cz_L0.0Ne9IUky5aZVSufenBc2BA"
      }
    ]
  }
}

Please note that redirect links presence is determined by selected authentication_type and authentication_method

Verify a Payment example

This endpoint URL has the following form:

PUT /corporate/v3/payments/<payment_id>/verify

This endpoint supports PUT HTTP method. The following headers must be used:

Content-Type: application/json
Authorization: Bearer {access_token}
X-IBM-Client: {client_id}
X-IBM-Client-Secret: {client_secret}
Digest: {digest}
Signature: {signature}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The body of the request will vary, determined by the authentication type chosen.

Example of DECOUPLED authentication type with MTA authentication method

{
  "authentication_type": "DECOUPLED",
  "authentication_method": "MTA"
}

Example of DECOUPLED authentication type with BANKID_SE authentication method

{
  "authentication_type": "DECOUPLED",
  "authentication_method": "BANKID_SE"
}

Example of REDIRECT authentication type

{
  "authentication_type": "REDIRECT",
  "redirect_uri": "http://test.com",
  "state": "state",
  "authentication_method": "BANKID_SE",
  "language": "en"
}

Where the payment request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "1b9484d183acb813",
    "creation_date_time": "2025-10-07T10:28:44.47366027Z",
    "http_code": 200
  },
  "response": {
    "_id": "3b87765c-fcaa-4859-b977-a854773494bd",
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "external_id": "4b37d7a2-0d95-4f02-a4e7-0732e2757980",
    "end_to_end_id": "13227asdfds",
    "amount": "123.45",
    "requested_execution_date": "2025-10-07",
    "execution_date": "2025-10-07",
    "currency": "EUR",
    "urgency": "NORMAL",
    "debtor": {
      "account": {
        "value": "FI6816603001007528",
        "type": "IBAN",
        "currency": "EUR"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "value": "FI1350001520000081",
        "type": "IBAN"
      },
      "name": "Screws and Nuts Ltd",
      "message": "Invoice 5071",
      "bank": {
        "bic": "NDEAFIHH",
        "country": "FI"
      }
    },
    "status_timestamp": "2025-10-07T10:28:44.473668442",
    "create_timestamp": "2025-10-07T09:42:35.400231551",
    "payment_status": "AUTHORIZATION_PENDING",
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd/confirm"
      },
      {
        "rel": "details",
        "href": "/v3/payments/3b87765c-fcaa-4859-b977-a854773494bd"
      }
    ]
  }
}

Cancel a Payment example

This endpoint URL has the following form:

PUT /corporate/v3/payments/<payment_id>/cancel

This endpoint supports PUT HTTP method. The following headers must be used:

Content-Type: application/json
Authorization: Bearer {access_token}
X-IBM-Client: {client_id}
X-IBM-Client-Secret: {client_secret}
Digest: {digest}
Signature: {signature}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The body of the request will vary, determined by the authentication type chosen.

Example of DECOUPLED authentication type

{
  "authentication_type": "DECOUPLED",
  "authentication_method": "MTA"
}

Example of REDIRECT authentication type

{
  "authentication_type": "REDIRECT",
  "redirect_uri": "http://test.com",
  "state": "state",
  "authentication_method": "BANKID_SE",
  "language": "en"
}

Where the payment request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "32f32df2b20a883e",
    "creation_date_time": "2025-10-07T10:50:05.582209265Z",
    "http_code": 200
  },
  "response": {
    "_id": "e6ad479f-7c33-4dcb-8442-d98288004503",
    "template_id": "SEPA_CREDIT_TRANSFER_FI",
    "external_id": "737317e2-30a6-4889-bd26-c269a4e9719b",
    "end_to_end_id": "13227asdfds",
    "amount": "123.45",
    "requested_execution_date": "2025-10-07",
    "execution_date": "2025-10-07",
    "currency": "EUR",
    "urgency": "NORMAL",
    "debtor": {
      "account": {
        "value": "FI6816603001007528",
        "type": "IBAN",
        "currency": "EUR"
      },
      "own_reference": "Own message"
    },
    "creditor": {
      "account": {
        "value": "FI1350001520000081",
        "type": "IBAN"
      },
      "name": "Screws and Nuts Ltd",
      "message": "Invoice 5071",
      "bank": {
        "bic": "NDEAFIHH",
        "country": "FI"
      }
    },
    "status_timestamp": "2025-10-07T10:50:05.582220592",
    "create_timestamp": "2025-10-07T10:49:41.890608235",
    "payment_status": "AUTHORIZATION_PENDING",
    "payment_status_reason": "info.payment.cancellation_in_progress",
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/e6ad479f-7c33-4dcb-8442-d98288004503/cancel"
      },
      {
        "rel": "details",
        "href": "/v3/payments/e6ad479f-7c33-4dcb-8442-d98288004503"
      }
    ]
  }
}

Cancel multiple payments example

This endpoint URL has the following form:

POST/corporate/v3/payments/cancel

This endpoint supports PUT HTTP method. The following headers must be used:

Content-Type: application/json
Authorization: Bearer {access_token}
X-IBM-Client: {client_id}
X-IBM-Client-Secret: {client_secret}
Digest: {digest}
Signature: {signature}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

The body of the request will vary, determined by the authentication type chosen.

Example of DECOUPLED authentication type

{
  "authorization_details": {
    "authentication_type": "DECOUPLED",
    "authentication_method": "MTA"
  },
  "payment_details": {
    "payment_id_list": [
      "aec7d35b-7c16-49fd-b48d-7c9e62dcfc52",
      "1394ca3e-9156-475a-be2d-4e44cfd9160e"
    ]
  }
}

Example of REDIRECT authentication type

{
  "authorization_details": {
    "authentication_type": "REDIRECT",
    "redirect_uri": "https://www.nordea.com",
    "state": "state",
    "authentication_method": "BANKID_SE",
    "language": "en"
  },
  "payment_details": {
    "payment_id_list": [
      "aec7d35b-7c16-49fd-b48d-7c9e62dcfc52",
      "1394ca3e-9156-475a-be2d-4e44cfd9160e"
    ]
  }
}

Where the payment request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "1885999074034ffa",
    "creation_date_time": "2025-10-07T10:55:06.832140124Z",
    "http_code": 200
  },
  "response": {
    "payments": [
      {
        "_id": "aec7d35b-7c16-49fd-b48d-7c9e62dcfc52",
        "template_id": "SEPA_CREDIT_TRANSFER_FI",
        "external_id": "06a66dab-ae3d-402b-b9b2-c66c71fed4c0",
        "end_to_end_id": "13227asdfds",
        "amount": "123.45",
        "requested_execution_date": "2025-10-07",
        "execution_date": "2025-10-07",
        "currency": "EUR",
        "urgency": "NORMAL",
        "debtor": {
          "account": {
            "value": "FI6816603001007528",
            "type": "IBAN",
            "currency": "EUR"
          },
          "own_reference": "Own message"
        },
        "creditor": {
          "account": {
            "value": "FI1350001520000081",
            "type": "IBAN"
          },
          "name": "Screws and Nuts Ltd",
          "message": "Invoice 5071",
          "bank": {
            "bic": "NDEAFIHH",
            "country": "FI"
          }
        },
        "status_timestamp": "2025-10-07T10:55:06.832154996",
        "create_timestamp": "2025-10-07T10:52:40.024764731",
        "payment_status": "AUTHORIZATION_PENDING",
        "payment_status_reason": "info.payment.cancellation_in_progress",
        "_links": [
          {
            "rel": "details",
            "href": "/v3/payments/aec7d35b-7c16-49fd-b48d-7c9e62dcfc52"
          }
        ]
      },
      {
        "_id": "1394ca3e-9156-475a-be2d-4e44cfd9160e",
        "template_id": "SEPA_CREDIT_TRANSFER_FI",
        "external_id": "8384bac2-b95a-41e6-9827-27fc5be7123e",
        "end_to_end_id": "13227asdfds",
        "amount": "123.45",
        "requested_execution_date": "2025-10-07",
        "execution_date": "2025-10-07",
        "currency": "EUR",
        "urgency": "NORMAL",
        "debtor": {
          "account": {
            "value": "FI6816603001007528",
            "type": "IBAN",
            "currency": "EUR"
          },
          "own_reference": "Own message"
        },
        "creditor": {
          "account": {
            "value": "FI1350001520000081",
            "type": "IBAN"
          },
          "name": "Screws and Nuts Ltd",
          "message": "Invoice 5071",
          "bank": {
            "bic": "NDEAFIHH",
            "country": "FI"
          }
        },
        "status_timestamp": "2025-10-07T10:55:06.832220324",
        "create_timestamp": "2025-10-07T10:52:27.576301444",
        "payment_status": "AUTHORIZATION_PENDING",
        "payment_status_reason": "info.payment.cancellation_in_progress",
        "_links": [
          {
            "rel": "details",
            "href": "/v3/payments/1394ca3e-9156-475a-be2d-4e44cfd9160e"
          }
        ]
      }
    ],
    "_links": [
      {
        "rel": "self",
        "href": "/v3/payments/cancel"
      }
    ]
  }
}

Get details of the BankID SE authentication example

This endpoint URL has the following form:

GET /corporate/v1/authentications/bankid_se/{authentication_id}

This endpoint supports GET HTTP method. The following headers must be used:

X-IBM-Client-Id: {client_id}
X-IBM-Client-Secret: {client_secret}
X-Nordea-Originating-Date: {date}
X-Nordea-Originating-Host: {host}

Where the request is valid the response will be 200 SUCCESS and formatted like the example below

{
  "group_header": {
    "message_identification": "64b536c0e92c3947bd2f993c1af39d44",
    "creation_date_time": "2024-01-15T11:03:30.04307331Z",
    "http_code": 200
  },
  "response": {
    "qr_data": "bankid.52083e2c180a520d450b49e3b3bc29b60f701c889b2e1f5d1b81d2013d161896.4.AIf7W1tf0CK8PV66IogxfLoEsneyfSkylxGICIyuhnmA1E0qc5mDGg66s2A8JU4M",
    "auto_start_token": "8441d326-2d6e-4e4f-9412-303ec3d0931c",
    "status": "WAITING_FOR_USER"
  }
}

Please note that “auto_start_token” and “qr_data” will not be present when “status” will be different then “WAITING_FOR_USER”

Sample test data

A good amount of sample data (users, authorization permissions, etc.) have been placed in the sandbox environment to allow developers to explore the Corporate Payments API features/behaviour and test their client application functionality. This data is detailed in the table below for your reference. Data available in Sandbox environment can be fetched by using endpoint GET /corporate/v2/authorize/users.

Test data for Danish payments

Agreement Number	Account IBAN	Account BBAN	Account Currency	User Logon Id	Payment Authorization Permission	Type
130348721209	DK8820000216144198	20000216144198	DKK	70313276	ACT_ALONE	Transactional
130348721209	DK4720000808505894	20000808505894	DKK	70313276	ACT_ALONE	Transactional
130348721209	DK0820001544959502	20001544959502	DKK	70313276	ACT_ALONE	Transactional
130348721209	DK1020005005538159	20005005538159	DKK	70313276	ACT_ALONE	Transactional
130348721209	DK1920005036552583	20005036552583	DKK	70313276	ACT_ALONE	Transactional
130474822200	DK1520000807622315	20000807622315	DKK	70312662	TWO_TOGETHER	Transactional
130474822200	DK1520000807622315	20000807622315	DKK	70313004	ACT_ALONE	Transactional
130474822200	DK5720001544465666	20001544465666	DKK	70312662	TWO_TOGETHER	Transactional
130474822200	DK5720001544465666	20001544465666	DKK	70313004	ACT_ALONE	Transactional
130474822427	DK5220000270491715	20000270491715	DKK	70311198	ACT_ALONE	Transactional
130474822427	DK5220000270491715	20000270491715	DKK	70311591	TWO_TOGETHER	Transactional
130474822427	DK7220001560155049	20001560155049	DKK	70311198	ACT_ALONE	Transactional
130474822427	DK7220001560155049	20001560155049	DKK	70311591	TWO_TOGETHER	Transactional
130474822427	DK2420005005528692	20005005528692	DKK	70311198	ACT_ALONE	Transactional
130474822427	DK2420005005528692	20005005528692	DKK	70311591	TWO_TOGETHER	Transactional
130474822427	DK2120001543991305	20001543991305	DKK	70311198	ACT_ALONE	Transactional
130474822427	DK6220005036579260	20005036579260	USD	70311198	ACT_ALONE	Transactional
130474822427	DK2120001543991305	20001543991305	DKK	70311515	ACT_ALONE	Cash Pool
130474822427	DK2120001543991305	20001543991305	DKK	70311591	TWO_TOGETHER	Cash Pool
130474822427	DK2120001543991305	20001543991305	DKK	70312055	TWO_TOGETHER	Cash Pool
130474822427	DK1820000970202021	20000970202021	DKK	70311198	ACT_ALONE	Cash Pool
130474822427	DK1820000970202021	20000970202021	DKK	70311515	ACT_ALONE	Cash Pool
130474822427	DK1820000970202021	20000970202021	DKK	70311591	TWO_TOGETHER	Cash Pool
130474822427	DK1820000970202021	20000970202021	DKK	70312055	TWO_TOGETHER	Cash Pool
130474822427	DK3620005036542383	20000970202021	DKK	70311198	ACT_ALONE	Cash Pool
130474822427	DK3620005036542383	20000970202021	DKK	70311515	ACT_ALONE	Cash Pool
130474822427	DK3620005036542383	20000970202021	DKK	70311591	TWO_TOGETHER	Cash Pool
130474822427	DK3620005036542383	20000970202021	DKK	70312055	TWO_TOGETHER	Cash Pool

Test data for Finnish payments

Agreement Number	Account IBAN	Account BBAN	Account Currency	User Logon Id	Payment Authorization Permission	Type
130348721209	FI4616603001014326	N/A	EUR	70313276	ACT_ALONE	Transactional
130348721209	FI4616603001014326	N/A	EUR	70313514	TWO_TOGETHER	Transactional
130348721209	FI5115963000005662	N/A	EUR	70313276	ACT_ALONE	Transactional
130348721209	FI6711123000311263	N/A	EUR	70313276	ACT_ALONE	Transactional
130348721209	FI6711123000311263	N/A	EUR	70313514	TWO_TOGETHER	Transactional
130348721209	FI8216603000004393	N/A	EUR	70313276	ACT_ALONE	Transactional
130348721209	FI8216603000004393	N/A	EUR	70313514	ACT_ALONE	Transactional
130474822427	FI4116603500005114	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI4715723000311878	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI4715723000311878	N/A	EUR	70311515	TWO_TOGETHER	Transactional
130474822427	FI4715723000311878	N/A	EUR	70311591	TWO_TOGETHER	Transactional
130474822427	FI5815723000312165	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI5815723000312165	N/A	EUR	70311515	TWO_TOGETHER	Transactional
130474822427	FI5815723000312165	N/A	EUR	70311591	TWO_TOGETHER	Transactional
130474822427	FI6116603001005423	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI6116603001005423	N/A	EUR	70311515	TWO_TOGETHER	Transactional
130474822427	FI6116603001005423	N/A	EUR	70312055	ACT_ALONE	Transactional
130474822427	FI6116603001012213	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI6116603001012213	N/A	EUR	70311515	TWO_TOGETHER	Transactional
130474822427	FI6116603001012213	N/A	EUR	70312055	ACT_ALONE	Transactional
130474822427	FI6816603001007528	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI6816603001007528	N/A	EUR	70311515	CREATE_ONLY	Transactional
130474822427	FI6816603001007528	N/A	EUR	70311591	TWO_TOGETHER	Transactional
130474822427	FI6816603001007528	N/A	EUR	70312055	TWO_TOGETHER	Transactional
130474822427	FI8015723000311381	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	FI8015723000311381	N/A	EUR	70311515	TWO_TOGETHER	Transactional
130474822427	FI8015723000311381	N/A	EUR	70311591	TWO_TOGETHER	Transactional
130474822427	FI6416605200008561	N/A	JPY	70312055	ACT_ALONE	Transactional
130474822427	FI6416605200008561	N/A	JPY	70311591	ACT_ALONE	Transactional
130474822427	FI8616605200008553	N/A	USD	70311198	ACT_ALONE	Transactional
130474822427	FI8616605200008553	N/A	USD	70311515	TWO_TOGETHER	Transactional
130474822427	FI8616605200008553	N/A	USD	70311591	TWO_TOGETHER	Transactional
130474822427	FI2724982400224961	N/A	EUR	70311198	ACT_ALONE	Cash Pool
130474822427	FI2724982400224961	N/A	EUR	70311515	ACT_ALONE	Cash Pool
130474822427	FI2724982400224961	N/A	EUR	70311591	TWO_TOGETHER	Cash Pool
130474822427	FI2724982400224961	N/A	EUR	70312055	TWO_TOGETHER	Cash Pool
130474822427	FI9117453000002297	N/A	EUR	70311198	ACT_ALONE	Cash Pool
130474822427	FI9117453000002297	N/A	EUR	70311515	ACT_ALONE	Cash Pool
130474822427	FI9117453000002297	N/A	EUR	70311591	ACT_ALONE	Cash Pool
130474822427	FI9117453000002297	N/A	EUR	70312055	ACT_ALONE	Cash Pool

Test data for Norwegian payments

Agreement Number	Debtor Account in IBAN	Debtor Account in BBAN	Account Currency	User Logon Id	Payment Authorization Permission	Type
130474822427	NO2268250512345	68250512345	NOK	70311198	ACT_ALONE	Transactional
130474822427	NO2268250512345	68250512345	NOK	70311515	TWO_TOGETHER	Transactional
130474822427	NO2268250512345	68250512345	NOK	70311591	TWO_TOGETHER	Transactional
130474822427	NO2268250512345	68250512345	NOK	70312055	ACT_ALONE	Transactional
130474822427	NO9768250512353	68250512353	NOK	70311198	ACT_ALONE	Transactional
130474822427	NO9768250512353	68250512353	NOK	70311591	TWO_TOGETHER	Transactional
130474822427	NO9768250512353	68250512353	NOK	70312055	ACT_ALONE	Transactional
130474822427	NO7568250512361	68250512361	NOK	70311198	ACT_ALONE	Transactional
130474822427	NO7568250512361	68250512361	NOK	70311515	TWO_TOGETHER	Transactional
130474822427	NO7568250512361	68250512361	NOK	70311591	TWO_TOGETHER	Transactional
130474822427	NO7568250512361	68250512361	NOK	70312055	ACT_ALONE	Transactional
130474822427	NO9464520503798	64520503798	NOK	70311198	ACT_ALONE	Cash Pool
130474822427	NO9464520503798	64520503798	NOK	70311515	ACT_ALONE	Cash Pool
130474822427	NO9464520503798	64520503798	NOK	70311591	TWO_TOGETHER	Cash Pool
130474822427	NO9464520503798	64520503798	NOK	70312055	TWO_TOGETHER	Cash Pool
130474822427	NO6564520501507	64520501507	NOK	70311198	ACT_ALONE	Cash Pool
130474822427	NO6564520501507	64520501507	NOK	70311515	ACT_ALONE	Cash Pool
130474822427	NO6564520501507	64520501507	NOK	70311591	TWO_TOGETHER	Cash Pool
130474822427	NO6564520501507	64520501507	NOK	70312055	TWO_TOGETHER	Cash Pool
130474822427	NO2265600440335	65600440335	EUR	70311198	ACT_ALONE	Cash Pool
130474822427	NO2265600440335	65600440335	EUR	70311515	ACT_ALONE	Cash Pool
130474822427	NO2265600440335	65600440335	EUR	70311591	ACT_ALONE	Cash Pool
130474822427	NO2265600440335	65600440335	EUR	70312055	ACT_ALONE	Cash Pool
130474822200	NO4468250512337	68250512337	USD	70312662	TWO_TOGETHER	Transactional
130474822200	NO4468250512337	68250512337	USD	70313004	ACT_ALONE	Transactional
130474822200	NO6668250512329	68250512329	EUR	70312662	TWO_TOGETHER	Transactional
130474822200	NO6668250512329	68250512329	EUR	70313004	ACT_ALONE	Transactional
130474822200	NO9468250512310	68250512310	USD	70312662	ACT_ALONE	Transactional
130474822200	NO9468250512310	68250512310	USD	70313004	ACT_ALONE	Transactional

Test data for Swedish payments

Agreement Number	Account IBAN	Account BBAN	Plusgiro Number	Account Currency	User Logon Id	Payment Authorization Permission	Type
130348721209	SE5695000099602605435979	99602605435979	5435979	SEK	70313276	ACT_ALONE	Transactional
130348721209	SE5695000099602605435979	99602605435979	5435979	SEK	70313514	ACT_ALONE	Transactional
130348721209	SE7595000099603400171769	99603400171769	171769	EUR	70313276	ACT_ALONE	Transactional
130348721209	SE7595000099603400171769	99603400171769	171769	EUR	70313514	ACT_ALONE	Transactional
130348721209	SE1895000099602613964515	99602613964515	13964515	SEK	70313276	ACT_ALONE	Cash Pool
130474822200	SE5595000099604200176040	99604200176040	176040	SEK	70313004	ACT_ALONE	Transactional
130474822200	SE5595000099604200176040	99604200176040	176040	SEK	70312662	ACT_ALONE	Transactional
130474822200	SE4830000000040161303354	40161303354	N/A	SEK	70312662	ACT_ALONE	Transactional
130474822200	SE4830000000040161303354	40161303354	N/A	SEK	70313004	TWO_TOGETHER	Transactional
130474822427	SE0295000099604213908314	99604213908314	13908314	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE0295000099604213908314	99604213908314	13908314	SEK	70311515	ACT_ALONE	Transactional
130474822427	SE0295000099604213908314	99604213908314	13908314	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE0295000099604213908314	99604213908314	13908314	SEK	312055	TWO_TOGETHER	Transactional
130474822427	SE9195000099602614054381	99602614054381	14054381	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE9195000099602614054381	99602614054381	14054381	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE8795000099601814438154	99601814438154	14438154	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE8795000099601814438154	99601814438154	14438154	SEK	70311515	ACT_ALONE	Transactional
130474822427	SE8795000099601814438154	99601814438154	14438154	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE6130000000034821701634	34821701634	N/A	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE6130000000034821701634	34821701634	N/A	SEK	70311515	ACT_ALONE	Transactional
130474822427	SE6130000000034821701634	34821701634	N/A	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE3930000000040161303419	40161303419	N/A	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE3930000000040161303419	40161303419	N/A	SEK	70311515	ACT_ALONE	Transactional
130474822427	SE3930000000040161303419	40161303419	N/A	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE9130000000041357802818	41357802818	N/A	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE9130000000041357802818	41357802818	N/A	SEK	70311515	ACT_ALONE	Transactional
130474822427	SE9130000000041357802818	41357802818	N/A	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE4530000000030167700413	30167700413	N/A	CHF	70311198	ACT_ALONE	Transactional
130474822427	SE4530000000030167700413	30167700413	N/A	CHF	70311515	ACT_ALONE	Transactional
130474822427	SE4530000000030167700413	30167700413	N/A	CHF	70311591	TWO_TOGETHER	Transactional
130474822427	SE4530000000030167700413	30167700413	N/A	CHF	70312055	TWO_TOGETHER	Transactional
130474822427	SE1695000099604200171892	4200171892	N/A	EUR	70311198	ACT_ALONE	Transactional
130474822427	SE1695000099604200171892	4200171892	N/A	EUR	70311591	TWO_TOGETHER	Transactional
130474822427	SE5095000099603413908389	99603413908389	13908389	EUR	70311198	ACT_ALONE	Transactional
130474822427	SE5095000099603413908389	99603413908389	13908389	EUR	70311591	TWO_TOGETHER	Transactional
130474822427	SE5095000099603413908389	99603413908389	13908389	EUR	70312055	TWO_TOGETHER	Transactional
130474822427	SE9195000099602614054381	99602614054381	14054381	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE9195000099602614054381	99602614054381	14054381	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE9195000099602614054381	99602614054381	14054381	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE9130000000041357802818	41357802818	N/A	SEK	70311198	ACT_ALONE	Transactional
130474822427	SE9130000000041357802818	41357802818	N/A	SEK	70311591	TWO_TOGETHER	Transactional
130474822427	SE5295000099602600119966	99602600119966	N/A	SEK	70311198	ACT_ALONE	Cash Pool
130474822427	SE5295000099602600119966	99602600119966	N/A	SEK	70311515	ACT_ALONE	Cash Pool
130474822427	SE5295000099602600119966	99602600119966	N/A	SEK	70311591	TWO_TOGETHER	Cash Pool
130474822427	SE5295000099602600119966	99602600119966	N/A	SEK	70312055	TWO_TOGETHER	Cash Pool
130474822427	SE4395000099603400105221	99603400105221	N/A	EUR	70311198	ACT_ALONE	Cash Pool
130474822427	SE4395000099603400105221	99603400105221	N/A	EUR	70311515	ACT_ALONE	Cash Pool
130474822427	SE4395000099603400105221	99603400105221	N/A	EUR	70311591	TWO_TOGETHER	Cash Pool
130474822427	SE4395000099603400105221	99603400105221	N/A	EUR	70312055	TWO_TOGETHER	Cash Pool

Test data for External payments

Agreement Number	Account Number	Account Currency	User Logon Id	Payment Authorization Permission
130474822427	SE8592700000092701058888	SEK	70311198	ACT_ALONE
130474822427	SE8592700000092701058888	SEK	70311515	TWO_TOGETHER
130474822427	SE8592700000092701058888	SEK	70311591	TWO_TOGETHER
130474822427	SE8592700000092701058888	SEK	70312055	TWO_TOGETHER
130474822427	DK7962034118980181	DKK	70311198	ACT_ALONE
130474822427	DK7962034118980181	DKK	70311515	TWO_TOGETHER
130474822427	DK7962034118980181	DKK	70311591	TWO_TOGETHER
130474822427	DK7962034118980181	DKK	70312055	ACT_ALONE
130474822427	FI2916603001015893	EUR	70311198	ACT_ALONE
130474822427	FI2916603001015893	EUR	70311515	TWO_TOGETHER
130474822427	FI2916603001015893	EUR	70311591	TWO_TOGETHER
130474822427	FI2916603001015893	EUR	70312055	TWO_TOGETHER
130474822427	PL39106000760000409950046599	EUR	70311198	ACT_ALONE
130474822427	PL39106000760000409950046599	EUR	70311515	TWO_TOGETHER
130474822427	PL39106000760000409950046599	EUR	70311591	TWO_TOGETHER
130474822427	PL39106000760000409950046599	EUR	70312055	ACT_ALONE
130474822427	77881122	GBP	70311198	ACT_ALONE

UK Corporate Accounts API v1 Corporate Payments Single SCA API v2