Tell us how we can improve docs for you.
BotPenguin updates
What's NewGo to dashboard

Common Meta Issues

This page will solve your common issues faced with meta

Issue: “Add a Valid Payment Method” Error Even After Adding a Card

Problem Description

You may encounter an error message stating “Add a valid payment method” even after successfully adding a credit or debit card to your WhatsApp Business Platform account. This prevents actions such as sending WhatsApp template messages or initiating paid messaging.

This issue usually indicates that Meta is not recognizing the payment method as valid, even though it appears added in the account.

Why This Happens

Based on Meta’s behavior and system checks, this error can occur due to one or more of the following reasons:

  • The payment method has not been fully verified by Meta

  • The card is inactive, expired, or temporarily blocked by the bank

  • Insufficient balance or credit limit on the card

  • Temporary Meta payment verification issues

  • The card type or issuing bank is not supported by Meta

  • Payment method added but not set as primary/default

  • A delay in Meta’s backend syncing after adding the card

When this happens, Meta may:

  • Block template message sending

  • Trigger a payment-related error webhook

  • Show errors similar to Business eligibility payment issue

How to Resolve the Issue

Follow these steps in order:

1. Verify Payment Method in Meta Account

  • Go to Meta Business Manager

  • Navigate to Business Settings → Payments

  • Ensure:

    • The card is marked as Active

    • The card is set as the Primary payment method

2. Try Adding a Different Card

If the issue persists:

  • Add a new card (preferably a different bank or card network)

  • Remove the old card after adding the new one

  • Set the new card as Primary

💡 International cards with online transactions enabled usually work better.

3. Check Card Validity

Make sure the card:

  • Is not expired

  • Has sufficient balance / credit limit

  • Supports international and online transactions

  • Is not blocked by the bank for recurring or API-based payments

4. Wait for Meta Sync (Recommended)

In some cases, Meta takes time to validate payment methods.

  • Wait 24–72 hours after adding the card

  • Avoid repeatedly removing and re-adding the same card during this time

5. Refer to Meta Help Center

If the issue continues, refer to Meta’s official guide:

  • “Add a credit card to your WhatsApp Business Platform account” (Meta Help Center)

This guide explains supported card types and payment requirements.

6. Retry Template Message Sending

After completing the above steps:

  • Retry sending a WhatsApp template message

  • Monitor if the error webhook or payment warning disappears

Important Notes

  • This error commonly affects template messages, as they require an active payment method

  • Even if a card is added, Meta must approve and validate it internally

  • Error webhooks related to payments usually indicate Meta-side validation failure

When to Contact Support

If none of the above steps resolve the issue:

  • Raise a ticket with Meta Business Support

  • Share:

    • Business Manager ID

    • WhatsApp Business Account ID

    • Screenshot of payment method status

Summary

The “Add a valid payment method” error usually means Meta has not approved or recognized your card yet—even if it appears added. Trying a different card, ensuring it’s set as primary, and waiting for Meta’s verification typically resolves the issue.

Issue: “Message Failed to Send” or Message Not Delivered

Problem Description

You may encounter a situation where WhatsApp messages (template or session messages) fail to send or show as undelivered, even though the API request is successful. This prevents businesses from reaching customers and may disrupt live or automated communication.

This issue typically indicates that Meta has blocked or restricted message delivery due to policy, user state, or system rules.

Why This Happens

Based on Meta’s error handling and delivery rules, this issue can occur due to one or more of the following reasons:

  • The recipient phone number is not registered on WhatsApp

  • The user has blocked your business number

  • The user has not accepted the latest WhatsApp Terms of Service

  • The user has been inactive for a long period

  • The message violates Meta’s spam or quality guidelines

  • The 24-hour customer service window has expired

  • Meta’s “healthy messaging ecosystem” rules are triggered

When this happens, Meta may:

  • Mark the message as undeliverable

  • Block retries for the same message

  • Lower the quality rating of the WhatsApp Business Account

  • Temporarily restrict message sending

