API Market documentation

API specific documentation

Changes from the previous version

This is the change log of the Cards API. The top most item is the latest change and the API changes described in it are relative to the version directly below. The current latest version of the API is 5.5.

NOTE: Cards API version 4.3 has been decommissioned. Cards API version 5 is to be used.

Version 5.5

KEY CHANGE: Adding note for transactions date range validation rule.

Notification for Household Cards transactions validation, when optional date range fields are provided in input request.

Version 5.4

KEY CHANGE: Card-ID prefix for Joustorahoitus has changed.

Modified response for /v5/cards - the field Card ID is now with CR2- as prefix for Finnish Flexi-Credit Card.
Modified table containing Sandbox data - adjusted record with Joustorahoitus due to changed data.
Updated example responses.

Version 5.3

KEY CHANGE: The field Transaction ID and Credit Card Number for Finnish Flexi-Credit Card is unavailable.

Modified response for /v5/cards - the field Transaction ID and Credit Card Number is unavailable for Finnish Flexi-Credit Card.
Modified table containing Sandbox data - adjusted record with Joustorahoitus due to missing data.
Updated example responses.

Version 5.2

KEY CHANGE: Removed supported Finance Cards for Sweden (Agrol, Everyday, Forex).

Modified response for /v5/cards - removed examples with new supported Finance Cards products for Sweden (Agrol, Everyday, Forex).
Modified table containing Sandbox data - added records with new supported Finance Cards for Sweden (Agrol, Everyday, Forex).
Updated example responses.

Version 5.1

KEY CHANGE: Added information about new supported Finance Cards for Sweden (Agrol, Everyday, Forex) and new supported Finance Cards for Finland (Flexi-Credit - Joustorahoitus).

Modified response for /v5/cards - added examples with new supported Finance Cards products.
Modified table containing Sandbox data - added records with new supported Finance Cards.
Updated example responses.

Version 5.0

KEY CHANGE: Flattening the structure of card list. The nested structure of parallel cards has been removed. From now on, a card in the card list contains additional information to identify its parent or sibling.

New fields added and used for cards in the card list:

card_ownership_type
parent_card_id
parent_card_available
sibling_cards_ids

Field removed from card on cards list:

parallel_cards

Field removed from card transaction:

masked_credit_card_number

Version 4.3

Enabling sandbox for Norway and Denmark.

Version 4.2

Enabling sandbox for Sweden.

Overview

The Card Accounts API provides real-time consolidated information on a Nordea customer’s credit card(s) and transactions on those cards. For the time being debit card information will be available through the regular account services. The information and hence the operations that the API provides can be divided into the following categories:

Card-related
- Card list
- Card details
Transaction-related
- Transaction history

Because the Card Accounts API provides only information about the card(s) and transaction(s), it is read-only, and therefore this API supports only GET requests.

The Card Accounts API includes three endpoints. The API can be used only to query information, and it, therefore, supports only the GET HTTP method. The three endpoints provided by this API offer:

listing of users’ cards
details of each card and
transaction history for each card.

Card accounts API endpoints

Endpoint	Supported HTTP Methods
`/cards`	GET
`/cards/{CARD_ID}`	GET
`/cards/{CARD_ID}/transactions`	GET

As you can see from the table above, the API endpoints support GET methods.

Access authorization scopes

There are two authorization scopes applicable to the Card Accounts API. These are CARDS_INFORMATION and CARDS_TRANSACTIONS. The following table lists the scopes that are needed for each of the API endpoints.

Endpoint	Required scopes
`/cards`	`CARDS_INFORMATION`
`/cards/`{CARD_ID}	`CARDS_INFORMATION`
`/cards/`{CARD_ID}`/transactions`	`CARDS_INFORMATION`+`CARDS_TRANSACTIONS`

Scope CARDS_TRANSACTIONS can only be requested in combination with scope CARDS_INFORMATION.

You can use the first endpoint to obtain a limited amount of information for all cards to which the user has shared access. See examples section for the full response example.

You can use the second endpoint to query information about a specific card. The information provided contains more information than the one provided through the /cards endpoint. For a comprehensive listing what information will be available in each case, please see section on data model field relevance below. Again, see the examples section for a full response example.

