WhatsApp Error 130403: Business Has Blocked the End User

WhatsApp error 130403 means your business has blocked the recipient on WhatsApp, so the message can't be delivered. Do not retry — unblock the user instead.

TL;DR: WhatsApp error 130403 means the message can't be delivered because your business has blocked that recipient on WhatsApp. Meta's details string is "Unable to deliver the message. This business has blocked the end user on WhatsApp". Don't retry — unblock the user via the Block API to resume messaging them.

What Error 130403 Means

130403 is a send/delivery error caused by your own block list: the business previously blocked this WhatsApp user, so outbound messages to them are refused. Meta's official details value is:

"Unable to deliver the message. This business has blocked the end user on WhatsApp"

Meta's guidance is explicit: do not retry — unblock the WhatsApp user to resume sending messages to them. (Note: this is your business blocking the recipient, not Meta blocking your account. A platform-level restriction on your account would surface as 368 or 131031, not 130403.)

Where You See It

It can surface synchronously in the /messages response and/or asynchronously in the message status webhook (statuses[].errors[]) as a delivery failure. Either way the cause is the same: the recipient is on your business's block list.

Common Causes

  • The recipient was explicitly blocked via the Block API or in WhatsApp Manager.
  • A spam/abuse-prevention workflow auto-blocked the user earlier and you later tried to message them.
  • A bulk block operation captured a number you now legitimately need to message.

How to Fix It

  1. Do not retry the send — it will keep failing while the block is in place.
  2. Unblock the user using Meta's Block API (or in WhatsApp Manager). See Meta's "Unblock a user" guide.
  3. Confirm the unblock succeeded, then resend.
  4. If you didn't intend the block, review the workflow that created it to prevent recurrence.

How to Prevent It

  • Keep your block/unblock workflow auditable so you know which numbers are blocked and why.
  • Avoid broad auto-block rules that can capture future legitimate recipients.
  • Reconcile your CRM "do not contact" list against your WhatsApp block list.

Related Errors

FAQ

Q: Who blocked whom in error 130403? A: Your business blocked the end user. (If the user blocked you, delivery fails differently, often surfacing as undeliverable / 131026.)

Q: Should I retry? A: No. Retrying won't deliver. Unblock the user first.

Q: How do I unblock? A: Use Meta's Block API "Unblock a user" endpoint (or WhatsApp Manager), then resend.

Q: Does 130403 mean Meta banned my account? A: No — that would be 368 or 131031. 130403 is specifically your business's block on one recipient.

How Dualhook Helps

Honest answer: 130403 is a send-side condition tied to your business's block list and your own send call, and Dualhook is not in the message path and never reads or stores message content — it can't unblock a user for you. The unblock is done against Meta's Block API from your backend. Where Dualhook is relevant: delivery-failure status webhooks route through your endpoint, and Dualhook helps ensure those webhooks are correctly subscribed and visible so you actually see the 130403 failure. See Messaging Webhook and Messaging Health Status.

Browse more docsStart Free Trial