WhatsApp Error 131042: Which of the Eight Causes Is Yours

What does WhatsApp error 131042 actually mean?

Meta gives this code one sentence of description: "There was an error related to your payment method." (Meta — WhatsApp Cloud API error codes). The send failed for a billing reason on the WhatsApp Business Account behind the number — not because of the message, the template, the recipient or the token.

Underneath that sentence Meta lists eight common problems and explains none of them. They are not variations on one theme. Three of the eight are about a payment method that is missing or exhausted, two are about a WhatsApp Business Account that no longer works at all, two are about fields on the account that, on some accounts, cannot be changed after the fact, and one is about an ownership request from a model Meta has since retired. Every vendor helpdesk answers 131042 with "add a card in Business Manager, set it as default, wait 24 hours". For most of the eight causes that advice is either irrelevant or actively impossible to carry out.

The first useful question is therefore not "which card did I attach" but "who is billed for this number's messages". That one fact routes you to a different part of Meta's list, and on two causes it decides whether a fix exists on this account at all.

• What does WhatsApp error 131042 actually mean?
• Which eight causes does Meta list under 131042?
• Why is the on-behalf-of cause a fossil?
• Why does adding a card do nothing on a partner credit line?
• How do you tell which onboarding path your number is on?
• Can a WABA's timezone or currency be corrected in settings?
• Why would a WhatsApp billing fault pause your Meta ads?
• Which cards does Meta take, and what is different in India?
• Where does your platform's invoice end and Meta's begin?
• What changes for 131042 on 1 October 2026?
• In what order should you rule these out?

Which eight causes does Meta list under 131042?

The error-codes page gives them as a bare list, with a pointer to the billing help article and no explanation of any entry. Here they are with what each points at, and who is in a position to clear it.

"Whoever holds the line" is doing real work in two of those rows: on a Solution Partner's embedded signup it is the partner, and on a business that put its WhatsApp Business Account onto its own Meta ads credit line it is you.

Two of these are not billing faults at all. A deleted or suspended WhatsApp Business Account surfaces here because billing is the first thing that fails against an account in that state, which is why 131042 sometimes turns out to be an account restriction wearing a payment error's clothes.

Why is the on-behalf-of cause a fossil?

The eighth entry, "MessagingFor request (On Behalf Of) is pending or declined", points at a model Meta has closed. Its own deprecation notice is unambiguous:

"We have deprecated the On-Behalf-Of ("OBO") account ownership model and replaced it with partner-initiated WABA creation." (Meta — On-Behalf-Of account ownership model deprecation)

The same page dates the close: "September 29, 2025: last day to onboard clients to the OBO model", and "All existing WABAs created under the OBO model should have been transferred to clients by October 1, 2025", with the remainder "auto-migrated in batches through the end of 2025". Meta's WhatsApp Business Accounts reference repeats it flatly — "The On-Behalf-Of WABA ownership model is deprecated and is no longer possible" (Meta — WhatsApp Business Accounts).

So this is not a request to chase. The documented route forward is partner-initiated WABA creation, not a message asking another business to approve something it can no longer approve.

Checked against Meta's documentation on 11 September 2026.

Why does adding a card do nothing on a partner credit line?

This is the single most common wrong answer to 131042, and Meta says so in plain words. Its credit-line help article describes what happens when a business is onboarded through a partner's embedded signup:

"If your business has signed up through the embedded signup flow offered by your Solution Partner, you will automatically be granted access to your Solution Partner's credit line. You will pay the Solution Partner for your WhatsApp usage. The Solution Partner will receive an aggregated invoice to pay Meta. You can't use your own credit line to pay for your WhatsApp usage." (Meta — About Credit Lines for WhatsApp Business Account)

Read the last sentence twice. A business in this position can attach a perfectly valid Visa card to its own business settings and watch 131042 keep returning, because the account is not billed against that card and never was. The card is not rejected; it is simply not consulted.

What is wrong in that case is upstream: the partner's line is over its limit, the allocation against your WABA was never made, or it was revoked. The same article is blunt about what an unpaid line leads to:

"Late payments may be subject to a service charge. If you don't make payment in full by the due date, we may suspend all or part of your access to the WhatsApp Business Platform until you make payment in full in accordance with the Meta Terms for WhatsApp Business." (Meta — About Credit Lines for WhatsApp Business Account)

