Flow description

Step 1: Authorize User's Accounts Consent

Authorizing access to client's personal banking data follows OAuth 2.0 Authorization Code Grant flow.

  1. This substep depends on the Application usage type.
    1. Final consumer: in case you are using Premium API as a Final consumer, you can avoid this substep and continue with number 2.
    2. TPP: in case you are using Premium API as a TPP, you have to create a consent with a specific consentId by making a POST.../v1/consents request. ConsentId will be used in an authorization call in the substep number 2. You have to paste the consentId to the scope parameter after value and colon (e.g. PREMIUM_AIS:2d5d8c-1d5fd8d-2x36d5-2d1g5g). Please note that it is not possible to test the functionality of consents in a Sandbox environment, therefore read the documentation regarding its usage carefully.
  2. Your application initiates the flow by directing user browser to the authorization endpoint. Initiation is carried out by making a GET.../auth/oauth/v2/authorize request (using /premium/sandbox or /premium/production as base URL).
  3. The bank authenticates user and establishes whether the user grants or denies your access request.
  4. Assuming user grants access, the bank server redirects the user browser to the result screen where the authorization code is displayed, or back to your application using the redirection URI provided during your application registration. In the latter case, the redirection URI includes an authorization code.
  5. Your application requests an access token from the bank server's token endpoint by including the authorization code received in the previous step. The authorization code exchange is carried out by making a POST.../auth/oauth/v2/token request.
  6. The bank server authenticates your application, validates the authorization code, and ensures that the redirection URI received matches the URI used to redirect your application in step 3. If valid, the bank server responds back with the access token and refresh token. Issued access token and refresh token expire after 90 days, due to required legislative 90 day re-authorization that is needed.

Token validity

Issued token can be revoked by user or after time period e.g. 180 days. In this case the bank server responses with HTTP 401 Unauthorized to your API call.

Step 2: Get Consented Accounts List

  1. Your application can initiate GET /v2/accounts request with valid access token.
  2. The bank server validates access token and returns consented accounts list.
  3. Record the accountId parameter, since it is used as input for the other API methods.

Step 3: Get Account Information and Balances

  1. To provide user with detail information about account your application initiates GET.../v2/accounts/{account-id} request with valid access token.
  2. The bank server validates access token and returns account's detail and balances.

Step 4: Get Account Transactions History

  1. Your application requests account transaction history by GET.../v2/accounts/{account-id}/transactions with valid access token.
  2. The bank server validates access token and returns a page with account's transactions.


Your application can provide a paginated response for transactions history that returns multiple transaction records. For a paginated responses, please ensure that the number of transaction records on a page (value of pageSize request parameter) are within reasonable limits.

Step 5: Refresh Expired Access Token

When the access token obtained through the authorization code grant expires, your application should attempt to get a new access and refresh token by calling POST.../auth/oauth/v2/token. For more information see Section 6 Refreshing an Access Token in of the OAuth 2.0 specification. If your application fails to get the access token by using a refresh token, your application would have to get your client to initiate a fresh authorization code grant using an existing consent