On this page
Error 141006 means Meta has no working payment method on your WhatsApp Business Account, so it will not deliver any message you start yourself, and from 1 October 2026 it also limits replies. Error 141010 is a different problem that shows up beside it: your business has not completed Meta's business verification. Both are fixed in your own Meta account, by an admin of the business, and neither is a VGraple CRM charge.
Symptom
Broadcasts, template sends, reminders and follow-ups fail or never leave, while messages from customers still arrive normally. On the number's channel card in Settings, then Channels, then WhatsApp, VGraple CRM shows the number as blocked or limited, and names the reason in plain words: no working payment method (141006), a business that is not verified (141010), or both. Individual messages may show Meta's own payment error, 131042, instead.
Receiving is unaffected. Meta does not charge for messages sent from a customer to a business, so a missing payment method cannot stop them arriving.
What is Meta's documentation for these codes?
Meta documents error 131042, and it does not document 141006 or 141010.
So the meanings of 141006 and 141010 below are what we observe in the account status Meta returns for numbers connected to VGraple CRM, not definitions from Meta's documentation. We have seen both on live accounts, and the reasons they report are consistent from one account to the next.
Which code is which?
| Code | What it reports | Who fixes it | Effect |
|---|---|---|---|
| 141006 | No working payment method on the WhatsApp Business Account | An admin of your business, in Meta billing | Meta will not deliver messages you start; replies limited from 1 October 2026 |
| 141010 | The business portfolio has not passed business verification | An admin of your business, in Meta Business Settings | Lower limits on how many people you can start conversations with |
| 131042 | Meta's documented payment error on a message | The same admin, in billing | That message fails |
If you were told that 141010 is also a payment problem, that is not what we see. Adding a card clears 141006 and leaves 141010 in place, and the reverse. Both can be present at once, which is common on new accounts.
Why does Meta require a payment method?
Meta bills message charges to a payment method attached to the WhatsApp Business Account that owns the number. Without one, Meta has nowhere to bill the messages it would deliver, so it refuses to deliver the ones that cost money. That includes every template: marketing, utility and authentication templates are all messages you start.
The payment method is a requirement on the account. It is not a bill for anything yet. You pay only for the messages Meta charges, at Meta's published rates, and Meta decides which messages those are. Our explainer on Meta's 1 October 2026 pricing change has the current rules and rates, and Meta conversation charges and billing shows how to estimate a month.
Whose bill is it?
Two companies bill you separately:
- Meta bills message charges to the payment method on your own WhatsApp Business Account, at its published rates. VGraple CRM adds no markup and does not touch this payment.
- VGraple CRM bills only your plan, if you are on a paid one.
Adding a card in Meta's billing is therefore not paying VGraple CRM, and nothing you pay Meta passes through us. Platform fee vs Meta charges sets the two side by side.
What changes on 1 October 2026?
From 1 October 2026 the missing payment method also affects replies. From 1 October 2026 Meta charges for replies too; the first 1,000 each month on each WhatsApp number are free. In practice Meta delivers the first 1,000 replies a month on each business phone number, then stops delivering replies from that number until a payment method is added.
That means an automatic reply or a reply typed in the VGraple CRM inbox is the thing that fails first for an account with no payment method, while inbound messages keep looking healthy. If you use flows, AI replies or sequences, check them before the change.
Note
If your number runs in coexistence mode and every reply is sent by hand from the WhatsApp Business app on your phone, nothing you do today changes. Messages sent from that app stay free and keep appearing in VGraple CRM. What stops is anything VGraple CRM sends itself.
Each number's card in Settings shows free replies used this month out of 1,000, and warns when the account has no payment method.
Fix error 141006
- Sign in to Meta Business Suite as an admin of the business that owns the WhatsApp Business Account, and open Billing and payments.
- Add a credit or debit card as a payment method for the WhatsApp Business Account behind this number. If your business has more than one WhatsApp account, choose the right one.
- Come back to VGraple CRM and press Check again on the channel card. Our in-app guidance says Meta can take up to an hour to lift the block after the card is accepted, though Meta does not publish a fixed time.
- If Meta declines the card or the option is missing, message us from Support inside VGraple CRM with a screenshot, and we will raise it with Meta as a Tech Provider.
Meta's own documentation notes that the common causes behind its 131042 error are an unattached payment account, a credit line over its limit and a currency or timezone that is not set. If a card is already on file and you still see the block, check those three first.
Fix error 141010
Business verification is a separate process with its own steps, and it does not need a card. Start it in Meta Business Settings under your business information, then follow Meta's prompts. Meta usually asks for a registration document and an address document in the business name. Review time is Meta's, and we cannot shorten it. The full walkthrough is in Meta business verification, and the effect on how many people you can message is in Messaging tiers and limits.
Start verification before you need the higher limits. It takes longer than adding a card.
What to send us
If an admin has added the card or started verification and the status does not change, message us from Support inside VGraple CRM with:
- A screenshot of the channel card showing the reason.
- The number in full international format.
- The name of your Meta business portfolio.
We can see what Meta returns for the account and raise it with Meta. We cannot add a payment method for you, we cannot see your card, and we cannot override Meta.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Templates and broadcasts fail, replies still go out | No payment method (141006) before the 1 October 2026 change | Add a card in Meta billing |
| Replies stop part way through a month | The month's reply allowance is used and there is no payment method | Add a card; see the pricing explainer |
| Card is on file but the block remains | Payment account not attached, credit line over limit, or currency not set | Check those in Meta billing |
| Can send but only to a few hundred people | Business not verified (141010) | Start business verification |
| Inbound messages arrive but nothing leaves | Automations sending through the platform, blocked by the account | Fix the block, or pause the automation |
Prevention
Add the payment method when you connect a number, not when the first broadcast fails. Keep it current, since Meta's payment error covers card problems as well as a missing card. Give at least two admins access to billing so a lapsed card is never waiting on one person. Check the number's card in Settings once a month for how much of the reply allowance is used and for any warning, and read Channel health for how the other blockers are reported.