Transactions
DateTo - parameter
End Booking DateTime should be in UTC format.
We recommend filling the
dateTovalue five minutes prior to the current date and time, because it takes some time for the transactions to be available in the system.
Search queries based on Last Transaction Timestamp
You can construct search queries using dateFrom and dateTo based on the timestamp of the last retrieved transaction, with dateFrom set to the previous transaction timestamp plus 1 nanosecond.
Here is an example:
| Time | Search query | Last transaction has timestamp |
|---|---|---|
| 08:00 | dateFrom=2026-02-22T06:00:00.000001Z dateTo=2026-02-22T08:00:00.000000Z | 07:00:00.000000 |
| 09:00 | dateFrom=2026-02-22T07:00:00.000001Z dateTo=2026-02-22T09:00:00.000000Z | 08:00:00.000000 |
| 10:00 | dateFrom=2026-02-22T08:00:00.000001Z dateTo=2026-02-22T10:00:00.000000Z | 09:15:00.000000 |
| 11:00 | dateFrom=2026-02-22T09:15:00.000001Z dateTo=2026-02-22T11:00:00.000000Z | no new transaction |
| 12:00 | dateFrom=2026-02-22T09:15:00.000001Z dateTo=2026-02-22T12:00:00.000000Z | 11:43:00.000000 |
The bookingDate and raboBookingDateTime are provided in GMT (UTC). When processing timestamps, ensure proper time zone conversion is applied.
Step 1 - Retrieve account-id
Endpoint:
Read Account ListGET /payments/insight/accounts
Purpose: Before making a request to balance endpoint, you must obtain the account-id by using the Read Account List endpoint of the Business Account Insight - Accounts API.
Step 2 - Retrieve transaction data
Endpoint:
Read Transactions GET accounts/{account-id}/transactions
Purpose: This endpoint helps you retrieve the transactions of a specific account.
Download API Specification
Updated about 23 hours ago