OTP / One-Time Passwords
Add secure, time-sensitive OTP verification to any Ghanaian app or user flow. Delivered through the same reliable BMS infrastructure your team already uses. One flag in the payload, that's it.
How it works
OTP is built on the same SMS API you already know. No extra integration, no separate SDK. Add a single field to your existing payload and your message is routed as a verified OTP.
Use the standard BMS SMS endpoint you already have integrated. No new endpoint, no extra authentication.
Include "sms_type": "otp" in your JSON payload. That one field tells BMS to route the message as a verified OTP send.
The OTP is delivered instantly to the recipient's phone over any network. GHS 0.035 is deducted from your main wallet per campaign.
API integration
Use your existing BMS API key. The only change is adding sms_type: "otp" to your payload. That single flag tells the platform to route the message as a verified OTP send.
curl -X POST \
"https://api.mnotify.com/api/sms/quick?key=YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recipient": ["0241234567", "0201234567"],
"sender": "mNotify",
"message": "Your verification code is 481923. Valid for 5 minutes.",
"is_schedule": false,
"sms_type": "otp" // ← add this to activate OTP routing
}'"sms_type": "otp" when the message is genuinely an OTP. Each OTP campaign deducts GHS 0.035 from your main wallet. Omit the field entirely for regular SMS blasts. Pricing
per OTP campaign
Common use cases
Account login / 2FA
Confirm identity before granting access to sensitive accounts.
Password reset
Send a short-lived code to verify ownership before allowing a reset.
Transaction confirmation
Authorize payments, transfers, or high-value actions with a one-time code.
Phone number verification
Confirm a real number during signup before creating the account.
Step-up authentication
Re-verify an already-logged-in user before sensitive operations.
API key / credential reveal
Gate access to secrets or export functionality behind a verified code.