UK Corporate Payments API v1

Version history

Version 1.1 - Available in Sandbox

Version 1.1 contain support for BACS payments including multi-beneficiary payment initiation and related payment flow handling.

Version 1.0 - Available in Sandbox

Version 1.0 of the UK Corporate Payments API is currently available only in the sandbox environment and supports Faster Payments and CHAPS.

Introduction

The UK Corporate Payments API enables TPP applications to initiate and manage credit transfer payments from Nordea UK corporate customer payment accounts.

Nordea provides these services to corporate customers in the UK. This API provides payment initiation services to Large Corporate customers, in compliance with the UK Payment Services Regulations (PSRs).

The API supports the following payment types:

Payment type	Description	Payment Currency
Faster Payments	UK domestic credit transfer, near-instant settlement	GBP
CHAPS	UK domestic high-value same-day settlement	GBP
BACS	UK domestic bulk credit transfer, two-working-day settlement cycle	GBP

Using the API, a TPP can:

Initiate (create) a payment instruction
Verify beneficiaries, when required for not yet verified beneficiaries
Confirm the payment — required before execution
Get payment status and details
List payments
Cancel a payment

Note: All payment endpoints can only be accessed with a token authorized by a PSU (Payment Service User) with a scope “PAYMENTS_UK”. 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 the Corporate Access Authorization API v3 documentation.

Payment Flow

Overview

Every payment follows the same top-level lifecycle:

Initiation — TPP submits a payment instruction. The payment instruction is created.
Beneficiary verification (conditional) — if one or more beneficiaries are not yet verified, the PSU must verify them before confirmation is possible.
Confirmation — the payment creator (PSU) must explicitly confirm the payment. PSU signs the confirmation in Nordea App.
Execution — after confirmation, the payment is submitted for processing and eventually executed.

At any stage, the TPP can:

Poll GET /uk/v1/payments/{payment_id} to check the current state.
Cancel the payment (subject to state restrictions).

BACS-specific note: A BACS payment can include multiple beneficiaries. If any beneficiary requires verification, the payment enters the verification flow before confirmation.

Happy path — no beneficiary verification required (all beneficiaries already verified):

sequenceDiagram
  participant TPP
  participant OB as Nordea Open Banking
  participant PSU as PSU (Nordea App)

  TPP->>OB: POST /uk/v1/payments
  OB-->>TPP: 201 Created<br/>PAYMENT_INITIATED
  OB-->>TPP: AUTHORIZATION_PARTIAL<br/>confirmation_required
  TPP->>OB: PUT /uk/v1/payments/{payment_id}/confirm
  OB->>PSU: Create confirmation signing order
  OB-->>TPP: 200 OK<br/>AUTHORIZATION_PENDING
  PSU-->>OB: Sign in Nordea App
  OB-->>TPP: PAYMENT_ACCEPTED
  OB-->>TPP: PAYMENT_EXECUTED

Happy path — with beneficiary verification required (single or multiple beneficiaries):

sequenceDiagram
  participant TPP
  participant OB as Nordea Open Banking
  participant PSU as PSU (Nordea App)

  TPP->>OB: POST /uk/v1/payments
  OB-->>TPP: 201 Created<br/>PAYMENT_INITIATED
  OB-->>TPP: AUTHORIZATION_PARTIAL<br/>verification_required
  TPP->>OB: PUT /uk/v1/payments/{payment_id}/verify
  OB->>PSU: Create verification signing order
  OB-->>TPP: 200 OK<br/>AUTHORIZATION_PENDING
  PSU-->>OB: Sign in Nordea App
  OB-->>TPP: AUTHORIZATION_PARTIAL<br/>confirmation_required
  TPP->>OB: PUT /uk/v1/payments/{payment_id}/confirm
  OB->>PSU: Create confirmation signing order
  OB-->>TPP: 200 OK<br/>AUTHORIZATION_PENDING
  PSU-->>OB: Sign in Nordea App
  OB-->>TPP: PAYMENT_ACCEPTED
  OB-->>TPP: PAYMENT_EXECUTED

Payment Initiation

POST /uk/v1/payments

Initial request to create a payment instruction. The request body includes the payment details and identifies the payment type via the template_id field:

Template ID	Payment type
`FASTER_PAYMENT_UK`	Faster Payments
`CHAPS_PAYMENT_UK`	CHAPS
`BACS_PAYMENT_UK`	BACS

In payment initiation request:

For Faster Payments and CHAPS, the payment instruction contains a single creditor object.
For BACS, the payment instruction contains a creditors array and one payment instruction may include multiple beneficiaries.

Nordea’s Open Banking service validates the payment instruction and, if successful, returns a payment_id that must be stored by the TPP and used in all subsequent operations (confirm, verify, cancel, get details).

In payment initiation response:

For Faster Payments and CHAPS, the response contains a single creditor object.
For BACS, the response contains a creditors array. Each creditor includes beneficiary_verification attribute to indicate verification need for that beneficiary.

In the initiation response for BACS, allowed beneficiary_verification values are REQUIRED and NOT_REQUIRED. Value VERIFIED is used only after beneficiary verification has been completed.

On success the initial response status is PAYMENT_INITIATED. This is a transient state — the service processes the request asynchronously and transitions to the next state without further action from the TPP. The TPP should poll GET /uk/v1/payments/{payment_id} to detect the transition.

After processing, the payment will be in one of the following states:

Resulting state	Condition
`AUTHORIZATION_PARTIAL` with `payment_status_reason: info.payment.verification_required`	For Faster Payments and CHAPS, the beneficiary must be verified. For BACS, one or more beneficiaries must be verified. Follow the beneficiary verification flow before confirming.
`AUTHORIZATION_PARTIAL` with `payment_status_reason: info.payment.confirmation_required`	No verification needed. Payment is ready for PSU confirmation.

Sandbox testing note: In sandbox, TPPs can use the optional X-Response-Scenarios header with POST /uk/v1/payments to control whether beneficiary verification is required in the initiation response.

If X-Response-Scenarios is set to paymentVerificationRequired:

For BACS payments, every second beneficiary in the creditors array is returned with beneficiary_verification: REQUIRED; the remaining beneficiaries are returned with beneficiary_verification: NOT_REQUIRED.

