Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

During regular refresh jobs, we request only new transactions from a bank (since last downloaded). However, some 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 process updated transactions correctly:

a) When calling transactions list with updatedFrom filter (preffered way), you can receive updated transaction. If there is any transaction with ID that it already stored in your database, you should update the given transaction.

...

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 lastUpdated than the newest transactions (because these were stored bit earlier).

Therefore, if you do not want to get historical transactions, you may combine parameter like bookingDateFrom (or valueDateFrom depending on your use case) together with updatedFrom. Once there is new transaction on the account bit later after the whole initial transaction download is finished, updatedFrom parameter should be sufficient.

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

...