WhatsApp API Payment Method: How to Add a Card
Why Meta asks for a card on your WhatsApp Business account, how to add the payment method, and what the number does until then, with error 131042 explained.
In this article
To send messages that start a conversation through the official WhatsApp API, the WhatsApp Business account needs a payment method registered with Meta. Whoever connects the number through a Tech Provider registers their own card, in their own Business Manager, and Meta charges directly. Without it, the number connects, turns green, and receives and replies to customers, but no template goes out: no promotion, no reminder, no verification code. Registering takes a few minutes and does not require reconnecting anything.
This guide explains why Meta asks you for the card and not the provider, how to recognize the block, the step-by-step to register, and the most common problems along the way.
Why Meta bills you directly
The official API has two bills, and only one of them goes through the provider. The provider charges for the software. Meta charges for using the platform, per delivered template message, as the article on WhatsApp Business API pricing shows.
Who pays Meta depends on the type of partner:
| Partner type | Who pays Meta | Where the payment method lives |
|---|---|---|
| Tech Provider | The company itself, directly to Meta | On the company's WhatsApp Business account, in its own Business Manager |
| Solution Partner | The partner, who passes the cost on to the company | On the partner's credit line, attached to the account |
Meta's page for Tech Providers is direct: businesses connected through a Tech Provider must add a payment method to their WhatsApp Business account, and Meta charges those businesses directly. Only a Solution Partner can extend credit and bill the customer on Meta's behalf.
Frame Conexa is a Meta-verified Tech Provider. That has a practical consequence worth knowing before you connect: there is no way for the provider to register the card for you. There is no screen, no integration, and Meta's connection flow does not cover that step. The upside is that Meta's invoice arrives with no markup at all, and the card never passes through the provider.
How to recognize an account without a payment method
The block for missing payment is deceiving because the number looks healthy. Quality is high, the connection is active, the template was approved, and still the bulk send does not go out.
| What you try | Without a payment method |
|---|---|
| Receive messages | Works |
| Reply inside the 24-hour window | Works, until 09/30/2026 |
| Marketing template | Does not go out |
| Utility template, such as a reminder or confirmation | Does not go out |
| Authentication template, with a code | Does not go out |
| Bulk sending | Does not go out |
Anyone who only handles support notices nothing. The problem shows up on the first send the company initiates, usually the first campaign or the first automatic reminder.
What Meta responds
There are two places where the block shows up by name:
- On sending. The message fails with error 131042, which Meta describes as a problem with the account's payment method: missing card, credit limit exceeded, or inactive billing line. The API error dictionary shows where it fits among the other codes.
- In the account's health. Meta exposes a sending diagnosis per account. Without a payment method, the WhatsApp Business account shows as blocked from sending, with code 141006 and the explanation that this blocks business-initiated conversations.
Missing payment is not missing verification
It is common to confuse two warnings that show up in the same diagnosis:
| Warning | Code | Effect |
|---|---|---|
| No payment method | 141006 | The account starts no conversations at all |
| Business not verified | 141010 | The account sends, with a cap of 250 people per day |
Business verification in Business Manager does not block sending. It defines how far sending goes: without verification, capacity starts at 250 different people per day outside the window. The article on messaging limits shows how to leave that tier. The payment method is a different matter, and without it the cap is zero.
Step by step to register the card
Registration happens at Meta, with a user from the company. Set aside five minutes and have the card at hand.
- Log in with the right user. Open Meta Business Suite with an account that is an administrator of the company's portfolio or has the finance editor role. Without one of those roles, the payment option does not appear.
- Open the company's WhatsApp Manager. In Frame Conexa, the payment warning carries a link that already opens WhatsApp Manager on the right portfolio. When the payment method is missing, that screen shows the alert "No valid payment method" and the Add payment method button.
- Add the card. Follow Meta's form. Use a credit card: debit cards are usually refused in this registration.
- Check the linked account. If the portfolio has more than one WhatsApp Business account, check that the payment ended up on the account of the number you connected.
- Go back to the dashboard. There is no need to reconnect the number or redo the template. The next send goes out.
If you prefer to get there through the menu, the path is in the portfolio settings, in the billing and payments area. Meta changes menu names often, and the dashboard link saves you the search.
Monthly invoicing for high spenders
Besides the card, Meta offers monthly invoicing through a credit line to companies with high spend. The request is made in the same payments area, depends on Meta's approval, and usually requires company documents. For most stores, clinics, and schools, the card does the job.
Reais or dollars
Meta began billing part of its Brazilian customers in reais (R$, the Brazilian currency) on July 1, 2026, and plans to migrate those customers' accounts to reais by June 30, 2027. For anyone connecting through a Tech Provider, the currency is a choice made by the owner of the WhatsApp Business account, not by the provider. The article on API pricing details the dates.
How long until the block lifts
After registration, Meta usually clears the account within a few minutes. The catch is that it notifies nobody: there is no Meta event saying "the payment method was registered." The diagnosis only changes when someone asks.
That is why Frame Conexa asks on its own. Accounts blocked for payment are checked at Meta every few minutes, and the warning disappears from the dashboard without you doing anything. When you open the number's screen, the dashboard checks right then, before showing the page. If the warning persists after half an hour, the cause is usually one of those listed below.
What will show up on the invoice
With the payment method registered, Meta charges for API usage, and only that:
- Delivered templates, at the rate for the category (marketing, utility, or authentication) and the recipient's country. A template that failed is not charged.
- Replies inside the 24-hour window, starting October 1, 2026. Today they are free; after that date they are charged per message, at the utility rate for the recipient's country. The 24-hour window explains when each message falls under each rule.
- Nothing for receiving. A received message is never charged.
With coexistence, messages the team sends through the phone app stay free and do not enter this invoice. The article Is WhatsApp Business free? compares what the app and the API cost.
Important: until September 30, 2026, an account without a payment method still replies to customers inside the 24-hour window, because those replies are not charged. From October 1 they carry a rate, and Meta had not detailed, as of this article's publication, what happens to the replies of an account without a payment method. Do not count on support working without a card after that date: register before.
To track spend before the invoice arrives, each delivered message carries Meta's billing object in the status notification, with the category and whether a charge applied. Anyone integrating through the API and webhooks can add that up by category.
Common problems with registration
The card was refused. Check that it is a credit card, that it accepts international purchases when the account bills in dollars, and that the bank did not block Meta's first charge. Trying another card usually solves it.
The card was registered, but the warning did not go away. The card may have ended up in another portfolio or another WhatsApp Business account. That happens to people who manage more than one company. Open WhatsApp Manager through the dashboard link, which already comes on the right portfolio, and check there.
The option to add payment does not show up. The user does not have the required role. Ask a portfolio administrator to register the card or to give you the finance editor role.
The account was using another partner's credit line. If the number previously went through a Solution Partner and the account still uses its credit line, Meta warns that there may be an error when changing partners. The account needs its own payment method. The article on disconnected coexistence shows the full provider switch.
Sending started failing again weeks later. An expired card, exceeded limit, or refused charge puts the account back in the block, and error 131042 reappears. The dashboard shows the warning again, with the same link.
How Frame Conexa warns you
Since the problem only shows up when the company tries to start a conversation, the dashboard does not wait for that moment:
- At connection. As soon as the number connects, the dashboard checks the account's health at Meta. If payment is missing, the connection screen ends with "one step left" and the link ready, instead of "done." This also applies to the connection link an agency sends to its customer.
- Day to day. The warning appears in the overview, in the numbers list, on the number's screen, and in the campaigns area, always with the link to the company's WhatsApp Manager.
- Before a bulk send. The campaign is not created while the account is blocked for payment, and the screen says why. Without this lock, the campaign would run and fail contact by contact.
- In support. Replying inside the window is not blocked by the dashboard as long as Meta accepts those replies.
Frame Conexa never asks for the card on your Meta account. The Frame Conexa subscription is charged separately, per number, with no per-message charge. The prices are in pricing.
Frequently asked questions
Do I need to register a card to use the WhatsApp API?
To start conversations, yes. Without a payment method on the WhatsApp Business account, no template goes out, whether marketing, utility, or authentication. Receiving messages and replying inside the 24-hour window work without a card until September 30, 2026. Anyone connecting through a Tech Provider registers the card in their own Business Manager, and Meta charges directly.
Where do I register the WhatsApp Business payment method?
In Meta Business Suite, with an administrator or finance editor user of the portfolio. The shortest path is the company's WhatsApp Manager, which shows the invalid-payment-method alert and the button to add one. Through the menu, the option is in the portfolio settings, in the billing and payments area.
What does error 131042 mean?
That Meta refused the send because of a problem with the WhatsApp Business account's payment method: missing card, exceeded limit, or inactive billing line. It is the typical error for someone who just connected and tried the first bulk send. After you register or fix the card, the next send goes out without reconnecting the number.
Can the provider pay Meta for me?
Only if it is a Solution Partner, which can attach its own credit line to your account and pass the cost on. A Tech Provider, like Frame Conexa, does not have that permission from Meta: the card has to be yours. The upside is that Meta's invoice arrives with no markup and the card never passes through the provider.
How long does it take to clear after I register the card?
Usually a few minutes. Meta does not announce when it clears, so Frame Conexa checks blocked accounts on its own every few minutes, and the warning disappears from the dashboard without any action from you. If the warning persists after half an hour, check that the card was registered on the right portfolio and WhatsApp Business account.
Next step
If your number is already connected and the dashboard shows the payment warning, use the warning's own link and register the card now, before October 1. If you have not connected yet, the per-number plans show what each number includes, and the article on Embedded Signup explains what happens in Meta's window.
Keep reading
Pricing
WhatsApp Service Message Billing Starts in October 2026
The 1,000 free service messages per number, Meta's charges from October 1, and how to control replies in Frame Conexa.
Pricing
Is WhatsApp Business Free? App, API and What Meta Charges
The WhatsApp Business app is free, the official API charges per message and coexistence combines the two. See what costs money in each case and when it pays off.
Pricing
WhatsApp Business API Pricing: How Meta Charges (2026)
How much the WhatsApp Business API costs in Brazil in 2026: Meta's per-message pricing, what is free, the October change and what a provider charges per number.
Connect the number you already use to the official WhatsApp API.
No switching numbers, no losing the app and no per-message fee from us. You pay per number; you pay Meta directly.