Introduction

The IMT Remittance API is the aggregator-mode integration point used by partner MTOs (Money Transfer Operators), banks and fintechs to send international remittances to mobile money wallets in the Democratic Republic of Congo (DRC).

Moko Afrika operates on the ground in DRC and provides the only direct interface to the local mobile money operators (Vodacom M-Pesa, Airtel Money, Orange Money, AfriMoney) for cross-border remittance. Partners outside DRC use this API to disburse funds to DRC beneficiaries without managing the complexity of telco integrations, FX, sanctions screening or compliance reporting.

Why partners use Moko

• Single integration for the whole DRC market. Four telcos, one API contract. No need to integrate M-Pesa, Airtel, Orange and AfriMoney separately.
• Compliance handled at the API boundary. BCC RTS Art.66 Instr.15 and FATF R.16 KYC fields enforced on every inbound. ScreenShield sanctions screening runs on every sender and receiver.
• On-the-ground presence. Moko has the local FX corridor, the settlement rails, and the direct contracts with the telco partners.
• Async-safe. HMAC-SHA256 signed callbacks with clear terminal statuses. Idempotent by reference.

What's in this documentation

• The Guide walks you through registration, authentication, the aggregator concept, compliance requirements, callbacks and error codes.
• The API Reference documents every endpoint, its payload schema, error codes and examples.
• The Postman collection has 40+ pre-built test cases you can import into Postman and run against the sandbox.

Environments

Environment	Base URL	Amount cap
Sandbox	https://staging.remittance.gofreshpay.com	1 USD per transaction
Production	https://remittance.gofreshpay.com	none

Every partner starts in sandbox. Production is unlocked after a successful Go Live request from the merchant dashboard.

What's new in v2.2 (2026-08-14)

• reason_of_transaction enum extended from 11 to 23 values (added: INVESTMENT, CONSTRUCTION, RENT, GENERAL, FUEL, REPAIRS, PERSONAL_CARE, FOOD_AND_GROCERIES, TRANSPORT, SHOPPING, ENTERTAINMENT, DONATIONS) so partners can forward the sender-selected label verbatim instead of collapsing everything into OTHER.

What's new in v2.1 (2026-08-13)

• 8 KYC fields promoted from soft-required to hard-required on /inbound, per BCC RTS Art.66 Instr.15 + FATF R.16: sender_birthplace, sender_document_type, reason_of_transaction, source_of_funds, receiver_birthdate, receiver_document_type, receiver_document_number, and either receiver_current_address or receiver_permanent_address.

Talk to us

• Integration support: remittance-support@mokoafrika.com
• For real-time debugging during certification: ask your Moko technical contact to open a dedicated Slack Connect channel.

Next step

Read Base URLs and then Authentication to make your first request.