May 4, 2023 Technical Committee Meeting Note
Attendees
@David Higgins @Satyajit Suri @Rachel Lawson (Unlicensed) @Damian Borowiecki (Deactivated) @Aleksander Reitsakas @Ingmar Vali @Kibuuka, Arnold @Nico Lueck @Mauree, Venkatesen @Meelis Zujev (Deactivated) Nyoman Ribeka @Sarah Farooqi @Steve Conrad @Taylor Downs @Valeria Tafoya @Wes Brown
Agenda | Presenter | Duration | Discussion |
Review pending action items | @Esther Ogunjimi | 10 minutes
| https://govstack-global.atlassian.net/browse/TECH-654
|
Status update | BB Leads @Meelis Zujev (Deactivated) @Steve Conrad @Tarek Rashed | 45 minutes
| Scrum standup-style (what we did this week; plans for next week; blockers/pain points and open/unresolved questions?
https://govstack-global.atlassian.net/browse/TECH-615 https://govstack-global.atlassian.net/browse/TECH-657
Please let Steve and Wes know when making any changes to the 1.0 spaces.
|
Payment BB expectation | @Kibuuka, Arnold | 10 minutes
| To align with other BBs on areas of alignments Cross cutting requirements - clarifications Steve - what information is needed to store the account mapper? Do we want to store the actual account information? What financial service provider will be used? Is the account mapper required to store the financial address or just the address of the FSP? Vijay - It is the intention not to keep the foundational ID in the mapper but in the functional ID. However, the functional ID cannot be used with the FSP. In situation where there is switch, there will be oracle that will map the financial address to what is already pre-existing; no information will be required from the user but the information will be directly from Oracle. In case where the switch is not available, the user will be requested to enter the information directly. All information is stored in tokenised form. Satya - How much of the implementation is MiFos specific? Can we pick out actual components and have different DPG for payments or the Oracle or the FSP or the switch and still try to assemble a payments BB going forward? How does GS payment BB retain it originality and still be able to have MiFos and other DPGs. Vijay - the account mapper will be custom developed for payment BB. The oracle will be Mojaloop and for switch stimulation. MiFos will be used for the voucher engine, payment server and payment hub. All these has been customised according to GS payment BB requirements. So, the API that's being exposed need to comply with APIs for payment hub. Arnold - The original components in the payments building are logical components of the payments hub. Ingmar - When moving information via Information Mediator, will the tokens be put together with the messages? Alek - This is up to how the APIs are designed
|
Concept of adaptor (contd) | @Steve Conrad | 15 minutes
|
|
Meeting recording