🛠️ How-to tutorials

WhatsApp error 131042: why your messages stopped sending

Updated 2026-09-24 · 5 min read · By the Convo360 team

In short

Error 131042 is Meta refusing to send because of a billing problem on the WhatsApp Business Account: usually no payment method, a declined card or an unpaid balance. Inbound messages keep working, which is why it is so often mistaken for a platform fault.

Key takeaways

131042 is always billing. Nothing in your bot configuration causes it.
Inbound continues working, which misleads almost everyone at first.
Fix it in Meta Billing Hub, not in your messaging platform.
Do not confuse it with 131026 or 131047, which mean completely different things.

The symptom that sends people down the wrong path

A business reports that its WhatsApp bot has stopped working. Customers are writing in and receiving nothing back. Naturally the first suspicion falls on the platform, the AI key or a recent change to a flow.

What makes 131042 confusing is that inbound is unaffected. Messages arrive, webhooks fire, the bot generates a reply, and the reply fails at the last step. Every dashboard looks healthy because everything up to sending is healthy.

Teams routinely spend an afternoon restarting things, rotating AI keys and re-checking webhook configuration before anybody looks at the actual send error. If outbound is failing while inbound works, check the error code first.

There is a version of this that is worse: the failure begins on a Friday evening. Inbound messages pile up all weekend, your bot dutifully generates replies that never arrive, and customers conclude you have ignored them. By Monday the problem is not the billing error, it is fifty people who think they were snubbed.

What the code means

131042 is Meta declining to deliver for a billing reason on the WhatsApp Business Account. The usual causes, in rough order of frequency:

No payment method attached to the WhatsApp Business Account.
A card that has expired or been declined.
An unpaid balance on the account.
A payment method attached to a different asset in the same Business Manager.
An Indian card without international payments enabled.

None of these are things your messaging platform can fix, because the relationship is between your business and Meta. A provider can tell you what the error means; only you can attach a card.

Note what is not on that list. Nothing about your flows, your AI provider, your webhook configuration or your templates causes 131042. If somebody suggests reconfiguring those, the diagnosis is wrong and the afternoon is about to be wasted.

Fixing it

Open Meta Business Manager and go to Billing. Find the payment settings for the WhatsApp Business Account that owns the affected number, and add or repair the payment method there.

Two checks people skip. First, confirm the method is attached to the WhatsApp Business Account specifically, because one added during ad account setup does not cover WhatsApp. Second, confirm there is no outstanding balance; adding a new card does not automatically settle an old failure.

Delivery usually resumes within minutes of the billing problem being resolved. If it does not, check whether Meta is showing a separate restriction on the account, which occasionally accompanies a long-standing payment failure.

If you are on a BSP rather than direct Cloud API billing, the fix is with them instead: the payment relationship sits between you and the provider, and the same error surfaces when your balance with them runs out. Knowing which model you are on before an incident saves a confusing call.

Errors that look similar and are not

Treating every send failure as a billing problem is its own trap. Three codes get confused with 131042 regularly.

Code	Meaning	What to do
131042	Billing problem on the account	Fix payment in Meta Billing Hub
131026	Message undeliverable to that recipient	Check the number is on WhatsApp and correctly formatted
131047	Outside the 24-hour window	Use an approved template instead
131048	Spam or quality limit reached	Slow down and review message quality

Convo360 treats only 131042 as a billing problem for this reason. If every failed send produced an email telling you to check your card, the one that genuinely mattered would be lost among false alarms from mistyped phone numbers.

Catching it before customers do

The cheapest fix is to never see this code during a busy week.

Convo360 tracks how many of your 1,000 free monthly service conversations have been used on each number and warns you as you approach the limit. Since 131042 most often appears when the allowance runs out on an account with no payment method, that warning is usually the last chance to act before anything breaks.

It also records send failures per channel, so a number that begins failing shows up in channel health rather than only in individual conversations. A quiet Sunday failure is otherwise invisible until Monday morning.

Set up an alert that reaches somebody who can act. A dashboard indicator nobody looks at on a Saturday is not monitoring. An email or a push notification to the person who holds the company card is, and this is one of the few support failures where the fix takes two minutes once the right person knows.

A five-minute prevention routine

Three habits prevent almost every occurrence of this error.

Attach a payment method before you need one, and verify it sits on the WhatsApp Business Account rather than elsewhere in Business Manager. Check the billing status once a quarter, because cards expire quietly and mandates lapse. And tell your finance team what the charge is, since a small foreign debit is exactly the sort of thing that gets queried and blocked with the best intentions.

If you use several numbers, check each one. Allowances and payment settings are per WhatsApp Business Account, so a business can easily have one number working perfectly while another has been silently blocked for a week.

None of this is interesting work. It is, however, the difference between a support queue that runs during your busiest week and one that does not.

When you have fixed it, go back through the conversations that failed during the outage. Convo360 records the failure against each message, so you can find them, and a short apology with the answer they were waiting for recovers most of the goodwill. Silence after an outage costs far more than the outage did.

Step by step

Confirm the codeCheck whether failing outbound messages report 131042 specifically, rather than assuming a billing cause from the symptom.
Open Meta Billing HubIn Business Manager, go to Billing and find the payment settings for the WhatsApp Business Account that owns the number.
Add or repair the payment methodAttach a valid card with international payments enabled, and clear any outstanding balance.
Verify it is on the right accountA method added for an ad account does not cover WhatsApp. Confirm the WhatsApp Business Account itself shows it.
Retest with one messageSend a single outbound message and confirm delivery before assuming the queue has cleared.

Fix a billing block before Monday

Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.

Start 14-day free trial →See pricing

Frequently asked questions

Can my platform provider fix 131042 for me?

No. The billing relationship is between your business and Meta, so only an admin of your Business Manager can attach or repair a payment method. A provider can identify the error and tell you exactly where to go.

Why do inbound messages still work?

Meta charges for delivering messages, not for receiving them, so a billing block only affects sending. That asymmetry is what makes the error look like a bot fault rather than a payment one.

How long does it take to resume after fixing?

Usually minutes. If delivery does not resume within an hour, check whether Meta is showing a separate account restriction, which sometimes accompanies a payment failure that ran for a long time.

Will queued messages send automatically?

That depends on your platform. Convo360 records the failure per message rather than retrying indefinitely, so review recent failed sends after fixing billing and resend anything still relevant.

Does this affect template messages too?

Yes. A billing block stops all outbound delivery, including marketing, utility and authentication templates, which means campaigns fail at the same moment as support replies.