One API for three markets.

REST and JSON, idempotent writes, signed webhooks. Send the country and the customer's phone number; we pick the network and route.

Collect a payment

Amounts are integers in the currency's minor unit: ngwee for ZMW, whole shillings for TZS and UGX. The response tells you which network the number belongs to; the final status arrives by webhook.

  • Test and live keys, with simulated networks in test mode
  • Idempotency-Key on every write
  • Webhooks signed with HMAC-SHA256 and retried with back-off
  • Payouts, refunds, invoices, payment links, SMS and OTP follow the same pattern
# Collect TZS 20,000 from a Vodacom M-Pesa customer
curl https://api.interseqtion.com/v1/payments \
  -H "Authorization: Bearer sk_test_..." \
  -H "Idempotency-Key: order-1042" \
  -d '{
    "country": "TZ",
    "amount": 20000,
    "phone": "0754123456",
    "reference": "order-1042"
  }'

# 201 Created
{
  "id": "pay_...",
  "status": "pending",
  "currency": "TZS",
  "network": "vodacom"
}

Endpoints

/v1/payments
Collect from a mobile money wallet
/v1/payouts
Send to a mobile money wallet
/v1/refunds
Return all or part of a payment
/v1/invoices
Create, send and track invoices
/v1/payment_links
Reusable or single-use links
/v1/messages
Send transactional SMS, singly or in batches
/v1/campaigns
Bulk SMS campaigns and recipient reports
/v1/verify/otp
Send and check one-time passcodes
/v1/verify/screening
Sanctions and PEP screening
/v1/balance
Available and pending balances per currency
/v1/webhook_endpoints
Register where events are sent

Ask for sandbox keys.

Request access