A Nigerian business's WhatsApp automation choice is downstream of three overlapping regulators — the Nigerian Communications Commission (NCC) for marketing-message discipline and Do Not Disturb enforcement, the Nigeria Data Protection Commission (NDPC) for NDPA 2023 obligations, and the Central Bank of Nigeria (CBN) for the payment-rail step. The NDPA 2023 replaced the earlier NDPR framework, and the 2025 General Application and Implementation Directive (GAID) sets Data Protection Compliance Officer (DPCO) thresholds — WATI-alternative articles that still cite the NDPR are describing the wrong regulatory reality. The defensible 2026 Nigerian stack is a WhatsApp Business Platform BSP with an NDPA-mapped Data Processing Agreement plus a CBN-licensed Payment Service Provider (Paystack, Flutterwave, Interswitch) for the payment step — not a single vendor claiming to cover all three rails.
The WATI-vs-alternative decision in Nigeria sits inside a three-regulator stack — NCC, NDPC, and CBN. Understanding the stack changes the vendor question.
The Nigeria Data Protection Act 2023 (NDPA 2023), enacted in June 2023, replaced the National Data Protection Regulation 2019 as the primary data-protection instrument in Nigeria. It is administered by the Nigeria Data Protection Commission (NDPC), which replaced NITDA as the regulator. In 2025 the NDPC issued the General Application and Implementation Directive (GAID), which operationalises the Act with specific thresholds, registration requirements, and breach-notification workflows. Two structural obligations relevant to a WhatsApp workflow. First, data controller and data processor registration: businesses meeting the GAID thresholds — annual revenue, employee count, or type of processing including electronic direct marketing — must register with the NDPC. Second, the Data Protection Compliance Officer (DPCO) framework: certain categories of data controller (typically those in the higher-tier thresholds) must appoint a licensed DPCO to manage compliance, audit posture, and breach response. Any WhatsApp automation platform used by a Nigerian business processes personal data on the business's behalf, making the business a data controller and the platform a data processor. The platform must provide a Data Processing Agreement (DPA) that maps to the NDPA 2023 and GAID 2025 specifically — a template DPA that references only NDPR or only GDPR is out of date and does not satisfy the Nigerian obligation. Ask the shortlisted vendor for the DPA text before committing. WATI, its alternatives, and the direct Meta Cloud API path all differ in how explicitly they map to the current framework, and that difference is a legitimate selection criterion.
The Nigerian Communications Commission (NCC) regulates communications services including consumer protection against unsolicited marketing messages. The NCC established the Do Not Disturb (DND) code — subscribers can register their mobile numbers by texting a keyword to the short-code 2442, opting out of promotional SMS from telecom operators and licensed marketing partners. Two implications for a Nigerian WhatsApp workflow. First, WhatsApp is not directly under the NCC's SMS Do Not Disturb rule (WhatsApp is over-the-top messaging, not carrier-mediated SMS), but the underlying consumer-protection principle — a subscriber's opt-out preference must be respected — informs NCC's broader stance on marketing communication and is echoed in the NDPA 2023 Section 6 consent framework for direct marketing. Second, the categorisation of WhatsApp messages under Meta's four-category pricing model (service, marketing, utility, authentication) has operational overlap with the NCC's consumer-protection framing. Marketing-category WhatsApp templates sent to a Nigerian recipient require the same lawful basis and consent architecture the NDPA 2023 sets out — the platform's category classification is not sufficient on its own; the underlying consent flag on the recipient must be positive. A WhatsApp automation that sends marketing templates without documented per-recipient marketing consent is not made compliant by the fact that Meta approved the template. That distinction is where most non-compliant workflows quietly sit.
The Central Bank of Nigeria's Payment Service Provider (PSP) and Payment Solution Service Provider (PSSP) licensing framework governs which entities may hold or route merchant funds in Nigeria. Every legitimate payment processor a Nigerian business uses — Paystack (Stripe-owned since 2020), Flutterwave, Interswitch, Monnify, OPay for business — operates under a CBN licence in one of the specified categories (PSSP, Switching and Processing, Mobile Money Operator). The Nigeria Inter-Bank Settlement System (NIBSS) operates the NIP (Instant Payment) rail that enables real-time interbank transfers, and the BVN (Bank Verification Number) infrastructure that underpins customer identity for financial services. Practical consequence for a WhatsApp automation: the workflow cannot hold funds and is not itself a PSP. The correct pattern is a payment-link dispatch — the WhatsApp automation sends a Paystack or Flutterwave payment link into the conversation, the customer authorises payment on the PSP's checkout, the PSP settles funds to the merchant's licensed bank account, and the confirmation webhook triggers the next automation step. A vendor that describes its WhatsApp automation as 'accepting payments' is misdescribing the flow — it is triggering a payment against a licensed PSP. Two questions to ask a candidate WATI-alternative vendor. First, does the platform provide a native webhook integration with Paystack or Flutterwave (versus requiring the merchant to build the integration themselves)? Second, does it handle the CBN-required receipt and reconciliation trail that lets the merchant close the books at month-end? Both are non-obvious selection criteria that only surface after the CBN rail is on the table.
With the three regulatory rails accounted for, the WhatsApp Business Platform itself is the operational surface. Meta prices business conversations in four categories — service (user-initiated), marketing (business-initiated promotional), utility (business-initiated transactional), authentication (OTPs) — with Nigeria-specific per-conversation rates published on developers.facebook.com/docs/whatsapp/pricing. Two structural points for Nigerian operators. First, marketing conversations are by an order of magnitude the most expensive category, and Meta's category classifier can reclassify a marketing-adjacent utility template downward at review, which shifts unit economics. Second, the free-tier rule (a set number of service conversations free per business per month) has moved twice in the last two years and cannot be modelled as permanent. Every Business Solution Provider — WATI, respond.io, 360dialog, Twilio, MessageBird (Bird), Interakt, BossBot — resells access to the Meta Cloud API and passes through Meta's per-conversation rate to the merchant. The platform's own subscription fee sits on top. For a Nigerian merchant modelling twelve-month total cost, the Meta pass-through is often the largest single line and is BSP-invariant; the BSP subscription and markup is what varies across vendors. Comparing WATI to alternatives on subscription alone misses the majority of the cost.
Set against the three-rail stack and the Meta pricing layer, the WATI-versus-alternative decision breaks down into concrete questions. Does the shortlisted BSP provide an NDPA-2023-and-GAID-2025 mapped DPA, or does it hand over a GDPR-only template? Does it document a native Paystack or Flutterwave webhook integration, or does it require the merchant to build one? Does its template management workflow handle the utility-versus-marketing category discipline the NDPA Section 6 consent framework requires? Is the tier structure priced against per-seat, per-conversation, per-MAU, or a hybrid model — and which of those matches the merchant's actual workflow shape? Is the settlement currency for the subscription NGN, USD, or something else, and what FX exposure does that create for a merchant with NGN-only revenue? WATI does some of these well (mature template management, established WhatsApp-specific product) and some less well (no native Paystack integration as of publication; USD-only subscription pricing). Its alternatives — respond.io, 360dialog, Twilio, Interakt, AiSensy, BossBot — have different strengths against these same axes. The right shortlist is not 'the cheapest alternative to WATI' — it is the vendor whose specific answers to the above questions map most cleanly to the merchant's rail obligations.
For a Nigerian business in 2026 running a WhatsApp workflow at scale — call it above 100 daily conversations or above two active agents — a defensible stack looks like this. Messaging: WhatsApp Business Platform via a Meta-approved BSP whose DPA maps explicitly to the NDPA 2023 and GAID 2025. Payment: a CBN-licensed Payment Service Provider (Paystack, Flutterwave, or Interswitch) with a native or well-documented webhook integration to the BSP so payment links dispatched in-thread flow back as confirmed settlements. Consent: a per-contact marketing-consent flag captured at the point of initial contact and respected by the automation at send time, separate from any general terms acceptance. Templates: utility-category templates for order confirmation, delivery updates, appointment reminders, and payment-link dispatch (cheap and reliably-approved by Meta's classifier); marketing templates only for consented promotional sends. Reconciliation: the BSP's conversation log exports and the PSP's transaction log reconciled monthly against the merchant's bank statement — for FIRS record-keeping, for NDPC breach-audit posture, and for the merchant's own cash-flow management. Registration: CAC Business Name or Limited Liability Company registration with the Corporate Affairs Commission, FIRS VAT registration if annual turnover exceeds the ₦25 million threshold (verify current threshold on the FIRS portal), and NDPC data-controller registration where the GAID 2025 thresholds are met. This stack does not require one all-encompassing vendor. It requires each rail to be defensibly correct on its own and the handoffs between rails to be documented — which is different work from picking the highest-scoring alternative in a feature-comparison table.
Data + numbers referenced in this article are sourced from these public documents:
BossBot provides an NDPA-2023-and-GAID-2025 mapped Data Processing Agreement, native Paystack and Flutterwave webhook integration, and NGN-friendly reporting for Nigerian merchants.
See BossBot for Nigerian businessesNot ready to sign up yet? Try the free demo →