Payments

MVP will cover only Government to people (G2P) payment type with the minimum required dataset. G2P payment principles are available here: 4 Key Digital Functionalities | bb-payments

We will concentrate on one payment method: UC-P-USCT-001: Payment - Unconditional Social Cash Transfer (bank payments)

Initial plan for involving actual BB candidates:

• Payment processing handled by MIFOS BB https://mifos.gitbook.io/docs/payment-hub-ee/overview/example

• Payment request initiated by OpenIMIS BB (see Registration | Normal course of registration in MVP )

Normal course of payment in MVP

Normal course is a description on what happens if the event is triggered and pre-conditions are met.

Preconditions:

• Information mediator IM is installed to the sandbox and enabled

• The mocked database acting as the bank IFMS ( Integrated Financial Management Information System) is created

• The beneficiary has registered to the the SRIS (Social Registry Information System),

  • beneficiary banc account number is added

• The beneficiary has been verified and enrolled into a program in BOMS

  • benefit amount is calculated

  • payment due date for the payment is filled

The payment BB assumes, that all identification, registration and enrollment is done by external systems and are compliant.

If Mifos product will be used as Payment BB we need to predefine data for:

• client is created (Create payer Client)

• product is created (saving Product)

• client account is created (savings accounts)

Trigger

Payment is triggered, when the message from IM is extracted and payment due date is reached

Data input and output

Below is described the minimum necessary dataset for USCT MVP.

NB! All additional backround data that is required for minimum data exchange between BB (RequestID, ResponseID, SourceBBID,….etc.) should be included to the input and output (marked as ……)