Skip to content

Commit af7ace6

Browse files
edcablegitbook-bot
edcable
authored and
gitbook-bot
committed
GitBook: [master] one page modified
1 parent 34d7599 commit af7ace6

File tree

1 file changed

+42
-55
lines changed

1 file changed

+42
-55
lines changed

‎payment-hub-ee/overview/accessing-lab-environment.md

+42-55
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,53 @@
11
# Accessing Lab Environment
22

3-
### Overview
3+
## Overview
44

5-
The Mifos Mojaloop Lab Environment consists of a number of a different ways for various stakeholders to access and interact with Mojaloop and a core banking system, Mifos/Fineract, at both an API level and user interface level. Transactions can be initiated directly via API Calls in Postman, an attached simulator or through reference customer-facing mobile apps.
5+
The Mifos Mojaloop Lab Environment consists of a number of a different ways for various stakeholders to access and interact with Mojaloop and a core banking system, Mifos/Fineract, at both an API level and user interface level. Transactions can be initiated directly via API Calls in Postman, an attached simulator or through reference customer-facing mobile apps.
66

7-
The transactions that have been completed can be viewed in a number of ways - as reflected in the core banking system from the perspective of staff of the DFSP, as reflected in a customer-facing mobile wallet or mobile banking app, and from the operational interface for the Payment Hub EE .
7+
The transactions that have been completed can be viewed in a number of ways - as reflected in the core banking system from the perspective of staff of the DFSP, as reflected in a customer-facing mobile wallet or mobile banking app, and from the operational interface for the Payment Hub EE .
88

9-
The Payment Hub provides both the gateway/integration layer with Mojaloop as well as a microservices workflow and orchestration engine. The Payment Hub is accessible via APIs or the operational UI. Access can be provided to the Zeebe engine which powers the Payment Hub, the Zeebe Operate UI would allow the configuration of new workflows which can be extended by building new connectors for other systems or new connectors for other payment systems to test routing transactions across different systems and networks outside of Mifos and/or Mojaloop, generating notifications, etc.
9+
The Payment Hub provides both the gateway/integration layer with Mojaloop as well as a microservices workflow and orchestration engine. The Payment Hub is accessible via APIs or the operational UI. Access can be provided to the Zeebe engine which powers the Payment Hub, the Zeebe Operate UI would allow the configuration of new workflows which can be extended by building new connectors for other systems or new connectors for other payment systems to test routing transactions across different systems and networks outside of Mifos and/or Mojaloop, generating notifications, etc.
1010

11-
Testing via third party and OTT API is also available via a set Open Banking APIs that are published through WS02 API Gateway and integration with the GSMA Mobile Money API.
11+
Testing via third party and OTT API is also available via a set Open Banking APIs that are published through WS02 API Gateway and integration with the GSMA Mobile Money API.
1212

13-
14-
### Core Banking System - Mifos/Fineract
13+
## Core Banking System - Mifos/Fineract
1514

1615
At the core banking system level, our lab environment consists of two generations of our core banking system being deployed:
1716

1817
* Fineract CN \(our next generation cloud-native microservices architecture that still only has limited functionality\) and
1918
* Fineract 1.x \(a very mature and functionally robust core banking platform, especially at the loan level\).
2019

21-
Both generations are accessible at an API level and via the user interface built on Angular. Multi-tenancy is leveraged so on the single instance of Fineract 1.x there are four separate Mifos X tenants set up and configured at the moment. New instances can be configured and deployed for each fintech participant if necessary. There are two tenants created on the Fineract CN instance. Tenants have been named with African wildlife names.
22-
20+
Both generations are accessible at an API level and via the user interface built on Angular. Multi-tenancy is leveraged so on the single instance of Fineract 1.x there are four separate Mifos X tenants set up and configured at the moment. New instances can be configured and deployed for each fintech participant if necessary. There are two tenants created on the Fineract CN instance. Tenants have been named with African wildlife names.
2321

2422
This Google Sheet has full details on accessing all the Fineract instances but here are details for one of the medium tenants:
2523

26-
#### Gorilla Tenant
24+
### Gorilla Tenant
2725

