# Participant Feature Matrix

This document provides a comprehensive matrix of different participant types, their requirements, and recommended connectivity solutions for Mojaloop integration.

## Payment Use-Case DFSPs

| Participant Category         | Description                                                                                                                                                                                                                     | Expected Use-Cases                                                                                                                                                                | Infrastructure Requirements for Mojaloop Integration                                                                                                                                                                                                                                | Expected Production SLA                                                                                                                                                                                                                                                                                                                                      | Likely Relevant Regulation              | Special Security Requirements                                                                                                                                                                                  | Solution Options                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Small self-hosting DFSP      | <p>- Small FI with single branch.<br>- Own workstations<br>- Minimal cloud and/or SaaS.</p>                                                                                                                                     | <p>- All moja transfer types except bulk.<br>- Open banking (incl PISP, AISP)</p>                                                                                                 | <p>- Single, cheap, low-end dedicated mini-pc (e.g. RPi)<br>- Single small business broadband Internet connection<br>- Self-hosted core banking system e.g. Mifos<br>- Use OS/Software firewall on same HW node as integration layer.</p>                                           | <p>- "Some" downtime acceptable if hardware fails.<br>- Some schemes may rule out DFSPs that cant meet a certain downtime SLA.<br>- May take many days/weeks to purchase replacement hardware on total failure.<br>- Full Mojaloop security feature set: mTLS, JWS, ILP<br>- ~10 TPS peak sustained for 1 hour.<br>- Max capable of 864000 per 24 hours.</p> | <p>- Record keeping?<br>- Security?</p> | <p>- No need to integrate with existing enterprise security platforms.<br>- Need a fully secure solution "in-a-box" following best industry practice for internet facing services i.e. including firewall.</p> | <p>The “Standard Service Manager” is recommended: A minimal functionality Integration Toolkit-based solution (accessible locally by means of a BI tool). This can be hosted in a basic server, ranging from a mid-specification server for a large MFI or a small bank, right down to a Raspberry PI for the smallest DFSPs with less rigorous service continuity requirements and lower transaction volumes. The Standard Service Manager does not support bulk payments.<br>- Docker compose based integration layer.<br>- Minimal, self-contained integration layer.</p> |
| Low Medium self-hosted DFSP  | <p>- Small FI with one or two branches.<br>- Own "data centre" i.e. broom cupboard with a few servers, router, firewall etc...<br>- Some cloud knowledge and/or SaaS usage.</p>                                                 | <p>- All moja transfer types<br>- Bulk (1000's of transfers).<br>- Open banking (incl PISP, AISP)</p>                                                                             | <p>- Single enterprise grade server hardware node.<br>- Use OS/Software firewall on same HW node as integration layer OR dedicated HW firewall.</p>                                                                                                                                 | <p>- "Some" downtime acceptable if hardware fails.<br>- Some schemes may rule out DFSPs that cant meet a certain downtime SLA.<br>- May take hours to replace hardware on total failure.<br>- Full Mojaloop security feature set: mTLS, JWS, ILP<br>- ~50 TPS peak sustained for 1 hour.</p>                                                                 | <p>- Record keeping?<br>- Security?</p> | <p>- May need integration with existing enterprise security platforms e.g. firewalls, gateways etc...<br>?? needs more clarification</p>                                                                       | <p>The “Enhanced Service Manager” is recommended: Based on the “Standard Service Manager” described earlier, this extends it by adding a Kafka deployment and support for bulk payments. It can be hosted at minimum in a basic server in the DFSP's own "data centre".<br>- Docker compose or docker swarm based integration layer.<br>- Minimal, self-contained integration layer.</p>                                                                                                                                                                                    |
| High Medium self-hosted DFSP | <p>- Small FI with one or two branches.<br>- Own "data centre" i.e. broom cupboard with a few servers, router, firewall etc...<br>- Some cloud knowledge and/or SaaS usage.</p>                                                 | <p>- All moja transfer types<br>- Bulk (1000's of transfers).<br>- Open banking (incl PISP, AISP)</p>                                                                             | - In order to tolerate failure on 1 hardware node 3 or more hardware nodes are required. (2n+1)                                                                                                                                                                                     | <p>- "Some" limited (minutes) downtime acceptable if hardware fails.<br>- Some schemes may rule out DFSPs that cant meet a certain downtime SLA.<br>- Should have spare hardware waiting or very fast replacement services in case of failures.<br>- Full Mojaloop security feature set: mTLS, JWS, ILP<br>- ~50 TPS peak sustained for 1 hour.</p>          | <p>- Record keeping?<br>- Security?</p> | - May need integration with existing enterprise security platforms e.g. firewalls, gateways etc...                                                                                                             | <p>The “Enhanced Service Manager” is recommended: Based on the “Standard Service Manager” described earlier, this extends it by adding a Kafka deployment and support for bulk payments. It can be hosted at minimum in a redundant, multiple server configuration in the DFSP's own "data centre".<br>- Kubernetes based integration layer<br>- Possibly have existing integration technology.</p>                                                                                                                                                                         |
| Large self-hosted DFSP       | <p>- Mature, multi-branch FI with high internal IT capability<br>- Has own data centre and experts to manage systems<br>- Comfortable with Cloud and hybrid applications<br>- Has internal software engineering capability.</p> | <p>- All moja transfer types including bulk.<br>- Bulk (1000000's of transfers in a transaction @ 1000 per chunk, sorted per payee DFSP).<br>- Open banking (incl PISP, AISP)</p> | <p>- High availability of internal infrastructure is necessary<br>- Multiple active instances of all critical integration services spread across multiple hardware nodes.<br>- High availability, replicated data storage.<br>- may be multi-site / availability zone / region.</p> | <p>- No downtime acceptable<br>- High-availability of connectivity.<br>- multiple active connections via diverse routes.<br>- Optional persistent storage.<br>- Scheme connection and integration layer SLA should match SLA for existing internal infrastructure.<br>- Up to 800 TPS peak sustained for 1 hour for e.g. FXPs.</p>                           | <p>- Record keeping?<br>- Security?</p> | - May need integration with existing enterprise security platforms e.g. firewalls, gateways etc...                                                                                                             | <p>The “Premium Service Manager” is recommended: A fully functional, Payment Manager-type service, for use by larger DFSPs. Operation of this needs significant resources; it must be hosted either in the DFSP’s existing data centre or in the cloud.<br>- Kubernetes based integration layer<br>- Possibly have existing integration technology.<br></p>                                                                                                                                                                                                                 |

## Fintechs which use PISP and/or AISP

| Participant Category               | Description                                                                                                                                                                                                                      | Expected Use-Cases                                                                             | Infrastructure Requirements for Mojaloop Integration                                                                                                                                                                                                                                | Expected Production SLA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Likely Relevant Regulation              | Special Security Requirements                                                                                                                                                                                  | Solution Options                                                                                                 |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Small self-hosting PISP/AISP       | <p>- Small org with single "branch" fintech with one or two products.<br>- Own workstations / servers<br>- Minimal cloud and/or SaaS.</p>                                                                                        | - Relatively small bulk payments e.g. salary payments for SMEs                                 | <p>- Single, cheap, low-end dedicated mini-pc (e.g. RPi)<br>- Single small business broadband Internet connection<br>- Self-hosted core banking system e.g. Mifos<br>- Use OS/Software firewall on same HW node as integration layer.</p>                                           | <p>- "Some" downtime acceptable if hardware fails.<br>- Some schemes may rule out DFSPs that cant meet a certain downtime SLA.<br>- May take many days/weeks to purchase replacement hardware on total failure.<br>- Full Mojaloop security feature set: mTLS, JWS, ILP<br>- Bulk interface SLA?<br>- How should this be defined? Batch size? time to send batch over API? response time for callbacks?<br>- Max batch size approx 10k payments<br>- Sending 10k payments via bulk API should take &#x3C; 30 seconds.<br>- Responding to callbacks should take &#x3C; 5 seconds.</p>                                              | <p>- Record keeping?<br>- Security?</p> | <p>- No need to integrate with existing enterprise security platforms.<br>- Need a fully secure solution "in-a-box" following best industry practice for internet facing services i.e. including firewall.</p> | <p>- Docker compose based integration layer.<br>- Minimal, self-contained integration layer.</p>                 |
| Low Medium self-hosting PISP/AISP  | <p>- Small org with one or two branches.<br>- Own "data centre" i.e. broom cupboard with a few servers, router, firewall etc...<br>- Some cloud knowledge and/or SaaS usage.</p>                                                 | <p>- Relatively small bulk payments e.g. salary payments for SMEs<br>- Account aggregation</p> | <p>- Single enterprise grade server hardware node.<br>- Use OS/Software firewall on same HW node as integration layer OR dedicated HW firewall.</p>                                                                                                                                 | <p>- "Some" downtime acceptable if hardware fails.<br>- Some schemes may rule out DFSPs that cant meet a certain downtime SLA.<br>- May take hours to replace hardware on total failure.<br>- Full Mojaloop security feature set: mTLS, JWS, ILP<br>- Bulk interface SLA?<br>- How should this be defined? Batch size? time to send batch over API? response time for callbacks?<br>- Max batch size approx 25k payments<br>- Sending 25k payments via bulk API should take &#x3C; 60 seconds.<br>- Responding to callbacks should take &#x3C; 10 seconds.</p>                                                                    | <p>- Record keeping?<br>- Security?</p> | <p>- May need integration with existing enterprise security platforms e.g. firewalls, gateways etc...<br>?? needs more clarification</p>                                                                       | <p>- Docker compose or docker swarm based integration layer.<br>- Minimal, self-contained integration layer.</p> |
| High Medium self-hosting PISP/AISP | <p>- Small org with one or two branches.<br>- Own "data centre" i.e. broom cupboard with a few servers, router, firewall etc...<br>- Some cloud knowledge and/or SaaS usage.</p>                                                 | <p>- Bulk payment for large organisations e.g. government depts.<br>- Account aggregation</p>  | - In order to tolerate failure on 1 hardware node 3 or more hardware nodes are required. (2n+1)                                                                                                                                                                                     | <p>- "Some" limited (minutes) downtime acceptable if hardware fails.<br>- Some schemes may rule out DFSPs that cant meet a certain downtime SLA.<br>- Should have spare hardware waiting or very fast replacement services in case of failures.<br>- Full Mojaloop security feature set: mTLS, JWS, ILP<br>- Bulk interface SLA?<br>- How should this be defined? Batch size? time to send batch over API? response time for callbacks?<br>- Max batch size approx 100-200k payments<br>- Sending 100-200k payments via bulk API should take &#x3C; 300 seconds.<br>- Responding to callbacks should take &#x3C; 120 seconds.</p> | <p>- Record keeping?<br>- Security?</p> | - May need integration with existing enterprise security platforms e.g. firewalls, gateways etc...                                                                                                             | <p>- Kubernetes based integration layer<br>- Possibly have existing integration technology.</p>                  |
| Large self-hosting PISP/AISP       | <p>- Mature, multi-branch org with high internal IT capability<br>- Has own data centre and experts to manage systems<br>- Comfortable with Cloud and hybrid applications<br>- Has internal software engineering capability.</p> | - Bulk payment for large organisations e.g. government depts.                                  | <p>- High availability of internal infrastructure is necessary<br>- Multiple active instances of all critical integration services spread across multiple hardware nodes.<br>- High availability, replicated data storage.<br>- may be multi-site / availability zone / region.</p> | <p>- No downtime acceptable<br>- High-availability of connectivity.<br>- multiple active connections via diverse routes.<br>- Optional persistent storage.<br>- Scheme connection and integration layer SLA should match SLA for existing internal infrastructure.<br>- Bulk interface SLA?<br>- How should this be defined? Batch size? time to send batch over API? response time for callbacks?<br>- Max batch size approx 1mil payments<br>- Sending 1mil payments via bulk API should take &#x3C; 600 seconds.<br>- Responding to callbacks should take &#x3C; 300 seconds.</p>                                              | <p>- Record keeping?<br>- Security?</p> | - May need integration with existing enterprise security platforms e.g. firewalls, gateways etc...                                                                                                             | <p>- Kubernetes based integration layer<br>- Possibly have existing integration technology.</p>                  |

## Document History

| Version |      Date     |     Author    |      Detail     |
| :-----: | :-----------: | :-----------: | :-------------: |
|   1.0   | 9th June 2025 | Tony Williams | Initial version |
