/ics/v3/card-accounts/{id}

Beta: This endpoint is currently in beta and subject to change.

Returns card account data for the card account ID given as an endpoint parameter.
The card account ID must first be retrieved via the Get Card Accounts call.

This API will return a 1426 error if consent is required.
API consumption is allowed only 4 times maximum per day per session as per PSD2 compliance.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The card account ID returned from the Get Card Accounts call.

Query Params
string
enum
required

The customer type for the request.

  • PERSONAL: personal card accounts
  • BUSINESS: business card accounts
Allowed:
Headers
string
required

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

string
required

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

string
required

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.

string

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".

string

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.
string

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.

string

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

string

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.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json