Why did my Meta payment fail?
A failed Meta payment is not a small billing hiccup. Ads pause, Click-to-WhatsApp stops delivering, and Cloud API can return error 131042 until the card, tax info, and outstanding balance are clean. Here is the official fix path — then how it shows up on Ominiflow. Common causes are a bank fraud block on the first Meta charge, billing address mismatch, an expired or over-limit card, or an outstanding balance from a previous decline. Confirm the exact Billing message before you retry.
Last updated: 2 September 2026
A failed payment on Meta pauses more than Facebook ads. The same Business Portfolio often funds Click-to-WhatsApp campaigns and WhatsApp Cloud API conversation fees. Until the charge clears, ads stop delivering and template sends can fail with error 131042 (business eligibility payment issue).
Meta’s Help Center article Fix a failed payment issue on Meta is the official billing path. This playbook keeps that intact, then maps the same failure to WhatsApp Business Platform on Ominiflow — because Indian D2C teams usually discover the problem when OTP and order templates stop, not when Ads Manager shows a red banner.
Primary: Fix a failed payment issue on Meta. WhatsApp Cloud API billing eligibility: Meta error 131042. Account-wide holds: disabled or restricted accounts. This is operational guidance, not a guarantee Meta will restore delivery on a given timeline.
Ads
delivery pauses until the outstanding balance clears
131042
Cloud API error when WhatsApp cannot charge conversation fees
1 retry
fix the method first — rapid “Pay now” clicks can trip a billing restriction
Too long? Start here
- Stop retrying. Write down the exact Billing wording (failed, pending, restricted, balance due)
- Match the card. Name, address, and PIN/ZIP must match the issuer. Call the bank and ask them to allow Meta / Facebook charges
- Add a backup method before you pay the outstanding invoice. One card is a single point of failure
- WhatsApp-specific: attach the payment method to the WABA, complete tax/GST, then retry one template send
- On Ominiflow: we pass Meta conversation fees at cost. If Meta cannot charge, we cannot send. Fix billing in Business Suite — start free
Two billing surfaces, one portfolio
Teams mix these up and “fix the wrong screen.”
| Surface | What it pays | If it fails |
|---|---|---|
| Ad account billing | Facebook / Instagram / Click-to-WhatsApp media spend | Campaigns stop. Leads stop arriving in chat |
| WhatsApp Cloud API billing | Meta conversation fees (marketing, utility, authentication) | Templates fail with 131042; in-window service replies may still go through |
Both live under the Meta Business Portfolio. A declined card on ads does not always break Cloud API, and a missing WABA payment method does not always pause ads — check both. Click-to-WhatsApp needs both to work: Ads Manager to buy the click, Cloud API to hold the thread. Product: Click-to-WhatsApp ads.
Fix the ads payment first (Meta’s path)
From Meta’s failed-payment help article, the safe order is:
- Open Ads Manager → Billing & payments on a computer. Note the exact error — declined, pending, restricted, or amount due
- Do not mash Pay now. Repeated declines look like fraud to both the bank and Meta
- Confirm billing name, address, and postal code match the card issuer exactly
- Call the bank. Ask the fraud desk to allow recurring charges from Meta Platforms / Facebook. Indian cards often block the first international merchant authorisation
- Add a second payment method. Set the working card as default
- Pay the outstanding balance once
Ads usually resume within minutes after a successful charge. If Billing says the account is restricted rather than failed, that is a different queue — advertising restrictions and Account Quality.
Fix WhatsApp Cloud API billing (error 131042)
Outgoing templates can fail even when Ads Manager looks green. Meta’s Cloud API returns 131042 — Business eligibility payment issue when it cannot attach a valid charge to the WABA.
- Meta Business Suite → WhatsApp Manager → Account tools → Billing (or Payment settings). Confirm a default method is attached to this WABA, not only to an unrelated ad account
- Complete tax info — GSTIN in India, VAT/EIN elsewhere. Incomplete tax forms are a common reason the developer dashboard still says “missing valid payment method”
- Clear any failed WhatsApp conversation invoices
- Confirm timezone and currency on the WABA. They cannot be edited after a line of credit is attached — get them right at setup
- Send one Authentication or Utility template to a test number. If 131042 persists after 24 hours with a valid card and zero balance, it can be a Meta eligibility sync issue — open Business Support Home, do not keep blasting templates
Ominiflow does not add a second markup on Meta fees. If Meta cannot bill the portfolio, the send fails on our side too. Onboarding checklist: API onboarding. India GST and rates: WhatsApp API India.
Retry storm
Five “Pay now” clicks in ten minutes. The bank declines, Meta flags unusual payment activity, and you now have a restriction instead of a failed charge.
Card on the wrong asset
Payment method lives on the ad account. The WABA still has none. Ads run; OTP templates die.
GST left blank
Card is valid. Tax info is empty. Developer dashboard keeps saying the method is missing.
Expired festival card
The card that funded Diwali ads expired in January. Utility shipping templates fail in February. Put a backup method on file before sale week.
What to do on Ominiflow while billing is down
- Pause Marketing campaigns in Ominiflow so you do not queue thousands of templates that will fail and still need cleanup
- Keep agents on the shared inbox — customer-initiated replies inside the service window often still deliver
- Do not open a second unofficial number to “get around” 131042. That is a policy risk, not a billing fix. See WhatsApp ban guide
- After Meta confirms the charge, send a 20-contact Utility test, then resume
CTWA best practices · Scale your WABA · Book a demo
FAQ
Why did my Meta payment fail? expand_more
The usual causes are a bank fraud block on the first Meta charge, billing address mismatch, an expired or over-limit card, or an outstanding balance from a previous decline. Confirm the exact Billing message before you retry.
Will a failed ads payment stop WhatsApp messages? expand_more
Not always. Ad-account billing and WABA billing are separate. Click-to-WhatsApp needs both. Cloud API templates fail when the WABA has no valid method or unpaid conversation fees (error 131042).
What is WhatsApp error 131042? expand_more
Business eligibility payment issue. Meta cannot charge conversation fees for that WABA. Attach a default payment method to the WhatsApp account, complete tax info, clear dues, then test one template.
Should I keep clicking Pay now? expand_more
No. Fix the method and the bank first, add a backup card, then pay once. Rapid retries can turn a failed charge into a payment restriction.
Does Ominiflow charge Meta conversation fees? expand_more
Meta conversation fees pass at Meta’s published rates. Ominiflow cannot send templates if Meta cannot bill your portfolio. Fix payment methods in Meta Business Suite. Published 2 September 2026. Summarised from Meta Business Help Center billing articles and Cloud API error 131042 behaviour. Banks and Meta can change decline codes without notice. Not a guarantee of reinstated delivery.
