The official Cloud API is the recommended path for anyone who wants to scale safely — a verified number, no ban risk from the method, uptime guaranteed by Meta. For specific cases, we also support QR Code upon assessment.
With QR Code, your number can be banned at any moment just for using an unauthorized tool — regardless of the content. With the official API, that doesn't exist.
Numbers on the official API can be verified by Meta — your company name appears in the customer's contact, increasing message open rates and trust in your service.
Since November 2024, Meta's policy allows receiving inbound messages at no extra cost via Cloud API. Scale your service without paying per received conversation.
Because the connection is directly to Meta's cloud, the assistant works 24/7 without relying on a phone being on, battery or a local internet connection. A power outage doesn't stop the service.
All communication uses WhatsApp's end-to-end encryption protocol. Messages in transit are protected by Meta's own infrastructure — not by an additional third-party layer.
Data processed within an environment with formal data contracts with Meta. Easier to document and demonstrate LGPD compliance to auditors and corporate clients.
QR Code is a valid option for some scenarios — early operations, secondary numbers, flow tests. But it's important that you decide with the right information: when a ban happens, the loss is yours, not the vendor's.
QR Code can be the right choice in early scenarios: flow validation, a secondary number, low-volume operation, or when the customer wants to start at a reduced cost before migrating to the API. We assess this together at implementation time.
For the official API: if the number is on personal WhatsApp or an unverified Business account, it must be migrated — we recommend a dedicated number. For QR Code: the current number can be connected directly, but it can't be active on another device at the same time.
Since November 2024, inbound conversations (the customer initiates contact) are free. Outbound conversations (your company initiates) have a 24-hour per-conversation cost set by Meta by region. Aurovia charges no markup on that — you pay Meta directly.
Via the official API, bulk sends (HSM templates) are possible upon content approval by Meta. Via QR Code, sending is also possible, but with more care — high volume increases the risk of suspension. We recommend moderation in both to preserve the number's reputation.
The official API is our recommended standard. But if QR Code makes more sense for your scenario, let's talk. Every operation has its own particulars.
Talk to a specialist →Assessment with no commitment · Assisted setup · Support in Portuguese
Reply
Learn
Agenda
Publish
Imob