​

Troubleshooting: WhatsApp sends blocked by a WABA billing failure (WHATSAPP_BILLING_ISSUE)

​

Symptom map

• WHATSAPP_ACCOUNT_LOCKED (Meta 131031) — a policy lock. Every send fails, but re-authentication and billing updates both do nothing; only a Meta Business Support appeal lifts it. See the account-lock section of Troubleshoot the WhatsApp connection.
• WHATSAPP_CONNECTION_INVALID — a dead or revoked access token. Fix is re-running Embedded Sign-up, not a billing update.
• WHATSAPP_BILLING_ISSUE — the WABA itself is healthy and the token is fine; Meta refuses sends only until billing is resolved. That is this page.

​

Read the failure

curl -X POST "https://api.orbit.devotel.io/api/v1/messages" \
  -H "X-API-Key: $ORBIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+15551234567",
    "channel": "whatsapp",
    "type": "template",
    "template": { "name": "order_shipped", "language": "en_US" }
  }'

{
  "error": {
    "code": "WHATSAPP_BILLING_ISSUE",
    "message": "Meta rejected the send because of a payment-method problem on your WABA. Update billing in Meta Business Manager.",
    "status": 409,
    "details": {
      "whatsappErrorCode": 131042
    }
  },
  "meta": {
    "request_id": "req_abc123",
    "timestamp": "2026-09-12T08:41:07Z",
    "docs_url": "https://docs.orbit.devotel.io/errors/WHATSAPP_BILLING_ISSUE"
  }
}

{
  "error": {
    "message": "(#131042) Business eligibility payment issue",
    "type": "OAuthException",
    "code": 131042
  }
}

​

Fix — update billing in Meta Business Manager

1. Open the WABA’s payment page. In Meta Business Manager go to Billing & payments → Payment settings (or, from the Orbit dashboard banner, click Fix billing on Meta — it deep-links to the offending WABA when Orbit knows which WABA failed).
2. Repair the payment method. If the card was declined or expired, update it or add a new one. If the WABA bills Pay-as-you-go instead of a card, top the balance back up above zero.
3. Wait for Meta to confirm. Meta re-checks eligibility within a few minutes of the update; during that window sends still return 409. There is no re-connect step at Orbit — the stored token and WABA row are untouched by a billing fix.
4. Re-send. Once the hold clears, sends pass immediately — queued campaign sends are not auto-replayed, so re-send the failed batch.

​

Verify before re-sending

curl "https://api.orbit.devotel.io/api/v1/brand-identity/status" \
  -H "X-API-Key: $ORBIT_API_KEY"

​

What not to do

• Do not retry-loop the send. The refusal is deterministic — the same request returns the same 409 until the billing state changes at Meta. A retry loop burns your API rate budget and marks every attempt as a failed send. Fix billing first, then re-send once.
• Do not re-run Embedded Sign-up. Re-authentication replaces tokens; it cannot touch Meta’s billing eligibility. The connect layer is healthy here and re-running it changes nothing.
• Do not look for a payment method in Orbit. Devotel never holds the WABA’s card — paid WhatsApp conversation charges settle between you and Meta directly. The Orbit wallet and spend caps are a separate ledger and stay unaffected.
• Do not disconnect and re-connect the WABA. Re-binding a billing- held WABA preserves the hold; sends fail identically until Meta accepts the payment update.

​

Escalation payload

1. Your WABA id (Meta Business Manager → WhatsApp Manager, or the waba_id on a template record).
2. The most recent failing meta.request_id from a re-send attempt after the billing update.
3. Which billing model the WABA uses (card on file or Pay-as-you-go).

​

Related codes

• Troubleshoot the WhatsApp connection — WHATSAPP_ACCOUNT_LOCKED (Meta 131031) policy locks, WHATSAPP_CONNECTION_INVALID token faults, and WHATSAPP_TOKEN_EXPIRED.
• Troubleshoot a WhatsApp template — pending, rejected, paused, and reclassified templates once billing is healthy again.
• Error codes — the full WHATSAPP_* catalog with HTTP statuses, including every Meta 13xxxx code Orbit maps.