Skip to main content
Error 131042 means Meta stopped the message because of a billing problem: the payment method or billing setup of your WhatsApp Business Account (WABA) isn’t working. The WABA is the Meta account that owns your WhatsApp number. The contact didn’t cause the error, so every send from that number can fail until you fix it.
Meta’s wording: There was an error related to your payment method. See Meta’s error codes and billing for your WhatsApp Business account.

What causes it

Meta lists these common causes:
  • No payment account is attached to the WABA.
  • The credit line is over its limit, or isn’t set up or active.
  • The WABA has been deleted or suspended.
  • The WABA has no time zone or no currency set.
  • A request to message on behalf of another business is pending or was declined.
From 1 October 2026, Meta also charges for service messages, the replies you send inside the 24-hour window, beyond a free allowance of 1,000 per number each month. Without a working payment method, replies can stop too once that allowance is used. See Pricing and categories.

How to confirm it in Flowella

Flowella doesn’t translate this code, so it shows WhatsApp’s own wording with the code, for example “Business eligibility payment issue (code 131042)”. You see it:
  • Under the failed message in the Inbox, next to a red alert icon.
  • In the Details column of the template’s Send log, on the Statistics tab, for test sends and bulk sends.
  • In HubSpot workflow history, where the error message includes 131042. The Error code output is FAILED, or FLOWELLA_META:generic if WhatsApp refused a template straight away. See Error codes in HubSpot.
Flowella can’t see your Meta billing, so it doesn’t warn you before this error. Any warning about a missing payment method comes from Meta.

How to fix it

1

Find the WABA that sends the messages

Each WhatsApp Business Account has its own payment method. A card on another account, such as an ad account or a WABA you used with another provider, doesn’t cover Flowella’s sends. In Flowella, open the Inbox for the number that sent the failed message. The web address follows the pattern /{organisation ID}/{WABA ID}/{phone number ID}/inbox. Find the account with that WABA ID in Meta Business Suite. See Add the card to the account Flowella uses and Find your WABA ID.
2

Check the payment method is set as Default

Check that a valid card is attached to that WABA and marked Default. See Confirm the card is set as Default.
3

Check for billing problems in Meta

In Meta’s billing area for the account (Billing & payments), look for a failed payment, an expired card or a credit line that is over its limit. Update the card or settle the balance.
4

Check the WABA's status, currency and time zone

In WhatsApp Manager, check that the WABA isn’t suspended or deleted, and that it has a currency and a time zone set.
5

Send one test message

Send one approved template to your own phone with Test Template. See Test a template. If it arrives, resume your sends.
Don’t keep resending while 131042 is active. The problem is on your account, so every send fails until Meta clears it.
If the error continues after you’ve checked everything, contact Flowella support. Include the time of a failed send, the WhatsApp number you sent from and the text under the failed message. Flowella can’t override Meta’s billing checks, so problems with the account itself may need Meta Direct Support.

How to prevent it

  • Keep a valid card set as Default on every WABA you send from.
  • Watch for Meta’s billing emails and notifications, and update an expiring card in good time.
  • When you add a new WhatsApp number in another WABA, add a payment method to that WABA before you send.

How it differs from similar codes

Last modified on November 18, 2026