What SMS messages can a cooperative or bank send?
Typical messages are deposit and withdrawal alerts, loan instalment due reminders, interest posting notices, general meeting dates, branch closure notices and OTP codes for login or payment approval. Each tells a member about their own account or membership. Send alerts from your core system through the API so they go out when the transaction happens.
Rs 5,000 deposited to your savings account ending 4421 on 30 Oct. Balance Rs 18,250. Not you? Call your branch.
How should OTP codes be sent for mobile banking?
Generate the code on your server, then send it through the API with a send-only API key kept on the server, never in the app. Add an idempotency key so a retry does not send a second code. Track each OTP by its status, and tell members that staff will never ask for the code.
Your mobile banking login OTP is 739204. It is valid for 3 minutes. Our staff will never ask for this code.
Do member alerts need consent?
Transaction alerts, instalment reminders and OTP codes relate to the member's own account, so on a plain reading they are transactional, not advertising. Messages promoting a new loan or deposit scheme are advertising and need the recipient's consent under the Advertisement (Regulation) Act 2076. This is general information, not legal advice for your institution.
Can alerts show the institution's name?
Yes, after approval. Request a branded alphanumeric sender ID of up to 11 characters from the dashboard, such as a short form of the cooperative's name. A recognisable sender helps members tell real alerts from fraud. Until it is approved, messages go out under a shared default sender ID, so name the institution in the text.
How does a bank or cooperative start?
Fill in the lead form on the contact page, then complete KYC with the institution's registration documents. A reviewer approves it, usually within 2 to 3 business days. Your IT team or software vendor then connects the core system using the API base URL provided with your account and a scoped API key.
Questions people also ask
Can members receive alerts in Nepali?
Yes. Nepali is supported. A Nepali alert holds 70 characters per segment, so keep it short to use one credit per member.
How do we confirm an alert reached the member?
Each message has a status in the dashboard and API. With a callback URL, a signed webhook is posted on delivered or failed, and credits for a failed message are refunded.
Can one API key be limited to sending?
Yes. API keys can be scoped, for example send-only, so the key in your core system cannot do more than it needs.