Skip to content

2024-07-11

Participants

  • Johan Dahlqvist
  • Ling Zhang
  • Shakib Loveimi
  • Zakarya Ali
  • Andy Kaminski
  • Gudmundur Hilmarsson
  • Gertian Mici
  • Li He

Reissue card flow

ReissueCard method handles three flows
- Reissue (same card / same expiry)
- Renew (same card / diff expiry)
- Replace (lost/stolen > new card/pan (flag in request))

Implementation is different from Galileo but no blockers managing them with Lithic

Update card flows

Given Wallet modularity (clear separation between 'Creating account', 'Creating card'…) changing the flows should not be difficult.

Open questions

  • Is it worth changing Galileo flow (may impact old apps)?
    • To sync with Product

Create Comprehensive Examples for Lithic Transactions and Ledger

Actions

  • Take scenarios created for Galileo integration tests and turn them into Ledger regression tests
  • Add test endpoint in lithic to command Lithic
  • Adapt scenarios to Ledger and Lithic languages (ex: ledger = usd + abs value VS lithic = ?? + positive values)
  • Create excel spreadsheet for PM + testers comprehension

Manage differences between Ledger and Reporting

  • https://majority.atlassian.net/browse/MIB-10777
  • Create a job that checks the followings between Ledger and Reporting
    • difference between rows
    • difference total sum
  • In Ledger solution, create a job that stores to reporting blob storage necessary data to analyze discrepancies

Actions

  • Review best approach with Victor

Open questions

  • How often should the job storing Ledger data run? (every 30 minutes? how to manage k8s jobs running in parallel)

Updates on roadmap

Next steps

Open questions