For Faster Payments and CHAPS, the single beneficiary is returned as requiring verification.

If X-Response-Scenarios is omitted or has any other value, the payment does not require beneficiary verification and moves to AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.confirmation_required.

Important: Validation errors during payment initiation return an HTTP 4xx error — no payment record is created. The TPP must correct the request and retry.

The payment must be confirmed (and if required, verified first) before the end of the requested execution date, or it will be rejected.

For request and response examples, see Create Payment examples.

Beneficiary Verification

PUT /uk/v1/payments/{payment_id}/verify

This endpoint is called when the payment status is AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.verification_required. In this process phase PSU must verify beneficiaries information.

Upon calling this endpoint, Open Banking creates a signing order in Nordea App. A beneficiary must be verified by the PSU through a signing process in Nordea App before the payment can proceed. Anyone who have KEY_IN rights into debtor account have permission to verify payment/beneficiaries.

For Faster Payments and CHAPS, verification applies to the single beneficiary in the payment.

For BACS, verification applies at beneficiary level:

The initiation (and also GET /uk/v1/payments/{payment_id}) response indicates verification need per beneficiary using beneficiary_verification.
Beneficiaries with beneficiary_verification = REQUIRED must be verified before confirmation is possible.
All beneficiaries that require verification are verified together in one verification signing flow; they are not verified separately.
After successful verification, those beneficiaries are returned with beneficiary_verification = VERIFIED. Beneficiaries that did not require verification remain NOT_REQUIRED.

When the PSU completes signing (ie verified beneficiaries) the payment transitions to:

AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.confirmation_required — verification complete, payment ready for confirmation.

For request and response examples, see Verify Payment examples.

Payment Confirmation

PUT /uk/v1/payments/{payment_id}/confirm

Each payment requires at least one confirmation before it can be executed. The first confirmation must be performed by the same PSU who created the payment.

When called, Open Banking creates a signing order in Nordea App. The PSU signs the payment. While the signing is in progress, the payment status is:

AUTHORIZATION_PENDING with payment_status_reason: info.payment.confirmation_in_progress

Once the PSU successfully signs, the payment transitions to:

PAYMENT_ACCEPTED — the payment has been fully authorised and submitted for execution processing.

Note - after successful signing payment can still transit into AUTHORIZATION_PARTIAL state if several confirmation is needed. This can happen if the payment requires multiple confirmations and the next confirmation is required from a different PSU. In that case payment_status_reason will be info.payment.confirmation_required and the next PSU must be nominated by calling the confirm endpoint again.

From PAYMENT_ACCEPTED, the payment is processed and transitions automatically to a final state (see payment states table in Payment Status Reference).

Note: Payments must be confirmed before the cut-off time on requested_execution_date, or they will be rejected.

For request and response examples, see Confirm Payment examples.

Getting Payment Details

GET /uk/v1/payments/{payment_id}

At any stage of the process, the TPP can retrieve the current status and full details of a payment. The payment_id must be the identifier originally returned from the payment initiation.

Use this endpoint to poll for state changes — for example, after calling confirm or verify, poll until the expected next state is reached.

For Faster Payments and CHAPS, the response contains a single creditor object. For BACS, the response contains a creditors array.

For BACS, each creditor includes beneficiary_verification, which indicates the beneficiary-level verification state. payment_status and payment_status_reason remain payment-level fields and indicate the overall payment state.

For request and response examples, see Get Payment Details examples.

Payment List

GET /uk/v1/payments

Returns a list of payment instructions with their current status and details, filtered by the search criteria provided as query parameters. Supported filters include for example creation date range, execution date range, debtor account, payment status, and others.

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

For Faster Payments and CHAPS, each payment item in the list response contains a single creditor object. For BACS, each payment item contains a creditors array.

For BACS, each creditor includes beneficiary_verification to indicate beneficiary-level verification state. payment_status and payment_status_reason remain payment-level fields for each listed payment.

See more about parameters and request and response examples in Payment List examples

Payment Cancellation

PUT /uk/v1/payments/{payment_id}/cancel

Used to cancel a payment. Upon calling this endpoint, Open Banking creates a cancellation signing order in Nordea App. While cancellation signing is in progress, the payment status is:

AUTHORIZATION_PENDING with payment_status_reason: info.payment.cancellation_in_progress

Once the PSU signs, the payment transitions to PAYMENT_CANCELLED, which is a final state. Cancelled payments remain visible but cannot be modified.

Not all payment statuses can be cancelled. Payments with status PAYMENT_REJECTED, PAYMENT_EXECUTED, PAYMENT_CANCELLED or AUTHORIZATION_PENDING cannot be cancelled.

For request and response examples, see Cancel Payment examples.

Payment Status Reference

The reported state of a payment can be any of the following:

