> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Argentina CCM/AFIP Rules

> Configure a tenant-owned Argentina messaging posture around ENACOM, consent, the National Do Not Call Registry, sender identity, and AFIP-backed KYC evidence.

# Argentina CCM/AFIP Rules

Argentina's **Ente Nacional de Comunicaciones (ENACOM)** regulates
telecommunications, including the communications networks and services used
for SMS and voice delivery. Argentina's data-protection and direct-marketing
posture also requires you to respect the recipient's right to object and the
**Registro Nacional No Llame** (National Do Not Call Registry) for covered
marketing calls. Treat the regime as an **opt-out posture**: identify the
recipient, give a clear way to stop, and honour a stop before the next send.

The sender must be identifiable. For an Argentina launch, keep your legal
business identity and **CUIT / AFIP evidence** aligned with the sender identity
that you submit to a carrier or registry. Orbit provides the sender, consent,
suppression, and evidence surfaces; **the tenant owns the legal posture,
including the decision to send and the evidence it keeps**.

<Note>
  This page is documentation, not legal advice. ENACOM, the Argentine data
  protection authority, and the National Do Not Call Registry can investigate
  or sanction non-compliant communications; carrier filtering and sender
  rejection are additional operational consequences. Have counsel confirm
  whether your traffic is marketing, which recipients are covered, and which
  CCM/AFIP or carrier documents your business must provide. Orbit does not
  certify a tenant's compliance or impose a global Argentina gate.
</Note>

***

## Argentina obligations mapped to Orbit

Use the live country row and your own legal review together. The table below
maps the evidence you control to the surface where Orbit stores or checks it.

| Argentina obligation | Tenant-owned posture | Orbit surface and evidence |
| - | - | - |
| Identify the business behind a message or call | Use a sender identity that matches the tenant's legal name; keep the CUIT and AFIP/CCM evidence current where a carrier or registry asks for it. | [Sender-ID Registration](/compliance/sender-id-registration) and [Documents & KYC](/compliance/documents-kyc). Submit the requested business and identity documents before relying on the sender. |
| Capture a defensible lawful basis for marketing | Record the purpose, channel, source, and time of consent when consent is your basis. If you rely on another lawful basis, document that decision in your own compliance records. | [Consent Management](/compliance/consent-management) and `POST /api/v1/compliance/consent`; verify with `GET /api/v1/compliance/consent/lookup` before a campaign. |
| Honour a recipient's objection or STOP request | Treat an objection as a revocation for the scope your tenant selected. Do not wait for the next campaign or rely only on a carrier response. | [Opt-Out & Suppression](/compliance/opt-out-suppression) and the suppression ledger. Store the source, timestamp, identifier, and scope so the decision is auditable. |
| Scrub covered marketing calls against the National Do Not Call Registry | Enable the tenant's DNC posture and scope the preflight to Argentina. A clear result is evidence of the lookup, not a substitute for your own suppression ledger. | [DNC Scrub](/compliance/dnc-scrub), using `country=AR`; retain the response and freshness fields with the campaign review. |
| Include a usable stop path in promotional messages | Publish a Spanish-language stop instruction appropriate to the channel and make sure the reply or preference flow records the revocation. | `stop_requirement` in the live country-rules row, plus the consent and suppression ledgers. Test the inbound keyword route before launch. |
| Keep campaign and regulatory evidence | Preserve the country row, sender approval, KYC documents, consent lookup, DNC result, message copy, and suppression decision for the review period your counsel sets. | [Consent and suppression export](/compliance/consent-suppression-export) and the tenant audit log. Orbit stores the platform records; the tenant decides retention and legal hold. |

***

## Sender and KYC posture

The **AFIP/CUIT** identity is part of the business evidence a tenant may need
to assemble for an Argentine sender. Do not put a tax identifier in message
content unless your legal or carrier requirements call for it. Instead:

1. Use a sender name or number that the recipient can associate with your
   legal business.
2. Assemble the requested company registration, CUIT/AFIP evidence, brand
   authorization, and contact details in [Documents & KYC](/compliance/documents-kyc).
3. Submit the sender through [Sender-ID Registration](/compliance/sender-id-registration)
   when the live row or your carrier marks registration as recommended or
   required.
4. Keep the approved sender, legal entity, and tenant organization aligned.
   A sender approved for one entity is not evidence for another tenant.
