Version 1.2 · In force since 2026-08-02 Publication address: https://lunahia.com.br/en/pricing Portuguese version: https://lunahia.com.br/precos Principal instrument: Helsen Platform Terms of Use, clause 9, published at https://lunahia.com.br/en/terms

Language notice. This is a courtesy translation. The original and legally prevailing text is the Portuguese version, kept in section-for-section parity with this one. Should any divergence in meaning arise, the Portuguese version prevails.

Document status. This table has been in force since 2026-08-02, the date it was published at this address. The figures are those recorded in the decision block below. External legal review by a lawyer has not been carried out as of that date: it is an open, tracked item, and it ceased to be a condition of entry into force on 2026-08-02. Any adjustment the review may require enters as a new dated version in the version history at the end of this page.

Commercial name. The product is offered to the market as Luna. The contractual term used in this table is Helsen Software, as defined in clause 1 of the Terms of Use — both names designate the same product, and this table uses the contractual term so as not to create a parallel vocabulary.

Decision of record

The operational test, answered by the responsible party and recorded here:

Question: does the Customer's invoice change if they send more messages? Answer: NO. The billable unit is exclusively the count of phone_number_id active during the period, and the band is one of number count, never of volume carried.

The invariants this table satisfies, and that no revision of it may loosen:

1. What Helsen charges

The billable unit, stated in words before any figure. The amount owed to Helsen is a function exclusively of how many phone_number_id the Customer keeps in an active state during the billing period. That is the unit of configuration of the software engaged — the same reasoning as software sold by seat, where you pay for an available seat and not for how much each seat worked.

What is included in any plan, and is the same in all of them: the versioned public API, the web console, event delivery with cryptographic signing, automatic redelivery, ordering guarantees per counterparty and a dead-letter queue, persistence for the periods declared in the privacy policy, operational observability, and the health dashboard for connected numbers.

No plan has a feature another lacks. The only difference between the plans is how many numbers fit in them.

Plan table — monthly term

How to read the last column, without ambiguity. Each plan's price is fixed for the band and does not vary with how many numbers are actually active within it. The column "price per number at full capacity" is the value per number when the band is occupied up to its ceiling — it is a division, not a tariff. A Customer who takes Growth and keeps 6 numbers active pays the BRL 990 of Growth. Anyone who wants exactly one number takes the standalone option; anyone who wants a count that does not fill a band may combine standalone numbers, and the choice between the two forms is always the Customer's.

The band is one of number count, and of nothing else. There is no band by volume carried, and no band in this table is defined, limited or qualified by a count of messages, conversations, templates or media.

No plan carries any quota. There is no message quota, no conversation quota, no template quota and no media quota. There is no allowance, no overage, no bundle, no volume tier and no consumable balance drawn down by sending.

The price does not vary with the volume carried. The invoice owed to Helsen does not change if the Customer or its End Businesses send more messages. No counter of messages, conversations, templates, media, sessions or windows enters, directly or transitively, into the calculation of any amount owed to Helsen. That statement is a contractual obligation — clause 9.3 of the Terms of Use — and not a commercial promise.

Proration within the cycle

Activation mid-cycle. A number activated after the cycle begins is charged pro rata by day, counted from the day of activation to the end of the cycle.

Deactivation mid-cycle. Deactivation releases the slot immediately, and the fraction of the period already paid and unused is offset against the following cycle's invoice.

What that offset is not. It is an adjustment for proportionality of the subscription, measured in days of contracted capacity. It is not a balance, not a consumable credit and not a bundle: it is not drawn down by sending a message, it does not convert into use of the Meta Platform, and no message event increases or reduces it.

What Helsen sells, so the distinction is on the record. Helsen sells software: integration, an API contract, reliable event delivery, persistence, observability. Helsen does not resell, does not sublicense and does not intermediate the WhatsApp Business Platform, and no amount in this table falls, directly or indirectly, on the use that the Customer or the End Business makes of that platform.

On what the price reflects. What is being engaged is access to the official WhatsApp Business Platform API, through Helsen's approved integration as a Tech Provider, and not an unofficial library operating outside Meta's terms and exposing the End Business's number to deactivation on that ground. This is not a warranty that Meta will not apply its own policies to a number: Meta decides on its own accounts at its own discretion, as the Terms state in clause 12.4.

2. Technical limits

Every limit that exists in the Helsen Software exists for reasons of infrastructure capacity. No limit is commercial.