You can use the third endpoint to query the transaction history for a specific card. The response is a transaction listing. The GET method lists the transactions relevant for the card. In all cases this includes the transactions made using the card. For example, in Finland, for cards of main or jointly-liable card holders, the list of transactions also includes the transactions on the credit account such as payment transactions, yearly fee transactions, etc. Like in previous endpoints, see the examples section for the full response example.

In addition to these endpoints, card IDs can be queried by using the assets endpoint from the Access Authorization API. This endpoint returns a list of card IDs for which the user has authorized access among other things. This endpoint is described in the Access Authorization documentation with examples on how to use it, and it also contains response examples.

Data model field relevance

CreditCard - card list

Field name	Principal card FI	Parallel card FI	Principal card SE	Parallel card SE	Principal card NO	Own parallel card NO	Non-own parallel card NO	Principal card DK	Parallel card DK	V5
`id`	Y	Y	Y	Y	Y	Y	Y	Y	Y	Y
`masked_credit_card_number`	Y**	Y**	Y	Y	Y	Y	Y	Y	Y	Y
`masked_debit_card_number`	Y*	Y*	N	N	N	N	N	N	N	Y
`product_name`	Y	Y	Y	Y	Y	Y	Y	Y	Y	Y
`cardholder_name`	N	N	N	N	Y	Y	Y	N	N	Y
`credit_limit`	Y	N	N	N	N	N	N	N	N	Y
`credit_available_balance`	Y	N	N	N	N	N	N	N	N	Y
`card_ownership_type`	N	N	N	N	Y	Y	Y	N	N	Y
`parent_card_id`	N	N	N	N	N	Y	Y	N	N	Y
`parent_card_available`	N	N	N	N	N	Y	Y	N	N	Y
`sibling_cards_ids`	N	N	N	N	N	Y	Y	N	N	Y

*Only available for combination products Nordea Credit, Nordea Gold, Nordea Black, Premium, Nordea Platinum, Finnair, Stockmann

**Not available for Finnish Flexi-credit card (Joustorahoitus)

CreditCard - card details

Field name	Principal card FI	Parallel card FI	Principal card SE	Parallel card SE	Principal card NO	Own parallel card NO	Non-own parallel card NO	Principal card DK	Parallel card DK
`id`	Y	Y	Y	Y	Y	Y	Y	Y	Y
`masked_credit_card_number`	Y**	Y**	Y	Y	Y	Y	Y	Y	Y
`masked_debit_card_number`	Y*	Y*	N	N	N	N	N	N	N
`product_name`	Y	Y	Y	Y	Y	Y	Y	Y	Y
`cardholder_name`	N	N	N	N	Y	Y	Y	N	N
`credit_limit`	Y	N	Y	N	Y	Y	Y	Y	Y
`credit_available_balance`	Y	N	Y	N	Y	Y	Y	Y	Y
`credit_booked_balance`	Y	N	Y	N	Y	Y	Y	Y	Y
`card_monthly_spending_limit`	N	Y	N	N	N	N	N	N	N

*Only available for combination products Nordea Credit, Nordea Gold, Nordea Black, Premium, Nordea Platinum, Finnair, Stockmann

**Not available for Finnish Flexi-credit card (Joustorahoitus)

CreditCard - card transactions list

Field name	Relevance FI	Relevance SE	Relevance NO	Relevance DK	Notes
`id`	Y*	Y	Y	Y	For Sweden, the transaction id is not guaranteed to be unique among transactions, nor is it guaranteed to be the same for one and the same transaction when listed for a main and parallel card. For Finnish Joustorahoitus (Flexi-credit card) this field is unavailable.
`transaction_type`	Y	N	N	N
`masked_credit_card_number`	N	N	N	N
`beneficiary`	Y	Y	Y	Y	Not available for some transactions
`amount`	Y	Y	Y	Y
`currency`	Y	Y	Y	Y
`original_amount`	Y	Y	Y	Y	Only available in case the transaction occurred in a currency different from the card currency
`original_currency`	Y	Y	Y	Y	Only available in case the transaction occurred in a currency different from the card currency
`transaction_date`	Y	Y	Y	Y
`booking_date`	Y	N	Y	Y	Not available for cover reservations

