GitBook: [#58] Payment Hub Integration

Author: Avik Ganguly

.gitbook/assets/Screen_Shot_2021-07-06_at_9.12.10_PM (1).png

@@ -12,8 +12,8 @@
   * [WSO2 authentication endpoint demo application](wso2-1/wso2-authentication-endpoint/README.md)
     * [Config, setup, build, deploy application](wso2-1/wso2-authentication-endpoint/config-setup-build-deploy-application-todo.md)
     * [web.xml](wso2-1/wso2-authentication-endpoint/web.xml.md)
-    * [oauth2\_authz.jsp and oauth2\_consent.jsp](wso2-1/wso2-authentication-endpoint/oauth2_authz.jsp-and-oauth2_consent.jsp.md)
-    * [uk.org.openbanking.v3\_1\_2 package](wso2-1/wso2-authentication-endpoint/uk.org.openbanking.v3_1_2-package.md)
+    * [oauth2\_authz.jsp and oauth2\_consent.jsp](wso2-1/wso2-authentication-endpoint/oauth2\_authz.jsp-and-oauth2\_consent.jsp.md)
+    * [uk.org.openbanking.v3\_1\_2 package](wso2-1/wso2-authentication-endpoint/uk.org.openbanking.v3\_1\_2-package.md)
     * [hu.dpc package](wso2-1/wso2-authentication-endpoint/hu.dpc-package.md)
   * [Signup and subscribe APIs as TPP/FPP](wso2-1/signup-and-subscribe-apis-as-tpp-fpp.md)
   * [How to add new bank user](wso2-1/how-to-add-new-bank-user.md)
@@ -50,8 +50,8 @@
 * [Technical Overview](payment-hub-ee/overview/README.md)
   * [Deployment models](payment-hub-ee/overview/deployment-models.md)
   * [Microservices orchestration - Zeebee](payment-hub-ee/overview/microservices-orchestration-zeebee.md)
-  * [An introductory Zeebe project \(Getting started\)](payment-hub-ee/overview/an-introductory-zeebe-project.md)
-  * [An introductory Zeebe project \(How it works\)](payment-hub-ee/overview/an-introductory-zeebe-project-how-it-works.md)
+  * [An introductory Zeebe project (Getting started)](payment-hub-ee/overview/an-introductory-zeebe-project.md)
+  * [An introductory Zeebe project (How it works)](payment-hub-ee/overview/an-introductory-zeebe-project-how-it-works.md)
   * [Lab environment](payment-hub-ee/overview/lab-environment.md)
   * [Accessing Lab Environment](payment-hub-ee/overview/accessing-lab-environment.md)
   * [Example](payment-hub-ee/overview/example.md)
@@ -62,8 +62,8 @@
   * [Tuning and performance](payment-hub-ee/overview/tuning-and-performance.md)
   * [Payment Process Overview](payment-hub-ee/overview/payment-process-overview.md)
   * [Development Environment](payment-hub-ee/overview/development-environment.md)
+  * [Bulk Disbursement Integration](payment-hub-ee/overview/bulk-disbursement-integration.md)
 
 ## Mifos - Mojaloop
 
 * [Mifos Wallet Solution](mifos-mojaloop/mifos-wallet-solution.md)
-

.gitbook/assets/Screen_Shot_2021-07-06_at_9.12.10_PM.png

@@ -2,21 +2,20 @@
 
 ### Git source repositories
 
-**WSO2 API Gateway helper \(login\)**  
-[https://github.com/openMF/openbanking-api-gateway  
+**WSO2 API Gateway helper (login)**\
+[https://github.com/openMF/openbanking-api-gateway\
 https://github.com/onlyonce/openbanking-api-gateway](https://github.com/onlyonce/openbanking-api-gateway)
 
-**First Party Server**  
-[https://github.com/openMF/openbanking-fpp-server  
+**First Party Server**\
+[https://github.com/openMF/openbanking-fpp-server\
 https://github.com/onlyonce/openbanking-fpp-server](https://github.com/onlyonce/openbanking-fpp-server)
 
-**Third Party Server \(ACEFintech\)**  
-[https://github.com/openMF/openbanking-tpp-server](https://github.com/openMF/openbanking-tpp-server)  
+**Third Party Server (ACEFintech)**\
+****[https://github.com/openMF/openbanking-tpp-server](https://github.com/openMF/openbanking-tpp-server)\
 [https://github.com/onlyonce/openbanking-tpp-server](https://github.com/onlyonce/openbanking-tpp-server)
 
 ### Compile Server App
 
-```text
+```
 > sudo ./mvnw clean package
 ```
-

.gitbook/assets/Screen_Shot_2021-07-06_at_9.25.06_PM (1).png

@@ -2,12 +2,12 @@
 
 ### Git source repositories
 
-**First Party client**  
-[https://github.com/openMF/openbanking-fpp-client  
+**First Party client**\
+[https://github.com/openMF/openbanking-fpp-client\
 https://github.com/onlyonce/openbanking-fpp-client](https://github.com/onlyonce/openbanking-fpp-client)
 
-**Third Party client \(ACEFintech\)**  
-[https://github.com/openMF/openbanking-tpp-client  
+**Third Party client (ACEFintech)**\
+[https://github.com/openMF/openbanking-tpp-client\
 https://github.com/onlyonce/openbanking-tpp-client](https://github.com/onlyonce/openbanking-tpp-client)
 
 
@@ -16,18 +16,17 @@ You must review and modify domain names, OAuth clientID, etc
 
 You can use in **src** folder to find required files:
 
-`grep -R 'elephant' *` 
+`grep -R 'elephant' * `
 
 ### openbanking-fpp-client
 
-`/src/config/server.js  
-/src/utils/externalUrlHelper.js`
+`/src/config/server.js`\
+`/src/utils/externalUrlHelper.js`
 
 
 
 ### Compile WebApp
 
-```text
+```
 > sudo npm run build
 ```
-

.gitbook/assets/Screen_Shot_2021-07-06_at_9.25.06_PM.png

@@ -4,13 +4,13 @@ description: How to configure the adapter to link the API user with Fineract cus
 
 # Setting up the adapter
 
-{% embed url="https://github.com/openMF/openbanking-adapter/blob/master/sources/openbanking-adapter/src/main/resources/db/changelog/sql/01-ob\_tn01\_init.sql" %}
+{% embed url="https://github.com/openMF/openbanking-adapter/blob/master/sources/openbanking-adapter/src/main/resources/db/changelog/sql/01-ob_tn01_init.sql" %}
 
 The above script provides information on the linking of the banking API user with the Fineract user inside the OpenBanking Adapter database.
 
 Example:
 
-```text
+```
 INSERT INTO `user` (`api_user_id`, `psp_user_id`, `active`) VALUES ("lionuser1", "1", 1);
 INSERT INTO `trusted_client` (`client_id`, `created_on`) VALUES ("Jg7O55zbOOlJiSJOaG9Qm5nq7qsa", current_date);
 ```
@@ -19,7 +19,5 @@ api\_user\_id - the user id provided via the API calls
 
 psp\_user\_id - the primary key of the client in the Fineract Database
 
-trusted\_client - required for first party client. The registered client ID assigned on the API gateway. Trusted clients could invoke the API services on behalf of the customer without the additional consent flow. 
-
-
+trusted\_client - required for first party client. The registered client ID assigned on the API gateway. Trusted clients could invoke the API services on behalf of the customer without the additional consent flow. 
 

SUMMARY.md

@@ -1,21 +1,19 @@
 # Business Overview
 
-Payment Hub EE is a gateway and integration layer enabling financial institutions \(DFSPs\) to seamlessly connect to external payment systems and operational control center to manage and monitor the transactions flowing through these systems.
+Payment Hub EE is a gateway and integration layer enabling financial institutions (DFSPs) to seamlessly connect to external payment systems and operational control center to manage and monitor the transactions flowing through these systems.
 
-It is built with a highly extensible and modular architecture, allowing additional connectors to be built for different payment systems, channels, and core banking systems. It is completely open source under the Mozilla Public License 2.0, enabling third parties to extend Payment Hub EE with additional features and/or distribute and support it as a commercial payment integration solution. 
+It is built with a highly extensible and modular architecture, allowing additional connectors to be built for different payment systems, channels, and core banking systems. It is completely open source under the Mozilla Public License 2.0, enabling third parties to extend Payment Hub EE with additional features and/or distribute and support it as a commercial payment integration solution. 
 
 The reference payment system connector is for Mojaloop along with an account management system connector for both generations of Mifos, Fineract 1.x and Fineract CN. For institution using a core banking system built on top of the Mifos and Fineract APIs, the Payment Hub EE is pre-integrated with Mojaloop.
 
 Design and development of the Payment Hub EE was led by the Mifos Initiative and its partner, DPC Consulting with grants provided by DIAL and the Gates Foundation. It is built and delivered as a digital public good for the sector to utilize in connecting to and participating in L1-aligned real-time payment systems.
 
 For those institutions looking to evaluate, adopt, and/or build on Mojaloop, the Payment Hub EE and our hosted lab environment provide both a robust, scalable production-ready solution to connect and an immersive lab environment to explore all use cases
 
-* Tier 1 and 2 institutions can use Payment Hub EE to connect to Mojaloop with their existing core banking system, simply by building an additional connector for their account management system, and are not limited to using Mifos or Fineract. 
+* Tier 1 and 2 institutions can use Payment Hub EE to connect to Mojaloop with their existing core banking system, simply by building an additional connector for their account management system, and are not limited to using Mifos or Fineract. 
 * Tier 3 microfinance institutions and SACCOs that choose to use Mifos as their core banking system have access to an end to end solution in the cloud to digitize and digitally transform by automating operations and connecting to Mojaloop
-* Third party fintechs can easily transact on a Mojaloop switch on behalf of customers of DFSPs by leveraging our Open Banking API layer or the soon to be released PISP API. 
-
-\*\*\*\*
-
-  
+* Third party fintechs can easily transact on a Mojaloop switch on behalf of customers of DFSPs by leveraging our Open Banking API layer or the soon to be released PISP API. 
 
+****
 
+\