View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011699 | Taler | taler-rust | public | 2026-07-30 09:00 | 2026-08-29 19:07 |
| Reporter | Antoine A | Assigned To | Antoine A | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | none | Severity | feature | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Target Version | post-2.0 | ||||
| Summary | 0011699: taler-wise: balance statement pagination | ||||
| Description | The Wise API endpoint https://docs.wise.com/api-reference/balance-statement offers very few guarantees regarding pagination. We have a start timestamp and an end timestamp. It is unclear whether these timestamps refer to booking or valuation, and whether new transactions will always appear with a more recent timestamp. We should always retrieve at transactions from the last day, if not more. This needs to be tested with non-instant SEPA transfers. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-30 09:00 | Antoine A | New Issue | |
| 2026-07-30 09:00 | Antoine A | Status | new => assigned |
| 2026-07-30 09:00 | Antoine A | Assigned To | => Antoine A |
| 2026-07-30 09:01 | Antoine A | Description Updated | |
| 2026-08-29 19:07 | Florian Dold | Target Version | => post-2.0 |
| 2026-11-03 07:21 | Status | assigned => implementing |