*NOTE: You will receive an access token from Nordea for a period defined by you up to 180 days. You are only entitled to access the payment transactions executed in the limitations below defined per country when using this access token, unless strong customer authentication is performed.

*NOTE: Transactions length per country: Norway: last 3 months (limited by token limitation), Sweden: all transactions (limited by token limitation), Finland: all transactions (limited by token limitation), Denmark: last 12 months (limited by token limitation). If page_size is not is specified in the request then the default size is 10.

*NOTE: When optional fields filtering the transaction date range are provided in request, then the following validation rule is applied: if end_date is given then start_date must also be given and start_date cannot be later then end_date.

*Field is unavailable for Joustorahoitus - Finnish Finance Card.

Card accounts API examples

Here you can find examples on how to use the Card Accounts API endpoints.

Note that in all the examples’ cURL commands, you must change the X-IBM-Client-Id, X-IBM-Client-Secret and Authorization: Bearer header values to the correct ones.

You can find the Client ID, and Client Secret from your app console and the Bearer is generated when you log in.

All of these examples can also be tried out in the API portals’ API Console easily, here we show cURL examples how to make the same API calls which can be performed by the API Console.

Remember to replace the {CARD_ID} URL parameter by correct values in the cURL examples below.

You can get a list of available CARD_IDs along with basic information about the cards by issuing the list cards example below. Please note that the CARD_IDs is not the same thing as a cardNumber. The latter cannot be used as a unique identifier and cannot be communicated though the API in full unmasked form due to Payment Card Industry Data Security Standard (PCI DSS) compliance regulations.

cURL examples

Example: list cards

Following cURL command can be used to fetch the card list after correct Application ID, Client Secret and Access Token are substituted in it:

This endpoint URL has the following form:

GET /v5/cards

This endpoint supports GET HTTP method.

The following cURL can be used to fetch card list from this endpoint.

$ curl -X GET \
  {{API_URL}}/v5/cards/ \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -H 'X-IBM-Client-ID: {{CLIENT_ID}}' \
  -H 'X-IBM-Client-Secret: {{CLIENT_SECRET}}' \
  -H 'cache-control: no-cache'

Here is the response for the query above for Sweden:

{
    "group_header": {
        "message_identification": "huJRJhI3ZA2YUnlb",
        "creation_date_time": "2022-10-31T11:26:13.517763Z",
        "http_code": 200
    },
    "response": {
        "cards": [
            {
                "id": "CS1-a62de472-4524-4bd3-b369-3c42ab273dc0",
                "masked_credit_card_number": "5451 **** **** 9591",
                "product_name": "Nordea Black"
            },
            {
                "id": "CS1-24092d1e-9260-46d4-9217-f25651081008",
                "masked_credit_card_number": "5209 **** **** 8788",
                "product_name": "Nordea Gold"
            },
            {
                "id": "CS1-4a761e0d-c847-4cc8-9811-80ca251ff7d4",
                "masked_credit_card_number": "5520 **** **** 7227",
                "product_name": "Nordea Platinum"
            }
        ]
    }
}

Here is the response for the query above for Finland:

