Other A2P SMS regulations

Brazil Tightens A2P SMS Traceability

For CPaaS providers, aggregators, and brands sending OTPs, transaction alerts, billing notices, or customer-service messages to Brazil, Anatel is moving A2P compliance beyond basic route management. Its decision published on November 4, 2026 introduces dedicated short codes, a centralized directory, automated traffic monitoring, incident cooperation, and traceability obligations across operators, aggregators, integrators, and message originators.

Published:11/07/2026 Updated:11/07/2026

1. Regulatory focus

On November 4, 2026, Anatel approved measures requiring enterprise messaging to move toward dedicated, standardized short codes rather than shared identifiers. A centralized directory will record the code, aggregator, and responsible brand, while mobile operators must be able to identify the effective user associated with each code. Operators must also implement automated A2P monitoring, fraud detection, incident handling, and controls against untrusted delivery channels.

2. Business impact

The impact extends beyond delivery rates. Brands must be able to prove message origin, campaign legitimacy, and accountability for each traffic path. Aggregators, integrators, and originators should retain customer identity data, authorization records, message logs, and incident evidence. OTP, account recovery, and payment-confirmation flows sent through unregistered codes or untrusted routes may face blocking, investigation, or forced rerouting. Anatel’s 180-day implementation report also leaves room for additional technical requirements.

3. Operating recommendations

Before expanding Brazilian traffic, map the accountability chain from brand to aggregator, short code, template, and terminating operator. Assign one identifiable sender to each OTP, transaction, and customer-service use case. Maintain an inventory of short codes and sender IDs, with KYC records, authorization documents, template versions, delivery logs, and blocking events. Connect anomaly alerts to an operational response queue. For critical authentication flows, prepare compliant backup routes, but do not substitute personal numbers or shared codes for registered enterprise identities.

Frequently Asked Questions

Does every Brazilian messaging customer need a separate short code?
The direction is to prevent multiple businesses from sharing one identifier, but the final allocation model will depend on Anatel’s technical rules. Aggregators should already separate code ownership by brand and business entity, retain authorization records, and avoid using one shared code for unrelated OTP, notification, or marketing traffic.
Do existing international SMS routes need to be changed immediately?
The immediate priority is an accountability and route inventory, not an overnight replacement of every path. Confirm whether each provider can trace the brand, aggregator, short code, and terminating operator. Put shared or untraceable routes on a remediation list, prioritizing OTP, payment, and account-recovery traffic.
What evidence should companies retain for Brazilian fraud reviews?
Retain brand and customer KYC, short-code or sender-ID authorization, template and use-case descriptions, timestamps, volumes, routing details, alerts, blocking outcomes, and incident records. For authentication and transaction messages, also preserve the triggering system, user action, and retry logic so the company can demonstrate that the message originated from the stated business process.
This article is for informational purposes only and does not constitute legal advice.

Related products

Need compliance guidance?

Contact us for guidance on target markets, message scenarios, and sending routes.

Get in Touch
Privacy Policy