OTP Authentication WhatsApp Template for Fintech
A ready-to-use, Meta-compliant WhatsApp one-time-passcode template built for Indian fintech — lending, neobanking, UPI, wallets, broking and insurance. It ships in the Authentication category with a secure copy-code button, the two variables you actually need, and the approval detail Meta looks for. Copy it below, drop in your OTP and brand name, and you can be delivering verification codes over WhatsApp within a day of template approval through InfiQ.
Variables
{{1}}= 482913{{2}}= PayNova
Verified business
10:24
Preview · as customers see it
When to use this OTP template
Reach for this template at any moment your fintech app needs to prove the person is who they claim to be: new-account signup, login on a fresh device, resetting an MPIN or password, adding or changing a bank account or beneficiary, stepping up before a high-value transfer, or re-verifying KYC. WhatsApp is a strong channel for these codes because delivery is confirmed and read rates typically run well above SMS, which matters when a customer is stuck at a checkout or a fund-transfer screen. Because it sits in the Authentication category, the template is purpose-built for exactly this — a short, secure code with a one-tap copy button — and cannot carry any promotional content.
- New signup and device-login verification
- MPIN / password / PIN reset flows
- Adding a beneficiary or changing bank details
- Step-up authentication before a large transfer
- Re-verifying KYC or contact details
Personalising the variables
Keep it lean — Authentication templates are deliberately minimal, so there are only two variables to fill. {{1}} is the numeric code your system generates for that session, and {{2}} is your brand name so the customer instantly recognises who the code is from. Do not try to inject the customer's first name, an offer, or a product line here; the Authentication category forbids marketing language, and adding it is the fastest route to rejection. Pass the code from your OTP service to InfiQ's API at send time, set a validity that matches your backend (10 minutes is a sensible default), and let the copy-code button handle the rest so the user never has to manually type digits.
- {{1}} — the one-time code, e.g. 482913
- {{2}} — your brand name, e.g. PayNova
- No names, offers or product mentions in this category
- Match the stated validity to your server-side expiry
Getting it approved by Meta
Submit this in the Authentication category, not Utility or Marketing — miscategorising an OTP template is the single most common reason these get bounced. Keep the wording to the standard security-code pattern shown above, attach the copy-code button, and avoid links, emojis, promotional phrasing or extra variables. Meta reviews Authentication templates quickly, usually within a day, and once approved you can send immediately. If you edit the copy later, keep it inside the category rules and re-submit for a fresh review. InfiQ's template management screen validates category, variable count and button type before you submit, so you catch formatting issues before Meta ever sees them.
- Choose Authentication as the category
- Use the copy-code button, no URL or call buttons
- No links, emojis or marketing wording
- Re-submit for approval after any wording change
What it costs to send
Since 1 July 2025 WhatsApp bills per delivered message by category, so every OTP you send is charged at Meta's Authentication rate for India — there is no per-conversation bundle any more and the 24-hour window is a free service window, not a billing unit. Authentication is one of the lower-priced categories, which makes WhatsApp OTP economical at scale for high-volume login and transaction flows. Through InfiQ you get transparent ₹ pricing (ex-GST), billed on delivery, so a spike in verification traffic maps cleanly to a predictable line item. Use the cost calculator to slide your monthly OTP volume and see the delivered-message total.
- Billed per delivered Authentication message
- No per-conversation charge and no free-window billing
- Transparent ₹ pricing, ex-GST
- Cost scales linearly with verification volume
Variations you can copy
The base template covers most flows, but a few tweaks help you fit specific journeys and audiences. A shorter build strips the security note for markets where you want the tersest possible message; a regional-language version in Hindi, Tamil, Telugu or your customers' primary language lifts comprehension and trust for verification, which is one place clarity really counts. You can also register the same template in multiple languages under one name so WhatsApp serves the right one automatically. Whatever you change, it must stay inside the Authentication category — any incentive or promotional angle belongs in a separate Marketing or Utility template, not here.
- Shorter: code + validity line only
- Regional language: Hindi or your customers' language
- Multi-language registration under one template name
- Keep every variant strictly Authentication-only
InfiQ vs SMS OTP
| InfiQ | SMS OTP |
|---|
Like this template? Send it live in 24 hours.