One API for authentication, WhatsApp & SMS.

Delivery is decided less by the template than by the number it leaves from. Our router pins each recipient to the WABA that last delivered to them, on a rolling 30-day window — rotating senders for the same person trains Meta to read the traffic as spam and drags the whole account down with it. A recipient with no history goes to the sender you nominate; beyond that, load is spread deterministically across your pool so no single number carries a campaign alone. Sender and template quality are re-read between waves, and a send halts against a number that has gone RED rather than pushing through it.

Real costs in India depend on your volume, channel mix, template categorization breakdown and fallback patterns. A static price list would either mislead you or price you well above the deal we can actually offer. Pricing is set by your monthly volume, and we guarantee it will be lower than any rate available to you in the market — compare us against any competitor. Aarav confirms your commercials within 24 hours of your application.

DLT (Distributed Ledger Technology) is the TRAI-mandated registry every Indian SMS sender, header and template has to be enrolled in. You don't have to handle it — our team takes care of DLT registration, sender ID and template approvals end-to-end, usually within 24 hours. Included on every plan, no extra charge.

No. WhatsApp Business API messages run on Meta's platform, so they're outside TRAI's DLT scope — only SMS needs DLT. That makes WhatsApp OTP a fast way to start sending verifications without waiting for sender-ID approval. We still recommend SMS as a fallback channel for unreachable numbers.

WhatsApp OTP sends the verification code to the user’s WhatsApp inbox instead of SMS. On Android and iOS our SDK auto-reads it, so the user rarely types anything. In India WhatsApp typically lands faster and cheaper than SMS and sidesteps SMS-pumping fraud — with SMS kept as the automatic fallback for users without WhatsApp. Both run on the same Meta Cloud API and the same QuickAuth verify flow.

Yes. On Android we use the SMS Retriever API (app-hash appended to the OTP message; no SMS-read permission needed). On iOS we set UITextContentTypeOneTimeCode so the keyboard auto-suggests the code from the SMS. For WhatsApp OTPs we use the message-format hint that triggers Android's system OTP-autofill prompt. Reduces friction at the verification step — fewer drop-offs between code-sent and code-entered.

Yes — that’s the point. QuickAuth runs auth (WhatsApp OTP, SMS OTP, multi-channel routing) and bulk WhatsApp business messaging (utility, marketing) on the same WABA, the same dashboard and the same template-categorization pipeline. Deliverability monitoring, template approvals and INR billing roll up across both — instead of stitching an OTP vendor, a marketing tool and a WhatsApp BSP into one stack.

Four overlapping layers. (1) suspicious-prefix scoring — a maintained block-list of MNC and country prefixes commonly used for artificial traffic. (2) velocity and ratio heuristics — abnormal request-to-verify ratios on a number range get throttled. (3) per-IP and per-device quotas with graceful back-off. (4) optional device fingerprinting at the request step. The bulk of pumping attempts get blocked at the request step, before any OTP fires and any cost is incurred.

Yes. The official SDKs — web (npm @quickauth/web), React Native, iOS (CocoaPods + SPM), Android (Maven Central in.quickauth:sdk) and Flutter (pub.dev) — are published and installable now. The platform is in production and the v1 API is generally available — most teams wire the SDK on day one and manage templates from the dashboard.

Mumbai (ap-south-1). Phone numbers are hashed; OTPs are wiped 5 minutes after verification. SOC 2 Type II and aligned with the DPDP Act 2023.