Settings
Configure Meta WhatsApp Cloud API Sending
Cloud mode sends through the shop's Meta WhatsApp Business setup instead of a locally linked phone. Credentials and approved templates must match the Meta app exactly.
- Menu path
- Manage -> Messaging -> SMS & WhatsApp Providers -> WhatsApp
- Verified from
- Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence
frontend/modules/settings_write.html messaging_wa_cloud, frontend/static/script/js/modules/js/messaging.js, api/src/services/messaging.service.js, api/src/services/whatsapp-cloud.service.js
Required Meta Values
| Posnic field | Get it from | Purpose |
|---|---|---|
| Access token | The shop's Meta app / WhatsApp Business configuration | Authorizes the send request; Posnic masks it after save. |
| Phone number id | WhatsApp API setup for the sending number | Identifies the registered sending number; it is not the visible phone number. |
| API version | The version supported by the Meta app, for example v20.0 | Selects the Graph API contract used for sending. |
| Template name | An approved Meta message template | Required for template-controlled marketing messages. |
| Template language | The exact approved template language, for example en_US | Must match the template variant approved in Meta. |
Configure and Prove Cloud Sending
- Sign in as a super admin and open Manage -> Messaging.
- Under WhatsApp, turn on Enable WhatsApp.
- Choose Meta WhatsApp Cloud API.
- Paste the access token and enter the phone number ID.
- Enter the API version and the exact approved template name and language used by the shop.
- Click Save; a stored access token later appears only as a saved-secret placeholder.
- Enter a controlled destination with country code and click Send WhatsApp test.
- Confirm both phone delivery and the Meta delivery/error record before enabling operational sending.
Safe Credential Changes
- Leaving the masked access-token field blank keeps the saved token; enter a value only when rotating it.
- A new token does not repair a wrong phone number ID, API version, template name or language.
- Do not paste a personal temporary token into a production shop unless its lifetime and permissions are understood.
- When Meta rejects a template, compare the exact approved name, language and message purpose in the Meta account.
- The public demo does not send outbound WhatsApp messages; use the shop's own tenant for the final proof.