Bank Account

Get a single bank account

Returns a single bank account for the PSU. Read more about bank accounts in the Glossary

get/psu/{psuId}/bank-account/{bankAccountId}

Request

  • Base URL: https://bankapidemo.svea.com
  • URL: https://bankapidemo.svea.com/psu/{psuId}/bank-account/{bankAccountId}
  • Auth: Bearer (a scheme the document does not define)

Path parameters

bankAccountIdstring uuid required
Example:ccf7c77a-8e32-4d9b-8f40-ea446f37d492
psuIdstring uuid required
Example:febbe8f2-bd6b-4e53-89c6-e89ca92ff5ee

Headers

Authorizationstring required
Example:Bearer {BearerToken}
X-Svea-ClientAppstring required

Tenant client app name, version, and optional comment <client-app-name>/<version>(/<comment>)

Example:TENANT-IOS/0.99.0
X-Svea-CorrelationIdstring uuid

The correlationId is a unique identifier value that is attached to requests and messages that allow reference to a particular transaction or event chain. Used to follow transaction information, especially for logging purposes.

Example:21436a05-d62d-4f29-a253-31b3815d148b
X-Svea-SessionIdstring uuid

The sessionId is a unique identifier value for a users session. This identifier should be the same for the entire duration of that users session. Mainly used for logging and troubleshooting purposes.

Example:afe56332-dee2-48b4-ae0b-d694a6174a7e

Response

OK

bankAccountIdstring uuid required
bankAccountNumberstring required
bankAccountTypeClass'transactionAccount' | 'savingsAccount' | 'loanAccount' | 'superAccount' | 'escrowAccount' | 'creditAccount' | 'unknown' required

BankAccountTypeClasses are unique per tenant and can be used for logic in the client.

Note! New bankAccountTypeClasses are created upon request by the tenant and must be supported in the clients before delivery to production.

bankAccountTypeNamestring required

Human readable name of the bankAccountType

bankGiroNumbersstring[] required
bicstring required
capabilitiesstring[] required

Note! New values might be added at any time and should be ignored if the client does not know how to handle them.

clearingNumberstring required
currency'SEK' required
customNamestring nullable required
ibanstring required
overdraftLimitstring nullable required
status'open' | 'blocked' required

Note! New values might be added at any time and it's up to the client how to handle unknown statuses.

Example response

{
  "balance": {
    "available": "107872.99",
    "current": "107872.99",
    "opening": "107872.99"
  },
  "bankAccountId": "ccf7c77a-8e32-4d9b-8f40-ea446f37d492",
  "bankAccountNumber": "3065548",
  "bankAccountTypeClass": "transactionAccount",
  "bankAccountTypeName": "Transaktionskonto",
  "bic": "SVEASESS",
  "capabilities": [
    "payToBGPG"
  ],
  "clearingNumber": "9669",
  "currency": "SEK",
  "customName": "9669-8590276",
  "iban": "SE3296600000096698590276",
  "interestPayable": {
    "accrued": "282.10",
    "lastDate": "2018-12-31",
    "rate": "1.25",
    "total": "-20.45"
  },
  "interestReceivable": {
    "accrued": "0.00",
    "lastDate": "2018-12-31",
    "monthlyRate": "0.00",
    "rate": "0.00",
    "total": "0.00"
  },
  "overdraftLimit": "0.00",
  "status": "open"
}

Changes

No recorded changes to this operation across all 1 revision of this API.