{
    "group_header": {
        "message_identification": "1QNQsx_RXjfEvbDg",
        "creation_date_time": "2022-10-31T10:46:57.838778Z",
        "http_code": 200
    },
    "response": {
        "cards": [
            {
                "id": "CS2-81a30a4f-67df-43d1-9279-24bf9774acc4",
                "masked_credit_card_number": "5521 **** **** 3409",
                "masked_debit_card_number": "5243 **** **** 3560",
                "product_name": "Nordea Platinum (credit)"
            },
            {
                "id": "CS2-9552f206-5de1-43c2-8438-9c6bc09bee97",
                "masked_credit_card_number": "5430 **** **** 8234",
                "product_name": "TUOHI",
                "credit_limit": "3000.00",
                "credit_available_balance": "3000.00"
            },
            {
                "id": "CS1-9bf5b541-a40d-4626-b090-e6faa7037596",
                "masked_credit_card_number": "5228 **** **** 8434",
                "product_name": "Nordea Credit",
                "credit_limit": "10000.00",
                "credit_available_balance": "10000.00"
            },
            {
                "id": "CS2-b141edf1-046f-4fee-b544-7e9c93da8514",
                "masked_credit_card_number": "5430 **** **** 4176",
                "product_name": "Premium",
                "credit_limit": "12000.00",
                "credit_available_balance": "12000.00"
            },
            {
                "id": "CS1-c2a5c660-af1c-4eb3-ac9e-447dfdbbe8c7",
                "masked_credit_card_number": "5225 **** **** 0734",
                "masked_debit_card_number": "5574 **** **** 6364",
                "product_name": "Nordea Gold (credit)",
                "credit_limit": "5000.00",
                "credit_available_balance": "5000.00"
            },
            {
                "id": "CS2-d807fe9e-8d8e-49cd-b80b-d40aa9720b58",
                "masked_credit_card_number": "5430 **** **** 8227",
                "masked_debit_card_number": "5124 **** **** 8229",
                "product_name": "Finnair Plus (credit)",
                "credit_limit": "10000.00",
                "credit_available_balance": "10000.00"
            },
            {
                "id": "CS2-e181cd28-0c12-45db-ae25-92f725f0b5be",
                "masked_credit_card_number": "5430 **** **** 0871",
                "masked_debit_card_number": "5127 **** **** 1203",
                "product_name": "Nordea Gold (credit)"
            },
            {
                "id": "CR2-70ad0a84-937c-eed4-0a6a-6e080d55e485",
                "product_name": "JOUSTORAHOITUS"
            },
            {
                "id": "CS2-7c7e1974-efa1-4222-a7e9-ea2ca42ec2aa",
                "masked_credit_card_number": "5430 **** **** 8228",
                "product_name": "Stockmann",
                "credit_limit": "5000.00",
                "credit_available_balance": "5000.00"
            }
        ]
    }
}

For Norway, other owners’ parallel cards are on the main list, with additional fields to determine the parent, e.g.:

{
    "group_header": {
        "message_identification": "kmsplRqh_SXoMGVN",
        "creation_date_time": "2022-10-31T11:33:49.81416Z",
        "http_code": 200
    },
    "response": {
        "cards": [
            {
                "id": "CS1-d927c5cc-e790-43a7-a249-842663b6f5f8",
                "masked_credit_card_number": "5218 **** **** 7468",
                "product_name": "Nordea Premium",
                "cardholder_name": "MAJA JENSEN",
                "card_ownership_type": "OWN"
            },
            {
                "id": "CS1-0a797fa1-368b-4979-a9e2-7faebb2445c6",
                "masked_credit_card_number": "5218 **** **** 0580",
                "product_name": "Nordea Premium",
                "cardholder_name": "MAJA JENSEN",
                "card_ownership_type": "OWN"
            },
            {
                "id": "CS1-5db1d364-2f05-40bb-b239-438801dcd0bf",
                "masked_credit_card_number": "5218 **** **** 7279",
                "product_name": "Nordea Platinum",
                "cardholder_name": "MAJA JENSEN",
                "card_ownership_type": "OWN"
            },
            {
                "id": "CS1-77bacc33-15b0-49bb-9ff8-5a0ba47b9f05",
                "masked_credit_card_number": "5218 **** **** 9964",
                "product_name": "Nordea Premium",
                "cardholder_name": "LEON STRAND",
                "card_ownership_type": "OWN",
                "parent_card_id": "CS1-d927c5cc-e790-43a7-a249-842663b6f5f8",
                "sibling_cards_ids": [
                    "CS1-803d4350-b1f2-11ea-b3de-0242ac130004"
                ]
            },
            {
                "id": "CS1-803d4350-b1f2-11ea-b3de-0242ac130004",
                "masked_credit_card_number": "5218 **** **** 9855",
                "product_name": "Nordea Premium",
                "cardholder_name": "ANDREAS HANSEN",
                "card_ownership_type": "OWN",
                "parent_card_id": "CS1-d927c5cc-e790-43a7-a249-842663b6f5f8",
                "sibling_cards_ids": [
                    "CS1-77bacc33-15b0-49bb-9ff8-5a0ba47b9f05"
                ]
            }
        ]
    }
}

Here is the response for the query above for Denmark:

