WhatsApp Error 131042: Business Eligibility / Payment Issue

WhatsApp error 131042 means your account has a payment-method problem blocking sends. The full Meta cause list, how to restore billing eligibility, and prevention.

TL;DR: WhatsApp error 131042 means your WhatsApp Business Account cannot be billed for the message you tried to send. The message developers see is "Message failed to send because there were one or more errors related to your payment method." It blocks paid (business-initiated) and template sends until billing is fixed — usually by attaching an active payment method/credit line to the WABA, or correcting timezone, currency, or tax settings.

What Error 131042 Means

131042 is an account/billing eligibility error. WhatsApp's paid messaging requires an active payment account on the WABA; when Meta cannot charge you, it refuses the send. The error message surfaced by Meta is:

"Message failed to send because there were one or more errors related to your payment method."

Meta's docs enumerate the common problems: payment account is not attached to the WhatsApp Business Account; credit line is over the limit; credit line (payment account) not set or active; WABA is deleted; WABA is suspended; timezone not set; currency not set; the "Messaging For" (On Behalf Of) request is pending or declined; the conversation free-tier threshold was exceeded without a valid payment method.

Where You See It

131042 typically arrives as a synchronous /messages API error, but because it is an account-state condition it can also surface on send attempts across your stack. It most often appears when sending business-initiated template messages (which are billable) rather than free-window service replies. It is not a payload error — the same request would succeed once billing is healthy.

Common Causes

  • A payment method exists in Meta Business Suite but is not assigned at the WABA level (the single most common practitioner cause).
  • The credit line is over its limit, inactive, or never set.
  • The WABA is deleted or suspended.
  • Timezone or currency was never configured on the account.
  • The "Messaging For" (On Behalf Of) request is pending or was declined.
  • The free-tier conversation threshold was exceeded with no valid payment method on file.
  • Community-reported: tax information has not been entered in Meta Business Manager where Meta requires it; or a small verification charge failed, leaving the account "ineligible."

How to Fix It

  1. Go to business.facebook.com → Business settings → WhatsApp Accounts, select the affected WABA, and open Billing / Payment settings.
  2. Confirm a valid payment method is assigned to this specific WABA, not just present in the portfolio.
  3. Clear any outstanding dues and verify the credit line is active and under its limit.
  4. Set timezone and currency if blank; add tax info where Meta requires it.
  5. If sending on behalf of another business, ensure the Messaging For / OBO request is accepted.
  6. Wait for eligibility to refresh and retry. Per Wetarseel's 131042 guide: "Once the card is correctly added, the error usually clears instantly. However, in some cases, it may take up to 24 hours for Meta's eligibility status to refresh."

How to Prevent It

  • Use a credit card that supports international recurring charges; verify no temporary holds are failing.
  • Monitor your account's billing/eligibility status proactively rather than discovering it on a failed campaign.
  • Keep the WABA out of suspension by maintaining policy and quality compliance.

Related Errors

FAQ

Q: I already added a card — why do I still get 131042? A: Adding a card to Business Suite is not enough; it must be the active payment method assigned to that WABA. Also check for outstanding dues or a failed verification charge.

Q: Is 131042 a billing problem with my BSP/provider? A: No. It is your WhatsApp/Meta billing, separate from any provider's invoice.

Q: How long until it clears after I fix billing? A: Often immediately; community reports (Wetarseel) indicate Meta's eligibility status can take up to ~24 hours to refresh.

Q: Why did marketing templates fail but service replies worked? A: Service replies inside the customer window may be free; billable business-initiated templates require a chargeable payment method.

How Dualhook Helps

This is an account-status code, so Dualhook adds real value. Using its advanced whatsapp_business_management access and account-level webhooks, Dualhook surfaces WABA connection and account-status signals so a billing/eligibility problem becomes visible in your monitoring views instead of as a surprise campaign failure. See Maintain Account Health and Capacity, Quality & Limits. The actual payment fix still happens in Meta Business Suite — Dualhook cannot charge a card or assign a credit line on your behalf — but it shortens the time from "something broke" to "I know which WABA and why."

Browse more docsStart Free Trial