Tangazo
4notify Tanzania · market guide
TANGAZO · Banks and fintechs · login and payment codes
Tangazo No
TNG-TZ-001
Date
2026-05-27
Status
In force
Category
Banking & payments

Bank & payment SMS alerts Tanzania

Tanzanian banks, microfinance lenders and payment businesses send a steady flow of short messages: transfer confirmations, card and account alerts and one-time codes. The Bank of Tanzania (BoT) oversees the payment system and expects institutions to protect customers with strong authentication. 4notify does not generate or verify codes: your banking system creates the code and calls the 4notify REST API, and 4notify delivers it by SMS, by email, or as a push inside your own app, with the delivery status of each message in the dashboard and API.

SMSPushEmail
Regulatory context

This Tangazo explains how a Tanzanian bank or payment business can deliver authentication codes and transaction alerts with 4notify. The legal references below are general context only; confirm the current text and your own obligations with your counsel and regulator.

Statutory basis
Bank of Tanzania Act, 2006

Background: the BoT mandate over monetary policy and the national payment system.

National Payment Systems Act, 2015

Background: the framework for payment systems and payment-service providers in Tanzania.

BoT Electronic Money Regulations, 2015

Background: rules for electronic-money issuers; check the current text for authentication and record-keeping duties that apply to you.

Implementation
01

Your system generates the code

The one-time code is created and later verified by your own banking or payments platform. 4notify only carries the message; it does not generate, store or verify codes.

02

Call the REST API

Your system sends the message to the 4notify REST API (JWT-authenticated, /api/v1/sms or /api/v1/email) with the recipient number and text.

03

Choose how it is sent

SMS goes out through the 4notify relay or through your own transport: a phone running the SMSGate app, an HTTP SMS provider, or a failover chain of several.

04

Delivery status and fallback

The delivery status of each message shows in the dashboard and API. If the SMS fails, your chain can fall back to another transport, to email, or to a push in your own app.

Delivery envelope
json
{
  "to": "+255712345678",
  "message": "CRDB Bank: your code to confirm a transfer of TZS 450,000 is 482193. Valid 5 min. Do not share it with anyone.",
  "topic": "transactional"
}
Sample message
SMS

CRDB Bank: your code to confirm a transfer of TZS 450,000 to J. Mwakasege is 482193. Valid 5 min. Do not share it with anyone.

Compliance checklist
  • Code generation and verification stay in your own banking system
  • REST API call from your system to 4notify configured with a JWT
  • SMS transport chosen: 4notify relay, SMSGate phone, HTTP provider or failover chain
  • Delivery status of codes monitored in the dashboard and API
The 4notify difference

Your bank system creates the code and calls one REST API; 4notify delivers it by SMS, email or in-app push, with delivery status for every message in the dashboard and API.

Frequently asked questions
Does 4notify verify the one-time code?

No. Your system generates and verifies the code. 4notify delivers the message and reports the delivery status of each one.

Which networks can receive the messages?

Messages are addressed to +255 numbers on Vodacom, Yas, Airtel, Halotel and TTCL. Actual delivery depends on the transport you choose, and 4notify publishes no delivery-time or uptime guarantee.

Prepared by
4notify editorial team
2026-05-27 · TNG-TZ-001

Start free

14 days, no card. English support on weekdays. Karibu Tanzania.

Other guides