AI disclosure: this document was drafted with assistance from Claude.
An engineering introduction to the Mojaloop PISP v2.0 workstream — the repositories you'll work in, where to track work, and how to get set up.
The main PISP repositories and their roles:
| Repository | Role |
|---|---|
tpp-api-svc |
PISP v2.0 module on the Mojaloop Switch. Third-party module the hub operator adds to the Mojaloop Hub to enable third-party services. Receives API requests and routes them to the appropriate Mojaloop central hub endpoint. |
thirdparty-api-svc |
PISP v2.0 Third Party SDK. Current implementation focuses on GooglePay; the workstream goal is to generalize it to support broader third parties. |
sdk-scheme-adapter |
PISP v2.0 DFSP. SDK used by a DFSP to communicate with the Mojaloop Hub. |
pisp-sig-docs/docs |
PISP v2.0 flow diagrams. |
Shared Mojaloop repositories also used by PISP:
| Repository | Role |
|---|---|
api-snippets |
Shared Mojaloop API definitions/snippets. |
central-services-shared |
Mojaloop shared central service. |
The example diagram below maps the repositories to the components they implement in a specific API request flow (in this case, Pre-linking):
| Component (in diagram) | Repository |
|---|---|
| Third Party | thirdparty-sdk |
| Payer DFSP | sdk-scheme-adapter |
| Mojaloop Hub (Mojaloop, Account Lookup Service, Auth-Service) | tpp-api-svc |
Bookmark these for quick access to PISP V2.0 work:
See Setup Guide.