Skip to main content
If Flowella or Meta reports error 131042 with a title such as Business eligibility payment issue, Meta blocked the delivery because of a problem related to your WhatsApp Business Account billing or eligibility — not because of the recipient.
Official Meta wording: There was an error related to your payment method. See Meta’s error codes and billing help.

What Meta documents as causes

From Meta’s Cloud API error reference, common problems include:
  • Payment account is not attached to the WhatsApp Business Account (WABA)
  • Credit line is over the limit
  • Credit line (payment account) is not set or not active
  • WABA is deleted or suspended
  • Timezone not set on the WABA
  • Currency not set on the WABA
  • MessagingFor / on-behalf-of request is pending or declined

What to check in practice (Flowella)

Work through these in order. A card can look fine in Meta’s Billing Hub while WhatsApp Manager or Flowella still shows a payment / eligibility warning.
1

Confirm the Default card is on the correct WABA

Open Meta payment method steps: Business Suite → Settings → Accounts → WhatsApp accounts → your WABA → Payment settings. The card that should be charged must show the Default badge on that WABA (not only on an ad account or a different WABA).
2

Match the WABA to Flowella

In Flowella Settings → Meta, confirm the connected WABA name and ID match the WABA you just edited. Sends bill against the connected WABA; editing a lookalike WABA will not fix the error.
3

Complete Meta business verification

Unverified businesses are often blocked from reliable paid messaging even when a card is on file. See Business verification. Flowella may show a verification banner separately from the send-log error.
4

Confirm currency and timezone were set before billing

Meta locks currency and timezone once a payment method is attached. If they were never set correctly, Meta support may be required — you generally cannot self-serve a fix after the fact. Prefer fixing this before attaching a card; see WhatsApp Business Account.
5

If it still fails, escalate with evidence

Capture the failed send time, the WABA ID, phone number ID, and any fbtrace_id / message ID from the failure. Contact Flowella support. Account-level Meta holds (for example WABA not active, or business verification incomplete) sometimes need Meta Direct Support — Flowella cannot override Meta eligibility.
Do not keep resending the same template while 131042 is active. The failure is account-level; retries will fail for every recipient until Meta clears the eligibility / payment state.

How this differs from similar codes

Last modified on October 7, 2026