Error 131042 is the one WhatsApp error that stops your messaging for reasons that have nothing to do with your code, your templates, or your recipients. Meta documents it as "Business eligibility payment issue," describing it as an error related to your payment method, with an HTTP status of 400 and a recommended action of verifying that billing setup is correct — naming the common issues as a missing payment account, an over-limit credit line, or missing timezone and currency settings (Meta for Developers, WhatsApp error codes reference, retrieved 2026-08-20).
That list is unusually specific for a Meta error description, and it is worth taking at face value: those four things are the causes, and three of them are configuration rather than money.
The version that catches growing businesses is the credit line. Everything works for months, volume rises, and sending stops mid-campaign because a spend limit nobody set deliberately has been reached. This guide covers each cause and the monitoring that prevents a billing outage. For the wider failure surface, our WhatsApp Business API error codes reference indexes the rest.
The Four Causes Meta Names
Cause | What it looks like | Fix |
|---|---|---|
No payment account | New WABA, worked in testing, fails on first real send | Add a payment method to the business account |
Credit line over limit | Worked yesterday, stopped mid-campaign | Raise the spend limit or settle the balance |
Missing timezone | Billing configured but sending still blocked | Set the account timezone |
Missing currency | Same signature as timezone | Set the account currency |
Missing payment account
The most common cause for a new WhatsApp Business Account, and the reason it surprises people is that a great deal of the integration works without billing configured. You can register a number, create templates, get them approved, and send to test recipients. Then the first real send fails.
The fix is adding a payment method to the business account in Meta Business Manager. What is worth noting operationally is who does it: this usually sits with finance rather than with the engineer holding the error, which is why it becomes a multi-day blocker in organisations where those people have never spoken. Identify the person who can add a payment method before you need them.
Credit line over limit
This is the one that takes down a working programme, and it has a distinctive signature: everything was fine, nothing changed in your code, and sends stopped part-way through a campaign.
Meta accounts carry a spend limit. As messaging volume grows, that ceiling gets reached — often during the exact campaign that made volume grow. Because the limit was set at account creation and nobody has looked at it since, it is invisible until it bites.
Two things make this manageable. Monitor spend against the limit as an operational metric, with an alert at a threshold well below the ceiling, not at it. And understand your cost drivers, because they determine how fast you approach it. Under the per-message pricing Meta adopted on 1 July 2025, all marketing templates are charged, utility templates are free inside an open customer service window and charged outside it, and non-template messages inside an open window are free (Meta for Developers, Pricing, retrieved 2026-08-20). A programme that reopens conversations and replies inside the window burns through a credit line far more slowly than one that broadcasts marketing templates — which is covered in error 131047 and the 24-hour window.
Our guides to WhatsApp API pricing and the January 2026 pricing update cover current rates by category and market.
Missing timezone and currency
These two are pure configuration, and they are the least intuitive of the four because a valid payment method is already on file. Billing cannot be computed without knowing which currency to charge in and which day boundary to bill against, so sending is blocked until both are set.
The signature is a business that has added a card and still cannot send, with no obvious billing problem visible. Check both fields in the business account settings before assuming something more complicated is wrong.
What To Do When It Hits
1. Stop the sender. Retrying does nothing — the block persists until billing is resolved, and repeated attempts against it only add rate limit pressure. Pause and hold messages in a durable queue so nothing is lost.
2. Check all four causes in Meta Business Manager, in the order above. Payment method present? Spend limit reached? Timezone set? Currency set?
3. Escalate to whoever owns the payment method. This is almost never the person who found the error. If the cause is the credit line, the request is either a limit increase or a settlement, and both need finance.
4. Protect transactional traffic while you resolve it. This is the decision that separates a billing incident from a customer-facing one. Order confirmations and OTPs matter more than a promotional campaign. If those flows run through the same queue with no prioritisation, a billing block takes down both. Businesses running separate numbers for transactional and promotional traffic have more room here, though a payment problem at account level affects everything on that account.
5. Then fix the monitoring, because the incident revealed you had none.
Preventing a Billing Outage
Error 131042 is unusual in this cluster: it is entirely preventable, and preventing it is an operations task rather than an engineering one.
Give the credit line a named owner and an alert. Spend against limit, checked automatically, alerting at a comfortable margin below the ceiling. This is the single highest-value control, because the credit line is the cause that hits established programmes rather than new ones.
Complete billing configuration during onboarding, not at launch. Payment method, timezone, and currency all set and verified before the first real send, alongside display name approval and number registration. These are lead-time items that share a habit of being discovered on launch day.
Forecast spend before a volume step-change. A campaign that will triple your monthly message volume should trigger a limit review beforehand. The cost model makes this calculable: count marketing templates separately from utility templates sent inside an open window, because only one of them is charged.
Alert on 131042 as a high-severity event. Like error 190, it is binary — it affects everything on the account or nothing. Any percentage-based error-rate threshold will page you long after every message has already failed.
Do not let a payment card expire quietly. A card that expires takes the account from working to blocked with no code change and no warning, which is the same failure shape as the credit line and equally avoidable with a calendar reminder.
Frequently Asked Questions
What does WhatsApp error 131042 mean?
There is a problem with your payment method or billing setup that makes the business ineligible to send. Meta documents it as "Business eligibility payment issue" with HTTP status 400 and recommends verifying billing setup, naming the common issues as a missing payment account, an over-limit credit line, or missing timezone and currency settings.
Why did my WhatsApp messages suddenly stop with a billing error?
The most likely cause is the credit line reaching its limit. Meta accounts carry a spend ceiling, and a growing programme reaches it during the campaign that grew it with no code change and no warning if nobody monitors spend. An expired payment card produces the same sudden pattern.
I have added a payment method and it still fails. Why?
Check timezone and currency in your business account settings. Meta names both among the causes, and billing cannot be computed without knowing which currency to charge in and which day boundary to bill against. A valid card with these fields blank still blocks sending, which is why this case feels inexplicable.
Should I retry after error 131042?
No. The block persists until the billing problem is resolved, so retries cannot succeed and only consume rate limit budget. Pause the sender, hold messages in a durable queue, escalate to whoever owns the payment method, and resume once billing is confirmed fixed.
Does error 131042 affect transactional messages too?
Yes. It is an account-level eligibility block, so it stops order confirmations and one-time passcodes alongside marketing campaigns. That is what makes credit line monitoring worth doing properly — a promotional overspend that silently takes down your OTP delivery is a customer-facing incident, not a finance one.
Monitor the Ceiling, Not the Error
Error 131042 is the least technical failure in this cluster and one of the most disruptive, because it stops everything on the account at once and the fix usually sits with a team that has never seen a WhatsApp error.
Three things prevent it entirely. Complete billing configuration — payment method, timezone, currency — during onboarding rather than at launch. Put an alert on spend against your credit line with real headroom. And name the person who can raise a limit or settle a balance before you need to find them at 9pm mid-campaign.
Want billing and account health watched rather than discovered? Helo.ai is a Meta Partner and Google RCS Anchor Partner of the Year, monitoring spend, account eligibility, and message cost mix for enterprise WhatsApp programmes. Talk to an expert.
Next: error 131047 for the free customer service window that lowers your spend rate, or error 131037 if display name approval is also outstanding.
