Khabar
4notify Pakistan · the Gazette
GUIDE · Banks and fintechs · login and payment codes
Khabar No
KHB-PK-001
Date
2026-05-28
Status
In force
Category
Banking and payments

Bank OTP and payment alerts by SMS

Pakistani banks, wallets and fintechs send a code with every login and every large transfer. Your system generates and checks the code; 4notify only carries the message. It sends the SMS to Jazz, Telenor Pakistan, Zong and Ufone numbers through the 4notify relay or through your own gateway, and shows the delivery status of every message in the dashboard and API.

SMSPushEmail
Preamble

Notice. This Khabar explains how a bank, wallet or fintech in Pakistan can hand its one-time passcodes and transaction alerts to 4notify for delivery. The State Bank of Pakistan and its payment rules are context for your own compliance work; 4notify is not connected to Raast or to any banking system and does not generate or verify codes.

Statutory framework
State Bank of Pakistan Act, 1956

Background only: the central bank supervises banks, and each bank decides its own authentication design.

Payment Systems and Electronic Fund Transfers Act, 2007

Background only: the general legal frame for electronic payments in Pakistan. 4notify delivers messages and takes no part in payments.

Your bank's own security policy

The rules for code length, lifetime and retries are set by you, not by 4notify.

Implementation
01

Your system creates the code

Your banking or wallet system generates the one-time passcode and decides how long it stays valid. 4notify does not generate, store as a secret or verify codes.

02

One API call sends the SMS

Your system calls the 4notify REST API with the number and the text. The SMS goes out through the 4notify relay, or through your own gateway: a phone running the SMSGate app, an HTTP SMS provider, or a failover chain of several routes.

03

Back-up by email or in-app push

If you also hold the customer's email, your system can send the same code by email. Push works only inside your own mobile app.

04

Delivery status per message

Each message shows its delivery status in the dashboard and API, so support can answer "did my code leave?" without guessing.

Delivery envelope
json
POST /api/v1/sms
Authorization: Bearer <JWT>

{
  "to": "+923211234567",
  "text": "HBL: your code to confirm a transfer of Rs.12,500 is 471295. Valid 5 min. Never share this code."
}
Sample message
SMS

HBL: your code to confirm a transfer of Rs.12,500 to A. Khan is 471295. Valid 5 min. Never share this code.

Compliance checklist
  • Code generation and checking stay inside your own system
  • SMS route chosen: 4notify relay or your own gateway
  • Delivery tested to Jazz, Telenor, Zong and Ufone numbers
  • Delivery status of every OTP visible in the dashboard and API
The 4notify difference

SMS to Jazz, Telenor, Zong and Ufone subscribers through the 4notify relay, your own phone or provider, with failover between routes and the delivery status of every message in the dashboard and API.

Frequently asked questions
Does 4notify verify the OTP or the customer?

No. Your system creates and checks the code. 4notify delivers the message and reports its delivery status.

Can push replace SMS for a code?

Push works only inside your own mobile app, so it suits customers who have the app installed. Keep SMS as the route that reaches every handset.

Issued
4notify Operations Department
2026-05-28 · KHB-PK-001

Start free

14 days, no card. English-language support across the working week. Mughal arches and truck-art floral panels — but a strictly modern SLA.

Other entries in this issue