FOR THE PEOPLE BUILDING

Your product.
Connected to the way your customers pay.

MTN MoMo and Orange Money, through one API. Keep your customer experience, connect the payment and bring the result back into your business.

Discuss your integration ↗

Public developer documentation is in preparation. It will be live soon.

A payment, from end to end.

ILLUSTRATIVE SANDBOX FLOW
Your serverYour product. Your orders.
Kwik Nkap
Kwik NkapYour business account
MTN MoMoOrange Money
MTN MoMo · Orange MoneyYour customer approves
POST /v1/paymentsCustomer approvalYour server → Kwik Nkap
create-payment.sh
curl -X POST https://api.kwiknkap.com/v1/payments \
  -H "X-API-Key: $KWIKNKAP_API_KEY" \
  -H "Idempotency-Key: order-demo-1042" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 5000,
    "phone_number": "237670000001",
    "payment_method": "mobile_money",
    "metadata": { "order_id": "DEMO-1042" }
  }'
Example only. This page sends no API requests.
01 / 04

Create the payment

Your server sends the amount, customer phone number and selected wallet. The API key identifies your business and chooses Sandbox or Live.

POST/v1/payments
Server-side secret · payments:write

A workspace for the business.
The controls for your code.

Your integration belongs to a business account. The portal is where you manage access, separate test traffic from live money and inspect what happened.

  1. 01 · Developers

    Enable developer mode

    Open Developers in the portal and supply a contact email when requested. Developer mode reveals the technical controls and the Sandbox / Live switch.

  2. 02 · payments:write / payments:read

    Create a scoped Sandbox key

    Choose API keys in the Sandbox environment. Grant only the scopes your server needs. Store the secret on your server; never in the browser or a mobile bundle.

  3. 03 · payment.success / payment.failed

    Connect your event endpoint

    Add your HTTPS webhook URL and select events in the portal. Use delivery logs to inspect attempts, responses and available resend actions.

  4. 04 · Sandbox → Live

    Review before moving to Live

    Test the full payment lifecycle, including pending and failed outcomes. Complete the required business verification and review Live keys, endpoints and permissions before handling real money.

Build the flow your customers need.

A custom checkout, a shareable payment page or a proper invoice. Connect each to the same business account.

The details that make a payment integration work.

Idempotency-Key

Retry the request, not the charge.

Reuse the same key and body when retrying one operation. A different operation needs a different key.

metadata.order_id

Keep your own reference in the flow.

Attach string metadata to the payment. Read it back with the record and the webhook to reconcile your order.

X-KN-Signature

Verify the event before acting.

Verify the signature against the original raw body. Make event handling safe to repeat before acknowledging delivery.

error.request_id

Trace the request that needs attention.

Use structured error details and keep the request ID for support. Review webhook delivery logs in the portal.

A proper starting point. On its way.

We’re preparing public integration guides and API reference documentation. Until they go live, talk to our team about your product, your checkout and the support you need.

Talk to the integration team ↗