🌐 Bahasa Indonesia

WhatsApp OTP for your application — two endpoints, done.

In Indonesia, WhatsApp is the messaging app people actually keep open — the annual We Are Social & DataReportal surveys consistently rank it first here, used by roughly 9 in 10 internet users. Your verification codes arrive in an app people open every day. Enable it once in the dashboard, then your application calls two endpoints — send code and verify code. Random code generation, hashed storage, expiry, attempt limits and resend throttling are handled by us. You pay Meta's authentication message rate, directly to Meta, with no markup.

Why OTP over WhatsApp

📱

The app is already on their phone

WhatsApp is the most widely used messaging app in Indonesia — roughly 9 in 10 internet users are on it (We Are Social & DataReportal). Your users install nothing.

📬

Delivery you can actually see

Codes arrive in an app people open many times a day — and delivered/read status comes back to you through webhooks instead of being guessed at, as with SMS.

🔐

Secure by default

Codes are never stored in the clear (hashes only), they expire automatically, attempts are limited and resends are throttled — without you writing any of that logic.

Questions about this

Do I need a special template?

The authentication template is prepared automatically when the feature is enabled — you do not write or submit anything to Meta.

What does it cost?

No extra charge from WACO — OTP is part of the subscription. Each OTP message is charged at Meta authentication message rates, paid directly to Meta.

More questions? See the WACO guides or say hello through the chat bubble.

Start today

All of this is included in one US$20/month subscription.