DNC Registry Access: Why Mexico/Argentina Isn't Self-Serve

DNC LATAM · Compliance guides

You can’t sign up for Mexico’s REPEP or Argentina’s Registro Nacional No Llame the way you sign up for the US National Do Not Call Registry, because neither is built as an open subscription product. The FTC lets any company create an account at telemarketing.donotcall.gov and subscribe by area code. REPEP and No Llame are Spanish-language government systems that expect a local tax identity, a responsible representative, and a filing process before they hand over a check — and PROFECO does not publish a public REST API for REPEP at all.

US outbound and compliance teams usually hit this wall after they’ve already scoped a Mexico or Argentina campaign the way they scoped their domestic one: find the registry, subscribe, scrub, dial. The first two steps don’t exist in the same form once the target market changes. It’s worth being precise about why, because “it’s just a different government website” undersells how different the access model actually is.

The US model: subscribe and go

The National DNC Registry is designed for exactly this kind of self-service. Any US company creates a telemarketing.donotcall.gov account, subscribes to the area codes it plans to call, and downloads the current file. No local entity requirement beyond being a US business, no representative filing, no manual approval step standing between account creation and a usable list. The TCPA and Telemarketing Sales Rule layer compliance obligations on top, but the registry access itself is a commodity transaction.

That model shapes expectations. If a company has only ever scrubbed +1 numbers, it reasonably assumes a Mexico or Argentina equivalent works the same way — a portal, a login, a download link, done in an afternoon.

Mexico: a zone-file purchase, not a subscription

REPEP, the Registro Público para Evitar Publicidad, is run by PROFECO and updates every 15 days. There’s no self-service REST API — the official path is a zone-file purchase on the Spanish-language PROFECO portal, and completing it means provider registration, tax details, and a legal representative who can respond to the Mexican authority. A foreign company without a Mexican operating structure generally can’t finish that registration on its own, which is why most international callers end up buying the check from a vendor that already holds the access, rather than becoming a REPEP user of record themselves.

Argentina: a tax ID is the first gate

Argentina’s Registro Nacional No Llame, run by AAIP under Law 26.951, works through TAD — the government’s Consultas automatizadas filing for AAIP’s No Llame API. That filing expects a prior inscription in the Registro Nacional de Bases de Datos Personales and a copy of the signer’s personería, on top of the CUIT tax identity and responsible representative every company-user account needs. A US company with no Argentine tax ID doesn’t have a login to create, let alone a file to download.

Colombia follows the same shape

Colombia’s RNE, administered by the CRC under Ley 2300, is queried through the CRC trámites portal — individual lookups, file uploads, or a government web service for volume. The portal and its manuals are in Spanish, and credentials and tokens are issued to local users. It’s a third version of the same underlying constraint: the registry is built for companies that already operate inside the country, not for a foreign caller trying to check a list before a campaign.

Why this isn’t a workaround problem

None of this is a bug in REPEP, No Llame, or RNE — each one is doing what a national consumer-protection registry is supposed to do: authenticate the companies that query it. The US National DNC Registry happens to solve authentication differently, with a low-friction subscription model that assumes a domestic caller. Mexico, Argentina, and Colombia solve it by tying access to a local tax identity and representative. Neither approach is wrong; they’re answering different questions about who gets to ask a government database whether a number is reachable.

The practical consequence is that “just go scrub the list” is a one-step instruction for +1 and a multi-week registration project for +52 or +54 — assuming a foreign company can complete that registration at all. DNC LATAM exists specifically for the gap this creates: it holds the official access for Mexico, Argentina, and Colombia and exposes the check as one DNC API or CSV, so a US company doesn’t need a Mexican tax registration or an Argentine CUIT to find out whether a number is on the list before it dials.

What to check before you assume “self-service” scales

If your team is scoping an outbound campaign into Mexico or Argentina for the first time, the self-service assumption is the one to test first, not last:

  • Does your compliance team have a local tax ID and representative for the country you’re calling? If not, direct registration with REPEP or AAIP isn’t available to you as a foreign entity.
  • Is the refresh cycle built into your process, not just the first download? REPEP releases on a 15-day cycle; a one-time scrub goes stale fast.
  • Is the US National DNC result being treated as coverage for +52 or +54? It isn’t — a clean US scrub means a number isn’t on the FTC list, not that it’s clear to call in Mexico or Argentina.

Getting these three straight before launch is cheaper than finding out mid-campaign that the registry you assumed was a subscription is actually a filing process you can’t complete without a local entity. Official access is the first step of contact center compliance for Mexico and Argentina, not a self-serve add-on to a US TCPA seat.