How to Resolve the Issue

Follow these steps in order:

1. Verify the Recipient Number

  • Ensure the phone number:

    • Includes the correct country code

    • Is active on WhatsApp

  • Ask the user to send a message to your number to confirm availability

2. Check the 24-Hour Window

  • If the last user message was more than 24 hours ago:

    • Use an approved WhatsApp template

    • Do not send free-form session messages

3. Reduce Message Frequency

  • Avoid sending multiple retries in a short period

  • Space retries by several hours if needed

4. Review Account Quality

  • Go to WhatsApp Manager → Account Quality

  • Check for:

    • Low quality rating

    • Warnings or restrictions

  • Improve opt-in flow if quality is degraded

5. Retry After Some Time

  • Some delivery blocks are temporary

  • Retry after 6–24 hours instead of immediately

Important Notes

  • Delivery errors often occur even if the API response is 200 OK

  • Repeated delivery failures can impact account quality

  • Marketing messages are more likely to be restricted than transactional messages

When to Contact Support

Contact Meta Business Support if:

  • Multiple valid numbers are failing consistently

  • Account quality shows warnings without clear reason

Provide:

  • WhatsApp Business Account ID

  • Phone Number ID

  • Sample message ID and timestamp

Issue: WhatsApp Template Approved but Not Sending

Problem Description

Your WhatsApp template shows as Approved in WhatsApp Manager, but messages using that template fail to send or return template-related errors.

This prevents businesses from initiating conversations or sending notifications.

Why This Happens

This issue usually occurs due to:

  • Template language mismatch in the API request

  • Incorrect template name or namespace

  • Template paused due to low quality

  • Variable count mismatch

  • Template disabled by Meta after repeated pauses

  • Using a template from a different WABA

Meta may:

  • Reject the message silently

  • Return a template-related error

  • Temporarily pause the template

How to Resolve the Issue

1. Verify Template Details

  • Confirm:

    • Exact template name (case-sensitive)

    • Correct language code (e.g., en_US, en_GB)

    • Correct WhatsApp Business Account

2. Check Variable Mapping

  • Ensure:

    • All placeholders ({{1}}, {{2}}) have values

    • No extra or missing variables are sent

3. Check Template Status

  • Go to WhatsApp Manager → Message Templates

  • Ensure the template is:

    • Approved

    • Not paused or disabled

4. Create a New Template (If Needed)

  • If the template is disabled:

    • Create a new template with revised content

    • Avoid promotional or spam-like wording

Important Notes

  • Approved templates can still be paused later due to quality

  • Template errors do not always appear immediately

  • Each language version is treated as a separate template

When to Contact Support

Raise a ticket if:

  • Template is approved but fails for all users

  • Status shown in UI does not match API behavior

Issue: WhatsApp Business Account or Phone Number Restricted

Problem Description

Your WhatsApp Business Account (WABA) or phone number becomes restricted, blocked, or unable to send messages without a clear explanation.

Why This Happens

  • Policy violations

  • High spam or block rate

  • Poor opt-in practices

  • Suspicious activity or automation misuse

  • Repeated message rejections

How to Resolve the Issue

  1. Check Account Quality in WhatsApp Manager

  2. Review Meta policy violations

  3. Improve opt-in and message relevance

  4. Submit an appeal via Meta Business Support

Important Notes

  • Restrictions may be temporary or permanent

  • Creating new WABAs to bypass restrictions is not allowed

Issue: WhatsApp Display Name Approved but Not Visible

Problem Description

Your WhatsApp display name shows as Approved in WhatsApp Manager, but it does not appear correctly to users on WhatsApp. In some cases, users may see only the phone number instead of the business name.

This issue usually indicates a Meta-side sync or caching problem rather than a setup mistake.

Why This Happens

This issue can occur due to one or more of the following reasons:

  • Delay in Meta syncing the approved display name

  • WhatsApp app cache on the user’s device

  • Recent bot reconnection or phone number changes

  • Meta backend inconsistencies

  • The display name was approved but not yet propagated globally

