4N-UG-001BANKING· Active · Banking and payments

Banking and mobile money OTPs by SMS in Uganda

Commercial banks in Uganda are supervised by the Bank of Uganda, which also oversees payment systems, including mobile money, under the National Payment Systems Act 2020. When a customer logs in or approves a payment, the bank's or payment provider's system generates the code and calls the 4notify REST API, which delivers it by SMS to MTN and Airtel subscribers. Push and email are available as additional channels through the same API.

SMSPushEmail

A one-time code is part of a bank's fraud controls: the customer must receive it from a name they recognise, and the bank must know what was sent, when and with what status. The Bank of Uganda's framework for banks, payment systems and consumer protection shapes how these messages and the data behind them are handled.

Delivery to MTN Uganda and Airtel Uganda subscribers, with an alphanumeric sender ID registered under each network's rules.

Laws and rules cited

  • Financial Institutions Act 2004
    Licensing and supervision of commercial banks and credit institutions by the Bank of Uganda.
  • National Payment Systems Act 2020
    Licensing and oversight of payment systems and payment service providers, including mobile money.
  • Bank of Uganda Financial Consumer Protection Guidelines 2011
    Fair treatment, transparency and complaint handling in a financial service provider's dealings with customers.

How it works

  1. 1
    The code is generated by your system
    Your authentication system creates and verifies the code. 4notify receives only the ready-to-send text and the recipient's number.
  2. 2
    The API call
    Your system obtains a JWT with client_credentials and sends POST /api/v1/sms with the number, sender ID and text.
  3. 3
    Delivery on MTN and Airtel
    The message leaves through the 4notify relay or your own SMS provider; if one route fails, 4notify switches automatically to the next configured SMS route.
  4. 4
    Delivery status
    Each message's status is visible in the panel and the API; the bank keeps the records its own control policies require in its own systems.

Event payload

{
  "event": "bank.otp.payment",
  "to": "+256772123456",
  "sender": "BANK",
  "text": "Your code is 481922. It expires in 5 minutes. Never share it.",
  "reference": "TXN-2026-11-19-5521",
  "amount": 250000,
  "currency": "UGX"
}

Sample message

SMS
Stanbic: your code is 481922. It expires in 5 minutes. Never share it; we will never ask for it by phone.

Compliance checklist

  • ✓The code is generated and verified only in your own system
  • ✓Alphanumeric sender ID approved on MTN and Airtel
  • ✓API calls authenticated with a JWT (client_credentials)
  • ✓Delivery status reviewed in the panel or through the API
What sets it apart
One REST API for banking and mobile money OTPs on MTN and Airtel, with automatic failover between SMS routes and a delivery status for every message.

Frequently asked questions

Does 4notify generate the OTP?
No. The code is created and verified by the bank's or payment provider's system; 4notify only delivers the message it receives through the API.
Is there a connector for MTN MoMo or Airtel Money?
No. If the system that runs your mobile money flows calls the 4notify REST API, we deliver its codes and confirmations; there is no native wallet connector.
How does the bank know the code arrived?
Every message has a delivery status in the panel and the API. If an SMS route fails, 4notify automatically tries the next configured route.
Create an accountSee the Playbook

More from the Playbook

← Back to 4notify Uganda