Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Wave Mobile Money website screenshot

Wave Mobile Money

Wave is a Dakar, Senegal-headquartered mobile money company on a mission to "make Africa the first cashless continent." Founded by Drew Durbin and Lincoln Quirk (who previously built the Sendwave remittance service) and publicly launched in Senegal in 2018, Wave provides a smartphone- and agent-based wallet that lets users deposit and withdraw cash for free and send money domestically for a flat 1% fee — roughly 70% cheaper than the telco-led mobile money incumbents in the region. Wave operates today in Senegal, Côte d'Ivoire, Uganda, Mali, Burkina Faso, and The Gambia, working through a dense network of human agents alongside the Wave app and a separate Wave Business portal for merchants and enterprises. In September 2021, Wave raised a USD 200M Series A led by Sequoia Heritage, Founders Fund, Stripe, and Ribbit at a USD 1.7B valuation — the largest Series A ever raised on the African continent at the time. For developers, Wave exposes a tier-1 B2B platform via api.wave.com, documented at docs.wave.com, with Checkout (hosted payment sessions), Payout (single and batch disbursements, reversals, recipient verification), Balance & Reconciliation (wallet balance, transactions, refunds), Aggregated Merchants (sub-merchant management for aggregators and PSPs), and Webhooks with HMAC-SHA256 signing for asynchronous event delivery. API keys are scoped per-API, support IP allowlisting and optional request signing, and the platform enforces idempotency on POST mutations.

agent aware

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Wave Mobile Money the way a machine reads it — 7 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Wave Mobile Money scores 29.4/100 (emerging), with a separate agent-readiness read of 16/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 29.4/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.0 / 20
Commercial Clarity 6.3 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Regulatory · Payments 8.5 / 15
Agent readiness — 16/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Wave Mobile Money

Each block below is one kind of artifact we hold for Wave Mobile Money. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 5

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Wave Checkout API

Hosted payment session API for accepting one-off payments from Wave wallet users. Create a checkout session, redirect the customer to the returned wave_launch_url, then receive ...

Wave Payout API

Programmatic disbursement API for sending money from a business wallet to individual Wave wallets, identified by E.164 mobile number. Supports single payouts, payout batches (su...

Wave Balance & Reconciliation API

Read-side API for inspecting a business wallet's current balance and enumerating its transactions for accounting and reconciliation. GET /v1/balance returns the live wallet bala...

Wave Aggregated Merchants API

Sub-merchant management API for aggregators, payment service providers, and platforms that accept Wave payments on behalf of many downstream businesses. Full CRUD over aggregate...

Wave Webhooks

Outbound event delivery channel for asynchronously notifying merchant systems when state changes on the Wave platform. Events include checkout.session.completed, checkout.sessio...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Wave Mobile Money Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Wave Mobile Money Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for Wave Mobile Money — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Other 3

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/wave-mobile-money · machine-readable index on apis.io