The limits are identical across all plans, from the standalone option to Scale, regardless of price or of how many numbers are contracted. The reason is direct: a more expensive plan that allowed more messages to be sent would be, to any auditor, a volume-based plan under another name — and the invoice would come to depend on how much the Customer sends, which is exactly what the Terms forbid in clause 9.4.

Where the numeric values live. They are published in the API's technical documentation, with the capacity justification beside each one, and they are the same for every Customer. They are not reproduced here so that there are never two places where the same figure can diverge — the same discipline that clause 10.1 of the Terms applies to retention periods. None of those values is subject to commercial negotiation, and no plan loosens them.

Limits that are not Helsen's. The Meta Platform itself imposes throughput ceilings per number, a minimum interval between messages to the same recipient, and file size ceilings. Those limits are Meta's, apply equally to everyone using the platform, and Helsen neither loosens nor tightens them as a function of plan. The values in force are those published by Meta in its own documentation.

3. What Meta charges your customer

This section is not about Helsen's invoice. It exists because the total cost of operating the channel has two origins, with two owners and two invoices — and confusing the two is the most expensive mistake a reader of this page can make. The subscription in section 1 does not include, does not cover and does not advance the cost of using the Meta Platform.

Who is invoiced. Use of the WhatsApp Business Platform is billed by Meta directly to the End Business — the company that owns the WhatsApp Business Account and keeps its own payment method registered with Meta. That charge is a relationship between the End Business and Meta, and arrives on an invoice from Meta, not from Helsen.

Currency. Businesses whose registered sold-to country is Brazil are billed by Meta in Brazilian reais (BRL).

What Helsen does not do, and cannot do. Helsen does not intermediate, does not advance funds, does not extend credit, does not offer instalments, does not waive, does not pass through and does not absorb any amount owed to Meta — under no circumstances, not temporarily, not while an End Business's payment method is failing. There are two reasons, and the second is stronger than the first: doing so would reconstitute the resale prohibited by the contract between Helsen and Meta; and Tech Providers have no line of credit with Meta — a line of credit is an attribute of a Solution Partner. Helsen did not decline to intermediate usage payments as a commercial choice; it does not possess the mechanism to do so.

The console displays, and never bills. The console displays the End Business's consumption on the Meta Platform, where Meta makes the figure available, with an explicit label stating that the amount is charged by Meta directly to the Customer's own client. Displaying is not billing: no figure shown on that dashboard enters into any calculation of an amount owed to Helsen.

4. Caveat on the pricing of non-template messages

This caveat exists so that nobody reads this page and concludes something Helsen cannot guarantee.

Under Meta's standard pricing, non-template messages sent inside the customer service window opened by the End User are free of charge. Meta has not announced the end of that.

And there is a separate policy. Meta maintains its own policy and rate card for providers of artificial intelligence technologies operating on the platform. For a sender classified under that policy, non-template messages cease to be free. According to the rate table Meta publishes for those providers, in the version captured and hash-verified by Helsen, for the Brazil market the rate is USD 0.0625 for each non-template message delivered, with a start date recorded as 11 March 2026 and no end date. For the European Union and European Economic Area markets the same table records an end date of 12 May 2026 — the charge ceased there and remains in Brazil.

Helsen does not say who is affected. Classification under that policy is made by Meta, at its sole discretion. Helsen does not request it, does not contest it on anyone's behalf, does not interfere with it and does not absorb the resulting cost difference — absorbing it would reconstitute exactly the violation described in section 3.

None of this changes the subscription. The rate this section deals with is charged by Meta to the End Business. It does not alter, add to or reduce any figure in the table in section 1.

Why the caveat is written and not omitted. Asserting that messages are free without it would be an incomplete statement on a public page: if an End Business is classified, the invoice it receives from Meta contradicts what it read here. The classification risk is allocated to the Customer by clause 7 of the Terms of Use, and this section is the information that supports that allocation.

5. Effective date and changes

Effective date. This table took effect on 2026-08-02, the date of its publication at this address. The figures are those recorded in the decision block on this page, dated 2026-07-30.

Changes. This annex may be updated independently of the Terms of Use. Any change is communicated to the Customer with at least 30 (thirty) days' notice before its effective date, at the contact address on record and at this publication address. A change that increases the price or reduces contracted capacity entitles the Customer to terminate without penalty up to the effective date — clause 3.3 of the Terms.

What a change may not do. No revision of this table may introduce a quota of messages, conversations, templates or media, nor a limit that varies by price, nor a band defined by volume carried. Those prohibitions are not revisable commercial policy: they are the boundary separating this model from what the contract between Helsen and Meta forbids.

Version history