> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp authentication templates for passcodes

> How WhatsApp authentication templates send passcodes: fixed wording, copy code, one-tap and zero-tap buttons, time-to-live, and sending from Flowella.

An authentication template sends a one-time passcode, for sign-in, account recovery or confirming a transaction. It's the only category allowed to carry a passcode, and the strictest: the wording is fixed by Meta, you add only the code and optional security and expiry lines, and the message includes a button that copies or fills in the code.

> [!NOTE]
>
> **In Flowella.** Partly supported. Flowella can send authentication templates through the [Flowella API](https://knowledge.flowella.io/hubspot/workflows/authentication-otp.md), with a different code for each recipient. Flowella's editor can't add passcode buttons, so create the template in WhatsApp Manager. A HubSpot workflow can't send passcodes.

## What the message contains

| Part | Content | Can you change it |
| - | - | - |
| Body | Meta's preset text: the code, followed by "is your verification code", translated into the template's language | Only the code |
| Security line | "For your security, do not share this code." | On or off |
| Expiry line | "This code expires in N minutes", from 1 to 90 minutes | On or off, and the number of minutes |
| Button | Copy code, one-tap autofill or zero-tap | The type, and for one-tap the app details |

Authentication templates can't contain links, media or emojis, and each variable is limited to 15 characters. Use only digits and letters in the code.

## Button types

| Type | How it works | Works on |
| - | - | - |
| **Copy code** | The person taps the button, WhatsApp copies the code, and they paste it into your app or website | Any phone, with no work on your side |
| **One-tap autofill** | The person taps the button and WhatsApp hands the code straight to your Android app | Android, with changes to your app |
| **Zero-tap** | WhatsApp passes the code to your Android app without a tap | Android, with changes to your app and Meta's zero-tap terms accepted |

On iOS 26 and later, iOS offers the code as a keyboard suggestion from the notification, for every authentication template, with no work on your side. Earlier iOS versions don't autofill, so copy code is the safe choice when you don't build a native Android app.

> [!WARNING]
>
> If your Android app starts the one-tap or zero-tap handshake with `PendingIntent`, move to Meta's OTP Android SDK before 31 January 2027, when Meta retires the `PendingIntent` method.

## Linked devices

WhatsApp delivers authentication messages only to the person's main phone. On linked devices, such as WhatsApp Web or a tablet, the message is hidden and the person is asked to check their phone. You can't turn this off.

## Time-to-live

| | Value |
| - | - |
| Meta's default | 10 minutes. Templates created before 23 October 2024 default to 30 days. |
| Range you can set | 30 seconds to 15 minutes |

Set the time-to-live no longer than your code is valid, so nobody receives a code that has already expired. Flowella has no time-to-live setting. If you need a custom value, set it on the template in WhatsApp Manager.

## Price

Authentication messages are charged per delivered message, with [volume tiers](https://knowledge.flowella.io/whatsapp/pricing/whatsapp-pricing.md#volume-tiers-for-utility-and-authentication). In some markets, Meta charges a higher **authentication-international** rate when an eligible business sends codes to numbers in that market. See [WhatsApp pricing](https://knowledge.flowella.io/whatsapp/pricing/whatsapp-pricing.md).

## Create one in WhatsApp Manager

**1. Start a template**

In [WhatsApp Manager](https://business.facebook.com/latest/whatsapp_manager/message_templates), click **Create template** and choose **Authentication**. You can also start from an authentication template in Meta's library.

**2. Choose the options**

Choose the button type, and turn on the security line and expiry line if you want them. For one-tap or zero-tap, add your Android app's package name and signature hash.

**3. Submit**

Choose the languages and submit. Meta writes the wording, so review is usually quick.

The template then appears on Flowella's **Templates** page, ready to send through the API.

## Send passcodes from Flowella

Your app creates the code, stores it with an expiry, and calls `POST /v1/templates/send` with the code as the body variable and the button value. Flowella refuses a code longer than 15 characters before it reaches Meta. For a full walkthrough with resend and lockout rules, see [Send one-time passcodes](https://knowledge.flowella.io/hubspot/workflows/authentication-otp.md).

## Good practice

* **Confirm the number first.** Make sure the WhatsApp number belongs to the person before you send a code to it.
* **Tell people the code is coming on WhatsApp**, especially if you also offer SMS or email.
* **Show that you received it.** When the person pastes the code, or your app receives it, confirm on screen.
* **Don't send codes in marketing or utility templates.** Meta rejects templates that carry passcodes in the wrong category, from the first day of the following month. See [Template categories](https://knowledge.flowella.io/whatsapp/templates/template-categories.md#when-meta-changes-a-category-after-approval).

## Related

> [card] [Send one-time passcodes](https://knowledge.flowella.io/hubspot/workflows/authentication-otp.md)
>
> The Flowella API walkthrough.

> [card] [Template library](https://knowledge.flowella.io/whatsapp/templates/template-library.md)
>
> Meta's ready-made templates.

> [card] [Template fundamentals](https://knowledge.flowella.io/whatsapp/templates/template-fundamentals.md)
>
> Names, languages, statuses and limits.

> [card] [WhatsApp pricing](https://knowledge.flowella.io/whatsapp/pricing/whatsapp-pricing.md)
>
> Authentication rates and the international rate.

Checked against Meta's documentation on 18 November 2026: [Authentication templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/authentication-templates/authentication-templates), [Template categorization](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization) and [Time-to-live](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/time-to-live).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.