poolpay/model/Transaction.py
0 → 100644
+71
−0
Loading
This mainly keeps and formats a few variables relevant to transactions. Not all transactions have a partner and purpose (in my case, specifically, the "Jahresabschluss" has neither of those, but is at least indicated by a different `posting_text`). As the transactions from FinTS come without any ID, the only way to deduplicate them is by checking if we already have a transaction with the exact same data, and then call that a duplicate (which is not always true, technically, you could run the same transaction twice in a row; e.g., if you want to make two payments in short sequence, and there would be no difference). We also add navigatability in both directions using SQL Alchemy