...
user is online - transactions are refreshed every minute
user is offline - transactions are refreshed 4 times during work hoursevery 30 minutes
for all users - transaction update job is triggered two times twice a day
Manual transaction refresh
...
Detailed endpoint description can be found here: Transaction Refresh Endpoint
Transaction update
...
Some banks might change the transaction data after transaction is processed in bank’s systems. To retrieve these transaction changes, we run transaction update job two times a day. This job retrieves 7 days of transactions history from a bank.When transaction data is changed, we After we receive new transaction data from bank, we update it and set new value for lastUpdated column. To identify changed transactions, you should save lastUpdated timestamp when transaction is retrieved
To get only the fresh transactions (i.e. those which has not been downloaded yet or newly updated ones), good approach is to use updatedFrom query parameter and store the maximum value of lastUpdated field among all downloaded transactions. Next time you should call the endpoint with stored value plus 1 millisecond.
| Info |
|---|
Very first download When the bank account is connected for the first time and |
...
the initial transactions download from the bank towards Everifin is started, the most recent transactions are stored at first. Download and storing of historical ones follows afterwards. As a result, the older transactions can have more recent timestamp in field Therefore, if you do not want to get historical transactions, you may combine parameter like |
Only new transactions
If you do not want to get updates described above, then you can use query parameter createdFrom (ISO timestamp) and store value from field createdAt of latest transaction. Next time you should call the endpoint with stored value plus 1 millisecond.
Get Transaction List
Transaction list for specific bank account can be obtained using the endpoint described in detail here: Bank Account Transactions
...