2826
* **Gorilla Tenant API**:
2927
* **Gorilla Tenant Staff User Interface**: [http://gorilla.mifos.io:9002/?baseApiUrl=https://gorilla.mifos.io:8443&tenantIdentifier=tn06](http://gorilla.mifos.io:9002/?baseApiUrl=https://gorilla.mifos.io:8443&tenantIdentifier=tn06)
3028
* Credentials: mifos/password
3129
* Customer ID: InteropMerchant
3230
* Customer MSISDN: 27710306999
3331

34-
This is the interface a staff user would log into to view the transactions that have been reflected on the customer accounts of that DFSP.
35-
36-
37-
Documentation on the specific Fineract APIs is accessible at [https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit\#gid=476821922](https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit#gid=476821922)
32+
This is the interface a staff user would log into to view the transactions that have been reflected on the customer accounts of that DFSP.
3833

34+
Documentation on the specific Fineract APIs is accessible at [https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit\#gid=476821922](https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit#gid=476821922)
3935

40-
### Initiating Transactions
36+
## Initiating Transactions
4137

4238
Transactions via Mojaloop can be initiated in a number of ways.
4339

44-
#### Directly via API Calls through Postman
40+
### Directly via API Calls through Postman
4541

46-
All of the Mojaloop APIs and Payment Hub EE APIs can be tested out across the various system endpoints within Postman. We have compiled these into a collection at <INSERT LINK>.
42+
All of the Mojaloop APIs and Payment Hub EE APIs can be tested out across the various system endpoints within Postman. We have compiled these into a collection at <INSERT LINK>.
4743

44+
### Through ACE Fintech App via Open Banking APIs through WS02 API Gateway App
4845

49-
#### Through ACE Fintech App via Open Banking APIs through WS02 API Gateway App
46+
The Ace Fintech App is a Third Party Provider app that allows a user to log in, get consent from its DFSP to initiate transactions or view account information on its behalf via an Open Banking API. The credentials below are for a TPP, Ace Fintech, on behalf of a customer of the Gorilla Bank.
5047

51-
The Ace Fintech App is a Third Party Provider app that allows a user to log in, get consent from its DFSP to initiate transactions or view account information on its behalf via an Open Banking API. The credentials below are for a TPP, Ace Fintech, on behalf of a customer of the Gorilla Bank.
48+
The [log-in credentials and process](https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit#gid=481267967) are documented below.
5249

53-
The [log-in credentials and process](https://docs.google.com/spreadsheets/d/1b8BRajrpNacFNEH6gGENDVWIGusLc0pGRd6MnKbqTKM/edit#gid=481267967) are documented below.
54-
55-
URL for Ace Fintech App:
50+
URL for Ace Fintech App:
5651

5752
| Acefintech URL | [http://acefintech.mifos.io/](http://acefintech.mifos.io/) | |
5853
| :--- | :--- | :--- |
@@ -61,71 +56,63 @@ URL for Ace Fintech App:
6156

6257
First access the URL and then log in as the app user. Then click the more menu on the right and log with user credentials at Gorilla Bank to authorize consent \(OTP has been simulated through a checkbox\) to be able to initiate transactions.
6358

64-
Through the Ace Fintech app, one should now be able to initiate transfers via Mojaloop via an Open Banking API.
59+
Through the Ace Fintech app, one should now be able to initiate transfers via Mojaloop via an Open Banking API.
6560

66-
#### Through MifosPay Mobile Wallet App
61+
### Through MifosPay Mobile Wallet App
6762

68-
Mifos Pay is a reference mobile wallet application. Below is an APK to download and the log-in credentials for a self-service user which is a customer of the Leopard DFSP instance.
63+
Mifos Pay is a reference mobile wallet application. Below is an APK to download and the log-in credentials for a self-service user which is a customer of the Leopard DFSP instance.
6964

7065
* APK Download
7166
* Credentials
7267

73-
#### Through Mifos Mobile Mobile Banking App
68+
### Through Mifos Mobile Mobile Banking App
7469

7570
Mifos Mobile is a reference mobile banking application. Below is an APK to download and the log-in credentials for a self-service user which is a customer of the Leopard DFSP instance.
7671

7772
* APK Download
7873
* Credentials
7974

80-
8175
Mojaloop APIs are documented at:
8276

83-
Payment Hub APIs are documented at: https://mifos.gitbook.io/docs/payment-hub-ee/overview/payment-hub-apis
84-
Mojaloop API
77+
Payment Hub APIs are documented at: [https://mifos.gitbook.io/docs/payment-hub-ee/overview/payment-hub-apis](https://mifos.gitbook.io/docs/payment-hub-ee/overview/payment-hub-apis)
78+
Mojaloop API
8579

86-
### Viewing Transactions
80+
## Viewing Transactions
8781

88-
#### View Transactions via Mifos X Web App \(Staff\)
82+
### View Transactions via Mifos X Web App \(Staff\)
8983

90-
Log in to the URL above and navigate to a customer and click the customer and then view account and view details of transactions.
84+
Log in to the URL above and navigate to a customer and click the customer and then view account and view details of transactions.
9185

92-
#### View Transactions via Payment Hub EE Operations App
86+
### View Transactions via Payment Hub EE Operations App
9387

94-
This provides the DFSP a view into all transactions going through the switch that they're connected to. One can view and search incoming and outgoing transactions and incoming and outgoing requests to pay.
88+
This provides the DFSP a view into all transactions going through the switch that they're connected to. One can view and search incoming and outgoing transactions and incoming and outgoing requests to pay.
9589

9690
* URL: [http://med-operations-ui.mifos.io/login](http://med-operations-ui.mifos.io/login)
9791
* Gorilla Credentials: mifos/password/tn06
9892

99-
#### View Transactions via Mobile Apps \(Customer\)
93+
### View Transactions via Mobile Apps \(Customer\)
10094

101-
Log into the respective apps and view transaction details or click into a specific account and then view transaction details.
95+
Log into the respective apps and view transaction details or click into a specific account and then view transaction details.
10296

103-
### Payment Hub EE
97+
## Payment Hub EE
10498

105-
#### Configuring New Workflows
99+
### Configuring New Workflows
106100

107101
New workflows routing transactions across different systems can be done through modifying the BPMN diagram and building/adding new connectors. Once the BPMN file is created in Zeebe Modeler, it needs to get deployed to the Zeebe cluster of the related environment.
108102

109-
#### Accessing Zeebe Operate
103+
### Accessing Zeebe Operate
110104

111105
To access the Zeebe Operate UI in a Payment Hub EE instance, please follow the below instructions:
112106

113107
* Ensure you have Azure credentials to access the AKS Kubernetes environment
114-
* Use the Azure CLI tools to set up kubernetes access on your local machine, with the following command (example shows the Large env configuration):
115-
```
116-
az aks get-credentials --resource-group dpc-large-dfsp --name large-dfsp
117-
```
118-
and follow the instructions given by the tool. Once this is set up, you can reach the environment from your developer box using `kubectl` or a more sophisticated tool like `k9s` (see https://k9scli.io/)
108+
* Use the Azure CLI tools to set up kubernetes access on your local machine, with the following command \(example shows the Large env configuration\):
109+
110+
```text
111+
az aks get-credentials --resource-group dpc-large-dfsp --name large-dfsp
112+
```
113+
114+
and follow the instructions given by the tool. Once this is set up, you can reach the environment from your developer box using `kubectl` or a more sophisticated tool like `k9s` \(see [https://k9scli.io/](https://k9scli.io/)\)
115+
119116
* Port-forward the zeebe-operate Service's port `8080` to your local machine, using `kubectl` or `k9s`
120-
* Access Zeebe Operate's local endpoint at http://localhost:8080/. The default credentials are `demo/demo`.
121-
122-
#### Accessing Fineract
123-
124-
To access the user interface of the For fineract, highlight login urls, show APIs, this where pepl
125-
126-
Payment Hub show
127-
Mojaloopday can initiate transactions via set of scripts, through these apps or could connect simulator, can them see balance reflected in UIs, show the APIs
128-
Can log into operations app to see transactions or can get access to zeebe, show the APIs for payment hub, can connect other systems, can connect other payment networks, can change the information that gets returned back.
129-
Initiating transactions, ace fintech app log in and request info or do transfer
130-
Show apk of other do app and log in and corresponding accounMobile wallet, mobile banking app, reference also having fintech app
117+
* Access Zeebe Operate's local endpoint at [http://localhost:8080/](http://localhost:8080/). The default credentials are `demo/demo`.
131118

0 commit comments

Comments
 (0)