2024-07-15¶
Participants¶
- Victor Blomqvist
- Ling Zhang
- Shakib Loveimi
- Zakarya Ali
- Andy Kaminski
- Gudmundur Hilmarsson
Manage idempotency in Ledger¶
If managed tx/Galileo/Lithic retry requests multiple times, current ledger would not have any issue with the balance, but would write transactions multiple times.
Requester usually has an idempotency property (lithic: request token / galileo: msg event id / managed transaction service: owner resource).
Action¶
- Create a new column in TransactionCore table (external_(event)_id?)
Implement Auth request logic in Lithic¶
Ling shared many questions:
- BAI missing (asked lithic how to get it https://majority.slack.com/archives/C07423MUSBE/p1721055601127549)
- Problems linked to ATM fees
- move ATM management logic to transaction service?
- for ATM transactions, do we call Risk or Ledger first?
- concurrency issue in Lithic / Galileo?
Actions¶
- create spreadsheet to list down values we send to Risk with Galileo and to compare with what we get from Lithic
- sync with Bank Product team to map deny code reason to lithic reasons
Manage differences between Ledger and Reporting¶
Add pending balance to ledger DB¶
As the only use cases for pending balance today are ACH and Checks, we will revisit / start implementing this feature when we take care of ACH for lithic
Open questions
- should we keep ledger balance table in transaction service?
- when to move balance checks from transaction db to ledger?