Meta may:

  • Show only the phone number to users

  • Show an old or partial display name

  • Delay name visibility without any error

How to Resolve the Issue

  1. Reconnect the WhatsApp Bot

    • Disconnect and reconnect the WhatsApp integration

    • Ensure the correct Phone Number ID is used

  2. Ask the User to Refresh

    • Ask users to:

      • Restart WhatsApp

      • Clear WhatsApp cache (Android)

      • Save the number as a contact

  3. Recreate the Bot (If Needed)

    • If reconnection does not work:

      • Create a new bot

      • Reattach the same WhatsApp number

  4. Wait for Meta Sync

    • Display name sync can take 24–72 hours

Important Notes

  • This is usually a Meta-side issue

  • Repeated display name changes are not recommended

  • The display name must comply with Meta naming policies

When to Contact Support

Contact Meta Support if:

  • Display name remains invisible after 72 hours

  • Name shows incorrectly across multiple users

Issue: 24-Hour Customer Service Window Expired

Problem Description

You may see errors when sending free-form messages because the 24-hour customer service window has expired. Messages fail unless sent using an approved template.

Why This Happens

This happens when:

  • The user has not replied in the last 24 hours

  • The business attempts to send session messages

  • No valid template is used to reinitiate conversation

Meta may:

  • Reject the message

  • Require template usage

  • Prevent message retries

How to Resolve the Issue

  1. Use an Approved Template

    • Send a template to reopen the conversation

  2. Wait for User Reply

    • Once the user replies, the 24-hour window resets

  3. Avoid Session Messages Outside Window

    • Do not send free-text messages after 24 hours

Important Notes

  • Each user has an independent 24-hour window

  • Templates are mandatory outside the window

When to Contact Support

No support required. This is expected Meta behavio

Issue: WhatsApp Template Paused Due to Quality

Problem Description

Your WhatsApp template status changes to Paused even though it was previously approved and working.

Why This Happens

Templates can be paused due to:

  • High user block rate

  • Low engagement or negative feedback

  • Spam-like wording

  • Misleading or promotional language

Meta may:

  • Pause the template automatically

  • Reduce delivery success

  • Disable the template permanently if issues persist

How to Resolve the Issue

  1. Review Template Content

    • Remove promotional or aggressive wording

    • Make the message clear and relevant

  2. Improve Opt-in Quality

    • Ensure users explicitly consented

  3. Create a New Template

    • Revised content

    • Submit for approval again

Important Notes

  • Paused templates cannot be used

  • Disabled templates cannot be recovered

When to Contact Support

Support cannot re-enable disabled templates. Create a new one.

Issue: WhatsApp Phone Number Not Receiving OTP During Setup

Problem Description

While registering a phone number for WhatsApp Business Platform, the OTP is not received via SMS or call, blocking setup.

Why This Happens

  • Incorrect country code or number format

  • SMS/call blocked by telecom provider

  • Number already linked to another WhatsApp account

  • Too many OTP attempts in a short time

Meta may:

  • Temporarily block OTP retries

  • Fail number registration

How to Resolve the Issue

  1. Verify Number Format

    • Include correct country code

    • Remove spaces or special characters

  2. Try Call Verification

    • Switch from SMS to Call option

  3. Wait Before Retrying

    • Wait 1–2 hours before retrying OTP

  4. Ensure Number Is Free

    • Remove the number from any existing WhatsApp account

Important Notes

  • Virtual or VoIP numbers may not work

  • Excessive retries can trigger temporary blocks

When to Contact Support

If OTP fails consistently for 24 hours, contact Meta Support.

Issue: Messages Sent Successfully but User Does Not Receive Them

Problem Description

The API returns a success response, but the end user does not receive the WhatsApp message.

Why This Happens

  • User has blocked the business

  • User muted or archived the chat

  • Meta delivery restrictions

  • Device offline or WhatsApp not updated

  • Healthy messaging ecosystem limits applied

