Open Banking Data
Algoan Products need Open Banking data in input in order to compute and give you insights and/or a score. These data can be obtained through an Account Information Service Provider (AISP, or more commonly an aggregator).
There are two ways to obtain and input these data to the APIs :
- Bring your own data : you already have Open Banking Data from an AISP. If we support your AISP, you can directly send the data with its format. Otherwise, you have to adapt them to Algoan input format.
- Use Algoan “Transaction Data” : integrate Bank Data in your existing customer journey and easily fetch your customer’s Open Banking data to ease the integration of Algoan’s Credit Decisioning product portfolio.
If you just want to test our APIs with fake data, you can download them here and follow the instructions in this page
Parameters
Here is the list all required and optional parameters defined in the Open Banking data to generate an analysis and explains why we need them.
Required parameters
List of required parameters to generate an Analysis.
Accounts
Account represents an end-user financial bank account.
| Properties | Reason |
|---|---|
balance | We use this property to create the daily balances of the accounts included in the analysis. |
balanceDate | Similar to the balance, this property is essential in the creation of the daily account balances. |
bank | We require at least bank.name as we use a combination of information to detect duplicated accounts in the request. |
currency | Our models are based on the local currency of each country. Therefore, this property is essential to avoid incoherent results. |
type | The account type is important in the detection of standard user behavior. For example, we require at least one CHECKING account to be present in order to create the analysis. |
usage | Our algorithms can only accept personal accounts. |
Transactions
Transaction represents a record of money in/out of an Account.
| Properties | Reason |
|---|---|
currency | Our models are created based on the local currency of each country. Therefore, this property is essential to avoid incoherent results. |
dates | With the exception of CHECKING accounts, our API accepts either of the types of dated below. |
dates.debitedAt | Transaction’s debit date. It's a required parameter for CHECKING accounts. |
dates.bookedAt | Transaction's date when the payment took place. |
description | Our algorithms need the transaction label in order to categorize it. |
amount | The amount is also important for our algorithms. Especially for the step called "clustering", which is the process of grouping transactions that have similar numerical values and further improve the categorization. Refer to the Categorization and Clustering page. |
Optional parameters
These parameters are not required to generate an analysis. However, it can be useful in certain cases.
| Properties | Reason |
|---|---|
| format | If you have integrated Powens, Linxo Connect or Tink on your side, you can create an analysis with their raw data. Please see the section Aggregator Raw Data for information. |
| parameters | You can use this parameter to disable one of our our products (Score or Credit Insights) or use the balance date as reference date of the analysis. |
| owners | The owner name is important in the detection of internal transfers. |
| number, iban, bic, name | These properties are also important to detect duplicated accounts. |
| All remaining properties | All remaining properties can be use purely for monitoring and tracking purposes. |