WhatsApp API Error 131042: The Eight Billing Failures Hiding Behind One Message Error
Production messaging stops. Every send returns the same code. The number is still connected, the templates are still approved, the webhook still fires — and nothing reaches a single customer.
Most teams read 131042 as ‘add a card and you're done'. Meta's own error reference does not say that. It lists eight separate conditions under one code, and the payment method is only one of them.
What Meta actually documents
On the WhatsApp Cloud API error reference, 131042 carries a deliberately broad description:
There was an error related to your payment method.
Meta for Developers — WhatsApp Cloud API error codes (updated 18 June 2026)The documented remedy is equally broad: verify that you have set up billing correctly. That is the entire official instruction. Meta then lists the common problems behind the code — and this is where 131042 stops being a billing error and reveals itself as an account-configuration error wearing a billing error's clothes.
The eight documented causes
These are the conditions Meta lists under 131042. Only the first three are anywhere close to what most teams assume the error means.
A payment method can exist inside the business portfolio and still not be attached to the WABA that is actually sending.
Nothing is misconfigured. The account has simply consumed its allocation, and every send fails until that changes.
A credit line that was never attached, or is no longer active, reads identically to a missing card from the API side.
The WABA no longer exists. The API still answers with a billing-shaped error rather than a clear account-state error.
An enforcement or integrity action against the account surfaces here too — which is why treating 131042 as a finance ticket wastes days.
A field almost nobody associates with sending messages. Left empty, it blocks delivery under a billing code.
Same category of failure. And once a line of credit is attached, currency and timezone can no longer be edited on that WABA.
The partner relationship that authorises you to message on a client's behalf was never completed, or was rejected.
The trap: five of these eight causes have nothing to do with money. A team that opens a billing ticket, adds a second card and waits will still be down — because the actual cause was an unset timezone, a suspended WABA, or a partner request that was declined weeks earlier.
Why this is harder than it looks
The error does not tell you which of the eight it is
Meta returns one code with one generic string. There is no subcode that narrows it, and no documented diagnostic endpoint that says ‘it is cause 6, not cause 2'. Isolating the real cause means checking each layer independently.
Billing lives in three different places
The payment method sits at one level, the credit line allocation at another, and the attachment to the specific WABA at a third. All three can look correct in isolation while the chain between them is broken.
Your billing model depends on who onboarded you
Meta documents that Solution Partners hold a line of credit and share it with the clients they onboard, while businesses onboarded by Tech Providers must add their own payment method to their WhatsApp Business account. Diagnosing 131042 without first establishing which of those two models applies produces the wrong answer every time. This is the same partner-type distinction covered in our guide to Embedded Signup and Tech Provider onboarding.
Some fields become permanent
Meta states that a WABA's time zone and currency cannot be edited once a line of credit has been attached, and that credit lines cannot be changed after being attached to a WABA — a different credit line requires a new WABA. Fixing the wrong field in the wrong order can leave you needing to rebuild the account rather than correct it.
Reseller and agency setups multiply the surface
When a partner shares a credit line with a client, Meta documents that the partner becomes the Bill To Party and is liable for that client's spend — and that when a WABA is unshared, all messaging for that WABA is blocked. In a multi-client estate, one relationship change can take several accounts offline at once.
How the diagnosis actually runs
This is the shape of the work, not a set of instructions. Each step below assumes access, correct roles and the right token type — and each one can end the investigation on its own.
Establish the account model first
Before touching billing, determine whether the WABA is funded by its own payment method or by a partner's shared line of credit. The two models fail in completely different places, and the fix for one is meaningless in the other.
Rule out account state before money
Deleted and suspended accounts both return 131042. Confirming the WABA is alive and unrestricted takes minutes and removes two of the eight causes immediately — and if it is a suspension, the entire remediation path changes.
Verify the funding chain end to end
Meta documents a verification procedure comparing the credit allocation's receiving credential against the WABA's primary funding ID. Matching values confirm the credit line reached the right account. Anything else means the chain is broken somewhere upstream.
Audit the configuration fields nobody checks
Timezone and currency are the two quiet failures. They are trivially fixable while they are still editable — and effectively frozen once a credit line is attached.
Confirm the On Behalf Of relationship
If you message for someone else, the MessagingFor request must be accepted, not merely sent. A pending or declined request looks exactly like a payment problem from the API.
Errors that get mistaken for 131042
Several other codes stop messages in ways that feel like a billing outage. Chasing the wrong one costs days:
- 130497 — the WhatsApp Business Account is restricted from messaging to users in certain countries. Policy, not payment.
- 131048 — restrictions on how many messages can be sent from the number, often after prior messages were blocked or flagged. This is a quality and reputation issue, covered in our post on the WhatsApp Business API quality rating.
- 131047 — more than 24 hours have passed since the recipient last replied, so a template message is required instead.
- 131026 — the message could not be delivered to that particular recipient at all.
Cost is a separate question from the ability to send. If the underlying concern is what the traffic will cost rather than why it stopped, start with WhatsApp Business API per-message pricing.
What the outcome looks like
A resolved 131042 is not ‘the card went through'. It is a funding chain that is verifiably attached to the correct WABA, an account confirmed to be active and unrestricted, configuration fields set correctly before they lock, and — where a partner is involved — a completed messaging relationship. After that, sending resumes on a correctly configured account rather than on hope.
Meta publishes no timeframe for how quickly a billing correction takes effect, and no statement that messaging resumes automatically once payment is fixed. Any source quoting you a number for either is not quoting Meta.
Where support helps
Most of the time lost to 131042 is not spent fixing it. It is spent looking in the wrong layer — finance instead of account state, the portfolio instead of the WABA, the payment method instead of the partner relationship. Working through the eight documented causes in the right order, with the right access and without making a permanent field change by accident, is what turns a multi-day outage into a short one.
If your production messaging is blocked and you need structured diagnosis and setup support across WhatsApp Business Platform billing, account state and partner configuration, see our services.
Every technical detail above is drawn from Meta's official WhatsApp Business Platform documentation on developers.facebook.com as published at the time of writing. Platform behaviour changes; always confirm against the current documentation. This site is independent and not affiliated with, endorsed by, or partnered with Meta, WhatsApp or any platform mentioned. No specific outcome can be guaranteed.