Meta may:

  • Silently drop the message

  • Prevent retries

How to Resolve the Issue

  1. Ask User to Reply

    • Confirms the number is reachable

  2. Reduce Message Volume

    • Avoid bulk or repetitive messages

  3. Retry After Time Gap

    • Wait several hours before retrying

Important Notes

  • Delivery is not guaranteed even on success response

  • User behavior heavily affects delivery

When to Contact Support

Only if multiple users are affected consistently.

Issue: Rate Limit or Throughput Exceeded

Problem Description

Messages fail when sending large volumes in a short time.

Why This Happens

  • Exceeding WhatsApp message throughput limits

  • Sudden traffic spikes

  • Low account tier limits

Meta may:

  • Reject messages

  • Delay delivery

  • Return rate-limit errors

How to Resolve the Issue

  1. Throttle Message Sending

    • Send messages in batches

  2. Upgrade Messaging Tier

    • Improve quality and engagement

  3. Monitor Webhooks

    • Detect rate-limit errors early

Important Notes

  • Limits vary by account quality

  • Gradual scaling is recommended

Issue: Error Code 190 – Access Token Has Expired

Problem Description

You may encounter Error Code 190 with the message “Access token has expired” while sending WhatsApp messages or making API calls to Meta. This error indicates that the access token used for authentication is no longer valid.

When this happens, all WhatsApp API requests fail until a new valid access token is generated and updated.

Why This Happens

This issue occurs due to one or more of the following reasons:

  • The access token has reached its expiry time

  • A short-lived access token is being used instead of a long-lived token

  • The system or bot has not refreshed the token automatically

  • Token was revoked due to permission or security changes

  • Business Manager or app permissions were modified

  • The Meta app was reconnected or removed and added again

Meta may:

  • Reject all API requests

  • Return authentication errors for message sending

  • Stop message delivery completely until the token is updated

How to Resolve the Issue

Follow these steps in order:

1. Generate a New Access Token

  • Go to Meta Developers Dashboard

  • Select your Meta App

  • Navigate to WhatsApp → API Setup

  • Generate a new access token

2. Update the Token in Your Platform

  • Replace the expired token in:

    • WhatsApp bot settings

    • API configuration

    • Environment variables (if applicable)

3. Use a Long-Lived Access Token (Recommended)

  • Convert short-lived tokens to long-lived tokens

  • Long-lived tokens reduce frequent expiry issues

4. Verify App Permissions

  • Ensure required permissions are granted:

    • whatsapp_business_messaging

    • whatsapp_business_management

5. Retry Message Sending

  • After updating the token:

    • Retry sending a WhatsApp message

    • Confirm the error no longer appears

Important Notes

  • Access tokens expire by default unless refreshed

  • Hard-coding short-lived tokens is not recommended

  • Token expiration is a common reason for sudden message failures

  • Always regenerate tokens after reconnecting a WhatsApp integration

When to Contact Support

Contact Meta Business Support if:

  • New tokens expire unexpectedly

  • Valid permissions still return Error 190

Provide:

  • Meta App ID

  • WhatsApp Business Account ID

  • Phone Number ID

  • Timestamp of the error

Issue: Error Code 100 – Invalid Parameter

Problem Description

You may encounter Error Code 100 with the message “Invalid parameter” when making API requests to Meta’s WhatsApp Business Platform. This error indicates that one or more parameters in the request are unsupported, incorrectly formatted, misspelled, or invalid.

This issue commonly occurs while sending messages, configuring WhatsApp Flows, registering phone numbers, or updating WhatsApp-related settings.

Why This Happens

This error can occur due to one or more of the following reasons:

  • One or more request parameters are misspelled

  • An unsupported parameter is included in the API request

  • Required parameters are missing

  • Incorrect data type is used (string instead of object, number instead of string, etc.)

  • Parameter value exceeds Meta’s allowed length limits

  • Incorrect or mismatched Phone Number ID

  • Using a Phone Number ID that does not belong to the current WhatsApp Business Account

  • Incorrect configuration during WhatsApp Flow setup

