Elisiário Couto 13e92ccd34 fix(api): resolve duplicate transactions with composite key migration ...

- Migrate transactions table to use (accountId, transactionId) composite primary key
- Replace unstable internalTransactionId with stable bank-provided transactionId
- Update persistence logic to use INSERT OR REPLACE for automatic conflict resolution
- Maintain API compatibility by preserving internalTransactionId field
- Update tests to match new transaction processing format

This resolves the issue where GoCardless returns different internalTransactionId
values for the same transaction across sync operations, causing duplicates.

2025-09-10 20:00:43 +01:00

34 KiB

Raw Blame History

View Raw