Idempotency-KeyRetry the request, not the charge.
Reuse the same key and body when retrying one operation. A different operation needs a different key.
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.
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" }
}'const response = await fetch(
"https://api.kwiknkap.com/v1/payments",
{
method: "POST",
headers: {
"X-API-Key": process.env.KWIKNKAP_API_KEY,
"Idempotency-Key": "order-demo-1042",
"Content-Type": "application/json"
},
body: JSON.stringify({
amount: 5000,
phone_number: "237670000001",
payment_method: "mobile_money",
metadata: { order_id: "DEMO-1042" }
})
}
);
if (!response.ok) throw new Error("Request failed");
const payment = await response.json();
// PENDING is not a paid order.{
"id": "knpay_test_example",
"status": "PENDING",
"amount": 5000,
"currency": "XAF",
"payment_method": "mobile_money",
"environment": "SANDBOX",
"metadata": {
"order_id": "DEMO-1042"
}
}{
"id": "knpay_test_example",
"status": "SUCCESS",
"environment": "SANDBOX",
"metadata": {
"order_id": "DEMO-1042"
}
}{
"id": "evt_example",
"type": "payment.success",
"created": 1794528000,
"data": {
"id": "knpay_test_example",
"status": "SUCCESS",
"amount": 5000,
"currency": "XAF",
"environment": "SANDBOX",
"metadata": {
"order_id": "DEMO-1042"
}
}
}Your server sends the amount, customer phone number and selected wallet. The API key identifies your business and chooses Sandbox or Live.
/v1/paymentsA created payment is not a completed payment. In Live, the customer approves the request in their Mobile Money wallet. Keep the order waiting while the payment is pending.
Request accepted ≠ payment settledRead the payment status using its ID. SUCCESS, PENDING and FAILED describe different outcomes. Keep your own order reference in metadata to connect the payment to your system.
/v1/payments/{paymentId}/statusRegister your webhook endpoint in the merchant portal. Verify the signature on the raw request body, handle repeat deliveries safely and return a 2xx response. Then update the order from the verified outcome.
Your HTTPS webhook endpointYour integration belongs to a business account. The portal is where you manage access, separate test traffic from live money and inspect what happened.
Open Developers in the portal and supply a contact email when requested. Developer mode reveals the technical controls and the Sandbox / Live switch.
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.
Add your HTTPS webhook URL and select events in the portal. Use delivery logs to inspect attempts, responses and available resend actions.
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.
A custom checkout, a shareable payment page or a proper invoice. Connect each to the same business account.
POST /v1/paymentsRequest an MTN MoMo or Orange Money payment from your own checkout. The customer still controls approval.
02POST /v1/payment-linksCreate a payment page to share with a customer, then manage the link and follow its payments.
03POST /v1/invoicesCreate the invoice, publish it when ready, send it and retrieve its PDF through the API.
Idempotency-KeyReuse the same key and body when retrying one operation. A different operation needs a different key.
metadata.order_idAttach string metadata to the payment. Read it back with the record and the webhook to reconcile your order.
X-KN-SignatureVerify the signature against the original raw body. Make event handling safe to repeat before acknowledging delivery.
error.request_idUse structured error details and keep the request ID for support. Review webhook delivery logs in the portal.
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 ↗