{
    "group_header": {
        "message_identification": "Gh-EcSRRShv6oG_z",
        "creation_date_time": "2022-10-31T11:56:42.329342Z",
        "http_code": 200
    },
    "response": {
        "cards": [
            {
                "id": "CS1-b6cd4999-e4b9-4822-8c66-1468a4fda24b",
                "masked_credit_card_number": "5218 **** **** 7468",
                "product_name": "Mastercard Premium"
            },
            {
                "id": "CS1-1c98fabe-e48f-47c3-9fa5-e3aeec22d0a4",
                "masked_credit_card_number": "5218 **** **** 7279",
                "product_name": "Nordea Platinum"
            },
            {
                "id": "CS1-2c2e6c7e-88ec-4742-b848-77b287032bf6",
                "masked_credit_card_number": "5429 **** **** 9302",
                "product_name": "Nordea Credit"
            }
        ]
    }
}

Example: fetch card details

In this example, we fetch card details by CARD_ID which can be found by listing the cards. The endpoint URL has the following form:

GET /v5/cards/{CARD_ID} HTTP/1.1

This endpoint supports GET HTTP method.

Here is cURL command to fetch the card details information:

$ curl -X GET \
  {{API_URL}}/v5/cards/CS2-81a30a4f-67df-43d1-9279-24bf9774acc4 \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -H 'X-IBM-Client-ID: {{CLIENT_ID}}' \
  -H 'X-IBM-Client-Secret: {{CLIENT_SECRET}}' \
  -H 'cache-control: no-cache'

Response:

{
    "group_header": {
        "message_identification": "vwe9lV-ubJl2PtPT",
        "creation_date_time": "2022-10-31T11:28:36.041738Z",
        "http_code": 200
    },
    "response": {
        "id": "CS2-81a30a4f-67df-43d1-9279-24bf9774acc4",
        "masked_credit_card_number": "5521 **** **** 3409",
        "masked_debit_card_number": "5243 **** **** 3560",
        "product_name": "Nordea Platinum (credit)",
        "card_monthly_spending_limit": "1500.00"
    }
}

Example: fetch transaction list

In this example, we fetch card transaction list by CARD_ID which can be found by listing the cards. The endpoint URL has the following form:

GET /v5/cards/{CARD_ID}/transactions HTTP/1.1

This endpoint supports GET HTTP method.

Here is cURL command to fetch the transaction list information:

$ curl -X GET \
  {{API_URL}}/v5/cards/CS2-70ad0a84-937c-eed4-0a6a-6e080d55e485/transactions \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -H 'X-IBM-Client-ID: {{CLIENT_ID}}' \
  -H 'X-IBM-Client-Secret: {{CLIENT_SECRET}}' \
  -H 'cache-control: no-cache'

Response:

{
    "group_header": {
        "message_identification": "lSKZ8cosSaDLaINA",
        "creation_date_time": "2022-10-31T11:36:40.214664Z",
        "http_code": 200
    },
    "response": {
        "transactions": [
            {
                "id": "30e9617f-cc59-487a-bf5a-2687972bdc74",
                "transaction_type": "ONLINE_PURCHASE",
                "beneficiary": "BENEFICIARY 18",
                "amount": "-1.98",
                "currency": "EUR",
                "transaction_date": "2022-10-27",
                "booking_date": "2022-10-27"
            },
            {
                "id": "8fc96c86-5a60-4bb9-bfcc-6b72edc50f45",
                "transaction_type": "ONLINE_PURCHASE",
                "beneficiary": "BENEFICIARY 22",
                "amount": "-0.23",
                "currency": "EUR",
                "transaction_date": "2022-10-27",
                "booking_date": "2022-10-27"
            }
        ]
    }
}

Example: fetch transaction list with continuation key

In this example, we fetch two pages of card transactions list by CARD_ID which can be found by listing the cards. The endpoint URL has the following form:

GET /v5/cards/{CARD_ID}/transactions HTTP/1.1

This endpoint supports GET HTTP method.

Here is cURL command to fetch the first page of transactions:

$ curl -X GET \
  {{API_URL}}/v5/cards/CS2-81a30a4f-67df-43d1-9279-24bf9774acc4/transactions \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -H 'X-IBM-Client-ID: {{CLIENT_ID}}' \
  -H 'X-IBM-Client-Secret: {{CLIENT_SECRET}}' \
  -H 'cache-control: no-cache'

