Configure the WhatsApp API payment method in Business Manager to be able to use it in SprintHub
This detailed guide will help you understand and perform the setup correctly, ensuring that your company can continue to communicate efficiently with your customers via WhatsApp.
Issue with support sessions
If your support sessions are appearing as shown below, it means there is a payment problem with the official WhatsApp; because of this Meta blocks communication with any integration:
Clicking on the icon should show the following error:
402 - Business eligibility β Payment issue
Which means:
The message was not sent because one or more errors related to your payment method occurred.
The payment account is not linked to a WhatsApp account The credit line exceeded the limit Credit line (payment account) not set or active The WhatsApp business account was deleted The account was suspended by us Time zone not set Currency not set The MessagingFor (on behalf of (OBO)) request is pending or refused The free conversation tier limit was exceeded without a valid payment method. (This type of error will be thrown on February 1, 2022). Check your payment setup in the WhatsApp Manager and try again.
π³ How to add a credit card to the WhatsApp API (WABA) account
To use the Meta Cloud API, send WhatsApp templates and keep your WABA active, it is necessary to have a registered payment method on Meta.
This card is added inside Business Manager β not on WhatsApp.
Make sure you are using the same Business Manager where your WABA is configured.
β 2. Go to Payment Settings
In the side menu:
Business Settings β Accounts β WhatsApp Accounts
Click on your WhatsApp account
In the right corner, click on Payment Settings
(Or Payment Settings / Payments, depending on the language)
If you prefer another path:
Business Settings β Billing / Payments
Your WABA also appears there.
β 3. Select the payment method
Click Add payment method
Choose Credit or debit card
Enter the details:
Card number
Expiration date
CVV
Cardholder name
Billing address
Click Save
β οΈ Important information
β The card must have:
International usage enabled
Available limit in dollars
Permission for online purchases (e-commerce)
Meta charges in USD, even if you are in Brazil.
π‘ Where exactly does this appear in BM?
Depending on your Business Manager version, names may vary. Possible locations are:
Location 1 β Payments (most common)
Business Settings β Payments
Here the WABA and ads tab appears.
Location 2 β Billing
Business Settings β Billing
Location 3 β In the WABA itself
Business Settings β Accounts β WhatsApp Accounts β Payment settings
β If the βAdd paymentβ button does not appear
This can happen if:
β Your business is not verified
Check in:Business Settings β Security Center β Business verification
β You do not have permission to manage payments
Ask someone to add the following for you:
Permission: Finance editor
β The WABA is linked to another Business Manager
The integration may be in another BM (very common).
To check:
Business Settings β Accounts β WhatsApp Accounts β Owner
π― Quick summary
Access the Business Manager
Go to Payments or WhatsApp Accounts β Payment settings
Click Add payment method
Enter the card
Save
π Payment Verification
After adding the credit card to your WABA account, it is important to confirm whether the payment method is working correctly. To do this, follow the steps below:
Send a test message using the WhatsApp API
Use your already configured integration
Send a message template (HSM) to any authorized number.
Check whether the message was sent successfully
If you are using SprintHub, you can check the log inside SAC360 or the integration logs.
With the provider, check the message status records.
If the message is not sent:
Review the payment settings in Business Manager.
Confirm whether the card has active, available limit and enabled for international purchases.
Check whether your business is verified, as this can block paid messages.
Make sure the card is selected as the default payment method for the WABA.
After confirmation, your account will be ready for continuous API use and template sending.