That suspension is not something your own card can lift. The only questions worth putting to the partner are what your allocation is and whether the line behind it is current.

How do you tell which onboarding path your number is on?

Four arrangements exist in practice, and Meta documents the difference between the two that matter most. The Embedded Signup overview states the rule for whoever built the signup you went through:

"If you are not a Solution Partner, or not partnered with one, the customer must first attach a payment method to their WABA before they can begin messaging." (Meta — Embedded Signup)

And the Solution Partner overview is explicit that a Tech Provider has no credit line to lend:

"Unlike Solution Partners, however, Tech Providers do not have credit lines. Instead, clients onboarded by Tech Providers must provide their own payment method after onboarding is complete." (Meta — Solution Partner)

The tell is cheap: open the account in Meta's own business settings and see whether the payment method shown belongs to you or to another business. If it is a credit line you never applied for, you are on path three, and nothing inside your own billing screen will move the error. What separates those partner tiers, and what each may charge you for, is set out in BSP vs Tech Provider vs Solution Partner.

Can a WABA's timezone or currency be corrected in settings?

Two of Meta's eight causes are "Timezone not set" and "Currency not set", and almost every page ranking for this error tells the reader to go and correct them. On an account with a credit line attached, that instruction cannot be followed. Meta's WhatsApp Business Accounts reference states it directly:

"A WABA's time zone and currency cannot be edited once a line of credit has been attached to it." (Meta — WhatsApp Business Accounts)

And the credit-line management guide closes the other exit:

"Credit lines cannot be changed after being attached to a WABA. If the WABA needs a different credit line, a new WABA must be created and the new credit line can then be attached to it." (Meta — Managing credit lines)

So for this flavour of 131042 on a credit-line account, the documented remedy is a new WhatsApp Business Account. That is not a settings fix; it is a migration, with its own template re-approvals and its own number move — and the strongest argument for checking both fields at the moment a WABA is created, while they are still editable.

Why would a WhatsApp billing fault pause your Meta ads?

Businesses that already run Meta ads on monthly invoicing usually put WhatsApp on the same line, because Meta tells them to. Its credit-line article addresses exactly that case:

"Have a credit line (monthly invoicing) for Meta ads currently. You can't apply for a separate credit line for your WhatsApp Business account(s). You will need to add your WhatsApp Business account(s) to your existing credit line and use this credit line to pay for your WhatsApp usage. If you receive a message or notification in your business portfolio that you have exceeded your credit limit, your Meta ads will be paused." (Meta — About Credit Lines for WhatsApp Business Account)

One shared limit, two products on it. A month of heavy template sending can present first as advertising stopping, and an overspent ad account can present first as 131042 on a send. Nobody writing up this error connects the two, so it tends to get diagnosed twice, by two different people, before anyone notices it is one number over one limit.

If your messages are accepted by the API and simply never arrive, that is a different problem with a different checklist — see the dashboard says connected and nothing is sending.

Which cards does Meta take, and what is different in India?

The self-serve path is narrower than most write-ups admit. Meta's help article on adding a credit card states:

"You can pay for messaging with a credit card via Visa or Mastercard. We currently don't accept American Express or digital payments such as PayPal. Credit card payment method is available if you're located in one of the supported countries." (Meta — Add a Credit Card to Your WhatsApp Business Platform Account)

That is the entire self-serve list: two card networks, no Amex, no wallet, and only in countries Meta supports. Check the brand before anything subtler, because a network Meta does not take and a payment method that was never attached reach the API as the same code.

One thing that reads like a billing fault and is not: Meta charges against a threshold rather than per send. "A payment threshold is an amount that you can spend on your WhatsApp usage before we charge you" (Meta — About the payment threshold for your WhatsApp Business account). A card that has never been charged is not evidence that it was never attached.

For India, what Meta documents is a billing-localisation regime rather than card folklore. Legal entities whose "Sold-to" country is India can only create WhatsApp Business Accounts in INR (Meta — About billing localization in India). The same article states that services billed by Facebook India are subject to applicable GST (18%) for all invoices issued by Facebook India, and, for monthly-invoicing customers, that payment will be strictly by wire transfer to Facebook India's bank account details stated in the invoice — with any payment made to a Meta bank account not affiliated with Facebook India refunded, leaving the customer to re-transfer it. A wire sent to the wrong Meta entity is therefore not a late payment; it is a payment that has to be made again. The migration deadline behind all of this is covered in WhatsApp INR billing: migrate your WABA before 2027.