Here is cURL command to fetch the second page of transactions:

$ curl -X GET \
  {{API_URL}}/v5/cards/CS2-81a30a4f-67df-43d1-9279-24bf9774acc4/transactions?continuation_key=2 \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -H 'X-IBM-Client-ID: {{CLIENT_ID}}' \
  -H 'X-IBM-Client-Secret: {{CLIENT_SECRET}}' \
  -H 'cache-control: no-cache'

Response:

{
    "group_header": {
        "message_identification": "udwD5E9loRU",
        "creation_date_time": "2019-11-12T16:20:41.681Z",
        "http_code": 200
    },
    "response": {
        "transactions": [
            "continuation_key": "2",
            {
                "id": "89617de4-f3dc-47fe-8234-c123aeb8c992",
                "transaction_type": "ONLINE_PURCHASE",
                "masked_credit_card_number": "5521 **** **** 3409",
                "beneficiary": "BENEFICIARY 9",
                "amount": "-256.24",
                "currency": "EUR",
                "transaction_date": "2019-11-12",
                "booking_date": "2019-11-12"
            },
            {
                "id": "8244fdf9-cd08-4a3a-bc7a-ec1d9203d488",
                "transaction_type": "ONLINE_PURCHASE",
                "masked_credit_card_number": "5521 **** **** 3409",
                "beneficiary": "BENEFICIARY 30",
                "amount": "-452.03",
                "currency": "EUR",
                "transaction_date": "2019-11-12",
                "booking_date": "2019-11-12"
            },
            {
                "id": "5ba9fa58-84ff-4518-a022-643c2692e2ee",
                "transaction_type": "ONLINE_PURCHASE",
                "masked_credit_card_number": "5521 **** **** 3409",
                "beneficiary": "BENEFICIARY 18",
                "amount": "-41.30",
                "currency": "EUR",
                "transaction_date": "2019-11-12",
                "booking_date": "2019-11-12"
            },
            ...37 more transactions omitted for clarity
        ]
    }
}

Second page response:

{
    "group_header": {
        "message_identification": "BKQgU0vTZp0",
        "creation_date_time": "2019-11-12T16:20:41.681Z",
        "http_code": 200
    },
    "response": {
        "transactions": [
            {
                "id": "2513f0fb-6eda-419e-9546-e48fe590dbbf",
                "transaction_type": "ONLINE_PURCHASE",
                "masked_credit_card_number": "5521 **** **** 3409",
                "beneficiary": "BENEFICIARY 41",
                "amount": "-147.11",
                "currency": "EUR",
                "transaction_date": "2019-11-12",
                "booking_date": "2019-11-12"
            },
            {
                "id": "5f324023-cfce-404c-a6d4-72432eeb59ef",
                "transaction_type": "ONLINE_PURCHASE",
                "masked_credit_card_number": "5521 **** **** 3409",
                "beneficiary": "BENEFICIARY 3",
                "amount": "-41.10",
                "currency": "EUR",
                "transaction_date": "2019-11-12",
                "booking_date": "2019-11-12"
            },
            {
                "id": "d2db4221-d17d-470b-b9c7-2c8b44da0cef",
                "transaction_type": "ONLINE_PURCHASE",
                "masked_credit_card_number": "5521 **** **** 3409",
                "beneficiary": "BENEFICIARY 17",
                "amount": "-3.22",
                "currency": "EUR",
                "transaction_date": "2019-11-12",
                "booking_date": "2019-11-12"
            }
        ]
    }
}

Sandbox data

Cards sandbox only supports a single end user’s view. The cards of that special end user are as listed in the following table. The end user, and respectively, the credit cards, are different for Finland, Sweden, Norway and Denmark.

