WhatsApp Business API Costs: Pricing, Open Rates, EU Hosting

WhatsApp is a direct channel in Germany, not a social media channel

Anyone who writes WhatsApp into the media plan next to Instagram and LinkedIn is comparing two different things. On Instagram you buy visibility in a feed. On WhatsApp you buy the delivery of a message to someone who gave you consent beforehand. That changes the cost logic, the frequency and the way you measure success. Where the channel sits in relation to the other networks is set out in the pillar Social Media Platforms Compared.

How big the channel is in Germany depends on how you count. Statista counts a conservative 44 million active users in Germany, while surveys such as Business of Apps arrive at around 60 million. The gap of 16 million is not a calculation error, it is the difference between a narrow and a broad definition of "active". For the channel decision this is secondary, because in both cases no other messenger in the German-speaking market comes close to that order of magnitude. How this compares with the user numbers of the other platforms is covered in Social Media Usage in Germany 2026.

Meta bundles several products under the brand that have nothing to do with each other in budget terms: the free Business app, Channels, and the paid business platform with API access. Only the third variant generates the message costs discussed here. On the business side, an analysis of Meta reports cites more than 200 million businesses using WhatsApp Business products worldwide. You should read that figure carefully: Meta's own milestone referred to 200 million monthly active users of the free Business app in June 2023, a fourfold increase on 50 million in 2020. Secondary sources like to turn that into "businesses". The figure is global, not DACH.

The reason the channel is on the agenda at all is the open rates. A vendor benchmark quotes open rates of 95 to 98 percent for WhatsApp Business messages against 20 to 25 percent for email. That comes from a messaging provider, not from an independent study, and it measures opening, not response, and certainly not revenue. The distance to email is still wide enough to put the considerably higher unit costs up for discussion in the first place.

WhatsApp Business API costs: what Meta charges since July 2025

Until mid-2025 Meta billed per conversation: one window of 24 hours, one price, any number of messages within it. Since 1 July 2025 Meta bills per message. Use cases with a lot of back and forth inside one conversation became more expensive, use cases with a single triggered message cheaper.

Billing follows the message category, and the rates differ by country. For Germany these orders of magnitude apply as of Q2 2026:

The rates of 0.1131 euros for marketing and 0.0456 euros each for utility and authentication in Germany come from a provider overview as of Q2 2026. Meta itself publishes the country prices only as a rate card for download, which is why such overviews are the more accessible source in practice. Germany is among the more expensive European markets, and provider price comparisons show noticeably lower rates for Spain and Portugal. For budget planning that matters more than the third decimal place.

A worked example makes the order of magnitude tangible. A marketing send to 5,000 opt-in contacts costs around 566 euros in pure Meta fees at these rates. Repeated monthly, that is about 6,800 euros a year before your provider earns anything at all. The same send by email costs a fraction of that. The calculation only works if opening and response actually offset the cost factor, and that cannot be claimed in advance, only tested.

The second lever lies in categorisation. Utility and authentication messages cost less than half a marketing message in Germany. Transactional communication therefore belongs in a properly set up utility template, not in a marketing template with transactional content. Anyone who mixes the categories pays the marketing price for every order confirmation.

The free windows are the real cost lever

Two time windows decide whether a WhatsApp programme runs economically.

The 24-hour service window: If a contact writes to you, all non-template messages within the following 24 hours are free. Support, advice and questions about an order incur no message fee as long as the window is open.

The free entry point window: If the contact arrives through a Click to WhatsApp ad or a call-to-action button on your Facebook page, the window stays free of charge for 72 hours. That is why Click to WhatsApp ads are the cheapest entry door in many setups: you pay the click price of the ad and then no message fee for three days.

A simple operating rule follows from this. Paid marketing templates exist to open a dialogue. As soon as the customer replies, you move everything else into the free window. Programmes that instead trigger every interaction with a fresh template pay for messages they could have had for nothing.

Choosing a BSP: what matters for EU hosting

In practice you get access to the API through a Business Solution Provider. It supplies the interface, automation, CRM connection and template management, and puts its own markup per message or a monthly base fee on top of Meta's prices. As a rule of thumb, the markup per message sits between a few tenths of a cent and about one cent; for total costs the base package usually weighs more.

