WhatsApp API error 131042: Business eligibility payment issue
Error 131042 means WhatsApp won't send because of a problem with the payment set-up behind the WhatsApp Business Account. Meta charges for delivered messages, and when it can't bill the account, sends stop.
Quick answer
Meta can't charge your WhatsApp Business Account for messages. Check which payment method or credit line covers the account and that it's active, within its limit and fully set up.What WhatsApp error 131042 means
Meta documents 131042 as: there was an error related to your payment method. Its list of common problems includes a payment account not attached to the WhatsApp Business Account, a credit line over its limit or not set or not active, a deleted or suspended account, the time zone or currency not set, and an on-behalf-of (MessagingFor) request that is pending or declined.
Why error 131042 happens
Account errors come from the set-up behind the number, not from the message. Check these:
- No payment method or credit line attached to the WhatsApp Business Account.
- The credit line has reached its limit, or was removed.
- The account's currency or time zone was never set during onboarding.
- The WhatsApp Business Account is suspended or was deleted.
- An on-behalf-of sharing request with the solution provider is still pending or was declined.
How to fix error 131042
Work through these in order; the first one that turns up a problem is usually the fix.
- Find out who pays Meta for this account: a payment method in your own Meta business settings, or your solution provider's credit line.
- If it's your own payment method, check it's attached to the account, valid, and not past its limit.
- Make sure the account's currency and time zone are set.
- If your provider's credit line covers the account, contact the provider with the trace ID of a failed send.
- Check the account isn't suspended, and approve any pending account-sharing request.
Should you retry after 131042?
Sends keep failing until the billing problem is fixed. Once it is, resend the failed messages; templates and contacts are unaffected.
How error 131042 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131042, the "(#131042)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 131042, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up. If InfiQ set up the account for you, send InfiQ support the InfiQ_traceid of a failed message so the billing set-up can be checked with Meta.