For WhatsApp Flows–specific cases, this error can occur when:

  • The business public key is not a valid 2048-bit RSA public key

  • The public key is not in PEM format

  • The public key contains extra spaces, missing headers, or invalid line breaks

Meta may:

  • Reject the request immediately

  • Block message or flow execution

  • Return a generic “Invalid parameter” error without detailed field-level feedback

How to Resolve the Issue

Follow these steps in order:

1. Verify API Parameters

  • Cross-check your request with the official endpoint reference

  • Ensure:

    • All parameter names are spelled correctly

    • Only supported parameters are included

    • Required fields are not missing

2. Validate Parameter Values

  • Confirm:

    • Correct data types (string, object, array)

    • Values do not exceed allowed length limits

    • No empty or null values are passed where not allowed

3. Verify Phone Number ID

  • Ensure:

    • The Phone Number ID belongs to the same WhatsApp Business Account

    • The ID matches the number currently registered

  • Avoid reusing a Phone Number ID stored from a previous or deleted setup

4. Check WhatsApp Flows Public Key (If Applicable)

  • Ensure the business public key:

    • Is a 2048-bit RSA key

    • Is in PEM format

    • Includes:

    • Does not contain extra spaces or invalid characters

5. Remove Unsupported Parameters

  • Eliminate:

    • Deprecated fields

    • Custom fields not recognized by Meta

  • Retry with a minimal valid request payload

6. Retry the Request

  • After correcting the parameters:

    • Resend the API request

    • Confirm the error no longer occurs

Important Notes

  • Error Code 100 is a validation error, not a server issue

  • Meta does not auto-correct invalid parameters

  • Even a single incorrect field can cause the entire request to fail

  • WhatsApp Flow setup is especially sensitive to public key formatting

When to Contact Support

Contact Meta Business Support if:

  • The error persists despite using a valid request structure

  • The parameter appears correct but is still rejected

Provide:

  • API endpoint used

  • Full request payload (excluding secrets)

  • WhatsApp Business Account ID

  • Phone Number ID

  • Error response with timestamp

Issue: API Permission Error (200–299 Range)

Problem Description

You may encounter an API Permission error (error codes in the 200–299 range) when making requests to Meta’s WhatsApp Business Platform. This error indicates that the access token being used does not have the required permissions, or that previously granted permissions have been removed or revoked.

When this happens, the API request is rejected even if the request structure and parameters are correct.

Why This Happens

This issue can occur due to one or more of the following reasons:

  • Required WhatsApp permissions were not granted to the Meta app

  • Permissions were revoked due to security or policy changes

  • The access token was generated before permissions were approved

  • The Meta app was reconnected or reauthorized

  • Business Manager ownership or role changes

  • The token belongs to a different app than the one linked to the WhatsApp Business Account

  • Using a system user token without proper asset assignment

Meta may:

  • Reject message sending requests

  • Block access to WhatsApp endpoints

  • Return authorization or permission-related errors

  • Prevent WhatsApp Flows or template operations

How to Resolve the Issue

Follow these steps in order:

1. Check Required Permissions

Ensure your Meta app has the following permissions enabled:

  • whatsapp_business_messaging

  • whatsapp_business_management

These permissions must be approved and active.

2. Verify Access Token Permissions

  • Open Meta Access Token Debugger

  • Paste the access token

  • Verify:

    • Token is valid and not expired

    • Required permissions are listed

    • Token belongs to the correct app and business

3. Re-generate the Access Token

  • Go to Meta Developers Dashboard

  • Select your app

  • Generate a new access token after permissions are granted

  • Update the new token in your WhatsApp integration or bot settings

4. Verify System User & Asset Assignment (If Applicable)

