Reference:
Corporate Accounts API - details
Corporate Accounts - API reference
Q:
Should CONFIRMED transaction status be treated as the final and definitive state of a transaction?
A:
Two statuses should be interpreted as final: CONFIRMED and BILLED. Booked transactions will be returned with status BILLED.
Note: transactions with RESERVED status are preliminarily booked transactions — in other words, transactions that are not booked yet.
Q:
Is transaction_id field guaranteed to remain unchanged over time?
A:
After a transaction has been batch booked, the transaction ID remains unchanged.
Q:
Does any SANDBOX accounts have any transactions which can be obtained via the GET /transactions call?
A:
Yes, such accounts exist and can be collected from endpoints : account_list, account_details or filter_accounts. Please make sure that you do not hit empty date range by checking value latest_transaction_booking_date .
Q:
Why does calling the sandbox endpoint:
GET /corporate/v3/accounts/SE30167700413-CHF/transactions?dateFrom=2025-03-01&dateTo=2025-03-31
result in no transactions, despite the account's having latest_transaction_booking_date: 2025-03-31?
A:
Please see the proper construction of the date range:
GET /corporate/v3/accounts/SE30167700413-CHF/transactions?from_date=2025-03-01&to_date=2025-03-31
Q:
A new customer is creating consent for private users with access to all PSD2 accounts. The user is a guardian or trustee with access to the relevant accounts. Could selecting all accounts cause the error: "code": "error.token.invalid", "description": "HOUSEHOLD token is not supported here. Please check url.", when using your corporate endpoint?
"response": {
"content": {
"error": {
"request": {
"url": "/corporate/v3/accounts?size=50&page=1"
},
"failures": [
{
"code": "error.token.invalid",
"description": "HOUSEHOLD token is not supported here. Please check url."
}
]
},
"group_header": {
"http_code": 401,
"creation_date_time": "2026-07-15T09:35:35.509664195Z",
"message_identification": "206170563537e4d215"
A:
The error indicates that a household (private) token was used to invoke the Corporate Accounts API. Corporate endpoints support only corporate tokens. If the PSU is acting as a guardian or trustee, a household token may be issued; however, that token is not valid for Corporate APIs. We recommend verifying that the customer is using the appropriate authorization flow and corresponding API family (Personal/PSD2 or Corporate) for the PSU being authenticated.