Aggregator model

This API is not a B2C product. The integrating party is always a regulated financial institution with its own end-user (sender) base. The aggregator model has three actors:

Actor	Role
Sender	End-user in the originating country who initiates the transfer. Outside the scope of this API.
Partner (you)	MTO, bank or fintech. Holds the sender relationship, performs originator KYC, calls this API.
Moko Afrika	Provides the DRC corridor: telco connectivity, FX, sanctions screening, settlement.

Because Moko is the only party with direct access to the DRC telco subscriber registries, certain compliance checks — live beneficiary name lookup, sanctions screening on the beneficiary leg — are performed by Moko and surfaced back to the partner.

Corridor coverage

Money flows into DRC from these countries. Send-side (partner) currency is auto-converted by Moko's FX layer before the DRC leg.

Country	Currency	Status
Uganda	UGX	Live
Nigeria	NGN	Live
Kenya	KES	Live
Tanzania	TZS	Live
Rwanda	RWF	Live
South Africa	ZAR	Live
Ghana	GHS	Live
Any (USD)	USD	Live

The DRC leg is always denominated in USD at the telco. If the partner sends CDF, EUR, GBP, etc., Moko converts to USD before submitting to the telco.

Distribution channels in DRC

Operator	Payload operator	Notes
Vodacom M-Pesa	mpesa	Primary channel, highest volume
Airtel Money	airtel
Orange Money	orange
AfriMoney	afrimoney
FBN Bank cash pickup	fbnbank	Requires receiver_document_type + receiver_document_number

Who owns which compliance obligation

• Partner owns:
  • Sender KYC (identity documents, source of funds, sanctions screening on the sender side per your regulator)
  • Populating every required field on /inbound truthfully — do not fabricate sender_birthplace or receiver_document_number to pass the schema check
  • Retention of source-of-truth records on your side per your regulator's rules
• Moko owns:
  • Beneficiary lookup against telco subscriber registries
  • Sanctions screening on the receiver leg (ScreenShield)
  • FATF R.16 name-match between the declared receiver name and the telco record
  • BCC (Banque Centrale du Congo) RTS Art.66 record-keeping on the DRC leg
  • Sanctions posture on the DRC-side beneficiary

The idea is that neither side is doing the other's work — you know your sender, we know the DRC beneficiary. Together the transaction is fully KYC'd.