Country	Card ID	Masked credit card number	Masked debit card number	Product	Card hierarchy level	Ownership	Payment day of month
FI	CS2-81a30a4f-67df-43d1-9279-24bf9774acc4	5521 ** ** 3409	5243 ** ** 3560	Nordea Platinum (credit)	PARALLEL	OWN	30
FI	CS1-9bf5b541-a40d-4626-b090-e6faa7037596	5228 ** ** 8434	N/A	Nordea Credit	MAIN	OWN	1
FI	CS2-b141edf1-046f-4fee-b544-7e9c93da8514	5430 ** ** 4176	N/A	Premium	MAIN	OWN	25
FI	CS1-c2a5c660-af1c-4eb3-ac9e-447dfdbbe8c7	5225 ** ** 0734	5574 ** ** 6364	Nordea Gold (credit)	MAIN	OWN	20
FI	CS2-e181cd28-0c12-45db-ae25-92f725f0b5be	5430 ** ** 0871	5127 ** ** 1203	Nordea Gold (credit)	PARALLEL	OWN	14
FI	CS2-d807fe9e-8d8e-49cd-b80b-d40aa9720b58	5430 ** ** 8227	5124 ** ** 8229	Finnair Plus (credit)	MAIN	OWN	1
FI	CS2-7c7e1974-efa1-4222-a7e9-ea2ca42ec2aa	5430 ** ** 8228	N/A	Stockmann	MAIN	OWN	15
FI	CS2-9552f206-5de1-43c2-8438-9c6bc09bee97	5430 ** ** 8234	N/A	TUOHI	MAIN	OWN	14
FI	CR2-70ad0a84-937c-eed4-0a6a-6e080d55e485	N/A	N/A	Joustorahoitus	MAIN	OWN	1
SE	CS1-24092d1e-9260-46d4-9217-f25651081008	5209 ** ** 8788	N/A	Nordea Gold	PARALLEL	OWN	17
SE	CS1-4a761e0d-c847-4cc8-9811-80ca251ff7d4	5520 ** ** 7227	N/A	Nordea Platinum	MAIN	OWN	25
SE	CS1-a62de472-4524-4bd3-b369-3c42ab273dc0	5451 ** ** 9591	N/A	Nordea Black	MAIN	OWN	4
NO	CS1-0a797fa1-368b-4979-a9e2-7faebb2445c6	5218 ** ** 0580	N/A	Nordea Premium	MAIN	OWN	25
NO	CS1-5db1d364-2f05-40bb-b239-438801dcd0bf	5218 ** ** 7279	N/A	Nordea Platinum	PARALLEL	OWN	17
NO	CS1-d927c5cc-e790-43a7-a249-842663b6f5f8	5218 ** ** 7468	N/A	Nordea Premium	MAIN	OWN	4
NO	CS1-77bacc33-15b0-49bb-9ff8-5a0ba47b9f05	5218 ** ** 9964	N/A	Nordea Premium	PARALLEL	OF ANOTHER OWNER	4
NO	CS1-803d4350-b1f2-11ea-b3de-0242ac130004	5218 ** ** 9855	N/A	Nordea Premium	PARALLEL	OF ANOTHER OWNER	4
DK	CS1-b6cd4999-e4b9-4822-8c66-1468a4fda24b	5218 ** ** 7468	N/A	Mastercard Premium	MAIN	OWN	13
DK	CS1-1c98fabe-e48f-47c3-9fa5-e3aeec22d0a4	5218 ** ** 7279	N/A	Nordea Platinum	PARALLEL	OWN	24
DK	CS1-2c2e6c7e-88ec-4742-b848-77b287032bf6	5429 ** ** 9302	N/A	Nordea Credit	MAIN	OWN	2

Going though the sandbox workflow, access authorization is automatically applied to the respective country-relevant subset of the above cards.

Sandbox transactions

Querying the transactions on a card would generate a new transaction on the card roughly on every fifth call to the operation. In other words, there are 20% chance that a new transaction would be generated on the card on every call to retrieve that card’s transactions.

As the available balance closes in on zero the frequency of new transactions being generated is going to drop substantially.

Once per month, on the payment day mentioned in the last column of the table above, a PAYMENT transaction is going to be generated on the credit account resetting the booked balance on the credit account to zero and the available balance on all cards as well as on the credit account to the value of the card monthly spending limit or the credit limit respectively.

To better simulate production behaviour where transactions become inaccessible after a certain cut-off period, sandbox is only going to serve transactions from the last month. A month is defined as the period from the same date of the previous month up to the present moment.

Dynamic Accounts API v5 Commercial Cards Auth V1