business payment error 131042 driving me mad

localpack

Anyone else hit this WhatsApp error? Our business-initiated messages keep failing with 131042 (Business eligibility payment issue). Here's the kicker: our billing hub shows an active/default card that's already been used for high-spend Ads, business and account are fully verified, the number is green and approved, and 24-hour customer window messages work fine. But outside that window? Crashes with 131042.

Spent three weeks getting through to support-actual humans who asked me to do irrelevant admin and pixel checks. Then they promised a direct line to their engineer team, only to redirect me to the community forum and hang up mid-call. Great, right?

A colleague figured it out: missing or invalid tax or business info on the payments page. Update that, wait an hour, and the error should vanish. I'd missed it too, even though my business is approved and the same payment method is live in Ads. Worth checking if you're stuck.

storyweaver

Oh, the classic "missing or dodgy tax info" dance. yeah, that'll trip the payment page right up. pop the correct details in, then go make a cuppa and give it an hour. should clear itself up like magic - or at least stop throwing a tantrum.

ranktracker

Getting the same error here despite cycling through multiple Visa, Mastercard, debit and credit cards. Found that Tax ID field on the business info page shows as optional, but from experience with Indian tax compliance, it's effectively mandatory. That video is spot on - I had to input the Tax ID (GST or PAN) before any payment method stuck. Even then, the error only cleared after I cleared browser cache and tried again with a fresh incognito session. Worth a shot.

bouncekiller

Oh look, another Meta support horror story. Been banging my head against this exact wall for a month. They close tickets with a cheerful "ask the community" - like mate, I am the community, and the community is just as f*cked as I am.

Configs all done properly - tax ID, business address, default payment method, currency, country, the whole bloody checklist. Business is verified, display name approved, service messages fly through fine. But business-initiated templates after that 24‑hour window? Dead silence. Nada.

Spoke to someone who switched from native cloud API to a BSP - everything worked instantly. Makes you wonder what Meta's actually doing behind that shiny dashboard.

Has anyone actually got a human from Meta support who didn't just paste a link to a help article? Or is the only fix to abandon native and pay a BSP?

localpack

Mate, head to Business Settings > Payments > Payment Methods - that's where those fields live. if your business is approved and the same payment method is already running ads, you're golden. can't screenshot here, but it's under 'Payment Settings', then 'View Details'. let me know if that's not where you're looking

storyweaver

honestly, I've been banging my head against this for weeks. After you mash that payment settings button, the very last card on the page should be the business info one. Sounds obvious, right? Except they've buried it so deep you'd think it's a secret level in a Mario game. Make sure every single field in that card is filled in - not just the ones that look important. Found that out the hard way after three support chats with people who clearly hate their jobs

localpack

Same issue here-no TAX field showing up. Probably because my client's based in Kuwait.

Really appreciate the help though, you've done more in a few minutes than Meta support managed in weeks 🙌

trafficcop

Oh, I love when Meta makes things this easy. 🙃 Same error 131042 here. Let me list out the absolute nonsense I've already done:

WhatsApp Business Account - approved ✅
Business verification - completed ✅
Account status - says "approved" ✅
Payment method linked - yep, shows right there in the settings ✅
Customer service replies within the 24h window - works like a charm ✅
Template messages outside that window? Error: 131042. Naturally.

So either there's some hidden billing/tax setting that's deliberately impossible to find, or Meta just enjoys watching us scream into the void. Anyone actually solved this, or is it just another "submit a ticket and wait six months" kind of party?

localpack

Mate, I feel your pain. Been stuck in the same loop myself with a few client accounts.

Spent three days going back and forth with support-absolute dead end. Turned out the issue was a mismatched business name on the payment method vs. the ad account. worth double-checking that every detail matches exactly what's in your business registration.

Did you ever get yours sorted?

trafficcop

Nope, still waiting. The business eligibility team must be on a permanent coffee break. Typical.