WhatsApp Business API in Saudi Arabia: Setup for KSA Companies

A Saudi company gets WhatsApp Business API access by registering a Meta business account, verifying the business with its Commercial Registration (CR) documents, connecting a dedicated phone number, and sending only approved templates to customers who opted in. You can do this through a Business Solution Provider (BSP) or build directly on Meta's Cloud API. Either way, the real work is clean documents, Arabic-first templates and proper opt-in records.

This guide covers each step for a KSA company, with a checklist, a comparison table and the mistakes that slow approvals down.

What do you need for WhatsApp Business API in Saudi Arabia?

You need a registered Saudi business, a Meta business portfolio, a phone number that is dedicated to the API, and proof that customers opted in. The business side matters most, because Meta's verification looks at documents about the legal entity.

Prepare these before you start:

• CR certificate from the Ministry of Commerce, with the exact legal name and CR number.
• Business address that matches your CR, ideally with your Saudi National Address.
• VAT registration certificate from ZATCA, if registered. It is a second document that shows the same legal name.
• Website or social page that shows the same business name. A landing page with the company name and contact details is enough to start.
• A phone number that can receive a verification call or SMS. Use a number that is not in daily use on a normal WhatsApp app.
• A payment method for the live account. Meta creates test accounts and test numbers automatically with Cloud API, with relaxed limits and no payment method needed. Use them to build and test first (Meta for Developers).

The exact documents Meta accepts can change. Always follow the list shown in your Business Manager verification flow, not a vendor's blog.

How do CR documents and Arabic company names affect verification?

Meta compares the name and details you type with the name and details on your documents, so any mismatch can cause a rejection or a delay. In Saudi Arabia the usual mismatch is the Arabic legal name versus the English trade name.

Check these points before you upload:

1. Use the legal name from the CR exactly. If the CR shows an Arabic name only, enter a faithful transliteration as a display name, but keep the legal name field identical to the document.
2. Match every document. The CR, the VAT certificate and your website footer should show the same entity. A group brand on the website and a different legal name on the CR is a common cause of delays.
3. Keep the address consistent. Use the same building, district and city on all documents. If your CR lists a branch, say which one you are verifying.
4. Upload clear, current files. Use a full-page scan or PDF, not a cropped photo. Do not upload an expired CR.
5. Verify the domain. Use a business email or website domain that carries your company name.

We could not confirm exact timing from a Meta source. Vendor pages quote one business day to about ten, but those are their marketing claims. Plan for a buffer.

BSP or direct Cloud API: which route should a KSA company choose?

Choose a BSP if you want help with onboarding, templates and connectors. Choose direct Cloud API if you have developers and want full control. Vendor pages often say API access must go through a BSP (Quali-D), but another Saudi guide describes direct Cloud API as a real option (H. Haboubi). Treat both routes as possible and check Meta's current documentation.

Comparison based on the H. Haboubi guide. Some BSPs ship Salla and Zid connectors, which helps if your store runs on those platforms.

Ask any provider these questions before signing:

• Is the WhatsApp number registered under my company's Meta business portfolio, or theirs? You want it under yours so you can leave.
• Are invoices in SAR, and is VAT shown separately?
• How are Meta's message charges passed through, and what is the markup?
• Is there an Arabic-capable agent inbox?
• Can I export my opt-in records and conversation history?

Meta publishes its own rate card. Check it directly instead of relying on a vendor's table, because rates and categories change.

How do you set up Arabic-first templates?

Write the Arabic template first, submit it for approval in the correct category, and add an English version only if you need one. Templates are the only message type you can send to a WhatsApp user outside the customer service window, and they carry quality scores and messaging limits (Meta for Developers).

Practical points for Arabic:

• Right-to-left display. WhatsApp shows Arabic text right to left on the customer's phone. Preview the template on a real handset, not only in the dashboard.
• Mixed text. Order numbers, tracking IDs and amounts are often Latin digits inside an Arabic sentence. Test that variables do not flip the order of the sentence.
• Placeholders. Put the variable in the middle of a sentence, not at the very start or end, to avoid layout surprises. Keep variable text short.
• Tone. Use clear Modern Standard Arabic or a light, neutral Gulf tone. Avoid heavy slang in a legal or payment message.
• Language selection. Pick Arabic as the template language when you create it, and send the matching version to customers whose language you know.

Choose the right category

Meta checks whether a template's content fits its category. Misuse is penalised in stages: a written warning, then rate limiting of utility messages, then utility templates being recategorised as marketing (Meta for Developers).

So do not hide a promotion inside an order update. A COD confirmation ("Your order 1042 will arrive tomorrow. Please keep SAR 180 ready") is a utility message. A "20% off this weekend" message is marketing.

How do you handle opt-in and PDPL?

Collect opt-in before you send any template, and record it. Meta requires opt-in before message templates, and the opt-in must state your business name and what the customer will receive (Meta for Developers). Saudi Arabia's Personal Data Protection Law (PDPL) is enforced by SDAIA. Read SDAIA's own guidance or take legal advice, because we could not verify its detail from a primary page for this guide.

A simple opt-in process:

1. Add a clear, unticked checkbox at checkout on your Salla, Zid or own website: "Send my order updates on WhatsApp."
2. State your company name and the type of messages, such as order updates or offers.
3. Save the phone number, the date and time, the wording shown and the channel.
4. Send a confirmation template. Meta's table lists opt-in management messages, such as confirming or cancelling opt-in, as a utility example.
5. Honour "stop" at once and record it.
6. Never upload a bought or scraped list. Broadcast only to contacts who opted in.

What does the setup look like step by step?

Most KSA companies follow this order:

1. Create or confirm your Meta business portfolio under your legal company name.
2. Gather the CR, VAT certificate, address proof and website.
3. Start business verification and fix any name mismatch.
4. Pick a route: BSP or direct Cloud API.
5. Test with the test number and test account first.
6. Register your dedicated number and display name.
7. Submit Arabic templates, then English if needed.
8. Connect the inbox your team will reply from.
9. Switch on opt-in capture on your store or website.
10. Start with a small group of opted-in contacts and watch template quality.

For step 8, Quickship's Meta Messaging Module gives your team a shared inbox for WhatsApp, Instagram and Messenger. Quickship is a software company. You still need your own verified Meta business account and WhatsApp number.

What mistakes slow KSA companies down?

• Different names on different documents. Fix this before you apply.
• Using the personal or sales team's active number. Use a dedicated one.
• Sending offers as "utility" templates. This triggers category penalties.
• No opt-in record. You cannot prove consent later.
• English-only templates for Arabic-speaking customers. Replies and trust drop. Do not assume results, but test with your own audience.
• Letting the BSP own the account. Keep your number under your own business portfolio.
• Expecting in-chat payments. Native WhatsApp Pay is not available in the Kingdom, so use a Saudi-licensed payment gateway and send a payment link (H. Haboubi).