WhatsApp OTP Authentication Template for Nonprofits
Donor portals, volunteer sign-ups and beneficiary self-service accounts all need a fast, trustworthy way to verify who is logging in. This is a ready-to-use, Meta-compliant WhatsApp one-time-password template built for Indian nonprofits — submitted under the authentication category, with a secure copy-code button and the exact variables Meta expects. Copy it, set your organisation name, and once your template is approved you can start sending verification codes in minutes through InfiQ, an official Meta Business Partner for the WhatsApp Business API.
Variables
{{1}}= 482913{{2}}= Asha Foundation
Verified business
10:24
Preview · as customers see it
When a nonprofit should send this OTP template
Reach for this template at any moment where a person must prove they own an account or a phone number before an action goes through. For nonprofits that typically means a donor logging in to a giving portal to view 80G receipts or update a recurring donation, a volunteer creating or resetting a password on your roster app, or a beneficiary opening a self-service account to check the status of aid or a stipend. Because the code is delivered the instant the user requests it, WhatsApp OTP fits naturally into the login and password-reset journey rather than sitting in a separate SMS gateway. The authentication styling WhatsApp applies to these messages also reassures a first-time donor that the prompt is genuine, which matters when trust is your organisation's most valuable asset.
- Donor portal login and account recovery
- Volunteer app sign-up and password reset
- Beneficiary self-service account verification
- Confirming a new phone number on file before it becomes the contact of record
The template and its variables
The body carries just two variables so it approves cleanly and reads unambiguously. Variable {{1}} is the numeric one-time code your system generates, and {{2}} is your registered organisation name so the donor knows exactly who is asking. A single Copy code button lets the recipient copy the OTP with one tap and paste it straight into your form, eliminating the transcription errors that plague long numeric SMS codes. Keep the ten-minute validity line and the do-not-share warning exactly as written — both are standard for the authentication category and help the template pass review. Do not add a name greeting, a logo, an image, or any link; the authentication category strips all of that out and rejects templates that include it.
- {{1}} — the one-time code, e.g. 482913
- {{2}} — your organisation name, e.g. Asha Foundation
- Button — Copy code (copies {{1}} in one tap)
Getting it approved by Meta the first time
OTP templates are among the fastest to clear because their structure is so constrained, but the constraint is exactly why organisations trip up. Submit under the authentication category, never marketing or utility. Use the standard code-plus-security-message format and the copy-code button rather than a URL button. Strip out anything promotional — no fundraising ask, no campaign line, no emoji, no donation link. Set your {{2}} value to your exact registered display name so it matches your verified WhatsApp Business profile. If you serve donors in more than one language, submit each language as its own template variant in advance, since each is reviewed separately. Get these details right and approval typically lands within a day, after which InfiQ can dispatch codes the moment a user triggers a login.
- Category must be Authentication
- Copy-code button, not a link button
- No greeting, logo, image, link or promotional text
- Submit each language version separately
What it costs to send
This template bills at the authentication category rate. Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category, so every verification code you send is priced individually at the authentication rate — one of the lower rates on the card. The old 24-hour window still exists, but it is a free customer-service window for replying to inbound messages, not a billing unit, so it does not change what an OTP costs. Through InfiQ you pay Meta's live authentication rate plus InfiQ's transparent ₹ platform pricing, quoted ex-GST, with no surprises on the invoice. Because OTPs are short and high-intent, they usually pay for themselves in reduced failed logins and fewer support tickets from locked-out donors and volunteers.
- Authentication rate, per delivered message
- 24-hour window is a free service window, not a billing unit
- Meta live rate card + InfiQ transparent ₹ pricing, ex-GST
Like this template? Send it live in 24 hours.