For a company based in the EU, the hosting location is the harder selection criterion. The message content runs through Meta's infrastructure anyway, but contact data, chat histories, segments and automation logic sit with the provider. Chatarmin states that it stores customer data on servers in Frankfurt and is certified to ISO 27001, hellomateo names AWS Frankfurt (eu-central-1) as the storage location. Both are provider self-declarations that you should have confirmed in the data processing agreement instead of taking them from a website.

These points belong on the table before you sign:

• Server location and subcontractors: not the label "EU", but the specific region plus the complete list of subprocessors.
• Data processing agreement: has to cover the transfer to Meta, including third-country transfer.
• Opt-in management: timestamp, source and withdrawal per contact, exportable and presentable in a dispute.
• Template handling: how quickly and how transparently approvals and rejections by Meta run.
• Pricing model: base fee, markup per message, cost per active contact, contract term.
• Exportability: contacts and histories have to come out of the system in plain text, otherwise a switch is effectively blocked.

The decision usually turns on the last two points. Prices can be renegotiated, a provider that will not hand over your contacts and histories in plain text cannot.

Consent is the operating basis, not a formality

Without documented consent, a WhatsApp marketing programme cannot be run in the EU. The number is personal data, the promotional message is electronic direct marketing, and you have to be able to prove the opt-in in a dispute. In practice that means: separate opt-in for marketing messages, no bundling with terms and conditions or newsletter sign-up, withdrawal possible in every message and technically effective immediately. Which legal basis carries which constellation is broken down in GDPR legal basis under Article 6. This does not replace legal advice, and the specific implementation belongs in the hands of a specialist lawyer, particularly for Austrian and Swiss specifics.

What does not work in Germany: closing the sale in the app

The sales stories from Asia and South America do not transfer to DACH. WhatsApp Payments for Business is currently available only in India and Brazil, plus Singapore with a restricted variant for business payments. An EU launch has not been announced.

In Germany, Austria and Switzerland exactly one step is missing, and it is the last one: closing the sale. The chat ends with the jump into your shop, and the payment runs there. If a concept builds on in-app payment, it falls over at precisely this point. Which channels in DACH actually carry through to checkout is covered by the pillar Social Commerce & Social Shopping.

Measurement: the channel creates traffic you cannot see

WhatsApp weighs heavily in dark social. If someone forwards your link in a private chat, that path leaves no trace your web analytics could follow, and the visit shows up as direct traffic. This affects forwarded links just as much as links from your own messages, as soon as someone copies them.

Two workarounds help: UTM parameters on every link you send yourself, and an open question about origin in the form. Both are imprecise, but considerably better than an attribution model that systematically sets the channel to zero. How to build this into a reliable measurement model is covered in the pillar Social Media Analytics, KPIs & Measurement.

WhatsApp or email: the channels are not competing

The most common wrong decision is to plan WhatsApp as a replacement for the newsletter. The two channels have different cost structures, different frequency tolerance and different jobs in the funnel.

A clear division of labour follows from this. The newsletter carries breadth and regular contact, WhatsApp carries the few messages where delivery and response speed decide revenue. Anyone who runs both from the same editorial plan loses at both ends.

Typical mistakes

Most failed programmes fail on frequency and categorisation, not on the creative. Anyone who transfers the email cadence one to one produces unsubscribes and blocks: WhatsApp sits in private space and tolerates less frequency than email, not more. The second expensive mistake happens in template management. Transactional messages that run as marketing templates cost more than twice as much in Germany, and that only shows up in the monthly invoice.

Three further points regularly go wrong in day-to-day operation:

• Giving away the free window: If a customer replies, communication is free for 24 hours. Many setups still send chargeable templates.
• Opt-in from the existing database: A phone number in the CRM is not consent for promotional messages.
• No cost limit: Without a spending cap per campaign, the invoice grows with every faulty automation run.

On top of that comes the mistake that is hardest to repair: opening WhatsApp creates questions in real time. Without capacity in the team, the fastest channel turns into the slowest.

When the channel pays off

At around 0.11 euros per marketing message you need a list with genuine purchase intent, not a reach audience. The channel carries its weight where a single message measurably triggers revenue or a qualified appointment: abandoned cart, reorder, appointment confirmation, contract renewal, time-critical service. For broad brand communication it is too expensive and too close to private space. Anyone who sets it up as a cheaper email replacement pays more and loses the list.