5. Re-check the live row after a regulator or carrier change. Do not infer
   registration status from this page's snapshot.

If a carrier asks for a **CCM** document or an AFIP/CUIT record, treat that as
an identity-verification requirement for the tenant's sender application. Keep
the submitted document and its approval outcome with the sender record; Orbit
does not make the carrier's approval decision.

***

## Send-time posture

Argentina's opt-out and registry obligations are tenant-owned. Before a
marketing send, keep the unknown-marketing policy conservative and require an
explicit consent record when consent is the basis for the campaign. A
suppression entry or recipient objection always wins over a consent record.

Read the live SMS row with this filter:

```bash theme={null}
curl "https://api.orbit.devotel.io/api/v1/compliance/country-rules?channel=sms&country_code=AR" \
  -H "Authorization: Bearer $ORBIT_API_KEY"
```

For voice, replace `channel=sms` with `channel=voice` and use the same
`country_code=AR` filter. Confirm `sender_types`, `registration`,
`content_restrictions`, `stop_requirement`, and `last_reviewed_at` before the
send. If `registration` is `required` or `recommended`, do not treat an
unregistered sender as launch-ready.

For covered marketing calls, scrub the tenant's audience with the Argentina
filter and inspect the response freshness:

```bash theme={null}
curl "https://api.orbit.devotel.io/api/v1/compliance/dnc/check?phone=%2B541112345678&country=AR" \
  -H "Authorization: Bearer $ORBIT_API_KEY"
```

A DNC response does not replace your suppression check. Run both checks, keep
the results with the campaign review, and stop when either surface says not to
contact the recipient.

***

## Worked pre-launch configuration

Use this sequence for an Argentina SMS campaign with an optional voice
follow-up. Each decision is made by the tenant and remains auditable.

1. **Classify the traffic.** Mark promotional messages and calls as marketing.
   Separate transactional notices from marketing content instead of assuming
   that a mixed message is transactional.
2. **Read the live rules.** Fetch the `AR` rows for `sms` and `voice`. Record
   the sender types, registration level, stop requirement, restrictions, and
   review timestamp in the launch checklist.
3. **Assemble identity evidence.** Upload the tenant's legal-entity,
   CUIT/AFIP, brand-authorization, and any requested CCM documents through
   [Documents & KYC](/compliance/documents-kyc). File the sender if the live
   row or carrier requires it, then wait for approval.
4. **Capture or verify consent.** For every recipient whose campaign relies on
   consent, write a purpose-specific record and check it with the consent
   lookup endpoint. Record the source and disclosure version in the tenant's
   evidence system.
5. **Configure the stop path.** Publish a Spanish stop instruction, test its
   inbound route, and confirm that it creates a suppression entry with the
   intended scope. Export or inspect a test suppression before launch.
6. **Preflight the audience.** Check the suppression ledger for every channel
   you might use. For voice, run the `country=AR` DNC scrub and retain its
   freshness fields. Remove every recipient that is suppressed, objected, or
   unresolved under your tenant policy.
7. **Approve the launch.** Attach the country-rule response, sender approval,
   KYC evidence, consent coverage, suppression result, DNC result, and final
   message copy to the campaign review. The defensible posture is: an
   approved, identifiable sender; current tenant evidence for the chosen basis;
   a working Spanish stop path; a checked suppression ledger; and, for covered
   voice marketing, a fresh Argentina DNC scrub.

***

## Related references

* [Country Compliance Requirements](/compliance/country-requirements) — the
  live per-country, per-channel row behind send-time checks.
* [Regional Posture Hub](/compliance/country-rules-directory) — the country
  matrix and routing workflow.
* [Sender-ID Registration](/compliance/sender-id-registration) — submit and
  track sender identity applications.
* [Documents & KYC](/compliance/documents-kyc) — upload business and identity
  evidence.
* [Consent Management](/compliance/consent-management) — record and verify
  consent evidence.
* [Opt-Out & Suppression](/compliance/opt-out-suppression) — record objections
  and STOP requests.
* [DNC Scrub](/compliance/dnc-scrub) — configure and review registry checks.
* [ENACOM](https://www.enacom.gob.ar/) · [Registro Nacional No Llame](https://www.argentina.gob.ar/produccion/consumidor/no-llame) · [AFIP](https://www.afip.gob.ar/) — official references.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.