Flow Configurations
Last updated
Was this helpful?
Last updated
Was this helpful?
Flow configurations (Business Process Modeling Notation) are broadly categorized into the following categories (some of which are overlapping) :-
Mock Flows - Simulates various events like account lookup, quotations, hold/deposit/withdraw funds, transfers with callbacks. This allows demonstration of Payment Hub without external dependencies being live and configured as per use case flows.
- This doesn't include AMS workers as Payment BB is not a switch/payment schema participant where it can directly interact with AMS.
- This is the Mojaloop transfer flow with AMS workers mocked out.
- This is the Mojaloop transfer flow with AMS workers mocked out and account lookup working with Identity Account Mapper integrated with ML Account Lookup service.
- This has mock transfer workers and real AMS Fineract connector workers.
Switch (Mojaloop) flows - These are P2P flows which are often embedded within G2P flows. These demonstrate disbursement to multiple payee DFSPIDs; i.e. multilateral clearing. This includes payee-side flows for account lookup, quotation and accepting transfers.
- This is the payer side of ML P2P flow with payee account lookup, quotation request, transfer, hold/release and booking of funds.
Voucher flows - Budget check, redemption and payment flows.
Mobile Money (GSMA) flows - These are configurations built as per of GSMA Mobile Money APIs. This includes configurations for use case flows of P2P, International Remittance, BillPay and Account APIs.
Collection implementation flows - These are inbound transfer (Customer initiated C2B/C2G) and outbound transfer request (Business/Gov initiated C2B/C2G) flows. This involves MMP specific schemes such as MPesa and MTN.
P2G Flows -
Bulk Processing Flows - This includes core (product) bulk processing flows and implementation specific bulk connector flows where debulking itself is in batch mode.
- After Bulk Processor debulks to Bulk Connector which consumes mock PH Batch Transfer API specifications. Can be configured to point to live payer FSP APIs if payer FSP is using PH/GovStack/GSMA API specifications.
Miscellaneous - Performance testing related closed loop configurations.