2024-07-02
Participants
- Gertian Mici
- Johan Dahlqvist
- Ling Zhang
- Rasmus Olsson
- Shakib Loveimi
- Zakarya Ali
- Gudmundur Hilmarsson
- Card related identifiers changes affect Wallet, Lithic and Card Data
- As Wallet is the PRNs' owner, Lithic area should handle mapping PRNs to card token
- Card id (information stored today for Galileo cards in CardData) is not a necessary
attribute for our Lithic implementation (except reporting?).
- If we generate PRN as external reference id (rename in hydra).
Decisions
- Wallet should generate PRNs as it is part of its domain (jira ticket)
- PRNs should be generated on the base of a sequential number (CFSB expects this structure for debit card: "692xxxxxxxxx")
- In Wallet table (TODO: find name of the table)
- Store identity column
- Create PRN prefix column
- Store the following attributes
- card token in Lithic and CardData areas (jira ticket)
- PRN in Lithic and Wallet areas
Action items
- list down other ids to consider (program token/id...?)
- Ask Lithic/ CFSB
- Should we create a prn per account and per card?
- How does Lithic map their ids for reporting files?
- In CFSB 'Account card' reporting Card Identifier (CAD) is requested but it is not part of the information shared by lithic (https://docs.lithic.com/reference/getcardbytoken). Why?