Skip to main content
Skip table of contents

Labelling Service Use Cases

Introduction

Labeling transaction use cases are mostly about learning more about the customer or finding out if a product might be of interest to a customer.

Information you can get from the transactions with the Labelling Service:

  • Labels to have a context for the transaction

  • Customer number, if the transaction contains a contract from a known company

  • Contract numbers, if the transaction contains a contract from a known company

  • Overdraft information from purposes of known Banks from settlement transactions

  • Chargeback amount, if the transaction contains a chargeback and additional information about the original amount and costs

The following use cases are examples to make them more “plastic”.

Banks

Use Case Bank-01: Bank wants to show labels on the transactions to give them a context

Actors

  • Bank

  • User

Systems

  • Online-Banking

  • finAPI Labelling Service

Goals

  • Adding labels to all transactions to give them context for the user

  • Users can search for labels to find transactions much easier

  • Present the transactions in a chart for better overview

Preconditions

  • User was logged in to the Online-Banking

Flow

  • The Online-Banking is after the login updating the transactions

    • If there are new transactions, the Online-Banking calls the finAPI Labelling Service to get the labels

    • After the labels are retrieved, they are saved to the transactions in the Online-Banking database

  • The user is navigating to the transaction overview

    • All displayed transactions have small labels under them

  • If the user clicks on the search, a dialog will be shown with form elements to select from the available labels and add them to a search

    • If the user now searches, all label-relevant transactions are displayed by a filter

  • A chart with the amounts of the labels (income and spending) can also be displayed to give the user a better insight into the current cash flow.

Use Case Bank-02: Bank wants to offer a loan and has to search for loans in its own transactions of the user

Actors

  • Bank

  • User

Systems

  • Online-Banking

  • finAPI Labelling Service

Goals

  • Find out, if the user already has some loans in the transactions of the account from the bank to allow automated loan applications

Preconditions

  • User was logged in to the Online-Banking

Flow

  • The Online-Banking is after the login updating the transactions

    • If there are new transactions, the Online-Banking calls the finAPI Labelling Service to get the labels

    • After the labels are retrieved, they are saved to the transactions in the Online-Banking database

  • The user is navigating to the loan application in the Online-Banking

  • The Bank loads all transactions, labelled with LOANANDINTEREST and calculates the monthly costs for the last 3 months as a basis for loan liabilities of the user

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.