Broadcasts and Automations now show where to recharge or pay for your WhatsApp messages. When a message fails because of a wallet or payment problem, the conversation shows a clear alert with links to fix it.
WhatsApp charges a fee for each template message. Where you pay depends on how your number is connected, and merchants often could not tell. Now the billing details sit on the pages where you send messages, and failed sends point you to the fix.
Numbers connected through Gupshup. The Broadcasts and Automations info bar shows your Gupshup wallet balance, a refresh icon, an info icon that explains what the wallet pays for, and a Recharge link. A low-balance banner also tells you when the balance is low, and the publish step for a broadcast shows your balance before you publish. The explainer says that message fees come out of your Gupshup wallet, that messages stop sending until you recharge, and that the minimum recharge is $10.
Numbers connected directly to Meta (Cloud API). There is no wallet. The info bar shows WhatsApp Billing (Meta) with an explainer, a View Usage link and an Add a payment method link. Both links open WhatsApp Manager, where Meta charges the card you added. You need admin or finance access in Meta to change it.
When a send fails. If a message was not sent because the Gupshup wallet balance was too low, or because Meta could not charge the payment method, the conversation shows a red alert. It says what happened and links to Recharge (Gupshup) or to Add a payment method and View Usage (Cloud API). Agents also see a line asking them to ask their admin to recharge the wallet or update the payment method, so they know who can fix it.
No setting needs to be turned on. For how WhatsApp pricing works and who you pay, see the related guide Meta Pricing - WhatsApp API Pricing Guide.
