MEMEH RTPO logo
Documentation menu
Docs Home Get Started Concepts Architecture Security RTP Guide Fintech Developer Guide Runtime Configuration UAT Operations Downloads API Reference
Overview

MEMEH RTPO Platform Documentation

MEMEH RTPO public documentation is organized for request submitters, developers, operators, architects, testers, risk teams, and support teams. It describes the complete Bank of Sierra Leone National Payment Switch Request-to-Pay orchestration platform: enablement, Central Addressing Service resolution, governed routing, orchestration, lifecycle monitoring, UAT, and operations. Participant implementation contracts are distributed separately through a controlled channel.

Start Integration API Reference Apply for Access
Bearer API Central Addressing Service Approved routing Lifecycle events
Platform concept
Components, ownership, enablement, and current user journeys.
Lifecycle and routing
Central Addressing Service resolution, provider delivery, and events.
Integration contracts
Current public APIs for fintechs, PayFacs, billers, and government services.
Operational readiness
Security controls, UAT, support, and rollout.
Need artifacts?
Postman collections, sample payloads, and downloads.
Downloads
Recommended path

From concept → first request

The sequence most teams follow before deep integration.

  1. 1
    Get Started
    View →
    Platform, enablement, runtime journey, and first request.
  2. 2
    Concepts
    View →
    Whole-platform purpose, components, ownership, and terms.
  3. 3
    Architecture
    View →
    Current services, resolution, routing, dispatch, and lifecycle.
  4. 4
    Security
    View →
    Implemented authentication, duplicate safety, and production controls.
Open Get Started
Tracks

Choose your path

Role-based documentation for integration and operations.

Fintech Developer Guide
Primary payment-request API contract, authentication, polling, errors, and integration responsibilities.
→
Architecture
Platform structure and lifecycle design.
→
Security
Current boundary controls, duplicate safety, and production hardening.
→
Operations & readiness
Runtime Configuration & Enablement → UAT & Certification → Operations →
Reading order

The sequence most teams follow

Fundamentals first, then architecture and security before deep integration.

Begin →
Get Started Concepts Architecture Security
© 2026 MEMEH RTPO — MEMEH Request-to-Pay Orchestrator
Developer & Integration Portal