Page Comparison

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

• Comments to the document here G2P use cases V1.1