DEV Community: Jovan Mwesigwa

Why Can’t I Access Mobile Money API Docs Without Compliance?

Jovan Mwesigwa — Wed, 01 Oct 2025 09:50:54 +0000

We’ve all been there. You’re exploring providers for your next project, trying to decide which payment solution works best for your use case. Then you hit a wall: you can’t even view the documentation without going through weeks of compliance hoops.

This is one of the most frustrating realities of building with mobile money in Africa.

Compliance Before Discovery

Across MTN, Airtel, M-Pesa, and others, it’s surprisingly common that you cannot access even the bare minimum of their API docs without first completing compliance and KYC.

Think about that. Imagine if Stripe or PayPal hid their documentation behind a “government and business KYC” process before you could decide whether their API was a good fit. Sounds crazy, right? Yet here, it’s normal.

And it creates real problems for developers and product teams.

Why This Hurts Developers

When you’re an early-stage technical team, you don’t have months to burn. You need to make decisions quickly, and that means evaluating a provider’s API against a checklist like:

Documentation quality: Is it robust and developer-friendly?
Stack compatibility: Does it support our language/frameworks?
Webhook handling: How does it notify us of payments?
Support: Can we reach a developer team if we’re stuck?
Pricing: What are their fees and rates?
Reliability: How often is their API down?
Transaction limits: What’s the min/max per transaction?

But if you can’t even see the docs, you’re left choosing blindly.

This leads to wasted time, wrong integrations, and sometimes having to rip everything out and start again with a different provider.

A Broken Onboarding Experience

This isn’t just inconvenient. It slows down innovation:

Prototyping becomes impossible: You can’t test before choosing.
Stakeholder buy-in is harder: No working demos for your team or investors.
Dead ends cost time: You realize too late that the API won’t work for your use case.

The result? African fintech teams move slower than they should, and developers burn months on bureaucracy instead of building.

A Different Approach

This is exactly why FundKit exists.

Instead of waiting weeks for compliance just to explore, FundKit gives you:

Instant sandbox access: Test MTN, Airtel, and M-Pesa APIs immediately.
Virtual mobile money network: Use our phone emulator to simulate real user flows.
Smart routing: FundKit auto-picks the cheapest, most reliable provider in real time.
Unified SDK: One integration works across multiple providers.

That means you can:

Prototype in minutes, not months.
Show stakeholders working demos early.
Switch providers easily without rewriting your stack.

Independence That Scales With You

The best part of FundKit is that it’s independent.

Once your compliance team is done with the paperwork and the provider has approved you, you can simply swap your sandbox API keys for production keys and FundKit will keep working with zero code changes.

Want to add another provider later? Just drop in their production keys, and FundKit will handle them the same way. No rewrites, no provider lock-in, no wasted development cycles.

This means your integration grows with you as your business expands.

Why This Matters

When developers have to wait for compliance just to start building, it kills momentum.

By flipping the order build first, compliance later FundKit makes it possible for teams to:

Validate faster.
Integrate smarter.
Launch quicker.

Final Thoughts

Compliance is important. No one is arguing against it. But forcing developers to commit before discovery is backwards.

FundKit is here to fix that.

Is MTNAPI Free? (And What You Should Know Before Integrating)

Jovan Mwesigwa — Tue, 30 Sep 2025 15:32:33 +0000

Is MTN API Free?

If you're a developer or fintech team looking to integrate MTN Mobile Money, one of the first questions you probably ask is:

“Is MTN API free?”

The short answer: Yes, but not really.

1. The Official MTN API Cost

No upfront fees: MTN typically provides API access for free.
Revenue share / transaction fees: You (or your client) pay fees on every transaction.
Compliance requirement: To access the real MTN API, you need to go through an onboarding and compliance process, which can take weeks or even months.

So while the API itself doesn’t have a price tag, the time cost is significant.

2. The Hidden Costs Nobody Talks About

Developers often discover that:

You can’t see MTN API docs until compliance is approved.
There is no sandbox or testnet → you can’t prototype without touching real money.
You burn development time waiting on paperwork.

This means the real cost is developer hours lost.

3. What If You Just Want to Start Building?

That’s where FundKit comes in.

With FundKit, you don’t need to wait for MTN’s compliance approval to begin development:

