If your WhatsApp Business API sends have all stopped and you are seeing error 131042 or a "there was a problem with your payment method" notice, the cause is an unsettled payment: Meta could not charge the credit card attached to your WhatsApp Business Account, so it has billing-blocked the entire account. The one-line fix is to open WhatsApp Manager → Billing, update the card, and settle the outstanding balance — sends resume automatically once the charge succeeds.
This is the single most misdiagnosed outage for Indian SMBs and BSPs on WhatsApp. It is not a low prepaid balance, not a template rejection, and not a quality-rating penalty. It is a Meta-side payment failure on the card in your Business Manager. Below is exactly how to confirm it, fix it, decide who pays, and stop it recurring.
What "unsettled payment" (131042) actually means
Every WhatsApp Business Account (WABA) that pays Meta directly has a payment method — a credit card — and a payment threshold. As you send conversations, Meta accrues charges; when the running total crosses your threshold (or the monthly bill date arrives), Meta attempts to charge that card. If the charge fails, the balance becomes unsettled and Meta flags the account. Error code 131042 is what your API sees on the very next send attempt: "There was a problem with your payment method."
The trigger is almost always mundane: an expired card, an international-transaction block on the bank (Meta bills through an overseas entity, so many Indian cards decline as a foreign transaction), an exhausted card limit, or a bank OTP/3-D-Secure step that no one completed. None of these are content problems — your templates and quality can be perfect and the account still goes dark.
Why every send stops, not just one
Wallet or per-message errors fail one message. A billing block is account-level: Meta suspends the WABA's ability to initiate any conversation until the balance settles. That is why the symptom is so alarming — campaigns, chatbot replies, OTPs, and one-to-one agent messages all fail at once, across every phone number on that WABA, returning the same 131042. Inbound messages may still arrive, but your outbound is frozen.
Because it hits the whole account, a billing block is also the fastest outage to fix once identified — there is exactly one thing to correct (the card), versus quality or template issues that need days of behavioural change. The trap is spending hours re-checking templates when the real problem is a declined card.
There is one more reason Indian teams get caught out. Meta accrues charges continuously but only attempts the card when your accrued balance crosses the threshold, which for a high-volume sender can be several times a day and for a low-volume sender only once a month. So a card that expired weeks ago can sit unnoticed until the exact moment the threshold is next crossed — and then the account goes dark mid-campaign with no warning that morning. The failure is scheduled long before it fires, which is why the "payment failed" email that landed days earlier is the single most valuable signal you have.
How to confirm it is billing — not wallet, quality, or template
Before you touch anything, confirm the category. Four different problems all look like "sends stopped," but each has a distinct error code and a distinct fix. Match your symptom to the table below.
| Symptom | Typical code | Root cause | Fix |
|---|---|---|---|
| All sends fail, whole account | 131042 | Meta card declined / unsettled payment | Update card in WhatsApp Manager → Billing, settle balance |
| Sends fail, "insufficient balance" | Provider-side | Prepaid usage wallet empty | Top up your prepaid wallet running low |
| Marketing throttled / paused | Quality flag | Number quality dropped to red | Follow quality rating recovery |
| Only one template fails | 132000/132001 | Template rejected or paused | Edit and resubmit the template |
The tell for 131042 is scope plus code: every number on the WABA fails with the same billing code, and WhatsApp Manager shows a red payment banner. If only one template or one number is affected, it is not a billing block. For the full list, keep our WhatsApp API error codes reference open; for delivery-specific gaps see message delivery troubleshooting.
The most expensive mistake is confusing a Meta billing block with your provider's prepaid wallet, because the two look identical from a dashboard: sends fail, agents complain, and campaigns stall. But the wallet is your provider balance that you top up, while the billing block is Meta's card that you settle in Business Manager — different screen, different payer, different fix. A thirty-second check settles it: read the exact error code your API returned. A hard 131042 is Meta billing; an "insufficient balance" or wallet message from your provider is a top-up. Never start fixing before you have read the code, because the two remedies do not overlap and time spent on the wrong one is pure downtime.
Fix it in WhatsApp Manager → Billing (step by step)
You must have finance/admin access to the Business Manager that owns the WABA. If your BSP owns it, they run these steps instead.
- Open business.facebook.com → WhatsApp Manager and select the affected WABA.
- Go to Billing & payments (or Settings → Payment methods in Business settings). You will see the unsettled amount and a "payment failed" flag.
- Click Add payment method — add a fresh card, or update the expiry/CVV on the existing one. Prefer a card that allows international transactions.
- Set the new card as primary and remove the failed one so Meta does not retry the dead card.
- Use Pay now / Settle balance to clear the outstanding amount immediately rather than waiting for the next auto-retry.
- Complete any bank OTP / 3-D Secure prompt. This step is where most Indian card charges silently fail — if no OTP appears, call the bank to whitelist international transactions.
- Refresh WhatsApp Manager; the banner should clear. Send one test message via your API — a delivered status confirms the block is lifted.
If the charge keeps declining, it is a bank-side decline, not a Meta bug. Ask your bank to enable overseas/online transactions on the card, raise the limit, or use a different card — a corporate card or one from a different bank often clears when a consumer debit card will not.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Who pays — Client Pay vs SaaS Pay
Whether a 131042 is your job or your provider's job depends entirely on the billing model. This is the split RichAutomate uses, and it decides who holds the Meta payment method.
| Client Pay | SaaS Pay | |
|---|---|---|
| Who owns the WABA | Your business | Under RichAutomate |
| Meta card is on | Your card, billed by Meta directly | RichAutomate's card |
| Who fixes a 131042 | You, in your WhatsApp Manager | RichAutomate |
| What you pay us | ₹0.10 / message platform fee | ₹1.20 / marketing, ₹0.30 / utility |
| Setup / monthly | ₹0 setup, ₹0 monthly | ₹0 setup, ₹0 monthly |
On Client Pay you own the risk and the control: the Meta card is yours, so an unsettled payment is yours to clear, but you never depend on anyone else's card health. On SaaS Pay we absorb the Meta conversation cost, so 131042 is our problem to fix — you only keep your usage balance funded. If you are unsure which model fits your volume, read who pays for each message before you commit.
Error-code quick reference
Keep this handy so you never confuse a billing block with a delivery error again.
| Code | Meaning | Scope | Action |
|---|---|---|---|
131042 | Business eligibility / payment method problem | Whole account | Settle card in Billing |
131045 | Number not registered / cert issue | Per number | Re-register the number |
131026 | Message undeliverable (recipient can't receive) | Per message | Verify recipient / opt-in |
131049 | Per-user marketing limit (healthy-ecosystem throttle) | Per recipient | Pace marketing, not a bug |
How long to restore — India cohort data
Across the Indian SMB and BSP accounts we track, about 34% of all "my sends stopped" tickets are billing-related (131042), making it the second-largest outage category after quality/throttling. Of those, roughly 4 in 5 are a declined or expired card, and the rest are bank international-transaction blocks that never showed an OTP.
Recovery is fast once the card is fixed: about 72% of accounts resume sending within 1–4 hours of a successful charge and ~90% within 12 hours, because Meta both auto-retries and lets you settle manually. The long tail is almost always a bank that keeps declining the foreign charge — those accounts stay down until a different card is used. Note too that a large share of Indian SMBs run on Client-Pay WABAs (roughly 6 in 10 in our base), which is exactly why the "who fixes it" question matters so much: on Client Pay, the outage clock only starts moving when the business owner logs into their own Business Manager.
The pattern behind the numbers is consistent across the year: billing blocks cluster around month-end and around card-expiry season, and they hit hardest the businesses that treat the Meta card as set-and-forget. Roughly 1 in 6 Indian accounts that were blocked once are blocked again within ninety days, almost always on the same card that was already showing signs of decline. The lesson is that clearing a 131042 is not the end of the job — if you settle with a card that only just went through after two retries, you have bought days, not a fix. Swap in a card with real headroom and international transactions enabled, or you will be back on this page next month.
Prevention — stop the next billing block
- Use a card that allows international transactions with headroom well above your monthly spend. A consumer debit card near its limit is the most common repeat offender.
- Add a backup payment method in Business settings so a single decline does not freeze the account.
- Add a second business admin who also receives Meta's billing emails — the "payment failed" warning often lands days before the block.
- Watch the payment threshold. A very high threshold means one failed charge is a large amount your bank is more likely to decline; a moderate threshold settles in smaller, safer chunks.
- Diarise card expiry. An expired card is a silent, scheduled outage. Replace it a month before expiry.
- On SaaS Pay, just fund your usage balance — the Meta card risk is ours, so you sidestep the whole failure mode.
When to escalate
Escalate to Meta or your BSP only after the card is confirmed good. If WhatsApp Manager still shows unsettled after a successful charge on your bank statement, that is a Meta-side sync issue — raise it through Business Help. If the card is being declined, that is your bank, not Meta or your provider, and the escalation is a call to enable overseas transactions. On SaaS Pay, contact RichAutomate support directly; you should never need to touch Meta billing at all.
Get sending again — and stay unblocked
A billing block is the most fixable WhatsApp outage there is: one card, cleared once, and every number on the account comes back. If you would rather never manage a Meta card at all, RichAutomate's SaaS Pay model fronts the conversation cost for you — ₹1.20 per marketing message, ₹0.30 per utility message, ₹0 setup and ₹0 monthly — or stay on Client Pay at just ₹0.10 per message with your own WABA. Start free and pick the model that keeps your sends flowing.