Retreiving Financial Accounts, Transactions and Balances

Once a consent is valid you can start fetching account data, including accounts, balances, and transactions from cash, cards, loans, savings, and securities accounts.

1. Request an API bearer token

Create a JWT with srv: "ais/tpp" and send it to /token.

{
  "sub": "user-123",
  "iss": "tpp/{TPP_ID}",
  "srv": "ais/tpp",
  "iat": 1728986260,
  "exp": 1728986860,
  "ttl": 600
}

curl --location --request POST 'https://{ENVIRONMENT}.feezback.cloud/token' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "token": "{GENERATED_JWT_TOKEN}"
  }'

The returned bearer token is valid for 600 seconds.

2. Fetch financial data

Use the bearer token to call Feezback's Aggregate Data API.

The userId path parameter is always:

{sub}@{tpp_id}

Use the correct TPP API host:

Send the bearer token in the Authorization header on each request:

curl --location 'https://{TPP_API_HOST}/tpp/v1/users/USERID/accounts' \
  --header 'Authorization: Bearer {ACCESS_TOKEN}' \
  --header 'X-Tpp-Id: {TPP_ID}'

Before fetching data, confirm the consent is valid — see consent status updates.

Recommended data retrieval flow

1. Confirm the user has a valid consent.
2. List the financial resources covered by the consent: accounts, cards, loans, savings, or securities.
3. Use each returned resourceId as the resource path parameter for detail, balance, and transaction calls.
   1. Fetch balances when the consent includes BALANCES.
   2. Fetch transactions when the consent includes TRANSACTIONS.
4. Use v2 transaction endpoints when you need:
   1. Pagination.
   2. Unique transactionId for CACC transactions.
      
      *recommended when you want to avoid transactions processing duplications.

Account data endpoints

Card data endpoints

Savings, loans, and securities endpoints

V2 transaction endpoints

Use V2 endpoints when you need:

• Paginated transaction reads from the dedicated typed transaction tables.
• Unique transactionId value
  
  *recommended when you want to avoid transactions processing duplications.

Pagination differs between v1 and v2:

Data deletion endpoint

Use the data deletion tasks endpoint to retrieve information about data scheduled for deletion.

GET /tpp/v1/data-deletion-tasks

Filter by deletionReason (expirationDeletion | consentDeletion), userId, page, pageSize, and taskStatus (RECEIVED | FAILED) when needed.

Common headers

Common query parameters

Response codes