The payment ID returned when the payment was initiated. For batch payments (when paymentProduct is 'batch-transfer'),
this should be the batchId returned from the batch payment initiation.

Specific method used for a payment, which is one of the following values: 'sepa-credit', 'domestic-transfer', 'domestic-scheduled-transfer', 'sepa-scheduled-credit', 'batch-transfer'.

Specifies the category of bank accounts to target for the request.

Accepted values:

• PERSONAL – retail / personal accounts. Default when the parameter is omitted.
• BUSINESS – business accounts, including corporate customers.

Payment endpoints: optional; defaults to PERSONAL when not supplied.

Note: Not all banks support every customer type. Available types are determined by
what each bank exposes through its PSD2 API.

The session Id returned in the response body when this session was created.

String that uniquely identifies a single end-user or device.

The IP Address of the end-user (PSU), which must be provided if the PSU actively requests information.
If this value is not provided, then the call will count towards the number of TPP calls without PSU interaction.
Leave it empty if the end user is not actively requesting account information, such as during automatic background updates.
Provided in either IPv4 or IPv6 format.

Identifier of the end-user, passed as the base64-encoded value of an encrypted string following
the guidelines given in Documentation > Development > Sensitive end-user data.
Depending on the channel of the request, this is the identifier of the person or of the organisation.
This parameter is required if x-psu-id is listed in the bank's requiredPsuHeaders (returned from the /banks
endpoint) for the channel of the request, or if the bank's 'personalIdentificationRequired' is "true".

Additional identifier of the end-user, sent together with x-psu-id to the few banks that need two
identifiers, e.g. the organisation the end-user acts for on business requests, in the format the bank expects.
This parameter is required if x-psu-corporate-id is listed in the bank's requiredPsuHeaders (returned from
the /banks endpoint) for the channel of the request; otherwise it is optional.

Value formats for the banks that use it today:

• Länsförsäkringar: required in addition to x-psu-id, and both are distinct. x-psu-id carries the
  signing person's personnummer (SSN), type SSSN; x-psu-corporate-id carries the organisationsnummer
  (org number), type SON. Confirmed with the bank: both values must be exactly 12 numeric digits — a
  continuous digit string with no hyphens, spaces, letters, or special characters (e.g. 12345678-0987 is
  not valid). Fewer or more than 12 digits fails validation.
• Sparebanken Vest / Folio: required on both consent initiation and every subsequent account/transaction
  read, not only at consent time. Carries the 9-digit Norwegian organisation number. x-psu-id is optional
  here and, if sent, must be the authorising person's national identifier — never the organisation number.
• DNB: send either x-psu-id or x-psu-corporate-id, depending on the customer type. Private (retail)
  customers: send x-psu-id with the 11-digit National Identification Number. Corporate customers: send
  x-psu-corporate-id which is the TX-ident, a DNB-specific ID of 7 characters (2 letters followed by 5 digits)
  that DNB gives the corporate user when they become a DNB corporate client.
• SEB Sweden: for business account reads, picks the company the end-user acts for. Carries either the
  14-digit SEB corporate id or the 10-digit organisation number. Send it only with the business-accounts
  scope: SEB does not accept it for private accounts. Without it, an end-user who is also a private SEB customer
  gets their private accounts.

The host where the request is originating from.
If you are using end to end encryption from our developer portal then this header is mandatory.

The request originating date.
If you are using end to end encryption from our developer portal then this header is mandatory.

The signature header consisting of the signature string
If you are using end to end encryption from our developer portal then this header is mandatory.

A Base64-encoded hash of the request body If you are using end to end encryption from our developer portal then this header is mandatory for all post/put/patch requests.

Content Length