Who should start here
Payment platform and fintech developers implementing the MEMEH Core API
Bank Adapter engineers implementing the participant and IPS boundary
Operators learning runtime configuration and enablement boundaries
Architects reviewing integration boundaries
In one sentence
MEMEH Core accepts a payment intent, resolves trusted aliases, builds and dispatches a canonical instruction through the selected Bank Adapter, and exposes lifecycle status and event history.
Start in 4 steps
1.
Read Concepts to understand what MEMEH is and is not.
2.
Read Security to understand HMAC, nonce, timestamp, and idempotency.
3.
Move to the fintech or bank integration guides.
4.
Complete sandbox, UAT, and approval workflow before production.
Quick flow
First example request
cURL
curl -X POST https://sandbox.memeh.org/api/v1/payment-requests \
-H "Content-Type: application/json" \
-H "X-Client-ID: SALONEPAY" \
-H "X-Signature: replace-with-real-signature" \
-H "X-Timestamp: 2026-03-21T10:00:00Z" \
-H "X-Nonce: uat-nonce-001" \
-H "X-Idempotency-Key: uat-idempotency-001" \
-d '{
"payer_alias": "+2320000001",
"payee_alias": "+2320009991",
"amount": "100.00",
"currency": "SLE",
"description": "Test Payment",
"reference": "TXN-001"
}'
Need Access?
Apply for MEMEH onboarding
Approved fintechs and banks can move from documentation to onboarding, sandbox access, UAT, and production readiness through a controlled process.