How do I send OTP codes by SMS in Nepal?
Your server generates the code, stores it, and calls the SMS API with the user's number and a message containing the code. The API accepts the request, returns a batch id and sends in the background. A webhook tells your server when the message is delivered or fails.
Your login code is 482913. It expires in 5 minutes. Do not share it with anyone.
What makes OTP SMS different from bulk SMS?
An OTP goes to one person, right after they act, and is useless if it arrives late. Bulk SMS goes to many people on your schedule. Both use the same account and credits, but OTP is sent from your application through the API rather than typed into the dashboard.
How do I avoid sending the same OTP twice?
Send an idempotency key with each API request. If a timeout makes your server retry, a request with the same key is processed only once, so the user never receives two different codes for one login. Generate one key per code you issue.
Which other transactional messages can I send?
Anything your system triggers for one customer: order and delivery updates, payment and invoice confirmations, appointment confirmations, password reset codes and account security alerts. Keep each message about the transaction itself. Adding an offer to a transactional message can turn it into an advertisement that needs consent.
- Order #1042 confirmed. Delivery expected on Friday.
- Payment of NPR 2,500 received. Thank you.
- Your appointment is on 12 Mangsir at 10:30am.
Questions people also ask
Can I send OTP SMS in Nepali?
Yes. Unicode is supported, but a Nepali message fits 70 characters per segment. Most teams keep OTP text in short English so the code fits one credit.
Where should the API key live?
On your server only. Never put the key in browser JavaScript or a mobile app, where anyone can extract it and send SMS on your balance.