Skip to content

Commit dd9a2b3

Browse files
tapaswenipathakgitbook-bot
tapaswenipathak
authored and
gitbook-bot
committedJul 12, 2022
GitBook: [#61] [Test Edit][GitBook] Fixes a few grammatical errors on https://mifos.gitbook.io/docs/ 
1 parent 4a6cb11 commit dd9a2b3

File tree

5 files changed

+31
-35
lines changed

5 files changed

+31
-35
lines changed
 

‎mifos-mojaloop/mifos-wallet-solution.md

+4-6
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ description: >-
66

77
# Mifos Wallet Solution
88

9-
The Mifos Wallet solution makes use of Fineract 1.x as the core back end banking system with the Mifos User Interface\(s\) for operations and consumer interactions.
9+
The Mifos Wallet solution uses Fineract 1.x as the core back end banking system with the Mifos User Interface(s) for operations and consumer interactions.
1010

11-
As of Sept 9th, 2020, _Fineract 1.4_ \(a derivative of the Mifos X code contributed to Apache Software Foundation\) source code is available here --> [https://github.com/apache/fineract/tree/1.4.0](https://github.com/apache/fineract/tree/1.4.0). A full lab environment with demo servers to test these systems is available; please request access via the [mifos.slack.com channel](https://join.slack.com/t/mifos/shared_invite/zt-frxj913a-VdiJRCNp6M6S9is_Aa2Ikg). Fineract is a core banking system, with APIs that cover accounts, transactions, customers, products, interest schemes, cron jobs, users, authentication, etc.
11+
As of Sept 9th, 2020, _Fineract 1.4_ (a derivative of the Mifos X code contributed to Apache Software Foundation) source code is available here --> [https://github.com/apache/fineract/tree/1.4.0](https://github.com/apache/fineract/tree/1.4.0). A complete lab environment with demo servers to test these systems is available; please request access via the [mifos.slack.com channel](https://join.slack.com/t/mifos/shared\_invite/zt-frxj913a-VdiJRCNp6M6S9is\_Aa2Ikg). Fineract is a core banking system, with APIs that cover accounts, transactions, customers, products, interest schemes, cron jobs, users, authentication, etc.
1212

13-
The _Mifos Payment Hub EE_ is used to connect to Mojaloop \(payments switch\) for inbound and outbound transactions. Payment Hub EE implements the Mojaloop API and maps to the [Fineract API](https://demo.fineract.dev/fineract-provider/swagger-ui/index.html). See \[payment-hub-ee\] for more info.
13+
The _Mifos Payment Hub EE_ is used to connect to Mojaloop (payments switch) for inbound and outbound transactions. Payment Hub EE implements the Mojaloop API and maps to the [Fineract API](https://demo.fineract.dev/fineract-provider/swagger-ui/index.html). See \[payment-hub-ee] for more info.
1414

15-
The [Mifos Wallet App](https://github.com/openMF/mobile-wallet) connects via a WSO2 API Gateway. This is under development and appropriate for prototyping. Again, contact the [mifos.slack.com](https://join.slack.com/t/mifos/shared_invite/zt-frxj913a-VdiJRCNp6M6S9is_Aa2Ikg) channel for access and configuration. Source code is available here:
15+
The [Mifos Wallet App](https://github.com/openMF/mobile-wallet) connects via a WSO2 API Gateway. This is under development and appropriate for prototyping. Again, contact the [mifos.slack.com](https://join.slack.com/t/mifos/shared\_invite/zt-frxj913a-VdiJRCNp6M6S9is\_Aa2Ikg) channel for access and configuration. The Source code is available here:
1616

1717
The API gateway built on WSO2 allows for new channel development on top of the Payment Hub EE.
1818

@@ -24,5 +24,3 @@ The API gateway built on WSO2 allows for new channel development on top of the P
2424

2525

2626

27-
28-

‎payment-hub-ee/business-overview/using-payment-hub-ee.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,6 @@
22

33
## Evaluating Payment Hub EE and Mojaloop
44

5-
### **Lab Environment **
5+
### **Lab Environment** 
66

7-
Our Payment Hub Lab Environment, hosted on Azure, provides a and provides a real-world environment consisting of multiple DFSPs connecting to a Mojaloop switch with operational web and mobile user interfaces for staff and clients to test and demonstrate transaction flows across the system. It demonstrates the multi-tenancy of both Mifos and the Payment Hub, consisting of the Payment Hub hosted in three different deployment topologies (small, medium, large). Both generations of Mifos are deployed and configured to represent different operational methodologies of DFSPs - MFI, SACCO, etc. In addition, our mobile wallet channel app is fully configured and deployed along with an WS02 API gateway and Open Banking API layer to simulate and facilitate participation of third party fintechs.
7+
Our Payment Hub Lab Environment, hosted on Azure,provides a real-world environment consisting of multiple DFSPs connecting to a Mojaloop switch with operational web and mobile user interfaces for staff and clients to test and demonstrate transaction flows across the system. It demonstrates the multi-tenancy of both Mifos and the Payment Hub, consisting of the Payment Hub hosted in three different deployment topologies (small, medium, large). Both generations of Mifos are deployed and configured to represent different operational methodologies of DFSPs - MFI, SACCO, etc. In addition, our mobile wallet channel app is fully configured and deployed along with an WS02 API gateway and Open Banking API layer to simulate and facilitate participation of third party fintechs.

‎payment-hub-ee/overview/bulk-disbursement-integration.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616

1717
![](../../.gitbook/assets/Screen\_Shot\_2021-07-06\_at\_9.25.06\_PM.png)
1818

19-
* Bulk processing designed as a separate system within Payment Hub EE architecture supporting
19+
* Bulk processing is designed as a separate system within Payment Hub EE architecture supporting
2020
* File integrity check with MD5/SHA256 checksum when received in channel connector
2121
* Bulk processor
2222
* Parse CSV file
@@ -26,12 +26,12 @@
2626
* Workflow Initiator
2727
* Pull messages from Kafka payments topic
2828
* Format data based on payment connector requirements
29-
* Initiate payment type specific workflows
29+
* Initiate payment type-specific workflows
3030

3131
**Key Considerations:**
3232

3333
* Kafka provides auto partitioning within topics based on throughput and data
34-
* Scalable and fault tolerant system provided by multi-cluster setup
34+
* Scalable and fault-tolerant system provided by the multi-cluster setup
3535
* Handle backpressure from Zeebe and throttle workflow initiation
3636
* Kafka will act as a buffer in this case
3737
* Advantageous when Zeebe is overloaded
@@ -41,15 +41,15 @@
4141
* Provide a visual workflow representation with Zeebe
4242
* Stores every state for workflow instances
4343
* Timers surviving node failures without interruptions
44-
* Using an efficient, high performance binary protocol (gRPC) for the clients to connect and receive tasks for execution
44+
* Using an efficient, high-performance binary protocol (gRPC) for the clients to connect and receive tasks for execution
4545
* Retry mechanism on the entire subprocess
4646
* But retry is already in place within subprocesses
4747
* Unified payment architecture
4848
* Easy integration with AMS if payment staging requires it
49-
* Incase of beneficiary creation during transfer
49+
* In case of beneficiary creation during transfer
5050
* Using Raft for log replication
51-
* Kafka has write ahead log replication as well.
52-
* Easy integration of pre and post transaction workers
51+
* Kafka to write ahead log replication as well.
52+
* Easy integration of pre and post-transaction workers
5353
* Such as bulk notification
5454

5555
#### References:

‎payment-hub-ee/overview/example.md

+16-17
Original file line numberDiff line numberDiff line change
@@ -1,46 +1,45 @@
11
# Example
22

3-
Payer Process
3+
Payer Process:
44

55

66

7-
![Payer Process BPMN model](https://lh6.googleusercontent.com/sev-9FQkXg0cILYGphQ-VBr7_hENrAJiIxe9hBHEwdLwBrm8VxGTSrAXwIzMehbq8aBOD7x_PtsPXBdHmosRJXJ6_55Aq3wROprMtKhRM9VOucGCMUVZDMtSQXUZ6uusfWv_yy1fcQ4)
7+
![Payer Process BPMN model](https://lh6.googleusercontent.com/sev-9FQkXg0cILYGphQ-VBr7\_hENrAJiIxe9hBHEwdLwBrm8VxGTSrAXwIzMehbq8aBOD7x\_PtsPXBdHmosRJXJ6\_55Aq3wROprMtKhRM9VOucGCMUVZDMtSQXUZ6uusfWv\_yy1fcQ4)
88

99

1010

11-
![Payer Process in Production](https://lh3.googleusercontent.com/Y_xsK_dkw4czwUCMn9kjaAraHS7_fVdsqEEg1xa2gVMPhwzzkD-U32b9LPiYRS0JkkB5WTCQsn_HAAqxhn98o513Z1hdBv-7_VGwPXde43Z4RdomXBGy5bMW65sG28KSy1tPPqbUulg)
11+
![Payer Process in Production](https://lh3.googleusercontent.com/Y\_xsK\_dkw4czwUCMn9kjaAraHS7\_fVdsqEEg1xa2gVMPhwzzkD-U32b9LPiYRS0JkkB5WTCQsn\_HAAqxhn98o513Z1hdBv-7\_VGwPXde43Z4RdomXBGy5bMW65sG28KSy1tPPqbUulg)
1212

13+
Payee Process:
1314

15+
![Payee Process BPMN](https://lh4.googleusercontent.com/NHseMrqkb7YThmLJj\_SqkJSzVL0lYLD3Q8QkPHUcDs4-aZsYmw6ScK0aQJvljsJz\_Ucu2WLCYHKG7G1jQmZ6v9Y0w3KKgHXTTbpsqqKM1nbhXKG7oD6lAQ6uPzFcJyFen9131AZNAmI)
1416

15-
![Payee Process BPMN](https://lh4.googleusercontent.com/NHseMrqkb7YThmLJj_SqkJSzVL0lYLD3Q8QkPHUcDs4-aZsYmw6ScK0aQJvljsJz_Ucu2WLCYHKG7G1jQmZ6v9Y0w3KKgHXTTbpsqqKM1nbhXKG7oD6lAQ6uPzFcJyFen9131AZNAmI)
1617

1718

19+
![Payee Process in Production](https://lh5.googleusercontent.com/OKdt8QryE\_eL3DSALEdFBV6WLI9E4fVrYvrSzeOC9lTRFpvSXaY9rKgZEaucTcJsRmOqREQigjOTdNbEMnWH\_J9D\_EC8oEbOlPA8ASR1sJFHmuKea4LAGlvLZ6sby6YmvnpBWXguXUY)
1820

19-
![Payee Process in Production](https://lh5.googleusercontent.com/OKdt8QryE_eL3DSALEdFBV6WLI9E4fVrYvrSzeOC9lTRFpvSXaY9rKgZEaucTcJsRmOqREQigjOTdNbEMnWH_J9D_EC8oEbOlPA8ASR1sJFHmuKea4LAGlvLZ6sby6YmvnpBWXguXUY)
21+
Operations UI:
2022

23+
![Operations UI - Summary page](https://lh5.googleusercontent.com/Af92k2hpcEgwLP1f\_cSEdXaodDHMO0BdlQS8IZecWpAyUbXhHYGDqfTGHkNooQX6MJfYw3CqRzPL0dMCdckF2PqNzjDjFV5ICS1GXGySOLzMdcx1ztFRPBW9LOdNKWqWP7rbrIhV5wY)
2124

2225

23-
![Operations UI - Summary page](https://lh5.googleusercontent.com/Af92k2hpcEgwLP1f_cSEdXaodDHMO0BdlQS8IZecWpAyUbXhHYGDqfTGHkNooQX6MJfYw3CqRzPL0dMCdckF2PqNzjDjFV5ICS1GXGySOLzMdcx1ztFRPBW9LOdNKWqWP7rbrIhV5wY)
2426

27+
![Operations UI - Transaction Details](https://lh4.googleusercontent.com/eSCLwMnEXMoAjetRFwDWER4f5LdXb-hei2TZwVcQqMncm8HHSZq1Wpb20WineK33jxjNA8FreXHEysbTyPd-ZYHDQHJAd1FI6zxMVCdr3J0rQFGlqY\_VGzGg3B-ETvm1Y1nWT\_kkLcc)
2528

29+
Transaction details:
2630

27-
![Operations UI - Transaction Details](https://lh4.googleusercontent.com/eSCLwMnEXMoAjetRFwDWER4f5LdXb-hei2TZwVcQqMncm8HHSZq1Wpb20WineK33jxjNA8FreXHEysbTyPd-ZYHDQHJAd1FI6zxMVCdr3J0rQFGlqY_VGzGg3B-ETvm1Y1nWT_kkLcc)
28-
29-
30-
31-
![Transaction details on Kibana](https://lh3.googleusercontent.com/HcxyB5_cWitQqookCV4HySNNJ0LZc-rtbuvngXSzt2wdbWJRPLa7Y1GzXShYFL8Dzw0RL0bfuvOI9TTu_5XS2XzVsh3FfBEL-tgWphgezJvLfvXYM4w6dkBaL7zqUeFgN96P6Ux7LR8)
32-
33-
![Payee Party Lookup BPMN](../../.gitbook/assets/image%20%283%29.png)
31+
![Transaction details on Kibana](https://lh3.googleusercontent.com/HcxyB5\_cWitQqookCV4HySNNJ0LZc-rtbuvngXSzt2wdbWJRPLa7Y1GzXShYFL8Dzw0RL0bfuvOI9TTu\_5XS2XzVsh3FfBEL-tgWphgezJvLfvXYM4w6dkBaL7zqUeFgN96P6Ux7LR8)
3432

33+
![Payee Party Lookup BPMN](<../../.gitbook/assets/image (3).png>)
3534

35+
Payer and Payee Transaction Request:
3636

3737
![Payer Transaction Request BPMN](../../.gitbook/assets/image.png)
3838

3939

4040

41-
![Payee Transaction Request BPMN](../../.gitbook/assets/image%20%282%29.png)
42-
43-
41+
![Payee Transaction Request BPMN](<../../.gitbook/assets/image (2).png>)
4442

45-
![Party Registration BPMN](../../.gitbook/assets/image%20%281%29.png)
43+
Party Registration:
4644

45+
![Party Registration BPMN](<../../.gitbook/assets/image (1).png>)

‎payment-hub-ee/overview/secondary-identifier-storage-and-registration.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
# Secondary Identifier Storage and Registration
22

3-
Documentation on the storage of secondary identifier \(e.g. MSISDN\) in Fineract
3+
Documentation on the storage of secondary identifiers (e.g. MSISDN) in Fineract
44

55
Document the registration API and process
66

7-
Retrieve the secondary identifier \(MSISDN\) for an account \(identified by external account ID\) API
8-
7+
Retrieve the secondary identifier (MSISDN) for an account (identified by external account ID) API&#x20;

0 commit comments

Comments
 (0)