How to Set Up the WhatsApp Business API for UK Clients Without Getting Blocked
If you are setting up a WhatsApp Business API integration for a UK-based client—or for your own UK entity while operating from India or Pakistan—you have probably already run into a wall. Maybe Meta rejected your Business Manager verification. Maybe your virtual UK phone number isn't receiving the registration OTP. Or perhaps you are staring at Meta's documentation trying to figure out why your webhook keeps failing.
This is not a theoretical guide. This is the exact process for getting a UK business approved, verified, and sending messages on the WhatsApp Cloud API without getting your account flagged or your number banned.
The Verification Hurdle: Getting a UK Company Approved
You do not technically need a verified Meta Business Portfolio (formerly Business Manager) to start using the API. Unverified accounts can send up to 250 business-initiated conversations per day. However, for any real UK business, this limit is too low. To lift this limit, you must verify the business identity.
Meta is incredibly strict with UK company verification. If you are registering a UK Limited Company (Ltd), the details you enter into Meta Business Suite must match the UK Companies House registry exactly. If your company is registered as "ABC SOLUTIONS LTD" on Companies House, do not type "ABC Solutions" into Meta. It will be rejected.
You will need to upload official documents. Meta accepts these specific UK documents:
- Certificate of Incorporation: This must show the official registration number and the company name.
- Filing History Documents: A recent CS01 (Confirmation Statement) or AA01 (Change of Accounting Reference Date) from Companies House.
- Utility Bills or Bank Statements: These must show the exact trading address of the business and the company name. If you are using a virtual office address in London (like those provided by 1st Formations or Your Company Formations), the utility bill must still bear the company name.
Do not upload scanned PDFs with blurry text. Meta uses automated OCR systems to read these documents. If the OCR engine cannot read the registration number or the address, a human reviewer will rarely look at it; it will simply be auto-rejected with a generic "Ineligible" error.
The Technical Setup: Cloud API vs. Business Solution Providers
You have two ways to access the API: directly through Meta's Cloud API, or through a Business Solution Provider (BSP).
For almost every developer or agency, the Meta Cloud API is the correct choice. It is hosted by Meta, meaning you do not pay hosting fees for the API container, and you get direct access to the latest features without waiting for a middleman to update their systems. You can set this up directly at developers.facebook.com.
To make the Cloud API work, you need a web server that can handle incoming HTTPS POST requests. When a UK customer sends a message to your API number, Meta's servers send a JSON payload to your webhook.
Here is a critical detail that catches developers out: your webhook server must respond to Meta's verification request (a GET request with a hub.challenge parameter) and must return a 200 OK status code within three seconds on all incoming POST requests. If your server takes too long to process the message (for example, if you are running a slow database query before responding), Meta will timeout, retry the delivery, and eventually disable your webhook entirely.
A Worked Example: The Real Cost of UK Messaging
Meta charges for the WhatsApp API based on 24-hour conversation windows. Once a message is sent or received, a 24-hour window opens. Any further messages sent within that window do not incur extra charges.
The rates depend on the country code of the recipient, not the sender. If your API number is a UK number (+44) and you are messaging a UK customer (+44), you pay the UK rate. If you message a customer in India (+91), you pay the India rate.
Meta categorizes conversations into four types. Let us look at a realistic monthly scenario for a UK-based e-commerce store. We will calculate the costs in USD, as Meta bills most international accounts in USD.
| Conversation Type | Description | UK Rate (Approx. USD) | Monthly Volume | Total Cost |
|---|---|---|---|---|
| Marketing | Promotions, discounts, abandoned cart alerts | $0.072 | 1,200 conversations | $86.40 |
| Utility | Order confirmations, shipping updates, 2FA | $0.041 | 2,000 conversations | $82.00 |
| Service | Customer support chats initiated by the user | $0.038 | 1,500 conversations | $19.00 * |
| Authentication | One-time passwords (highly regulated) | $0.045 | 100 conversations | $4.50 |
* Note on Service Conversations: Meta gives every WhatsApp Business Account 1,000 free Service conversations per month. In the math above, only 500 of the 1,500 service conversations were billed (500 x $0.038 = $19.00).
This means the total monthly Meta bill for this UK store would be $191.90. This is paid directly to Meta via the credit card linked to your Meta Business Portfolio. If you use a third-party software to manage these chats, you will pay their monthly subscription fee on top of this.
What Does Not Work (And What We Do Not Recommend)
We have set up hundreds of these accounts. Here is what fails, what gets blocked, and what you should avoid doing.
1. Cheap Virtual Numbers
Do not use cheap, disposable VoIP numbers from random mobile apps to register your API. Meta's system checks the carrier database. If the number is flagged as a non-fixed VoIP number with no SMS capability, you will not receive the registration OTP, or Meta will flag the account for suspicious activity within 48 hours. If you need a virtual UK number, use a reputable telecom provider that offers real SIM cards or enterprise-grade virtual numbers that support inbound SMS and voice calls from international senders.
2. Migrating an Active Number Without Planning
You cannot use the same phone number on the regular WhatsApp Business App and the WhatsApp API at the same time. If you register a number on the API, it is instantly disconnected from your phone app. All existing chat history on that phone is lost permanently. If you need to keep your history, do not migrate the number. Buy a new, clean number for the API.
3. Ignoring GDPR and UK Data Protection Laws
If you are handling UK customer data from India or Pakistan, you must comply with the UK GDPR. This means you cannot simply buy a list of UK mobile numbers and blast them with marketing templates. If UK users click the "Report Spam" button on your message, Meta's system will immediately drop your phone number's quality rating. If your rating stays "Low" for more than a few days, Meta will restrict your daily sending limits or suspend your templates.
You must provide a clear opt-out. We recommend adding a quick-reply button to your marketing templates that says "Opt Out" or "Stop". When a user clicks it, your webhook must catch this payload and flag their record in your database so you never message them again.
To drive traffic to your API cleanly without spamming, you can use tools like WA Link to generate click-to-chat links. WA Link is a simple link generator that creates a direct URL or QR code containing a pre-filled message. You can place this link on your UK client's website, Instagram bio, or local print flyers. However, remember that WA Link is just a router; it does not host your database, build your chatbots, or bypass Meta's verification rules.
Frequently Asked Questions
Can I use a UK landline number for the WhatsApp API?
Yes. During the registration process in the Meta Developer Console, you can choose to verify the phone number via a voice call instead of an SMS. Meta's automated system will call the landline and read out the six-digit verification code. Ensure your landline does not have an interactive voice response (IVR) system active during this time, or the automated call will fail.
What is Meta Error Code 131031?
This is one of the most common errors developers face. It means "Account has outstanding balance or payment method is missing." Even if you are within your free tier limits, Meta requires a valid credit card attached to the WhatsApp Business Account billing section before you can send template messages to UK numbers.
Can I register a UK WhatsApp API using a non-UK credit card?
Yes. You can use an Indian or Pakistani credit card to pay for Meta's UK traffic. However, your bank may charge international transaction fees, and you must ensure that international payments are enabled on your card. The billing currency of your Meta account will determine the currency of your invoices.
How long does Meta Business Verification actually take for a UK company?
If your documents are perfect and match Companies House exactly, verification usually takes between 2 hours and 48 hours. If there is a discrepancy in the address or name, it can drag on for weeks with repeated rejections. Always double-check the spelling of the company name on your utility bill before uploading.
Can I send PDFs and images to UK customers?
Yes, but you must use media message templates. You cannot send arbitrary media files to a user unless they have messaged you first within the last 24 hours. For business-initiated messages, you must upload the document or image to Meta's servers first, or provide a public URL to the media file within the template payload.
Your Next Step
Do not spend days reading more documentation. Go to developers.facebook.com/apps, create a business app, add the WhatsApp product, and use the temporary test number provided by Meta to send a single curl request to your own phone. Once you see that test message land on your screen, the rest of the architecture will make sense.