# Target Users of Payment Hub EE

Payment Hub EE is primarily intended for DFSPs to connect to and effectively participate in L1-aligned payment systems like Mojaloop. It provides an open source production-ready tool to directly connect to Mojaloop. 

Likewise shared service providers, aggregators, and integrators providing core banking services and/or Mojaloop integration services will be a key user as they can leverage the multi-tenancy and scalability of the Payment Hub to provide a connection to multiple DFSPs.

## Current Mojaloop Use Cases Supported

With the Mojaloop connector that ships with Payment Hub EE, the following use cases are supported:

* Peer to Peer Transfer via MSISDN
* Merchant Proximity Payment via QR Code 
* Merchant Request to Pay (Payee-initiated transfer)
* Registration of Secondary Identifier to an Account
* Operation UI Monitoring and Actions
  * Incoming and outgoing transfers
  * Incoming and outgoing request to pay
  * Secondary identifier registration
  * Refund of incoming transfer
  * Manual Override

## How is Payment Hub EE Currently Being Used

### **Connection for GSMA mobile money APIs**

Point of Integration with Mobile Money API for real-time synchronization with mobile money transactions. Work is underway to integrate with the GSMA mobile money API standard as a reference implementation to support real-time synchronization of mobile money transactions affecting loan and savings accounts and Fineract and facilitate being able to initiate transactions via mobile money from the Mifos web and mobile interfaces. Integration with this standard OTT API for mobile money will serve as the blueprint for other mobile money connectors. 

* Efforts are underway in the community to build Payment Hub EE connectors for MTN Uganda and Safaricom/M-Pesa in Kenya. 

### **Connection to other Real-time Payment Systems**

A number of partners are working on deploying the payment hub to provide a seamless point of integration with their local real-time payments system by building an additional connector into the Payment Hub EE. In Mexico, efforts are ongoing to build a connector to SPEI. Partners in Canada are exploring building an Interac connector and partners in Europe are exploring building a SEPA connector. Connection to other real-time payment systems like SEPA, SPEI, etc.

#### Tier 1 DFSPs

* Robust Performance 
* Deployment Flexibility 
* Ease of Connecting Operational Controls 
* Seamless Channel Integration
* Core Banking System
* Agnostic 
* Highly configurable workflow engine 
* Extensible via connectors 
* Ready to customize and extend 
* Vendor-agnostic 
* Operational Control Center

#### **Fintechs**

* Ease of Connection 
* Rapid Innovation 
* Sandbox 
* API Standardization 
* Use Case Prototyping
* OS Reference Apps 
* Interactive Lab Environment 
* End to End OS Stack for DFS 
* Open Banking API Layer 
* GSMA Mobile Money API support

#### **Regulators**

* Transparency & Visibility 
* More input into Fraud Detection 
* Velocity of Cash
* DFSP-level fraud monitoring 
* Visibility into on-us transactions 
* Generate regulatory reports 
* Consistency of data 
* User Access for regulators


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mifos.gitbook.io/docs/payment-hub-ee/business-overview/target-users-of-payment-hub-ee.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.