import { PaymentClient } from "@fundkit/core";

const client = new PaymentClient({
  apiKey: process.env.FUNDKIT_SANDBOX_KEY,
  environment: "sandbox",
  providers: ["mtn"],
});

async function run() {
  const payment = await client.collection({
    provider: "mtn",
    amount: 5000,
    currency: "UGX",
    accountNumber: "+256700000000",
    description: "Test MTN payment",
  });

  console.log("Payment:", payment.status);
}

run();

Works just like MTN’s live API.
Includes a phone emulator → simulate what your users will see.
Test collections, payouts, and even error scenarios.

4. When You’re Ready to Go Live

Once compliance is cleared with MTN, you simply swap in your production keys:

const client = new PaymentClient({
  apiKey: "sk_live_your_key",
  environment: "production",
  providers: {
    mtn: { apiKey: "your_mtn_key" },
  },
});

No refactoring required.
Your prototype → becomes production-ready.

5. Final Answer

So, is the MTN API free?

Technically, yes.
But the real cost is time, compliance, and lack of a sandbox.

With FundKit, you start coding immediately, without waiting on compliance.

Learn More

Why MTN and Airtel make you sign contracts before seeing their API docs (and how to start building without waiting)

Jovan Mwesigwa — Tue, 30 Sep 2025 14:55:59 +0000

The Compliance Gate Problem

If you've ever tried to integrate mobile money payments in Africa, you know the drill:

Find the provider's API documentation (if it exists)
Get redirected to a compliance form
Wait weeks for approval
Finally get access to docs that are... underwhelming

This is the reality for developers trying to work with MTN, Airtel, M-Pesa, and other African mobile money providers. But why does this happen, and more importantly, how can you start building without waiting?

Why Providers Gate Their Documentation

1. Regulatory Compliance Requirements

African mobile money providers operate under strict financial regulations. They need to ensure that anyone integrating with their systems:

Has proper business registration
Complies with anti-money laundering (AML) requirements
Meets know-your-customer (KYC) standards
Has appropriate financial licenses

2. Risk Management

Mobile money involves real money transactions. Providers need to vet potential partners to:

Prevent fraud and money laundering
Ensure proper transaction monitoring
Maintain system security and integrity
Protect their reputation and regulatory standing

3. Resource Allocation

API documentation and support are expensive to maintain. Providers want to focus their resources on:

Verified, serious businesses
Partners who will generate significant transaction volume
Companies with proper compliance infrastructure

The Developer's Dilemma

This creates a classic chicken-and-egg problem:

You need to see the API to understand if it fits your use case
You need to build a prototype to get stakeholder buy-in
You need to test integration to estimate development time
But you can't do any of this without compliance approval

The FundKit Solution

This is exactly why we built FundKit. Here's how we solve the compliance gate problem:

1. Unified API Documentation

We provide comprehensive, always-available documentation for all major African mobile money providers:

// MTN Mobile Money API
const mtnPayment = await client.collection({
  provider: "mtn",
  amount: 1000,
  currency: "UGX",
  accountNumber: "+256700000000",
});

// Airtel Money API
const airtelPayment = await client.collection({
  provider: "airtel",
  amount: 1000,
  currency: "UGX",
  accountNumber: "+256700000000",
});

2. Sandbox Environment

Test with virtual mobile money without any compliance requirements:

const client = new PaymentClient({
  apiKey: "sk_test_your_key",
  environment: "sandbox",
  providers: ["mtn", "airtel", "mpesa"],
});

3. Real Provider Integration

When you're ready for production, simply switch your API keys:

const client = new PaymentClient({
  apiKey: "sk_live_your_key",
  environment: "production", // <-- change variable to production 
  providers: {
    mtn: { apiKey: "your_mtn_key" },
    airtel: { apiKey: "your_airtel_key" },
  },
});

Getting Started Today

Ready to start building without waiting for compliance approval?

Sign up for FundKit (free, no compliance required)
Get your sandbox API key (instant access)
Start building with our comprehensive documentation
Test with virtual mobile money in our sandbox
Deploy to production when you're ready

Next Steps

The future of mobile money integration shouldn't be gated behind compliance paperwork. Start building today with FundKit.