Status	`payment_status_reason`	Meaning
`PAYMENT_INITIATED`	—	Synchronous create response received; no immediate verification indicator returned. Payment is still under asynchronous processing and may still be rejected.
`PAYMENT_INITIATED`	`info.payment.verification_required`	Synchronous create response received with immediate indication that verification will be required. Payment is still under asynchronous processing and may still be rejected.
`AUTHORIZATION_PARTIAL`	`info.payment.verification_required`	One or more beneficiaries require PSU verification before payment can be confirmed.
`AUTHORIZATION_PARTIAL`	`info.payment.confirmation_required`	Payment is ready for PSU confirmation.
`AUTHORIZATION_PENDING`	`info.payment.verification_in_progress`	Beneficiary verification signing order is active in Nordea App. Awaiting PSU signature.
`AUTHORIZATION_PENDING`	`info.payment.confirmation_in_progress`	Confirmation signing order is active in Nordea App. Awaiting PSU signature.
`AUTHORIZATION_PENDING`	`info.payment.cancellation_in_progress`	Cancellation signing order is active in Nordea App. Awaiting PSU signature.
`AUTHORIZATION_FAILED`	`error.payment.missing_authorization_rights`	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.
`AUTHORIZATION_FAILED`	`error.payment.technical_error` or `error.payment.unexpected_error`	Indicate system failure, customer could retry with same user or nominate another one.
`PAYMENT_ACCEPTED`	—	Payment fully authorised and submitted for processing.
`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. Final state.
`PAYMENT_CANCELLED`	—	Payment cancelled. Final state.
`PAYMENT_REJECTED`	—	Payment has been rejected. Reason is provided within the payment_status_reason code in response. Final state.

For BACS, beneficiary-level verification need is provided per creditor via beneficiary_verification.

Cut-off times

Payments must be confirmed before their cut-off time. Cut-off times vary by payment type. For cut-off times, refer to the Nordea UK cut-off list: NBI Cut-off Times

Payment Templates

Each payment initiation request must identify the payment type using a template_id field in the request body. The template determines the payment scheme and the high-level request and response model.

In the current sandbox publication, UK payments support three templates:

Template ID	Payment type	Settlement	Amount limit	Payment Currency
`FASTER_PAYMENT_UK`	Faster Payments	Near-instant	Max £250 000 per payment	GBP
`CHAPS_PAYMENT_UK`	CHAPS	Same-day	No upper limit	GBP
`BACS_PAYMENT_UK`	BACS	Two working days	No upper limit	GBP

High-level request and response model by template:

Faster Payments and CHAPS: payment initiation request contains one beneficiary object (creditor), and response returns one beneficiary object (creditor).
BACS: payment initiation request contains a beneficiaries array (creditors), and response returns a beneficiaries array (creditors).

For BACS, beneficiary verification is determined at beneficiary level and returned in the response at beneficiary level, while payment_status and payment_status_reason remain payment-level fields.

API reference

Nordea offers open api definitions available for our consumers under UK Corporate Payments API v1 documentation. The documentation includes detailed information about the request and response structure, field definitions, and validation rules for each payment type.

Authentication and Authorization

Authentication

The only supported authentication method is NordeaID (MTA).

Access Token

All payment endpoints require a PSU token. Admin tokens are not supported. For more details please see the Corporate Access Authorization API v3 documentation.

Required HTTP Headers

Every request must include the following headers:

Header	Required	Description
`Authorization`	Yes	`Bearer <access_token>` — PSU access token
`X-IBM-Client-Id`	Yes	Client ID issued at TPP onboarding
`X-IBM-Client-Secret`	Yes	Client secret issued at TPP onboarding
`Content-type`	Yes (with body)	`application/json`
`Signature`	Yes*	RSA-SHA256 request signature (see Request Signing)
`X-Nordea-Originating-Host`	Yes*	Domain name of the originating server
`X-Nordea-Originating-Date`	Yes*	Request timestamp in RFC 7231 format, e.g. `Wed, 24 Apr 2019 14:00:37 GMT`
`Digest`	Yes (with body)	SHA-256 or SHA-512 hash of the request body
`X-Nordea-Originating-User-Ip`	No	PSU IP address, if TPP is in session with PSU
`X-Nordea-Originating-User-Agent`	No	PSU agent information, if TPP is in session with PSU

** Required on all requests. The Digest and Content-type header is required only when the request contain a body.*

Request Signing

Requests must be signed at the application level using the Signature header as defined in RFC draft “Signing HTTP Messages” version 10.

Requirements:

Algorithm: RSA-SHA256
Minimum key size: 2048 bit
keyId: the X-IBM-Client-Id value
Headers to include in the signature:
- Requests without body: (request-target), X-Nordea-Originating-Host, X-Nordea-Originating-Date
- Requests with body: (request-target), X-Nordea-Originating-Host, X-Nordea-Originating-Date, Content-Type, Digest

For GET requests, no request body is sent and therefore no Digestand Content-typeis required.

Strong Customer Authentication (SCA)

SCA is required when a PSU confirms, cancels or verifies a payment. Following two authorization flows are supported:

Decoupled flow

The PSU authenticates directly on their NordeaID device without leaving the TPP application. The request body must include:

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

Redirect flow

The PSU is redirected to the Nordea authentication page. The request body must include:

{
  "authentication_type": "REDIRECT",
  "authentication_method": "MTA",
  "redirect_uri": "https://example.com/callback",
  "state": "38ee6abc-fd48-4b11-bd6a-97501fce702e"
}

Only supported language in authentication flow is English.

Examples

The examples in this section are illustrative and show the general request and response structure for the API. Header values such as Authorization, Signature, Digest, X-Nordea-Originating-Date, and X-Nordea-Originating-Host are omitted for brevity.

Create Payment examples

POST /uk/v1/payments

This endpoint is used to create a payment instruction. The request body structure is the same for Faster Payments and CHAPS. The main differences are the template_id, amount limits, and message formatting rules described in API definition - see from API reference.

Faster Payments — request example

This Faster Payments example shows a payment with a single beneficiary and here beneficiary verification required. The template_id identifies the payment type and determines the applicable validation rules.

{
  "payment_instruction": {
    "template_id": "FASTER_PAYMENT_UK",
    "amount": 1.0,
    "currency": "GBP",
    "requested_execution_date": "2026-04-23",
    "debtor": {
      "account": {
        "currency": "GBP",
        "value": "3046697121"
      },
      "own_reference": "own message"
    },
    "creditor": {
      "account": {
        "value": "30466971"
      },
      "bank": {
        "bank_code": "445566",
        "name": "Example Bank",
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "country": "GB"
      },
      "message": "message",
      "name": "Name"
    },
    "external_id": "f1642fe6-ebdf-4f71-b5ab-14dd88da3a80"
  }
}

Faster Payments — response example

{
  "group_header": {
    "message_identification": "2d785ebab22c3050",
    "creation_date_time": "2026-04-22T11:47:31.224336203Z",
    "http_code": 201
  },
  "response": {
    "_id": "7f8bb693-47b3-40b8-8db3-f923aa6429f8",
    "template_id": "FASTER_PAYMENT_UK",
    "external_id": "f1642fe6-ebdf-4f71-b5ab-14dd88da3a80",
    "amount": "1.0",
    "requested_execution_date": "2026-04-23",
    "currency": "GBP",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "own message"
    },
    "creditor": {
      "account": {
        "value": "30466971"
      },
      "name": "Name",
      "bank": {
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "bank_code": "445566",
        "country": "GB",
        "name": "Example Bank"
      },
      "message": "message"
    },
    "payment_status": "PAYMENT_INITIATED",
    "payment_status_reason": "info.payment.verification_required",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments"
      },
      {
        "rel": "verify",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/verify"
      },
      {
        "rel": "cancel",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/cancel"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8"
      }
    ]
  }
}

The payment is then processed asynchronously. The TPP should poll GET /uk/v1/payments/{payment_id} until the payment transitions to either:

AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.verification_required, or
AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.confirmation_required

CHAPS — request example

Here beneficiary verification is not required, so the payment can be confirmed immediately after initiation.

{
  "payment_instruction": {
    "template_id": "CHAPS_PAYMENT_UK",
    "amount": 285000.00,
    "currency": "GBP",
    "requested_execution_date": "2026-04-23",
    "external_id": "0c2efdc7-a2cb-4df8-9d4e-dc3bfc508e71",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "Property completion"
    },
    "creditor": {
      "name": "Smith and Co Client Account",
      "country": "GB",
      "address": {
        "line_1": "22 Market Road",
        "line_2": "Manchester"
      },
      "account": {
        "value": "87654321"
      },
      "bank": {
        "bank_code": "445566",
        "name": "Example Bank",
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "country": "GB"
      },
      "srd_roll_number": "MATTER7788",
      "message": "Completion funds. Ref 2026-041. Client A"
    }
  }
}

CHAPS — response example

{
  "group_header": {
    "message_identification": "11b15d6184a6bb0a",
    "creation_date_time": "2026-04-22T11:56:39.894821855Z",
    "http_code": 201
  },
  "response": {
    "_id": "1a9485ba-aee8-4412-bfcb-a5be44779964",
    "template_id": "CHAPS_PAYMENT_UK",
    "external_id": "0c2efdc7-a2cb-4df8-9d4e-dc3bfc508e71",
    "amount": "285000.00",
    "requested_execution_date": "2026-04-23",
    "currency": "GBP",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "Property completion"
    },
    "creditor": {
      "account": {
        "value": "87654321"
      },
      "name": "Smith and Co Client Account",
      "address": {
        "line_1": "22 Market Road",
        "line_2": "Manchester"
      },
      "bank": {
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "bank_code": "445566",
        "country": "GB",
        "name": "Example Bank"
      },
      "message": "Completion funds. Ref 2026-041. Client A",
      "srd_roll_number": "MATTER7788"
    },
    "payment_status": "PAYMENT_INITIATED",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments"
      },
      {
        "rel": "confirm",
        "href": "/uk/v1/payments/1a9485ba-aee8-4412-bfcb-a5be44779964/confirm"
      },
      {
        "rel": "cancel",
        "href": "/uk/v1/payments/1a9485ba-aee8-4412-bfcb-a5be44779964/cancel"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/1a9485ba-aee8-4412-bfcb-a5be44779964"
      }
    ]
  }
}

BACS — request example

This BACS Payment example shows a payment with a multiple beneficiaries and here beneficiary verification required for some of the beneficiaries. The template_id identifies the payment type and determines the applicable validation rules.

{
  "payment_instruction": {
    "template_id": "BACS_PAYMENT_UK",
    "requested_execution_date": "{{2_days_from_today}}",
    "control_sum": 250.00,
    "number_of_transactions": 3,
    "external_id": "{{randomUUID}}",
    "debtor": {
      "account": {
        "currency": "GBP",
        "value": "3046697121"
      },
      "own_reference": "BACS-Multiple Beneficiaries"
    },
    "creditors": [
      {
        "name": "Beneficiary One",
        "amount": 100.00,
        "external_id": "{{randomUUID}}",
        "message": "Invoice A1-001",
        "account": {
          "value": "12345678"
        },
        "bank": {
          "bank_code": "203456"
        }
      },
      {
        "name": "Beneficiary Two",
        "amount": 100.00,
        "external_id": "{{randomUUID}}",
        "message": "Invoice A1-002",
        "account": {
          "value": "87654321"
        },
        "bank": {
          "bank_code": "203456"
        }
      },
      {
        "name": "Beneficiary Three",
        "amount": 50.00,
        "external_id": "{{randomUUID}}",
        "message": "Invoice A1-003",
        "account": {
          "value": "11223344"
        },
        "bank": {
          "bank_code": "203456"
        }
      }
    ]
  }
}

BACS — response example

{
  "group_header": {
    "message_identification": "6389e4b27fa001c3",
    "creation_date_time": "2026-07-24T12:15:09.613391254Z",
    "http_code": 201
  },
  "response": {
    "_id": "32ac01e9-5f8c-418f-832b-da1cc4cdeea5",
    "template_id": "BACS_PAYMENT_UK",
    "external_id": "ebdc834e-effa-4073-8dab-3f0c631197cf",
    "requested_execution_date": "2026-07-26",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "BACS-Multiple Beneficiaries"
    },
    "number_of_transactions": 3,
    "control_sum": "250.00",
    "creditors": [
      {
        "account": {
          "value": "12345678"
        },
        "name": "Beneficiary One",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-001",
        "amount": "100.00",
        "beneficiary_verification_status": "REQUIRED"
      },
      {
        "account": {
          "value": "87654321"
        },
        "name": "Beneficiary Two",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-002",
        "amount": "100.00",
        "beneficiary_verification_status": "NOT_REQUIRED"
      },
      {
        "account": {
          "value": "11223344"
        },
        "name": "Beneficiary Three",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-003",
        "amount": "50.00",
        "beneficiary_verification_status": "REQUIRED"
      }
    ],
    "payment_status": "PAYMENT_INITIATED",
    "payment_status_reason": "info.payment.verification_required",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments"
      },
      {
        "rel": "verify",
        "href": "/uk/v1/payments/32ac01e9-5f8c-418f-832b-da1cc4cdeea5/verify"
      },
      {
        "rel": "cancel",
        "href": "/uk/v1/payments/32ac01e9-5f8c-418f-832b-da1cc4cdeea5/cancel"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/32ac01e9-5f8c-418f-832b-da1cc4cdeea5"
      }
    ]
  }
}

As with Faster Payments, the initial response only confirms that the payment instruction has been created. The payment must still progress through the authorization flow before execution.

Get Payment Details examples

GET /uk/v1/payments/{payment_id}

This endpoint returns the current payment status together with the payment details originally submitted at initiation.

Request example

This is example of above Faster payment created above.

GET /uk/v1/payments/24bcfc34-4502-4d3e-bcfe-f80c477f4e08

Response example

{
  "group_header": {
    "message_identification": "2d785ebab22c3050",
    "creation_date_time": "2026-04-22T11:47:31.224336203Z",
    "http_code": 201
  },
  "response": {
    "_id": "7f8bb693-47b3-40b8-8db3-f923aa6429f8",
    "template_id": "FASTER_PAYMENT_UK",
    "external_id": "f1642fe6-ebdf-4f71-b5ab-14dd88da3a80",
    "amount": "1.0",
    "requested_execution_date": "2026-04-23",
    "currency": "GBP",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "own message"
    },
    "creditor": {
      "account": {
        "value": "30466971"
      },
      "name": "Name",
      "bank": {
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "bank_code": "445566",
        "country": "GB",
        "name": "Example Bank"
      },
      "message": "message"
    },
    "payment_status": "AUTHORIZATION_PARTIAL",
    "payment_status_reason": "info.payment.verification_required",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments"
      },
      {
        "rel": "verify",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/verify"
      },
      {
        "rel": "cancel",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/cancel"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8"
      }
    ]
  }
}

In this example, the payment has been created successfully and beneficiary verification is required. The next step for the TPP is to call PUT /uk/v1/payments/{payment_id}/verify.

The same endpoint can also return other states, for example:

AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.confirmation_required
AUTHORIZATION_PENDING with payment_status_reason: info.payment.confirmation_in_progress
PAYMENT_ACCEPTED
PAYMENT_EXECUTED
PAYMENT_CANCELLED
PAYMENT_REJECTED
AUTHORIZATION_FAILED

BACS — response example

{
  "group_header": {
    "message_identification": "73c0f71497ee2230",
    "creation_date_time": "2026-07-24T12:26:30.691184839Z",
    "http_code": 200
  },
  "response": {
    "_id": "32ac01e9-5f8c-418f-832b-da1cc4cdeea5",
    "template_id": "BACS_PAYMENT_UK",
    "external_id": "ebdc834e-effa-4073-8dab-3f0c631197cf",
    "requested_execution_date": "2026-07-26",
    "execution_date": "2026-07-26",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "BACS-Multiple Beneficiaries"
    },
    "number_of_transactions": 3,
    "control_sum": "250.00",
    "creditors": [
      {
        "account": {
          "value": "12345678"
        },
        "name": "Beneficiary One",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-001",
        "amount": "100.00",
        "beneficiary_verification_status": "VERIFIED"
      },
      {
        "account": {
          "value": "87654321"
        },
        "name": "Beneficiary Two",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-002",
        "amount": "100.00",
        "beneficiary_verification_status": "NOT_REQUIRED"
      },
      {
        "account": {
          "value": "11223344"
        },
        "name": "Beneficiary Three",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-003",
        "amount": "50.00",
        "beneficiary_verification_status": "VERIFIED"
      }
    ],
    "payment_status": "AUTHORIZATION_PARTIAL",
    "payment_status_reason": "info.payment.confirmation_required",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments/32ac01e9-5f8c-418f-832b-da1cc4cdeea5"
      },
      {
        "rel": "confirm",
        "href": "/uk/v1/payments/32ac01e9-5f8c-418f-832b-da1cc4cdeea5/confirm"
      },
      {
        "rel": "cancel",
        "href": "/uk/v1/payments/32ac01e9-5f8c-418f-832b-da1cc4cdeea5/cancel"
      }
    ]
  }
}

Verify Payment examples

PUT /uk/v1/payments/{payment_id}/verify

This endpoint is used when the payment is in AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.verification_required.

Request example

This example continues the Faster Payments example above and starts beneficiary verification using the decoupled SCA flow.

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

Response example

{
  "group_header": {
    "message_identification": "3e86b80d01e488c5",
    "creation_date_time": "2026-04-22T12:03:07.515600485Z",
    "http_code": 200
  },
  "response": {
    "_id": "7f8bb693-47b3-40b8-8db3-f923aa6429f8",
    "template_id": "FASTER_PAYMENT_UK",
    "external_id": "f1642fe6-ebdf-4f71-b5ab-14dd88da3a80",
    "amount": "1.0",
    "requested_execution_date": "2026-04-23",
    "execution_date": "2026-04-23",
    "currency": "GBP",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "own message"
    },
    "creditor": {
      "account": {
        "value": "30466971"
      },
      "name": "Name",
      "bank": {
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "bank_code": "445566",
        "country": "GB",
        "name": "Example Bank"
      },
      "message": "message"
    },
    "payment_status": "AUTHORIZATION_PENDING",
    "payment_status_reason": "info.payment.verification_in_progress",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/verify"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8"
      }
    ]
  }
}

In this example, Open Banking has created a verification signing order and the payment is now waiting for PSU action in Nordea App.

After the PSU successfully signs, the payment will transition to:

AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.confirmation_required

The TPP should poll GET /uk/v1/payments/{payment_id} and, once the payment reaches that state, continue with PUT /uk/v1/payments/{payment_id}/confirm.

{
  "group_header": {
    "message_identification": "cc1e8c0e00e4bd80",
    "creation_date_time": "2026-07-24T14:04:07.833943448Z",
    "http_code": 200
  },
  "response": {
    "_id": "5caeb1b0-5126-4dca-89e8-c698e443667a",
    "template_id": "BACS_PAYMENT_UK",
    "external_id": "ed23c0b2-2b2d-4cc8-8612-cb2b7e37afe2",
    "requested_execution_date": "2026-07-26",
    "execution_date": "2026-07-26",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "BACS-Multiple Beneficiaries"
    },
    "number_of_transactions": 3,
    "control_sum": "250.00",
    "creditors": [
      {
        "account": {
          "value": "12345678"
        },
        "name": "Beneficiary One",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-001",
        "amount": "100.00",
        "beneficiary_verification_status": "REQUIRED"
      },
      {
        "account": {
          "value": "87654321"
        },
        "name": "Beneficiary Two",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-002",
        "amount": "100.00",
        "beneficiary_verification_status": "NOT_REQUIRED"
      },
      {
        "account": {
          "value": "11223344"
        },
        "name": "Beneficiary Three",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-003",
        "amount": "50.00",
        "beneficiary_verification_status": "REQUIRED"
      }
    ],
    "payment_status": "AUTHORIZATION_PENDING",
    "payment_status_reason": "info.payment.verification_in_progress",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments/5caeb1b0-5126-4dca-89e8-c698e443667a/verify"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/5caeb1b0-5126-4dca-89e8-c698e443667a"
      }
    ]
  }
}

{
  "group_header": {
    "message_identification": "75adac649e206d85",
    "creation_date_time": "2026-07-24T14:04:34.134919639Z",
    "http_code": 200
  },
  "response": {
    "_id": "5caeb1b0-5126-4dca-89e8-c698e443667a",
    "template_id": "BACS_PAYMENT_UK",
    "external_id": "ed23c0b2-2b2d-4cc8-8612-cb2b7e37afe2",
    "requested_execution_date": "2026-07-26",
    "execution_date": "2026-07-26",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "BACS-Multiple Beneficiaries"
    },
    "number_of_transactions": 3,
    "control_sum": "250.00",
    "creditors": [
      {
        "account": {
          "value": "12345678"
        },
        "name": "Beneficiary One",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-001",
        "amount": "100.00",
        "beneficiary_verification_status": "VERIFIED"
      },
      {
        "account": {
          "value": "87654321"
        },
        "name": "Beneficiary Two",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-002",
        "amount": "100.00",
        "beneficiary_verification_status": "NOT_REQUIRED"
      },
      {
        "account": {
          "value": "11223344"
        },
        "name": "Beneficiary Three",
        "bank": {
          "bank_code": "203456"
        },
        "message": "Invoice A1-003",
        "amount": "50.00",
        "beneficiary_verification_status": "VERIFIED"
      }
    ],
    "payment_status": "AUTHORIZATION_PARTIAL",
    "payment_status_reason": "info.payment.confirmation_required",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments/5caeb1b0-5126-4dca-89e8-c698e443667a"
      },
      {
        "rel": "confirm",
        "href": "/uk/v1/payments/5caeb1b0-5126-4dca-89e8-c698e443667a/confirm"
      },
      {
        "rel": "cancel",
        "href": "/uk/v1/payments/5caeb1b0-5126-4dca-89e8-c698e443667a/cancel"
      }
    ]
  }
}

Confirm Payment examples

PUT /uk/v1/payments/{payment_id}/confirm

This endpoint is used when the payment is in AUTHORIZATION_PARTIAL with payment_status_reason: info.payment.confirmation_required.

For BACS payments, confirmation follows the same process as Faster Payments and CHAPS after all required beneficiary verification has been completed. No separate BACS confirmation example is provided because the confirmation request is the same signing-initiation payload, and BACS-specific beneficiary verification details are covered in the initiation, verification, and get payment details examples.

Request example

This example continues the Faster Payments example above after beneficiary verification has been completed and the payment is ready for confirmation.

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

Response example

{
  "group_header": {
    "message_identification": "97fec32d3f0db402",
    "creation_date_time": "2026-04-22T12:05:31.834792973Z",
    "http_code": 200
  },
  "response": {
    "_id": "7f8bb693-47b3-40b8-8db3-f923aa6429f8",
    "template_id": "FASTER_PAYMENT_UK",
    "external_id": "f1642fe6-ebdf-4f71-b5ab-14dd88da3a80",
    "amount": "1.0",
    "requested_execution_date": "2026-04-23",
    "execution_date": "2026-04-23",
    "currency": "GBP",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "own message"
    },
    "creditor": {
      "account": {
        "value": "30466971"
      },
      "name": "Name",
      "bank": {
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "bank_code": "445566",
        "country": "GB",
        "name": "Example Bank"
      },
      "message": "message"
    },
    "payment_status": "AUTHORIZATION_PENDING",
    "payment_status_reason": "info.payment.confirmation_in_progress",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/confirm"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8"
      }
    ]
  }
}

In this example, Open Banking has created a confirmation signing order and the payment is now waiting for PSU action in Nordea App.

After the PSU successfully signs, the payment will transition to:

PAYMENT_ACCEPTED

From there, the payment is processed automatically and will later move to a final state such as PAYMENT_EXECUTED or PAYMENT_REJECTED.

The TPP should poll GET /uk/v1/payments/{payment_id} until the payment reaches the next state.

Cancel Payment examples

PUT /uk/v1/payments/{payment_id}/cancel

This endpoint is used to cancel a payment that is still cancellable. This example uses the CHAPS payment created in Create Payment examples.

For BACS payments, cancellation follows the same process as Faster Payments and CHAPS when the payment is in a cancellable state.

Request example

This example assumes that the CHAPS payment has not yet been executed and is still eligible for cancellation.

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

Response example

{
  "group_header": {
    "message_identification": "6373625f227b7289",
    "creation_date_time": "2026-04-22T12:09:21.678957383Z",
    "http_code": 200
  },
  "response": {
    "_id": "1a9485ba-aee8-4412-bfcb-a5be44779964",
    "template_id": "CHAPS_PAYMENT_UK",
    "external_id": "0c2efdc7-a2cb-4df8-9d4e-dc3bfc508e71",
    "amount": "285000.00",
    "requested_execution_date": "2026-04-23",
    "execution_date": "2026-04-23",
    "currency": "GBP",
    "debtor": {
      "account": {
        "value": "3046697121",
        "currency": "GBP"
      },
      "own_reference": "Property completion"
    },
    "creditor": {
      "account": {
        "value": "87654321"
      },
      "name": "Smith and Co Client Account",
      "address": {
        "line_1": "22 Market Road",
        "line_2": "Manchester"
      },
      "bank": {
        "address": {
          "line_1": "22 Market Road",
          "line_2": "Manchester"
        },
        "bank_code": "445566",
        "country": "GB",
        "name": "Example Bank"
      },
      "message": "Completion funds. Ref 2026-041. Client A",
      "srd_roll_number": "MATTER7788"
    },
    "payment_status": "AUTHORIZATION_PENDING",
    "payment_status_reason": "info.payment.cancellation_in_progress",
    "_links": [
      {
        "rel": "self",
        "href": "/uk/v1/payments/1a9485ba-aee8-4412-bfcb-a5be44779964/cancel"
      },
      {
        "rel": "details",
        "href": "/uk/v1/payments/1a9485ba-aee8-4412-bfcb-a5be44779964"
      }
    ]
  }
}

In this example, Open Banking has created a cancellation signing order and the payment is now waiting for PSU action in Nordea App.

After the PSU successfully signs, the payment will normally transition to:

PAYMENT_CANCELLED

If the payment has already been executed before the cancellation is completed, cancellation will fail and the payment may instead remain in PAYMENT_EXECUTED.

The TPP should poll GET /uk/v1/payments/{payment_id} until the payment reaches its final state.

Payment List examples

GET /corporate/v3/payments This endpoint returns a list of payments filtered by the specified query parameters.

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}
requested_execution_from_date: {requested_execution_from_date}
requested_execution_to_date: {requested_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": "4f8c4dc934a6ca20",
    "creation_date_time": "2026-04-22T12:15:45.858435217Z",
    "http_code": 200
  },
  "response": {
    "payments": [
      {
        "_id": "1a9485ba-aee8-4412-bfcb-a5be44779964",
        "template_id": "CHAPS_PAYMENT_UK",
        "external_id": "0c2efdc7-a2cb-4df8-9d4e-dc3bfc508e71",
        "amount": "285000.00",
        "requested_execution_date": "2026-04-23",
        "execution_date": "2026-04-23",
        "currency": "GBP",
        "debtor": {
          "account": {
            "value": "3046697121",
            "currency": "GBP"
          },
          "own_reference": "Property completion"
        },
        "creditor": {
          "account": {
            "value": "87654321"
          },
          "name": "Smith and Co Client Account",
          "address": {
            "line_1": "22 Market Road",
            "line_2": "Manchester"
          },
          "bank": {
            "address": {
              "line_1": "22 Market Road",
              "line_2": "Manchester"
            },
            "bank_code": "445566",
            "country": "GB",
            "name": "Example Bank"
          },
          "message": "Completion funds. Ref 2026-041. Client A",
          "srd_roll_number": "MATTER7788"
        },
        "payment_status": "PAYMENT_CANCELLED",
        "_links": [
          {
            "rel": "details",
            "href": "/uk/v1/payments/1a9485ba-aee8-4412-bfcb-a5be44779964"
          }
        ]
      },
      {
        "_id": "7f8bb693-47b3-40b8-8db3-f923aa6429f8",
        "template_id": "FASTER_PAYMENT_UK",
        "external_id": "f1642fe6-ebdf-4f71-b5ab-14dd88da3a80",
        "amount": "1.0",
        "requested_execution_date": "2026-04-23",
        "execution_date": "2026-04-23",
        "currency": "GBP",
        "debtor": {
          "account": {
            "value": "3046697121",
            "currency": "GBP"
          },
          "own_reference": "own message"
        },
        "creditor": {
          "account": {
            "value": "30466971"
          },
          "name": "Name",
          "bank": {
            "address": {
              "line_1": "22 Market Road",
              "line_2": "Manchester"
            },
            "bank_code": "445566",
            "country": "GB",
            "name": "Example Bank"
          },
          "message": "message"
        },
        "payment_status": "PAYMENT_ACCEPTED",
        "_links": [
          {
            "rel": "details",
            "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8"
          },
          {
            "rel": "cancel",
            "href": "/uk/v1/payments/7f8bb693-47b3-40b8-8db3-f923aa6429f8/cancel"
          }
        ]
      }
    ],
    "_links": [
      {
        "rel": "first",
        "href": "/uk/v1/payments?execution_from_date=2026-04-23&execution_to_date=2026-04-23&page=1&size=20"
      },
      {
        "rel": "self",
        "href": "/uk/v1/payments?execution_from_date=2026-04-23&execution_to_date=2026-04-23&page=1&size=20"
      },
      {
        "rel": "last",
        "href": "/uk/v1/payments?execution_from_date=2026-04-23&execution_to_date=2026-04-23&page=1&size=20"
      }
    ]
  }
}

{
  "group_header": {
    "message_identification": "947e432885b20fc8",
    "creation_date_time": "2026-07-27T09:22:59.021217542Z",
    "http_code": 200
  },
  "response": {
    "payments": [
      {
        "_id": "6e5d0ba8-f69c-484a-baa9-ff901ac05b64",
        "template_id": "BACS_PAYMENT_UK",
        "external_id": "9e8a3e59-76b1-4b62-a52c-2cd83bb1bfa2",
        "requested_execution_date": "2026-07-29",
        "execution_date": "2026-07-29",
        "debtor": {
          "account": {
            "value": "3046697121",
            "currency": "GBP"
          },
          "own_reference": "BACS-A1-HappyPath"
        },
        "number_of_transactions": 3,
        "control_sum": "250.00",
        "creditors": [
          {
            "account": {
              "value": "12345678"
            },
            "name": "Beneficiary One",
            "bank": {
              "bank_code": "203456"
            },
            "message": "Invoice A1-001",
            "amount": "100.00",
            "beneficiary_verification_status": "REQUIRED"
          },
          {
            "account": {
              "value": "87654321"
            },
            "name": "Beneficiary Two",
            "bank": {
              "bank_code": "203456"
            },
            "message": "Invoice A1-002",
            "amount": "100.00",
            "beneficiary_verification_status": "NOT_REQUIRED"
          },
          {
            "account": {
              "value": "11223344"
            },
            "name": "Beneficiary Three",
            "bank": {
              "bank_code": "203456"
            },
            "message": "Invoice A1-003",
            "amount": "50.00",
            "beneficiary_verification_status": "REQUIRED"
          }
        ],
        "payment_status": "AUTHORIZATION_PENDING",
        "payment_status_reason": "info.payment.verification_in_progress",
        "_links": [
          {
            "rel": "details",
            "href": "/uk/v1/payments/6e5d0ba8-f69c-484a-baa9-ff901ac05b64"
          }
        ]
      }
    ],
    "_links": [
      {
        "rel": "first",
        "href": "/uk/v1/payments?requested_execution_from_date=2026-07-20&created_by_me=true&page=1&size=20"
      },
      {
        "rel": "self",
        "href": "/uk/v1/payments?requested_execution_from_date=2026-07-20&created_by_me=true&page=1&size=20"
      },
      {
        "rel": "last",
        "href": "/uk/v1/payments?requested_execution_from_date=2026-07-20&created_by_me=true&page=1&size=20"
      }
    ]
  }
}

Sandbox Test Data

This section lists the test data available in the sandbox environment for the UK Corporate Payments API.

Agreement and Users

The following agreement has UK payment accounts available. The sandbox provides five users with different payment authorization permissions on every account:

Agreement number: 164301528862

User (PSU login)	Authorization permission	Can initiate & confirm payment?
`11497209006`	`ACT_ALONE`	Yes — can confirm a payment alone
`11497209007`	`TWO_TOGETHER`	Partial — requires a second authorized user to also confirm
`11497209008`	`KEY_IN`	No — view and key-in only, cannot authorize payments
`11497209009`	`VIEW`	No — read-only access
`11497209010`	`NONE`	No — no payment access

Use user 11497209006 (ACT_ALONE) for straightforward single-user payment flow testing. Use users 11497209007 together with another TWO_TOGETHER user for multi-authorization testing.

UK Payment Accounts

All accounts below belong to agreement 164301528862. The retail_number is the 10-digit account number used in the debtor.account.value field when initiating a payment.

IBAN	Retail number (debtor account value)	BBAN	Currency
`GB29NDEA40487846428401`	`3046654287`	`NDEA40487846428401`	`GBP`
`GB09NDEA40487854447654`	`3046796220`	`NDEA40487854447654`	`GBP`
`GB31NDEA40487845059501`	`3046573096`	`NDEA40487845059501`	`GBP`
`GB74NDEA40487806400929`	`3046421846`	`NDEA40487806400929`	`GBP`
`GB17NDEA40487809595389`	`3046433462`	`NDEA40487809595389`	`GBP`
`GB32NDEA40487847590601`	`3046734026`	`NDEA40487847590601`	`GBP`
`GB20NDEA40487807595389`	`3046432615`	`NDEA40487807595389`	`GBP`
`GB71NDEA40487842141506`	`3046458267`	`NDEA40487842141506`	`GBP`
`GB09NDEA40487846750801`	`3046680181`	`NDEA40487846750801`	`GBP`
`GB87NDEA40487843803701`	`3046518162`	`NDEA40487843803701`	`GBP`
`GB04NDEA40487845948701`	`3046622101`	`NDEA40487845948701`	`GBP`
`GB22NDEA40487844725401`	`3046556882`	`NDEA40487844725401`	`GBP`
`GB07NDEA40487846984801`	`3046839296`	`NDEA40487846984801`	`GBP`
`GB98NDEA40487846804101`	`3046684053`	`NDEA40487846804101`	`GBP`
`GB14NDEA40487846039701`	`3046627425`	`NDEA40487846039701`	`GBP`
`GB16NDEA40487846057901`	`3046628030`	`NDEA40487846057901`	`GBP`
`GB54NDEA40487842999001`	`3046492389`	`NDEA40487842999001`	`GBP`
`GB20NDEA40487854447650`	`3046796099`	`NDEA40487854447650`	`GBP`
`GB62NDEA40487844206701`	`3046535828`	`NDEA40487844206701`	`GBP`
`GB50NDEA40487847376101`	`3046719869`	`NDEA40487847376101`	`GBP`
`GB36NDEA40487845987701`	`3046624400`	`NDEA40487845987701`	`GBP`
`GB60NDEA40487846962701`	`3046697000`	`NDEA40487846962701`	`GBP`
`GB31NDEA40487806212456`	`3046421483`	`NDEA40487806212456`	`GBP`
`GB70NDEA40487806595389`	`3046800092`	`NDEA40487806595389`	`GBP`
`GB52NDEA40487846007201`	`3046626215`	`NDEA40487846007201`	`GBP`
`GB35NDEA40487847113501`	`3046707527`	`NDEA40487847113501`	`GBP`
`GB40NDEA40487846780701`	`3046682601`	`NDEA40487846780701`	`GBP`
`GB56NDEA40487847304601`	`3046715997`	`NDEA40487847304601`	`GBP`
`GB40NDEA40487843880401`	`3046811950`	`NDEA40487843880401`	`GBP`
`GB09NDEA40487844859301`	`3046564021`	`NDEA40487844859301`	`GBP`
`GB39NDEA40487846519401`	`3046662031`	`NDEA40487846519401`	`GBP`
`GB79NDEA40487846252901`	`3046641582`	`NDEA40487846252901`	`GBP`
`GB26NDEA40487845644501`	`3046605524`	`NDEA40487845644501`	`GBP`
`GB92NDEA40487806412924`	`3046784241`	`NDEA40487806412924`	`GBP`
`GB74NDEA40487846964001`	`3046697121`	`NDEA40487846964001`	`GBP`
`GB28NDEA40487843771201`	`3046517436`	`NDEA40487843771201`	`GBP`
`GB83NDEA40487847550301`	`3046731485`	`NDEA40487847550301`	`GBP`
`GB56NDEA40487847550302`	`3046731486`	`NDEA40487847550302`	`EUR`
`GB29NDEA40487847550303`	`3046731487`	`NDEA40487847550303`	`USD`
`GB83NDEA40487847550304`	`3046731488`	`NDEA40487847550304`	`SEK`
`GB83NDEA40487847550305`	`3046731489`	`NDEA40487847550305`	`NOK`
`GB83NDEA40487847550306`	`3046731490`	`NDEA40487847550306`	`DKK`
`GB83NDEA40487847550307`	`3046731491`	`NDEA40487847550307`	`CHF`
`GB83NDEA40487847550308`	`3046731492`	`NDEA40487847550308`	`JPY`
`GB83NDEA40487847550309`	`3046731493`	`NDEA40487847550309`	`CAD`
`GB83NDEA40487847550310`	`3046731494`	`NDEA40487847550310`	`AUD`
`GB83NDEA40487847550311`	`3046731495`	`NDEA40487847550311`	`PLN`

All five users listed in Agreement and Users section have access to every account above, each with their respective permission level.

UK Corporate Accounts API v1 Corporate Payments API v3