2023-02-28 - Technical Implementation Meeting - G2P Use Cases

 Date

Feb 28, 2023

 Participants

  • @Kibuuka, Arnold

  • @Soban Najam

  • @Mauree, Venkatesen

  • David Higgins

  • Ali Mesia

  • @Vikash Madduri

  • @Satyajit Suri

  • @Manoj VM

  • @Oscar Correia

  • Vijay Vujjini

  • @Avik Ganguly

  • @Ed Cable

  • @PSRAMKUMAR

  • Sasi Kumar

  • @Sawaya Elie

  • @Esther Ogunjimi

 

Meeting recording: Payments BB Technical Implementation Meeting - G2P Use Cases-20230228_175934-Meeting Recording.mp4

 Goals

  • Update from MiFOS on updated G2P Use Case and APIs Doc

  • Comments on G2P Use Case Documents

  • Next Steps

  • P2G use cases

 Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

  1. Update from MiFOS on updated G2P Use Case and APIs Doc

@Soban Najam

  • Presented the the main components of the payments BB implementation (the mapper, voucher engine and the payment hub)

  • @RamKumar added that it would be importatant point out the exteranal elements that will connect to the voucher engine.

  • Ramkumar also requested if there is an API that can be used to check the status of a voucher, whether redeemed

  • Vijay clarified that the mapper would be seeded at the ime of onboarding

  • @Soban pointed out that bulk payments and single G2P paymements will take the same form as they require the same request parameters.

  • @Soban Najamadded that for bulk payments, the file will be parsed as JSON string from the requesting BB

  • @Soban added that there are APIs to check vouchers in query.

  • @Mauree, Venkatesen added that they are security requirements that need to complied to as well and that the functional requirements in the payments BB specifications need to checked and validated that they have been implemented in the document.

  • @Oscar also pointed out that they are security issues that relate with updating the aaccount mapper.

  • @Soban Najam added that the update on the mapper is instaciated by the registration building block and that will happen after the beneficiary has consented - the due deligence is handled by the registration building block and done after a proof of life.

  • The account mapper will be used to validate eligibility agents, merchants, enrolling of the beneficiary ID and payment modality.

  • The voucher engine also identifies the different states that a voucher can contain, 5 states have been defines for the vouchers (inactive, active, utilised, canceled and expired).

  • The payment hub componet communicates with the payment system or the FSPs and handles bulk account validation, bulk requests and batch credit confirmatons.

  • Comments on G2P Use Case Documents



 Action items

Clearing and settlement will be discussed in another meeting
@Oscar Correia and @Soban Najam to have another call on vouchers
Other building blocks to review and provide comments to the G2P use cases document ([Legacy] G2P use cases V1.1)
Follow-up call on Friday to discuss the P2G cases - proposed for Friday at 11 AM CET

 Decisions

Unresolved issues that involve other building blocks can be reviewed by the technical committee.
MIFOs to start working on the P2G use cases.