Payment Manager
Introduction
Payment Manager is an interface to connect to a downstream payment system, like a payment hub. A program must have exactly one Payment Manager. Different programs may have different Payment Managers configured.
Payment Batches
In each program cycle, the payment transactions can be done in batches. There could be several reasons for batching the payments. The transaction limits may be imposed by payment switch, DFSP or any other entity in the payments chain. The payment batches and batch size are configured in the Payment Manager.
Payment Manager types
Each program's payment configuration is specific to the payment system employed by that program. Hence there is a dedicated Payment Manager type for each payment system. OpenG2P supports these Payment Manager types:
Payment Hub EE Payment Managers
This manager uses Mifos Payment Hub for cash disbursements. To learn the steps to create this Payment Manager type, click here.
Default Payment Managers
This is the default manager created automatically. This is the simplest of all Payment Managers and provides configuration for domain filters and batch size. Program administrators can use this manager to create payment batches. Since it does not have any payment system configuration, it cannot send payments to the beneficiaries. To learn the steps to create this Payment Manager, click here.
Payment Interoperability Layer Payment Managers
This Payment Manager is created for payment through Mojaloop. Mojaloop can send payments for a variety of payment modes such as mobile wallets, IBAN, bank account numbers, registrant ID, etc. To learn the steps to create this Payment Manager, click here.
Cash Payment Managers
This Payment Manager is used to record cash payments instead of sending payments to the beneficiary's account/wallet. Once the entitlement is approved, the program administrator provides an entitlement voucher to the beneficiary. Once the cash is disbursed at a bank, cash counter, or disbursement centre, the program administrator records the payment as paid. To learn the steps to configure this Payment Manager, click here.
File Payment Managers
This Payment Manager is used mainly to send a list of approved beneficiary entitlements to the bank or a similar disbursing authority. The list is sent in a PDF/CSV file. The program administrator can also configure a template and QR code for this file. To learn the steps to configure this Payment Manager, click here.
Payment Manager configuration
Configuring a Payment Manager in a program is a two-step process.
Create a Payment Manager type
The program administrator must create exactly one Payment Manager according to the payment system/process employed by the program. To learn more about this step, click here.
Add the Payment Manager to a program
The program administrator needs to add the Payment Manager created in the first step to the program. To learn more about this step, click here.
Sending payments
Once the Payment Manager is configured, the program administrator navigates to the program cycles and performs these actions:
Validate entitlements: This step will validate all the entitlements that were approved. To learn more about the approval process, click here.
Prepare payments: This step will create the payment batches based on the batch size.
Send payments: This step will send the payments to the beneficiary accounts/wallets. To learn more about these steps, click here.
The figure below shows the cycle view with the action buttons to perform the three tasks described above.
How-To Guides:
Create Payment Hub EE Payment Manager
Create Payment Interoperability Layer Payment Manager
Create Default Payment Manager
Last updated