One correction worth making while we are here, because it appears on nearly every page ranking for this error: "you have not added your tax information" is not one of Meta's eight causes. What Meta actually says is softer and sits in the card-setup article, not the error list — "Note: When you set up the payment method, you may be required to provide your tax information as part of your business information" (Meta — Add a Credit Card to Your WhatsApp Business Platform Account). That is a step you may be asked for. It is not a documented cause of 131042, and promoting it into one sends people to the wrong screen.

Where does your platform's invoice end and Meta's begin?

Most businesses pay two separate bills for one WhatsApp number, and only one of them can produce this error. Meta bills the WhatsApp Business Account for message delivery, against the payment method or credit line attached to it. The software you send with bills you separately, for the software.

On a Tech Provider platform the two cannot merge, because the tier is not permitted to resell Meta's per-message fees — which is why WabaCRM's billing screen shows only the software subscription, and why a workspace with every invoice settled there can still throw 131042 on every send. A paid platform invoice says nothing about the state of your Meta payment method. What Meta charges for, as against what a platform charges for, is set out in is the WhatsApp Business API free? and on our own pricing page.

What changes for 131042 on 1 October 2026?

Today, a broken payment method mostly bites outbound template sends, because ordinary in-window replies cost nothing. Meta's pricing page is explicit on that point: "Non-template messages, which can only be sent within an open customer service window, are free" (Meta — Pricing on the WhatsApp Business Platform).

That ends on a date now three weeks away. Meta's non-template-messages page states:

"Effective October 1, 2026, Meta will charge for service messages, which have not been charged since November 2024." (Meta — Pricing for non-template messages)

The same page removes the usual escape valve for volume: "Volume tiers: None. Meta does not offer volume tiers for service messages."

Two things about that date are widely got wrong. The first is what Meta has not written down. A monthly allowance of 1,000 free service messages per business phone number, charging from the 1,001st, is repeated almost word for word across vendor coverage of this change, usually beside a 30 September 2026 deadline to have a payment method on file. Both Meta pages quoted above were searched on 11 September 2026 for the figure, for the phrase "free service messages", and for that September date. Neither page carries any of them. That is not proof no allowance exists; it is a statement about what is sourceable today, which is the only thing worth budgeting against.

The second is the blast radius. The error-codes page describes the code, not the message categories it is raised against, so Meta does not say whether a free in-window reply can fail this way now. What is checkable is the direction of travel: from October, the category of message that has been free since November 2024 becomes a charged one, and an account that cannot be billed has one fewer thing left that costs nothing. The rest of that change, and the allowance figure we could not source, is covered in service message pricing: what changes on 1 October 2026.

Checked against Meta's documentation on 11 September 2026.

In what order should you rule these out?

The error text is identical for all eight causes, so the only fast approach is a fixed order that eliminates the unfixable cases first.

1. Establish who is billed. Open the account in Meta's business settings and read whether a credit line or your own payment method is attached, and whose it is. On a partner credit line, stop here and contact the partner — every step below is a waste of your afternoon.
2. Check the account is not deleted or suspended. Two of the eight causes are not billing faults, and both are indistinguishable from one until you look at the account's status.
3. Check the limit before the instrument. An over-limit credit line and a missing card produce the same code. If Meta ads on the same portfolio have also stopped, the limit is where to look first.
4. Then check the payment method itself — brand first, per Meta's Visa-and-Mastercard statement, then whether it is set for this account rather than merely present on the portfolio.
5. Only then look at currency and timezone, and only after confirming whether a line of credit is attached. If one is, the fields are frozen, and the answer is a new WABA rather than a form you cannot submit.

Doing this in the order most pages suggest — attach a card, set it as default, add tax information, wait a day — inverts it, and starts with the step that is useless on two of the four onboarding paths.

Every Meta quotation on this page was read from Meta's own documentation on 11 September 2026. Meta changes that documentation without notice; the linked pages are authoritative and this one is not.