WhatsApp Error 131042 (Business Eligibility Payment Issue): Causes and Fixes for India

Error 131042 means Meta found a problem with the payment setup behind your WhatsApp Business Account, so it won't deliver chargeable messages. Meta lists the causes as: no payment account attached, credit line over its limit or not active, WABA deleted or suspended, timezone or currency not set, or a pending or declined MessagingFor (On Behalf Of) request. Most fixes happen in Meta Business Suite → Billing & payments, or with your provider if you're on their credit line.

In API responses or webhooks you'll see code 131042. Meta's current reference describes it as "an error related to your payment method". The title text has commonly read "Business eligibility payment issue", but the exact wording can vary, so rely on the code:

"code": 131042,
"message": "(#131042) Business eligibility payment issue"

Your dashboard may simply show "failed". Order confirmations, OTPs and campaigns all stop together, which is why this error usually shows up as an "everything stopped" panic during a sale.

Meta's error code reference lists these common problems for 131042:

1. Confirm it's 131042. Ask your provider or developer for the exact error code. Don't guess from "failed".
2. Open Meta Business Suite → Settings → Billing & payments → Messaging accounts. Find the WhatsApp account that's failing. If several are listed, check the ID of each.
3. Look at the payment method. Expired card? "Action needed"? An unpaid balance? Fix it, or add a new Visa/Mastercard card. Meta's help article explains adding a credit card.
4. Complete business and tax details. Meta notes you may need to give tax information when setting up payment. In India, enter your GSTIN, legal name and address exactly as on your GST certificate. Many businesses report the error clears once this is done.
5. Check for a failed charge. Meta's general guide to fixing a failed payment covers retrying a balance and bank blocks.
6. Check requests. In Business Suite, look for any pending partner requests for your WhatsApp account and accept the one from your current provider.
7. Send one test template to your own number. Only resume campaigns after it's delivered.
8. Still failing? Raise a ticket via Meta Direct Support with the WABA ID, phone number ID, a failed message ID and the timestamp, or ask your provider to raise it.

Many Indian BSPs pay Meta through their own credit line and bill you via a prepaid wallet. In that setup, 131042 often means:

• The provider's credit line for your account was removed or not shared yet (common right after onboarding or switching providers).
• Your wallet ran out and the provider stopped covering usage.
• You switched providers, but the old credit line is still attached. Meta's support docs mention errors when a client still shares a previous partner's credit line.

You can't fix these from your side alone. Message the provider with the error code and your WABA ID.

• INR migration. Meta requires eligible India accounts to move to INR by December 31, 2026. Its pricing page says non-INR accounts of eligible customers stop delivering from January 1, 2027. When a WABA is cloned into INR, credit cards must be re-added manually; a missing card on the new WABA looks a lot like 131042.
• Service messages are now charged. From October 1, 2026, replies beyond 1,000 free per number per month need a payment method. A business that never added one (because it "only replied") can now hit payment failures.
• Card mandates. Indian banks may block recurring or international online charges. If Meta's charge fails, ask your bank to allow it, or use another card.

1. A backup card ready in the business name, so you can swap it in quickly.
2. A calendar reminder a week before card expiry.
3. Payment failure alerts. Route failed-message webhooks with code 131042 to Slack or email right away.
4. Don't launch a big campaign right after a billing change. Send a test first.
5. Know your billing model. Write down whether Meta bills you directly or your provider does, and who to call.

On WatsBerry you onboard via Embedded Signup with your own WhatsApp Business Account and your own payment method. Meta bills WhatsApp usage directly to you (0% markup), and WatsBerry charges a separate platform plan (₹1,599 / ₹2,999 / ₹5,999 per month + GST). There's no provider credit line in between to run out, and failed-message alerts can go to Slack. You still need a working card on Meta's side; no platform can make chargeable messages free.

If your messages are failing right now, message me from watsberry.com with the error code and when it started. I'll help you work out whether it's billing, quality or policy.

Abbas Ali, Founder, WatsBerry