If using a system user token:

  • Go to Business Settings → Users → System Users

  • Ensure the system user:

    • Has access to the WhatsApp Business Account

    • Has access to the Phone Number

    • Has the required permissions assigned

5. Reconnect WhatsApp Integration

  • Disconnect and reconnect the WhatsApp integration

  • This refreshes permission bindings between the app and WABA

6. Retry the API Request

  • After fixing permissions:

    • Retry sending a message or API call

    • Confirm the error is resolved

Important Notes

  • Permission errors are not caused by invalid parameters

  • Tokens generated before permission approval will not work

  • Revoked permissions require token regeneration

  • Permission changes may take a few minutes to propagate

When to Contact Support

Contact Meta Business Support if:

  • Permissions appear correct but requests still fail

  • Access Token Debugger shows missing or incorrect permissions

Provide:

  • Meta App ID

  • WhatsApp Business Account ID

  • Access token type (user/system)

  • Screenshot of Access Token Debugger results

  • Error code and timestamp

Issue: Error Code 368 – Temporarily Blocked for Policy Violations

Problem Description

You may encounter Error Code 368 with the message “Temporarily blocked for policy violations” when sending messages or performing API actions on the WhatsApp Business Platform. This error indicates that the WhatsApp Business Account (WABA) associated with your app has been restricted or disabled due to a violation of Meta’s platform or WhatsApp policies.

When this happens, message sending and other WhatsApp-related operations are blocked until the restriction is reviewed or lifted.

Why This Happens

This issue can occur due to one or more of the following reasons:

  • Sending messages without proper user opt-in

  • High user block or report rates

  • Spam-like or misleading message content

  • Repeated template rejections or low template quality

  • Violating WhatsApp Commerce, Messaging, or Platform Policies

  • Abnormal message volume spikes

  • Misuse of automation or bulk messaging tools

  • Multiple policy warnings ignored over time

Meta may:

  • Temporarily restrict the WhatsApp Business Account

  • Disable message sending across all phone numbers

  • Reduce messaging tiers or throughput

  • Permanently disable the WABA in severe cases

How to Resolve the Issue

Follow these steps carefully:

1. Review Policy Enforcement Details

  • Go to Meta Business Manager

  • Navigate to Account Quality or Policy Enforcement

  • Review:

    • Violation type

    • Affected assets

    • Restriction duration (if shown)

2. Identify the Violation Source

Check for:

  • Recent campaigns or message blasts

  • Marketing or promotional templates

  • Non-compliant opt-in flows

  • Repeated user blocks or complaints

Document what may have triggered the restriction.

3. Improve Compliance Before Appealing

Before contacting Meta:

  • Stop all message sending from the affected WABA

  • Update opt-in processes to be explicit and documented

  • Revise templates to be:

    • Clear

    • Non-promotional (unless explicitly opted in)

    • Honest and relevant

  • Reduce messaging frequency

4. Submit an Appeal (If Available)

  • Go to Meta Business Support

  • Submit an appeal for the restricted WhatsApp Business Account

  • Clearly explain:

    • What caused the issue

    • What corrective steps have been taken

    • How future violations will be prevented

5. Wait for Meta Review

  • Reviews can take several business days

  • Do not attempt to bypass restrictions by:

    • Creating new WABAs

    • Using new phone numbers for the same use case

Important Notes

  • Error 368 is a policy enforcement action, not a technical error

  • Temporary blocks can become permanent if violations continue

  • Creating new accounts to avoid restrictions violates Meta policy

  • Message delivery will remain blocked until Meta lifts the restriction

When to Contact Support

Contact Meta Business Support immediately if:

  • Your business use case is legitimate and compliant

  • You believe the restriction was applied incorrectly

  • The block affects production or live users

Provide:

  • WhatsApp Business Account ID

  • Business Manager ID

  • Description of your messaging use case

  • Corrective actions taken

  • Screenshots from Account Quality or Policy Enforcement page

PreviousMeta AdsNextContacts & Chats APIs

Last updated

Was this helpful?